We need code coverage set up across all modules.

#stratic on Freenode is a thing now; we should document the hell out of it.

It'd be real nice if I went through all the modules in the pipeline and tried to make sure they use streams, for performance.

Maybe the JS logo's yellow background with a | character and a file? I really don't know. I also like how "Stratic" kinda sounds like "stratosphere", but...

https://staticsitegenerators.net/

It's just come to my attention that stratic-posts-to-index's examples in the README still reference stratic-parse-header. I should go through and make sure other modules don't do this.

Need an Atom feed module.

Things like:

• Support NODE_DEBUG=
• Have a README
• Contributor Covenant
• Etc.

We need some way to do "read more" links in posts.

It'd be nice if we had a Yeoman generator that could generate Stratic modules, since https://github.com/straticjs/RFCs/tree/master/module-standards is actually getting to be kind of a long list.

I wonder if there's something we can do to decouple the concept of an index type from consuming modules. Right now everything has to obey the contract imposed by stratic-posts-to-index, but maybe that should change.

Properly use gulp PluginErrors across modules. https://github.com/gulpjs/gulp-util#new-pluginerrorpluginname-message-options

Deprecating stratic-parse-header in favor of YAML frontmatter made it clear that the current "attach properties directly to the file" approach is a serious composability problem. The consumer should be able to drop in pretty standard Node modules for the parsing step and with the custom properties, they can't.

This might also simplify post.jade, but I'm not sure. I think gulp-attach-to-template will probably stick around, which means that this won't help. But maybe not.

Moved from straticjs/generator-stratic#4.

On my personal blog I would like a way to specify some default categories and have posts automatically included in those categories unless I specify otherwise.

We need a Jekyll importer.

Moved from straticjs/generator-stratic#1.

Need a way to truncate indexes. Mostly useful for the RSS support.

This would probably function similarly to stratic-paginate-indexes internally.

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, #22
• Move to gulp 4, #34
• Policy on pulling modules into the straticjs org, #21

Website:

• Blog needs to be enabled, straticjs/straticjs.github.io#2
• Put the logo on there somewhere, straticjs/straticjs.github.io#3

Documentation:

• Project-wide design documentation, straticjs/straticjs.github.io#1
• At minimum, an index of available modules/what modules to use for different tasks, straticjs/straticjs.github.io#2
• Document #stratic, #19
• generator-stratic README is awful, straticjs/generator-stratic#23
• Finish static to Stratic

Miscellaneous cleanups:

• I don't go by Alex anymore so make sure everything says AJ, #31
• Make sure package.json repository metadata is correct, #32
• Ensure READMEs don't reference Stratic header parsing, #25
• Consistently use PluginErrors everywhere, #23
• 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.

When this is on npm I should PR to sindresorhus/awesome-nodejs.

Moved from straticjs/generator-stratic#2.

We should do YAMLFeed. You know, 4 the lulz.

A lot of these still refer to strugee/* instead of straticjs/*.

May be enough to satisfy #9, #8. Maybe not.

Some parts of the system like e.g. stratic-indexes-to-rss create and assume clean URLs without extensions. I should go through all the modules and make sure that they handle URLs consistently.

We need to support drafts.

We need to do this across modules.

I'm thinking it would be nice to have a module that would attach additional metadata to the Vinyl file based on the author. Things like the author's URL, etc. This would be particularly useful on blogs where multiple people are authoring content.

There's a bunch of useful stuff you might want on indexes, like the English-language month name, or the number in permalinks (which may have to have a 0 appended to it), etc. Currently all this is just done inline in templates, but it'd probably be good to push this out into a reusable module everyone can share.

Turns out we need to do a better job taking the UTC offset into account. See strugee/strugee.github.com#40.

Things that need to be fixed:

• stratic-date-in-path
• stratic-posts-to-index
• stratic-indexes-to-rss
• #18, because this is getting complex enough that that's just a requirement now
• generator-stratic Pug

Jekyll has a notion of "themes", which are reusable cross-project. Maybe we should too?