10 Comments

  1. Frederic Sune
    · Reply

    Amazing where Automattic is going with Gutenberg and blocks!
    Really like the event one, so easy to use and implement. For small website, it is perfect so you don’t need to install a full event solution. Not a big fan of the stars or waves but still nice to see the animation. Thanks for sharing.

    Report

  2. Marcus Kazmierczak
    · Reply

    Thanks for noticing our experiments and the kind words. 🙇‍♂️
    (Note: I work at Automattic on the team behind these experiments)

    The blocks in general are experiments in the open, trying out different ideas, pushing on what we can do with blocks and also a place to play. Blocks may start here, but then get promoted elsewhere, which is why some may not be listed in the block directory.

    For example, the Image Compare block will be launching in the next version of Jetpack next week. The Layout Grid block we hope to bring to core, but need to refine more and optimize the CSS payload before introducing there. Also the Rich Image block is a just about ready to merge to the Gutenberg plugin as an experiment to iterate on there.

    Thanks again for the kind article, we are excited for the possibilities with the new platform, and plan to keep iterating and exploring what can be done with Gutenberg. So hopefully much more to come.

    Report

  3. JDP
    · Reply

    I’ve given up on hoping each Gutenberg release will have a dedicated metadata API or at least some simple implementation of taking some of the important (to me) php developed metadata components I’ve customized for my site over the years. Your prior post about the Fields API was encouraging but that seems DOA.

    Textarea controls with html/Tinymce editing capability to store metadata and any kind of AJAX related population of html form control options/values are nightmare fuel. I understand most users want easy to generate polished content and rarely use metadata but for me, I can’t use Gutenberg to do the same stuff I did in classic without some serious workarounds and learning investment.

    Report

  4. Nollind Whachell
    · Reply

    When is WordPress going to get something like an Article Embed block that let’s you embed a news article from any site (rather than just from WordPress sites only)? In effect, a feature that most social networking platforms have built-in as a core feature to make sharing articles of interest super easy to do by just pasting in the article URL.

    I mean there’s this emphasis to post content on your website first (Indieweb), rather than having it scattered across the Web on different social network platforms, yet WordPress doesn’t even have the same basic functionality and ease of use that these platforms have when sharing news articles.

    Why is this so complicated to implement? And why is that no one seems to see it as a crucial component to attract people to the platform for blogging, instead of using other social network platforms? For example, I thought JetPack would have implemented something like this a long while ago (to replicate something like Embed.ly) but still nothing.

    Report

    • Justin Tadlock
      · Reply

      This is a post about Automattic’s block experiments, so we’re getting a bit off-topic from that discussion. The embedding system also doesn’t really have anything to do with blocks. The embed-related blocks are merely a wrapper over the existing oEmbed system.

      Honestly, I don’t think this is a widely-needed feature. It was tough to turn up many results when searching for similar requests. For the average user, WordPress covers a vast array of providers that will cover their needs. If there’s an oEmbed provider missing from the core list, there is likely a plugin out there that will cover it.

      I’m not 100% up to speed on how Twitter, Facebook, etc. handle embeds, but believe it is a much different type of system that takes a snapshot of a URL and caches the data (image, title, description) on their servers. That seems more like the type of thing that would fall more squarely within plugin territory.

      Embeds, as we know them in WordPress, should never happen unless the site owner explicitly allows them through something like oEmbed. A big part of this is because such embeds use resources from the third-party website.

      The embed system is one of my weak spots in development knowledge, so I hope I described that correctly.

      Report

    • Nick Hamze
      · Reply

      I don’t know if it’s exactly what you are looking for but I made something called Fancy Links which tries to replicate the experience of sharing links via Social Media:
      https://wordpress.org/plugins/fancy-links/

      Report

      • Justin Tadlock
        · Reply

        I thought you had built something that might work. So, I dug into it and found the Whatever plugin, which obviously didn’t cover this use case. Thinking I had found the plugin I was thinking about, I stopped looking.

        Report

      • Nollind Whachell
        · Reply

        Nick, that plug-in is brilliant! Exactly what I was looking for. Thank you. I’ve been looked for something like this for a while but couldn’t find anything when searching within plug-ins.

        “Honestly, I don’t think this is a widely-needed feature.”

        Justin, my apologies for posting it here but I saw it as an area where I’d like to see “experimentation” and development in WordPress because I see it as a basic need (especially for an an end user who wants to migrate off a social network to maintain and own their own content but also maintain a similar easy workflow).

        But most developer focused WordPress sites that I’ve visited and raised things like this, pretty much respond in the same way. They don’t see a need for features (from a developer’s perspective) that to me are basic needs for an end user. For example, when I told my wife about this lack of basic feature on WordPress (that most social networks have), she thought it was crazy.

        Another quick example of developers not seeing what’s essential to an end user is quote blocks. The basic quote blocks within most WordPress Themes have been stylized to have default font sizes equivalent to something that you’d use with a larger pull quote. So font sizes that are way, way too large for quotes. The developers I’ve mentioned this to, think I’m strange for raising such a point. Yet if you’re an end user who does research, often sharing quotes from your research, this is completely frustrating thing to encounter in theme after theme. Like try going to a website like Brain Pickings and dramatically increase the quote fonts sizes. Again it looks absurd but no one seems to care about end users encountering these basic issues when using WordPress.

        Again, sorry for deviation.

        Report

        • Nick Hamze
          · Reply

          I think this is as illustration on the disconnect it seems like there is between developers and users. When you posted your reply I knew exactly what you we talking about and I too thought it was a basic feature that WordPress was missing too.

          I agree about quotes too. I never use them as they are usually so huge they look ridiculous.

          Report

Leave a Reply to Nollind Whachell Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: