Some constructive criticism, if it helps: it takes a while to understand what this is. On the home page, if you can have two panes, some code on the left with your framework and output on the right to quickly get a grasp perhaps?
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.
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.
Edit: A UI toolkit-toolkit for building design systems.
Reading this I see a lot of things described by new names that we're used to know as "components", "modules" or "widgets".