Release 1.0 #35
Description
Stratic is getting mature enough that it's time to start pushing towards a 1.0 release. Here's what I think we have to do before that can happen.
General:
- Decide on a logo, Logo #22
- Move to gulp 4, Move to gulp 4 #34
- Policy on pulling modules into the straticjs org, Policy on pulling modules into the straticjs org #21
Website:
- Blog needs to be enabled, Fix up the blog straticjs.github.io#2
- Put the logo on there somewhere, Put the logo on the website straticjs.github.io#3
Documentation:
- Project-wide design documentation, Planning for the new website straticjs.github.io#1
- At minimum, an index of available modules/what modules to use for different tasks, Fix up the blog straticjs.github.io#2
- Document #stratic, Document #stratic #19
- generator-stratic README is awful, README is awful generator-stratic#23
- Finish static to Stratic
Miscellaneous cleanups:
- I don't go by Alex anymore so make sure everything says AJ, Alex to AJ #31
- Make sure package.json repository metadata is correct, Fix github.com/strugee in package.jsons #32
- Ensure READMEs don't reference Stratic header parsing, Ensure READMEs don't reference Stratic header parsing #25
- Consistently use PluginErrors everywhere, PluginErrors #23
- Support NODE_DEBUG, Support NODE_DEBUG #4
We may want to do #14 too, before we get too many users? We might want to do straticjs/generator-stratic#16 and straticjs/generator-stratic#15 too, I'm not sure.