Title: Introducing WordPress.org/blocks
Author: annezazu
Published: August 11, 2023
Last modified: August 16, 2023

---

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
6:23 pm _on_ August 11, 2023      

# Introducing WordPress.org/blocks

To better tell the story of blocks, both within WordPress and as a broader framework
for folks to consider with their next project, [a new page](https://wordpress.org/blocks/)
has been created on WordPress.orgWordPress.org The community site where WordPress
code is created and shared by the users. This is where you can download the source
code for WordPress core, plugins and themes as well as the central location for 
community conversations and organization. [https://wordpress.org/](https://wordpress.org/)
that attempts to pull together the ease and power of blocks into a single source:

[[

This work was wrangled in [this GitHub issue](https://github.com/WordPress/wporg-main-2022/issues/245)
and [this figma file](https://www.figma.com/file/cehwvnioJlfRsHo0SFEYrF/.Org-Website-Hub?type=design&node-id=1708-60165&mode=design&t=8J2eKCyxhOgGa2en-0)
before diving into the editor itself to implement it thanks to help from a wide 
group of folks with special shout outs to [@ryelle](https://profiles.wordpress.org/ryelle/)
[@matveb](https://profiles.wordpress.org/matveb/) [@saxonfletcher](https://profiles.wordpress.org/saxonfletcher/)
[@kellychoffman](https://profiles.wordpress.org/kellychoffman/) [@youknowriad](https://profiles.wordpress.org/youknowriad/)
[@markoserb](https://profiles.wordpress.org/markoserb/) [@joen](https://profiles.wordpress.org/joen/)
[@ndiego](https://profiles.wordpress.org/ndiego/) [@provenself](https://profiles.wordpress.org/provenself/).
You will soon find this page [under the “Extend” menu](https://github.com/WordPress/wporg-mu-plugins/issues/417)
to better improve discoverability and highlight blocks.

**Let’s iterate with feedback**

This is intended to be a starting point and not a final destination. Your feedback
is welcomed and needed to get to the next iteration. Please leave a comment below
and consider the following questions

 * What would make this page more compelling?
 * What points of confusion remain?
 * What visuals would you like to see to better communicate the story of blocks?
 * What additional resources need to be created to guide folks?
 * Where else should this page be linked from to improve discoverability?

Going forward, the intention is to update this page semi-regularly as it makes sense,
with progressive features in WordPress releases and increasing resources.

_Thank you to [@ndiego](https://profiles.wordpress.org/ndiego/) and [@cbringmann](https://profiles.wordpress.org/cbringmann/)
for reviewing this post._

### Share this:

 * [  Threads ](https://make.wordpress.org/meta/2023/08/11/introducing-wordpress-org-blocks/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/meta/2023/08/11/introducing-wordpress-org-blocks/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/meta/2023/08/11/introducing-wordpress-org-blocks/?share=bluesky)
 * [  X ](https://make.wordpress.org/meta/2023/08/11/introducing-wordpress-org-blocks/?share=x)
 * [  Facebook ](https://make.wordpress.org/meta/2023/08/11/introducing-wordpress-org-blocks/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/meta/2023/08/11/introducing-wordpress-org-blocks/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2023%2F08%2F11%2Fintroducing-wordpress-org-blocks%2F%23respond&locale=en_US)

 1.  ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
     s=32&d=mm&r=g)
 2.   [annezazu](https://profiles.wordpress.org/annezazu/)  6:27 pm _on_ August 11,
     2023
 3.  I’ll jump in first to offer items on my mind to iterate on:
 4.   * More illustrations, less text.
      * Consider evolving [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
        to align better with this page.
      * Integrate something like the[ blockbook project](https://youknowriad.github.io/blockbook/)
        into the experience, perhaps using WP Sandbox.
      * Consider how best to use WP Sandbox to have folks try out more of what’s discussed
        here.
      * Add some sort of a visual that better represents the connection between blocks
        > patterns > themes. Below is an extremely rough idea:
 5.  [⌊screen-shot-2023-07-25-at-3.06.03-pm⌉⌊screen-shot-2023-07-25-at-3.06.03-pm⌉[
 6.  ![](https://secure.gravatar.com/avatar/62ed6669556644a294591975f01137cd76ea6d1dcd8bf8b3328c1e2bf6e2a80d?
     s=32&d=mm&r=g)
 7.   [Dion Hulse](https://profiles.wordpress.org/dd32/)  7:22 am _on_ August 14, 2023
 8.  This page is now available to Rosetta sites (ie. [https://de.wordpress.org/blocks/](https://de.wordpress.org/blocks/)
     and [https://es.wordpress.org/blocks/](https://es.wordpress.org/blocks/) ) – Translations
     are [within this translate project](https://translate.wordpress.org/projects/meta/wordpress-org/).
 9.  For future changes, it would be great if the imagery and visuals were somewhat
     language neutral.
 10. I also note some links to `wordpress.org/patterns` and `wordpress.org/gutenberg`,
     those being linked to `/patterns/` and `/gutenberg/` respectively helps keep locale
     sites linking to their translated variants.
 11.  * ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
        s=32&d=mm&r=g)
      *  [annezazu](https://profiles.wordpress.org/annezazu/)  10:19 pm _on_ August
        14, 2023
      * Added to this tracking issue for a first iteration! [https://github.com/WordPress/wporg-main-2022/issues/318](https://github.com/WordPress/wporg-main-2022/issues/318)
        Thanks so much.
 12. ![](https://secure.gravatar.com/avatar/ac1671dfdcc1266ed3bd2c4f26ab7356f0f574c67144534354d5372429221204?
     s=32&d=mm&r=g)
 13.  [Ren](https://profiles.wordpress.org/renrams/)  6:36 am _on_ August 16, 2023
 14. The hero image looks good, but I think a nice screenshot or gif of the blockBlock
     Block is the abstract term used to describe units of markup that, composed together,
     form the content or layout of a webpage using the WordPress editor. The idea combines
     concepts of what in the past may have achieved with shortcodes, custom HTML, and
     embed discovery into a single consistent API and user experience. editor with 
     an opened list-view would could work a lot better. The relationship between blocks
     in the list view and patterns in the editor could be highlighted, and make a better
     point this way explaining that blocks are basically a more simplified and end-
     user friendly version of htmlHTML HTML is an acronym for Hyper Text Markup Language.
     It is a markup language that is used in the development of web pages and websites..
     Basically jsx for designers.
 15.  * ![](https://secure.gravatar.com/avatar/ac1671dfdcc1266ed3bd2c4f26ab7356f0f574c67144534354d5372429221204?
        s=32&d=mm&r=g)
      *  [Ren](https://profiles.wordpress.org/renrams/)  7:18 am _on_ August 16, 2023
      * I’d also mention that accessibilityAccessibility Accessibility (commonly shortened
        to a11y) refers to the design of products, devices, services, or environments
        for people with disabilities. The concept of accessible design ensures both“
        direct access” (i.e. unassisted) and “indirect access” meaning compatibility
        with a person’s assistive technology (for example, computer screen readers).(
        https://en.wikipedia.org/wiki/Accessibility) is cared for with blocks because
        it’s one of the biggest pain points building custom sites from scratch.
      * Devs and designers already use similar solutions elsewhere (Tailwind, Shadcn,
        Client First, Relume) and mentioning that blocks are similar and tie into a
        bigger design framework that’s native to WordPress could be a plus.
      * I’ve tried some non WP all in one marketer focused page/business builders in
        the past weeks and the blockBlock Block is the abstract term used to describe
        units of markup that, composed together, form the content or layout of a webpage
        using the WordPress editor. The idea combines concepts of what in the past 
        may have achieved with shortcodes, custom HTML, and embed discovery into a 
        single consistent API and user experience. editor and blocks despite their 
        flaws and potential complexity are infinetly more pleasant to use if you have
        any form of design intent.
      * Maybe try to score some testimonials from marketer/business influencers who
        prefer blocks. The people behind the commercial block based “Popcorn Theme”(
        not in the repo) are well known in SEO circles and on Youtube.
      * ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
        s=32&d=mm&r=g)
      *  [annezazu](https://profiles.wordpress.org/annezazu/)  7:10 pm _on_ August 
        18, 2023
      * Thanks for diving in to share feedback. Let’s go through each part.
      * > The hero image looks good, but I think a nice screenshot or gif of the blockBlock
        > Block is the abstract term used to describe units of markup that, composed
        > together, form the content or layout of a webpage using the WordPress editor.
        > The idea combines concepts of what in the past may have achieved with shortcodes,
        > custom HTML, and embed discovery into a single consistent API and user experience.
        > editor with an opened list-view would could work a lot better.
      * Agreed. The hero image definitely needs to be iterated upon and I cover better
        visuals in the [iteration issue ](https://github.com/WordPress/wporg-main-2022/issues/318)
        so know this is noted!
      * > Devs and designers already use similar solutions elsewhere (Tailwind, Shadcn,
        > Client First, Relume) and mentioning that blocks are similar and tie into
        > a bigger design framework that’s native to WordPress could be a plus.
      * Yes, yes, yes! This framework approach is key to underscore and I think having
        better visuals will go a long way. I’m tempted in reading this feedback to 
        completely have a separate section driving that home more.
      * > Maybe try to score some testimonials from marketer/business influencers who
        > prefer blocks. The people behind the commercial block based “Popcorn Theme”(
        > not in the repo) are well known in SEO circles and on Youtube.
      * In reading this, I added an item to connect this page to the Showcase overhaul
        work! I think rather than trying to seek out and find testimonials, we can 
        point to work being done with blocks from the showcase instead. Getting quotes
        and figuring out who to feature can be gnarly.
 16. ![](https://secure.gravatar.com/avatar/ccd0cec9803f6a9a825da61d20d11d73743dfcc9246fe4d011ab26ae9d434e90?
     s=32&d=mm&r=g)
 17.  [David Innes](https://profiles.wordpress.org/david-innes/)  4:29 pm _on_ August
     16, 2023
 18. Unless you want ordinary users to continue installing the Classic Editor pluginPlugin
     A plugin is a piece of software containing a group of functions that can be added
     to a WordPress website. They can extend functionality or add new features to your
     WordPress websites. WordPress plugins are written in the PHP programming language
     and integrate seamlessly with WordPress. These can be free in the WordPress.org
     Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
     or can be cost-based plugin from a third-party., any page claiming to explain 
     blocks needs to be primarily about how blocks benefit day-to-day end users, not
     programmers.
 19. Programmers, especially ReactReact React is a JavaScript library that makes it
     easy to reason about, construct, and maintain stateless and stateful user interfaces.
     
     [https://reactjs.org](https://reactjs.org/) professionals, are already going to
     be 100% on board. All you need is a single row at the bottom of the page pointing
     to those four links, changing the discouraging-to-ordinary-user title from “Only
     the beginning” to “For programmers.”
 20. You absolutely _should not_ have a flipping code snippet anywhere on this page,
     even if it’s “just” for creating a blockBlock Block is the abstract term used 
     to describe units of markup that, composed together, form the content or layout
     of a webpage using the WordPress editor. The idea combines concepts of what in
     the past may have achieved with shortcodes, custom HTML, and embed discovery into
     a single consistent API and user experience. that says “hello world.” Yes, everyone
     who’s studied programming knows what this means, just like they know that “foo”
     is a throwaway variable name. Unfortunately non-programmers are going to take 
     one look at that snippet and decide, “geez, you have to be able to write your 
     own blocks just to put text on a page?”)
 21. So is this new page exclusively for programmers? Because while it promises “complete
     control” and that creating sites “has never been easier” there’s a brief description
     of common blocks, a gallery of pre-baked patterns, and then the rest is all about
     how “building a block is ‘as simple’ as spinning up a full-stack programming environment.”
 22. Correct me if I’m wrong (the continuing popularity of the Classic Editor plugin
     says I’m not) but most WordPress users aren’t experienced programmers.
 23. Everything on the page except the last row should be, as annezazu says in another
     comment, all about what blocks should mean for the authors, shop and business 
     owners, event managers, service professionals, bloggers, etc., who are saddled
     with a page-builder interface when they’re instead going to spend 90% or more 
     of their time writing or editing articles, posts, product and event descriptions,
     class descriptions, service tips, testimonials, case studies, etc.
 24. A site with only finished pages is a dead website. Only 10% of the work is done
     once a site is built and launched. Everything else is day-to-day content creation,
     and this proposal doesn’t address that at all.
 25. So as annezazu says the page should start with block fundamentals like what is
     a block, what kinds of blocks are there, how do blocks speed the process for adding
     and editing post/product/event/etc. content after a site is built, and generally
     making a case for not installing the Classic Editor.
 26. Seriously!
 27.  * ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
        s=32&d=mm&r=g)
      *  [annezazu](https://profiles.wordpress.org/annezazu/)  7:22 pm _on_ August 
        18, 2023
      * Thanks so much for taking the time to share feedback, ideas, and wider context.
      * > Unless you want ordinary users to continue installing the Classic Editor 
        > pluginPlugin A plugin is a piece of software containing a group of functions
        > that can be added to a WordPress website. They can extend functionality or
        > add new features to your WordPress websites. WordPress plugins are written
        > in the PHP programming language and integrate seamlessly with WordPress. 
        > These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
        > or can be cost-based plugin from a third-party., any page claiming to explain
        > blocks needs to be primarily about how blocks benefit day-to-day end users,
        > not programmers.
      * This is the tricky part that we need to balance: it needs to be for both. To
        do this, I think we need to iterate on the language to show how user friendly
        blocks are _in order to_ then encourage developers and designers to use the
        overall framework, whether in WordPress or outside of it. [Here’s part of one of the early mockups](https://www.figma.com/file/cehwvnioJlfRsHo0SFEYrF/.Org-Website-Hub?type=design&node-id=1708-60165&mode=design&t=dXdZzqwKdNN2DlbM-0)
        I had that tried to cover this just with words (and why I want more visuals
        to show that instead):
      * Sounds like we need to both incorporate that back into a next iteration and
        make sure it’s towards the top of the page. [Consider that noted in this tracking issue](https://github.com/WordPress/wporg-main-2022/issues/318).
 28. ![](https://secure.gravatar.com/avatar/2a79f74edcf1a1f2b35b6d3a2bdc6b31074bdb9fd0378ccdd45ce2b243044c46?
     s=32&d=mm&r=g)
 29.  [Jeff Sandquist](https://profiles.wordpress.org/jeffsand/)  4:22 pm _on_ September
     19, 2023
 30.  a. Consider using View Documentation vs create your own on the main landing page?
         It is often the first term a developer / builder looks for on a page. The term
         is also used later on.
      b. What if we use animation via GIF or other acceptable media format in one of the
         images to show a useful blockBlock Block is the abstract term used to describe
         units of markup that, composed together, form the content or layout of a webpage
         using the WordPress editor. The idea combines concepts of what in the past may
         have achieved with shortcodes, custom HTML, and embed discovery into a single
         consistent API and user experience. in action? Might help convey possible use
         cases better.
 31. ![](https://secure.gravatar.com/avatar/5d3c9f94a1020cb54008bc80a5661b3a57c94d87d08af6cad57683c08bd069ad?
     s=32&d=mm&r=g)
 32.  [Pablo Honey](https://profiles.wordpress.org/pablohoneyhoney/)  7:48 pm _on_ 
     October 16, 2023
 33. Good to see this out!
 34. In general, great as a first iteration. A few thoughts for bettering:
 35.  * There’s something playful and engaging about larger imagery and animations,
        like [https://order.design/project/block-by-block](https://order.design/project/block-by-block);
        ours feel a bit too boxy (even if pun is intended).
      * Mobile is not great, even less appealing, images are super small, not thought
        for that environment.
      * Headings and paragraphs aren’t well aligned.
 36. Content wise:
 37.  * There’s a hint at what you can do with blocks but minimal, needs more focus
        and amplitude on that.
      * Same with blockBlock Block is the abstract term used to describe units of markup
        that, composed together, form the content or layout of a webpage using the 
        WordPress editor. The idea combines concepts of what in the past may have achieved
        with shortcodes, custom HTML, and embed discovery into a single consistent 
        API and user experience. types, feels limiting to only surface eight.
      * It could have a CTA on top.
      * The patterns don’t render high-res on my side.
 38. I hope this is helpful! Left it on the issue as well [https://github.com/WordPress/wporg-main-2022/issues/318#issuecomment-1765166603](https://github.com/WordPress/wporg-main-2022/issues/318#issuecomment-1765166603)

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/meta/2023/08/11/introducing-wordpress-org-blocks/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2023%2F08%2F11%2Fintroducing-wordpress-org-blocks%2F&locale=en_US)
to post a comment.

# Post navigation

[← Organizations Supporting WordPress.org](https://make.wordpress.org/meta/2023/08/09/organizations-supporting-wordpress-org/)

[Matrix chat Summary – August… →](https://make.wordpress.org/meta/2023/08/17/matrix-chat-summary-august-2/)