-
Notifications
You must be signed in to change notification settings - Fork 22
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
Current state of the try/block-theme branch #128
Comments
Hi @apeatling! We have some more complete developer.wordpress.org designs: Since you started on this, we've added a fair bit of work to the parent theme. I'm thinking about forking this, integrating the parent, and using what I can of the styles you came up with. I'm curious about what your thoughts on this are. Do you think it's a logical approach? Any other suggestions? |
Firstly I won't be offended if you don't use any of it, it was really just an exploration! From what I can see the design deviates quite a bit from what is here, so I'm not sure how useful the styles might be? One part that could be useful is the individual blocks that render parts of the code pages in the editor. They are fairly rudimentary, but worth a look. They may not be useful if you are not making those pages editable in Gutenberg though. If there's anything you can pick at and use in the direction you take feel free, I'm happy to help with any thoughts you need. |
I'm going to close this. It's far behind now and we reused some of this. |
I've been experimenting with this repo and updating the design of developer.wordpress.org to be based on a more compact version of the designs in this HH Figma.
At the same time I've also been working on converting the theme to be block based, and support full site editing.
Here's the status of each section:
Landing Page
The landing page keeps the same general layout, but matches the landing pages from the HH design. It also includes some links that might be good starting points.
Some thoughts:
Handbook Pages
The handbook pages continue to use the content coming directly from Github markdown files. The changes largely consist of the improved styling, as well as converting the sidebar and ToC sections into sever side rendering blocks.
Some thoughts:
Code Reference Pages
These pages have had the least work done on them. Essentially the whole thing needs to be converted to server side rendered blocks, which I have started in the repo. Doing this will allow much greater control over the structure and design of these pages.
Here's a mockup I made using the new design as a base:
Some thoughts:
Other Thoughts
Still quite a lot to do on this, and a bunch of design things to settle. It would be great to be able to get this in a setup where we can open PRs against it so others can more easily contribute and review. If anyone is interested in helping out on current issues, or anything mentioned above, go for it. Feel free to ping me on slack: apeatling.
The text was updated successfully, but these errors were encountered: