9 Comments

  1. Kel
    · Reply

    Wow. I sure hope designer Ricardo is taking notes and is not put off by the “tough love” tone here. ;)

    Report

  2. stefanos
    · Reply

    Matt as you have said yourself asked us to learn JavaScript deeply.

    The speed is of vanilla JS is quite impressive and as far as I know, ECMAScript 6 is supported on major browsers we all know and use.

    So my question is: why choose React and not go with vanilla JavaScript?

    Report

    • Justin Tadlock
      · Reply

      I think this is more of a “why recreate the wheel” sort of thing. Whether it’s React or some other library, WordPress would essentially have to create an entirely new JavaScript framework to do the things it wants to do with the block editor. It makes more sense to use an established framework that is attractive to outside talent rather than an in-house solution that would add months or years to the timeframe.

      Report

  3. Dave Loodts
    · Reply

    Wow, this is probably the greatest article in 2020 so far.
    Well written. As i’m reading my own workflow transition..
    Blocks are the future, wether you like it or not. I didn’t like it at the start, now i see the enormous power and possibilities.

    A few things to say about javascript: that knowledge is not needed for the majority of ‘webdesigners’. HTML, CSS and PHP is enough. I can’t write javascript, but i can build almost everything. Thanks to PHP, snippets AND the live-saver-tool called ACF.

    About full-site editing: i don’t believe in this feature (yet). Mostly because of the header. For basic sites with basic navigation that would be OK. But out of the box, WordPress never ever will come close to the options that WPAstra of Kadence Theme have. So, i don’t see the point to invest so much time in here.
    The Block Editor is a content editor, leave it like that for the moment. WordPress must focus on that, cause there are a lot of shortcomings of options for a ‘content editor’: padding, margins, differences in responsiveness…

    Why i’m suggesting that focus? History is repeating itself. Elementor got the become kings cause WordPress lacked the content editing aspect. Now, a few others are in the block-design-race to become the next ‘Elementor’ for blocks. It will be just a new ‘ecosytem’. And any ecosystem has one big minor thing: locked-in issues. And i always believed Gutenberg gonna solve that locked-in effect, as a few times stated on State of the Words. But at the moment with these number of ‘design’ options in core, (the desktop-focus only): it’s just shifting the locked-in to other plugins like Ultimate Gutenberg Add or Kadence Blocks. So, i really hope that i can rely more on core blocks in the future for designing websites (without adding classes which client’s don’t get)

    Report

    • Justin Tadlock
      · Reply

      I am not completely on board with FSE yet myself. However, I did want to touch on this:

      About full-site editing: i don’t believe in this feature (yet). Mostly because of the header. For basic sites with basic navigation that would be OK. But out of the box, WordPress never ever will come close to the options that WPAstra of Kadence Theme have. So, i don’t see the point to invest so much time in here.

      If done right, WP could make “header” design much better. I envision themes coming packaged with multiple plug-n-play headers. Whether that’s through the template part or pattern system, I don’t know. However, this could make things simpler for end-users in the long run.

      Imagine going into the site editor, clicking on the header area, and selecting from a dozen different header patterns/templates that best suits your site. Then, just making adjustments as needed.

      Report

  4. Henning
    · Reply

    Great series, marvelous idea to pick up on questions like these…! Agree with you, still gotta make the leap myself :)

    Keep it up!

    Report

  5. Csaba
    · Reply

    Great thoughts. Thanks, Justin!
    A good way to learn (to work with blocks) is to get involved in developing WordPress and its default themes: a shiny new one is coming (https://make.wordpress.org/core/2020/09/23/introducing-twenty-twenty-one/). :-)

    Report

  6. Marcus Tibesar
    · Reply

    Great prose Barkeeps! I am using WPForms to capture site visitors’ content for posts. You gave me a lot to explore for developing alternative methods for capturing user submissions. Thank you! Power on.

    Report

  7. Ricardo
    · Reply

    Hi guys
    & thanks for the feedback, Justin!
    It feels great to be heard. A true Tavern! (I’m from Portugal and a taverna is a very special spot around here).
    Best answers always have some love involved (thanks, Kel, for the concern   :)

    To be honest, I think I’m not that off. I’ve begun learning JS (and React) for some time, done some courses, I think I’m prepared for blocks and don’t feel scared about the future. I think I’m just uncertain of a solid pathway. I believe I’m in search of the Holy Grail of WP right now – how to build a solid website.

    Maybe this isn’t the place to share long thoughts. I was preparing what was starting to be a huge response – that, and the fact I was on sick leave, justifies the off timing of this response. Sorry for that.

    I don’t want to delay this answer anymore, so, I think I’m going to arrange that huge thing I was writing and maybe “Ask the Bartender” in separate instances.

    Just a quick one.. in ACF docs we have:
    – “ACF blocks differ from WP blocks in that the data is decoupled from the design. This allows for faster development of blocks by focusing only on the HTML output.”
    – “Block data is saved within the “post_content” as an HTML comment. This makes them unique to metaboxes which save data to the “postmeta” table.”
    – “WordPress saves block data as HTML comments in the post_content. ACF blocks follow suit and save their data as a JSON object within that HTML comment.”

    Can’t we think of ACF as a framework, like React, that solves things cleaner & more future proof?

    Thanks &
    See you all!

    Report

Leave a 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: