Skip to content
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

Intrinsic design vs. device view points #9

Closed
bph opened this issue Sep 22, 2022 · 24 comments
Closed

Intrinsic design vs. device view points #9

bph opened this issue Sep 22, 2022 · 24 comments
Assignees
Labels
Design flow: needs input let's discuss this.

Comments

@bph
Copy link
Collaborator

bph commented Sep 22, 2022

How Gutenberg developer implement responsiveness for the block editor.

Resources:

From conversations...
An answer to Why are there no breakpoints and responsiveness in blocks?

"The projects is implementing intrinsic design, that reacts to any screen size, and not just arbitrary break points. From there it aims to adjust typography and layouts in patterns. The first implementation is available with the Row and Stack variation of the Group block."

Fluid Typography comes to WordPress 6.1: "Fluid typography" describes how a site's font sizes adapt to every change in screen size, for example, growing larger as the viewport width increases, or smaller as it decreases."

Could emphasize how breakpoints immediately bring a lot of cognitive overhead for users, which is present in all the block libraries that do it. Furthermore, artificial breakpoints are not flexible enough (fixed sizes for mobile, tablet, web), don’t account for patterns inserted in different contexts, etc.

Page Builders, like Elementor or Beaver Builder, started five to seven years ago. Breakpoints were all that was available back then. Jen Simmons discussed Intrinsic design at the A List Apart Event in April 2019

@bph bph added flow: needs writer the idea/pitch needs a writer flow: needs input let's discuss this. labels Sep 22, 2022
@bph bph added the Design label Oct 6, 2022
@annezazu
Copy link

annezazu commented Oct 7, 2022

Great video here that touches on aspects of intrinsic web design vs breakpoints, along with the limitations of breakpoints: https://heypresents.com/talks/be-the-browser-s-mentor-not-its-micromanager

@bph
Copy link
Collaborator Author

bph commented Oct 9, 2022

Nice find, @annezazu Thank you!

@bph
Copy link
Collaborator Author

bph commented Oct 10, 2022

Screenshot_20221003-230516

The proliferation of screen sizes - too many to control by break points. ...

@bph bph moved this from Todo to Need approval in Developer Blog Content Board Oct 25, 2022
@colorful-tones
Copy link
Member

This is a great idea and I would be happy to run with this as my first piece.

@bph bph moved this from Topic needs approval to To-do in Developer Blog Content Board Dec 1, 2022
@bph bph removed the flow: needs writer the idea/pitch needs a writer label Dec 6, 2022
@colorful-tones
Copy link
Member

I have some time set aside on Friday to try and drop an outline.

@colorful-tones
Copy link
Member

I'm feeling a bit perplexed about a sound title for this piece. I'm not too keen on "something vs something", because of the binary and winner vs loser contention.

Here is my rough, high-level outline.

  • Brief history of breakpoints: challenges they seek to overcome, shortcomings
  • Fluid typography & spacing: rather recent introductions to WordPress, but not a recent concept. Again, cover the challenges they seek to address and possible shortcomings
  • Where the future may lie? - exciting potential for upcoming features

@bph
Copy link
Collaborator Author

bph commented Dec 22, 2022

@colorful-tones
Almost every post that started as an issue ended up with a different title. It was more the idea that some people aired grievance that the editor is not responsive because it doesn't over break viewpoint as seen by 5 top seven-year-old 3rd party page builders, while overlooking the primary approach to responsiveness is the newer fluidness and intrinsic designs, rather than burden users with view points.
You are the writer, and you determine the title. :-)

Starting with the second bullet point and then come back to the first - would get the reader off to a better start learning how it works. Apart from that, the outline appears to be solid.

@colorful-tones
Copy link
Member

I got started on a draft for this yesterday, but it still has a way to go. I'm hoping to have a complete draft ready for review by the end of next week.

@bph bph moved this from To-do to In Progress in Developer Blog Content Board Jan 5, 2023
@colorful-tones
Copy link
Member

Here is a rough draft that I've been working on: https://docs.google.com/document/d/1fS8McxhIVHA8n15FnktL8WCEqZYIzWvrww6LOYnhI5A/edit?usp=sharing

@annezazu
Copy link

annezazu commented Jan 6, 2023

I'll review this early next week!

@annezazu
Copy link

annezazu commented Jan 9, 2023

Reviewed! It's a great start. I would opt for clarity over cleverness in the title and intro. Overall, the pieces are factual and descriptive but I think could be made more compelling, perhaps with visuals like the one shared here.

@bph
Copy link
Collaborator Author

bph commented Jan 10, 2023

Thanks @colorful-tones for taking on this post. I like the straight forwardness in examples from the various themes. It's a bit short why view points are not helpful anymore.
There was also a great discussion about this topic posted by Joen Asmussen in the issue: WordPress/gutenberg#34641

It might help giving it a bit more meat on the theory and rationale behind it opting for the fluid and intrinsic design.

the section "Shortcomings of responsive design by media query" - Is a bit thin in explanation...

If you want to add more theory: https://css-tricks.com/intrinsic-typography-is-the-future-of-styling-text-on-the-web/
from 2021 is a very good article.

