13 Comments

  1. Pablo

    Congrats!

    Maybe the ” › ” character is better than ” / ” to segment the breadcrumbs?

    Good luck!

    Report

    • Justin Tadlock

      It’s best to leave the separator up to theme authors to match their themes since it is a design element. I have a general preference for the / character, so I’m just using it right now.

      Report

  2. Jamie

    Thanks Justin, great article.
    I also built my first block last week. I understand your sentiment around it being both overwhelming and limiting. I hadn’t even heard of the “supports” API until this article.

    I think as the Block Editor has iterated so quickly, there is so much conflicting information, even within the official documentation itself. The code examples in the docs could also be vastly improved.

    With that said, the actual implementation by the team is great. If I had to build my block again it would be in a vastly shorter time now that I know what I need to do. It’s unfortunate that the initial barrier to entry is so high due to all the conflicting information and sheer overwhelming number of options.

    Articles like yours are super useful, so thank you!

    Report

  3. Aleksandr Samokhin

    Great read. I’m also on the same path of starting my block journey soon. I haven’t tried this tool yet. What confuses me is how to handle basic WordPress query stuff, is it via REST or is there another approach? Also, does it make sense to buy courses like Zack Gordon has some about Gutenberg?

    Report

    • Eliezer

      You can do that “loop stuff” with “select” or “use select”, also you can handle that with the rest API if the “select” API isn’t enough for your needs (it’s common extend the rest API if you need an advanced and complex queries).

      Report

  4. Bastian

    The documentation is almost useless. The examples in there are very basic and not helpful at all. The docs might be enough for building basic blocks such as a pricing table, but not for more advanced blocks that need to show dynamic data.
    Crucial functions for developing dynamic blocks (a basic feature for client work) such as getEntityRecords/getEntityRecord are an afterthought in the docs. There is just one example with them and it still uses higher-order components instead of the much simpler React hooks.
    If it weren’t for StackOverflow, I wouldn’t have gotten very far building blocks.

    Report

  5. Ronald Huereca

    Just a heads up. The docs for serverside component mentions this:

    ServerSideRender should be regarded as a fallback or legacy mechanism, it is not appropriate for developing new features against.

    Report

  6. Paal Joachim Romdahl

    Hey Justin!

    Perhaps the next stage is to check out this Breadcrumbs issue:
    https://github.com/WordPress/gutenberg/issues/21943
    As I checked the issue again I also noticed that Andrew Serong made a Pull Request 28 days ago. It looks like Andrew made some initial work but that the PR has stalled. Here is a nice chance to help it along.

    Report

    • Justin Tadlock

      Core is welcome to use my breadcrumbs code, which is linked in that ticket. There’s over a decade of work there covering almost every imaginable scenario. I feel like if I worked on that ticket I’d have to help build an inferior server-side solution. But, if there’s interest in bundling a third-party library for this, I’d be happy to help move it along.

      Now, for the JS part, I’m highly interested in that. I’ve already learned from reading the code there. If I have something that I think would improve it, I’ll definitely pass it along.

      Report

  7. SOUMYA MONDAL

    Is it possible to create any WordPress plugin with just Basic PHP Functions like -“Get header” or something and just by using Javascript?

    Report

Comments are closed.

%d bloggers like this: