Break into smaller pieces: `@webc/html`, `@webc/css`, `@webc/js`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 46
- Avg merge
- 10m
- Merged PRs (30d)
- 2
Description
Hey Zach! I've a question for you. Do you think we can break down this project into smaller subprojects?
I absolutely adore WebC as a template engine. It's incredibly convenient, easy to understand, and beautiful. However, I'm uncomfortable with how WebC handles styles, scripts, and components. I'd prefer to have a template engine only.
I feel like WebC is more than just a part of 11ty; it's something new that I truly believe in. Maybe we should consider creating a separate organization and splitting it into different repositories? For example, we could have @webc/html for markup, @webc/css for styles, and @webc/js for scripts, @webc/webc for all of them.
What are your thoughts on this?
Contributor guide
No contributing guide indexed for this repository
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. Start by examining the current project boundaries for WebC markup, styles, scripts, and components, then determine whether separate @webc/html, @webc/css, @webc/js, and @webc/webc packages are feasible; done means an agreed project-splitting plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100