How do we handle neat and bitters?

[whmii]

I would assume that we are going to end up forking this repo and creating 3 repositories for each of the 3 libraries. Sounds scary but it'll probably work.

One question that I have is if we plan on releasing updates to the 3 repositories simultaneously and how far we should take this repo before we fork it.

The other is what will the bitters page be? the old site wont work and the project doesn't really have "documentation"

This was brought on by the realization that Neat 2.0 will basically remain unusable, even if it is in a beta state, until there is some level of documentation accessible by the web.

[tysongach]

• Bitters is quite different in that it’s not a library like Bourbon and Neat are
• Bitters does not use SassDoc
• You’re right in that Bitters doesn’t have “documentation”, per se, just an example page of the styles it affects
• I don’t think we need to worry about simultaneous releases because Bourbon, Neat and Bitters are not super coupled together; Bitters just uses a bit of Bourbon
• What do you mean by “the old site wont work…” in reference to the Bitters website?
• During development of Neat 2.0, a change log can be immensely helpful
• The current Neat site already runs on SassDoc…can we have it parse Neat 2.0 and have a publicly available URL during dev (while still making it clear that 1.x is the current stable)?

[tysongach]

@whmii If you don’t want to use the existing Neat site, my recommendation would be to stand up a simple site that at least parses the SassDoc, so that as you develop, you can see the docs evolve. I wish I did that earlier with Bourbon.

[tysongach]

@whmii Does the above help? I’m going to close this as it is not actionable for this repo at this time.

[whmii]

FWIW this has been adressed. neat.bouurbon.io repo now exists