Closed JohnPixle closed 8 months ago
After some further research and considerations about the future maintenance, I am back with the final list of Pattern categories that we will have in Raft.
1. Featured - This will include a basic set of commonly used patterns 2. Headers - Header patterns 3. Footers - Footer patterns 4. Heroes / Page titles - Hero sections and titles for posts and pages 5. Features - features, services, cards 6. Content - Several patterns to present content, including
As soon as we create the categories, I will then assign the existing patterns to each of them, as well as any new pattern I will create. As a reminder, we will remove any core pattern from the library.
@HardeepAsrani this week I am working on the design of these patterns in Figma, so it would be good to work in this one in parallel so I can start adding building them next week. Let me know if you need any clarifications or help on this one!
@JohnPixle You can find the PR here: https://github.com/Codeinwp/raft/pull/71
Here you can find all the registered patterns in case you want to make any modifications to their title/slugs: https://github.com/Codeinwp/raft/pull/71/files#diff-b2ab93a7ea5192f0e9924b2d8d3afe199235614e83100664ca7b451f944af6baR60
And the patterns will currently show up in Uncategorized as we need to assign them to appropriate categories. Let me know if you have a list so I could do that or you'd be doing it as you create new patterns.
:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
What problem does this address?
In the pattern library, we want to provide a theme-tight experience regarding patterns and page layouts. Currently in our themes, we follow the default/core pattern folder structure, and we also include many of the core patterns, which are inconsistent with the styles and layout of our theme.
Additionally, we now keep our theme patterns in their own folder, which does not help with discoverability and workflow integration.
What is your proposed solution?
In order to create a safe and efficient environment for our users, we can:
This issue is also aligned with Neve FSE library direction Also, let's keep in mind how this enriched library experience will interplay with the onboarding wizard.
cc @mghenciu
Will this feature require documentation? (Optional)
None