The css/sass architecture and "best practices" in Tapestry is very defined which is not optimal for new projects. Every project is different and has their unique needs, so I would prefer a clean slate and less of a "Twitter bootstrap" solution.
I am interested in the pattern library functionality more than the CSS architecture.
Should I see this architecture as an example of implementation or are there some thoughts about the structure and dependencies? How should I go about to remove these and make my own selections? Is there some core scss/css somewhere or can I safely delete everything?
I would recommend to split the architecture up a bit, with a skeleton framework with minimal CSS (No design, just basic functionality) and then example code to build the demo.
The developer can then select by themselves the kind of tools, grids, frameworks, SMACSS, OOCSS architectures and so on.
The css/sass architecture and "best practices" in Tapestry is very defined which is not optimal for new projects. Every project is different and has their unique needs, so I would prefer a clean slate and less of a "Twitter bootstrap" solution.
I am interested in the pattern library functionality more than the CSS architecture.
Should I see this architecture as an example of implementation or are there some thoughts about the structure and dependencies? How should I go about to remove these and make my own selections? Is there some core scss/css somewhere or can I safely delete everything?
I would recommend to split the architecture up a bit, with a skeleton framework with minimal CSS (No design, just basic functionality) and then example code to build the demo.
The developer can then select by themselves the kind of tools, grids, frameworks, SMACSS, OOCSS architectures and so on.