Codeinwp / Codeinwp/templates-patterns-collection
Converting it to a generic solution that works with any theme
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 56
- Forks
- 10
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
What problem does this address?
I think the idea when we started this and used a generic name was that eventually, this can work across themes, over time we have realized that is not very easy to achieve consistency and pretty much dropped the idea.
I was thinking however that we do have good technology to design, export & import full sites, which can be valuable outside Neve as well. I am wondering if with the standardization of FSE themes in terms of how colors, fonts are set and so on, can we create a set of patterns, page layouts & starter sites that can work well across multiple FSE themes?
What is your proposed solution?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by reviewing the repository's current theme and full-site export/import flow alongside the FSE conventions for colors and fonts; done should be a defined set of patterns, page layouts, or starter sites that works consistently across multiple themes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wordpress
- Domain
- design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100