-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking: Blocks page v1 and beyond #318
Comments
Here's the copy feedback I kindly got via DM:
|
Completed the following and have an update waiting to be synced:
These two items remain for an additional update this week:
|
Added a PR to the parent theme to hide the arrows on all child themes (including this one): WordPress/wporg-parent-2021#94 @annezazu regarding the code block, I'm still seeing |
Synced the latest content in beba657, deploying that now. |
Ah got it. That's my mistake. I have updated the page to remove the text colors -- can you handle an update once more? @ryelle Of note, I've also updated this overall issue into "Now" and "Next" to better structure what can be fixed right now and what will need to be considered further into the future for another iteration. |
Removes `mark` elements from code example. See #318
@ryelle Not to distract from this discussion, but that redesign test page has an alarming number of accessibility issues. Where is that work currently being tracked? Is it early on enough that I shouldn't be reporting such bugs? I never have a feel for how fast stuff moves in this project until something hits production and that's extremely frustrating. I am sure some of these issues probably came from the old codex and developer resources days but if we're redesigning, no reason the ccode shouldn't be fixed. |
@alexstine We halted work on that site a few months ago, and are just now restarting, so now would be a great time to add that feedback. That project is tracked in this repo: https://github.com/WordPress/wporg-developer/ |
After adding a more comprehensive "next" section and receiving more feedback, I've updated the title of this issue to indicate a larger iteration in the future. |
With the Showcase launching on the 18th, I want to do a super minor update in this section here to connect the two, likely just as a simple button: Right now, I'm leaning towards something simple like this: Curious to hear what @marko-srb thinks! |
Hey @annezazu, That works, I can add the button and the sentence. I believe we want to update this only after the Showcase is out (Oct 18th), correct? |
That's correct! Thank you 🥳 |
Good to see this out! In general, great as a first iteration. A few thoughts for bettering:
Content wise:
|
I've just push the update here. @adamwoodnz can we get this update after the Showcase is out? I can ping again for timing (should be on Thursday this week), just want to make sure this lands on Neso's table and it happens soon after the Showcase i2 is published... Thanks! CC: @jasmussen |
Bringing a question/comment I've seen referenced a few times around this effort: What is the role of this page compared to /gutenberg? How can we consolidate and distinguish these efforts? As a result, I've kicked off this open discussion and wanted to cross link to this more intentionally as it's something that might influence future iterations depending on what comes up: #379 |
@marko-srb we've gotten some direction around /blocks 🌟 and how best to distinguish from /gutenberg going forward:
I think this simplifies what we need to do into a few sections. At a high level:
Are you able to get started on an iteration with the above in mind and we can go from there? Here's a version below using this figma file that's quick and dirty: |
@marko-srb, no rush at all, but when you have a chance, can you provide a design update here? I hope to reference this on Thursday in my community update in the #website-redesign channel. Thanks! 🙏 |
Noting for my future self that if/when /gutenberg is changed, we'll need to update the "try blocks live" link to go to a playground install OR perhaps have a playground block there: https://wordpress.org/plugins/interactive-code-block/ cc @adamziel in case you have some background insight on what would be most reliable. |
@annezazu Either of these options would work. What would be the goal of that showcase? To show WordPress core blocks? If so, either redirecting to Playground or embedding it directly on /gutenberg or /blocks via the WordPress Playground block would do the trick. |
Thanks so much for this set of iterations! It's exciting to see some fresh designs. I liked the following sections, pulled from each. I think because some of the content isn't filled out, I had a hard time with others. Notes: I love the way this shows content and clearly labels the block type. I think this is a dynamic and beautiful way to communicate what blocks are. Notes: this feels very jazzy and in line with broader approaches on WPORG, again nicely emphasizing blocks and showing them as free flowing/interconnected. Notes: I really like the gist of this visual but it's not quite there for me. I do think showing a block in the center then perhaps branching out to show the code side of it as you do and maybe what it might look like to extend it or have a variation of the same block would be neat. As is, it isn't quite there but I like the promise of the idea and think it could work nicely for a visual for devs who want to build with blocks. As a reminder from this discussion:
To note what feels missing, I think we need a solid visual around the block directory. |
To be honest, I’m not confident any of these versions is much more compelling than what is currently live. The visuals are nice, but holistically I can’t tell who this is for. Who is this page for? Developers who need convincing? People who don’t know what blocks are? Enterprise teams investigating the use of the Block Editor? Developers looking for block-related answers? I can’t tell from these explorations, nor the live version. Dependent on that focus, the content structure should adapt. Perhaps it’s more block + code examples, like on Tailwind, that show a pattern with its block markup. Or an example of a block with its block.json file. Or if we’re trying to convince someone to use blocks, we should clearly communicate the value of building, and using, blocks. |
To answer this I'm going to pull from a separate thread on the /Gutenberg page: "He kindly clarified that /blocks is meant to be about how WordPress uses blocks, the block directory, and an introduction for developers who want to build with blocks. In contrast, the /gutenberg page should be more about devrel, the architecture of gutenberg, and its use outside of just WordPress." |
I find the layered approach most interesting which would include what the actual block looks like. The icon only tells part of the story as you might have custom blocks are more functional (like a form) or even animated in some way. https://www.radix-ui.com/ might provide some inspiration. I’d also communicate that blocks can be style agnostic in that one block can be presented in many different ways depending on the theme/font/colour. As for page structure, the original intent behind 2.2 was to present information in a way that aligns with how a user may interact with a block.
|
I agree with @richtabor point. This conversation ties into the homepage discussion a little bit, and the general feeling that wordpress.org site feels quite fragmented and ambiguous at times.
A missing piece there is the actual editing experience. I'd personally like to see:
|
Nice work. I quite like the reduction of a block into just a single rounded square with the icon, the same element even visually echoes some of the block editor, so it can be a strong branding element. Reading through this, and echoing Saxon above, it’s very clear you’ve had to carefully manage multiple stakeholders and differing visions of what this page could and should be. To that end, I’d think there’s enough material here to work with to decide, what actually is the V2 of this page, before diving back into the work. So any visual feedback I have, I’d postpone to after that feedback has landed, it’s entirely possible it will be moot. Some small things:
This is my favorite part of the whole thing: The colors are maybe a tad pastel and we can refine the shadows, but there’s a spark here that combines the conceptual blocks with photography, typography, a “pattern”, very literally showing you able to compose artwork. I wonder, what would it look like if there was a range control or a toggle? Perhaps even a resize handle or focal point picker? Combined with beautiful typography and photography, the illustrations for the entire page could consist of abstract collages like this one, that show precisely how blocks with their associated design tools compose into patterns, ultimately into a page. Nice work Marko. |
Thanks, all, for chiming in here! For larger changes, let's put that on pause until we can sync up with Matías. For now, I want to move forward with some light visual changes and an addition of a link to the block directory. I'll work with @jasmussen on this and follow up with a screenshot of the editor as we get closer. |
I was looking at SEO the other day in a different context and it appears that users are still searching for "gutenberg blocks", not so much "blocks" or "WordPress blocks". Although I recognize we probably want to transition away from those keywords, it may be a good idea to include that language to meet users where they are. Edit: This page doesn't return for those keywords. |
Yeah, "Gutenberg" isn't going anywhere 😅 |
Here's a video of the iteration! Light changes in placement and design, a new more internationally focused patterns section (different languages), and an addition around 6.5/the latest to show off how things are actively being iterated upon: blocks.iteration.movBig props to @jasmussen. |
To pull together the initial iteration of the blocks page, I'm gathering feedback here with what's known to update for a quick iteration:
Now
aria-hidden
. @ryelle can you handle?Next
For design:
For dev/other:
The text was updated successfully, but these errors were encountered: