There should also be a way to get back to the index file

Inside a bloom.json file, in your folder, do something like

{
    "title": "This is real",
    "subtitle": "so real so real",
    "words" : true,
    "alphabetical" : true,
    "sequential" : true,
    "ftp" : false,
    "googleAnalyticsID" : "UA-hey hey hey"
}

This would add a snippet to each page of the built static site, so you can track things.

Chances are you'll be publishing changes or updating things - especially if you use bloom-cli as a blog. Why not a question to ask if you want to update the RSS feed if there's one? And what to update it to?

This is in order to enable easier automation with Amazon Polly :)

https://www.npmjs.com/package/comma-number

This should be a lot more specific and less open ended. Basically, I need any tests, and they should be targeted and I can open specific issues for tests I want to write.

Closing this.

You should be able to generate a QR code with the web location of the site you're making, with the version of the book, with whatever url or metadata you want, as part of the bloom.

https://www.npmjs.com/package/qr-image

Why!

This would generate a .htaccess file so that the folder is password protected when you bloom

This will help for sharing. Right now the title reflects the index page title.

The selections a user makes during while running the CLI can be saved into a bloom.rc file - json key/value pairs

Acceptance criteria:

• "Would you like to save this configuration so typing bloom will prompt fewer questions?" or something to that effect added the CLI (at the end)
• A bloomfile is generated if this is selected
• bloom command asks to use bloom.json file if there is one in the current directory
• If there's a bloom file but you say don't use it, don't prompt to save again

Probably just parse them out?

Writing in Ulysses on iPad isn't great for curly quotes. So Bloom should handle curlifying quotes by default until there are people who ask for having it as an option.

If someone were using bloom-cli to create index and subsequent pages, they might want to do some kind of basic file prepension in order to do auth or query string parameter parsing. If you were prepending PHP the file extension would have to change.

Images should maybe work independently from how the ULSS stylesheets say they should. Update the CSS for images.

Can either use it to generate the folder structure or just as another output option

Maybe I want a Javascript widget on every page, or a React component. Maybe I'd rather generate a single page app than a multipage static site. One I thought of would be: "Generate write-good output too?"

Would put an extra link next to the title so you could open two windows one with the story, another with the write-good output. OR put it in the same file I don't know.

#2 bloom watch should ask all the same questions as bloom but should then allow for automatic bloom every time a subsquent export from Ulysses happens.

Probably only need to watch the "index.html" file in the bloom folder