Re:Fabricator – modular website design system
by rrrx3 on Friday January 01, 2016 @10:04PM
(#10824762)
Interesting. Looking around at the source now, it looks like it's not optimized to imply that sort of architectural thinking. That's a bummer. I'd love to have seen it take the React style approach of co-locating all the relevant parts to a module together.
Re:Fabricator – modular website design system
by lukeaskew on Sunday January 03, 2016 @03:36PM
(#10832219)
Creator here. The lack of architectural direction is very much intentional. I'm a strong believer that those decisions will vary from project to project and developer to developer. My goal was to provide the least obtrusive set of tools as possible.
I do have some plans to create a boilerplate toolkit that includes some of the architectural patterns I use often. Hopefully that helps guide developers who are less experienced with building large modular systems.
The tool does enforce and encourage atomic design architecture when it comes to HTML. At best, I'd describe Fabricator as a static-site/documentation generator. However, I wouldn't recommend using it Fabricator to generate documentation in the 'toolkit' way that's recommended in it the docs because it tightly couples that static site/documentation generation to UI library source. There are plenty of static site generators that work well for generating docs that I'd rather use (jekyll, hugo, etc).
I'd encourage developers considering Fabricator to proceed with caution. Although, it boasts ease of UI development based on atomic designs, the tool does not aide in code modularity or UI component re-usablity.