@colorful-tones
Copy link
Member

perhaps with visuals like the one shared here.

That is certainly a compelling visual. However, what are the guidelines around using images and crediting sources? I'm not sure where that image came from and who to credit.

@bph @annezazu I'm not sure I'll have the bandwidth to get this over the finish line. All of your observations and feedback are spot on and I'm missing some gaps in knowledge for the WordPress roadmap or critical theories apparently.

For now, I'm going to unassign this so I don't hold editorial expectations. 👍

I'll leave my Google Doc draft publicly available in case anybody wants to try and run with it. Thanks for all the great feedback!

@colorful-tones colorful-tones removed their assignment Jan 10, 2023
@bph
Copy link
Collaborator Author

bph commented Jan 11, 2023

Additional discussion from project contributors/leadership:

@bph
Copy link
Collaborator Author

bph commented Jan 19, 2023

@colorful-tones So sorry to hear that our comments let you shy away from finishing this post. The post is well structure and the examples are great. Thanks for keeping the Google Doc available, so we can give you co-author props. :-)

I see you posted a different topic idea on the discussion board. Thank you for that! :-) I also want to know how this gradient thingy works.

Cheers!

@justintadlock justintadlock self-assigned this Feb 6, 2023
@justintadlock
Copy link

@colorful-tones Thank you for your work toward this so far. I'm happy to take it and run with it. :)

@justintadlock
Copy link

I've finished the bulk of the draft, which is in a Google Doc. Most of what's left will be the code example pieces at the end. I wouldn't normally post for feedback at this stage, but I think it would be helpful to iron out the early sections of the piece around what intrinsic design is and why it's useful. Are there things I'm missing? Are the definitions fleshed out enough? etc.

@annezazu
Copy link

I'll review this next week as best as I can!

@annezazu
Copy link

I don't seem to have edit access so offering feedback here for now!

There is nothing wrong with this question and those similar to it.

I'd rephrase this more positively: "These are important questions to ask-- Designers have been having these discussions for decades at this point". I love the rest of that paragraph. It's excellent and specific.

Web design needed to evolve to handle a rapidly-changing world where site visitors were suddenly carrying around computers in the palm or their hands or reading from the comfort of their big-screen TV in the living room.

Minor typo: "palm of their hands". You use "evolve" three times in the first section. I'd try to cut back.

From the health of the WordPress project, this meant making some tough decisions about not jumping head first into adding every possible CSS property as an option in the interface.

I might say "For the health" (I think that's what you mean).

Instead, it is an iterative process where developers have seen the release of new tools and techniques over the last few major releases and can expect more to come.

I'd perhaps link to https://make.wordpress.org/core/2022/09/26/core-editor-improvement-catalyst-for-creativity/

Finally, I might note the upcoming 6.2 release including min font size: WordPress/gutenberg#42489 (comment) It might be too in the weeds but it might be a good example of the iteration and evolution you wonderfully emphasize.

Great job :)

@justintadlock
Copy link

Thanks, @annezazu. This is great feedback. I'll be doing a copyediting review of it today and will fix up all the typos and smooth out some of the rougher bits.

The biggest thing was making sure I was getting the descriptions and definitions right in the early sections.

I'd rephrase this more positively:

You know, I literally thought to myself when I read through again yesterday, "Anne will tell me to make this more positive." Should've trusted my what my brain was telling me. :)

@annezazu
Copy link

Hah! Glad I've become predictable. I think the framing is excellent and it feels all very relatable/understandable.

@justintadlock justintadlock moved this from In Progress to Needs 2nd review in Developer Blog Content Board Feb 21, 2023
@justintadlock
Copy link

Thanks to @mburridge for also providing a copyediting review. 🙌

I'm officially moving this over to "Needs second review" now. I believe the draft is in a good enough state for this stage, but I'm also going to reach out to a couple of others who are more knowledgeable on intrinsic design to make sure the concepts are well explained.

Here is the doc for review: https://docs.google.com/document/d/1AkMehEMKDd-aoZhonw2UV7yNTm1mePDA84H16pp4yXk/edit#

@bph
Copy link
Collaborator Author

bph commented Feb 22, 2023

@justintadlock I feel this is ready to go. It's a great write-up. I just added the publishing checklist here, for posting it to the blog. :-)

  • Post Title in Sentence case
  • Are Category or Categories selected?
  • Are Tags identifies?
  • Is there an Excerpt?
  • Props added?

@bph bph moved this from Needs 2nd review to Ready to publish in Developer Blog Content Board Feb 23, 2023
@justintadlock justintadlock moved this from Ready to publish to Published (Done) in Developer Blog Content Board Feb 23, 2023
@justintadlock
Copy link

Published: https://developer.wordpress.org/news/2023/02/intrinsic-design-theming-and-rethinking-how-to-design-with-wordpress/

@github-project-automation github-project-automation bot moved this from Published (Done) to Ready to publish in Developer Blog Content Board Feb 23, 2023
@justintadlock justintadlock moved this from Ready to publish to Published (Done) in Developer Blog Content Board Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design flow: needs input let's discuss this.
Projects
Status: Published (Done)
Development

No branches or pull requests

4 participants