-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Extract data format and flow docs into their own architecture document. #25299
Conversation
Size Change: 0 B Total Size: 1.2 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, the one concern I have is the main page as the Project Overview, hopefully it will not increase the number of items at the top level but just a single item with the other parts nested. It hasn't always done what I expected. :-) So we can see after publishing and adjust as necessary.
I completely agree with the design docs, I've been trying to setup the Contributor's section as the area to go if you want to contribute to the project. So it makes sense there for discussing design aspects of the platform.
The design/develop bifurcation from the start is unfortunate, live and learn, but ideally the split is extending the platform (plugins/themes) and contributing to the platform (project itself).
There is always going to be a fair amount of overlap since the platform is built on itself, most obvious example is the block library, but numerous others with components.
Looks like we have two issues: https://developer.wordpress.org/block-editor/
|
@youknowriad As mentioned in Slack, I removed the extra Project Overview page, and renamed the top level document. |
There's a couple things here:
Note
There's a few other things I want to do separately as well: