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.
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/htmlfor markup,@webc/cssfor styles, and@webc/jsfor scripts,@webc/webcfor all of them.What are your thoughts on this?