aboutsummaryrefslogtreecommitdiff
path: root/TODO.md
diff options
context:
space:
mode:
Diffstat (limited to 'TODO.md')
-rw-r--r--TODO.md24
1 files changed, 11 insertions, 13 deletions
diff --git a/TODO.md b/TODO.md
index c72e9cd..7df20e3 100644
--- a/TODO.md
+++ b/TODO.md
@@ -16,6 +16,7 @@
## Refactor
+* [ ] Consider merging `ChangeLog.md` with `_changelog.yml`.
* [ ] Create a `bookup` script:
* [ ] Able to read all the YAML config files, which should be the central
places to hold all the configuration.
@@ -32,19 +33,11 @@
* [ ] Slides:
* [ ] Improved slides workflow (compilation etc).
* [ ] Citation:
- * [ ] How to cite, by using `@projectName` in the frontmatter.
* [ ] Add the corresponding BibTeX entry.
-* [ ] Recent changes:
- * [ ] Build the recent changes section through a `snippets/changes.md` file?
- This is partially implemented, but commented.
- As an alternative (or meanwhile), the notebook can be used.
- * [ ] Alternativelly, build the recent changes using a `snippets/changes.yml`
- or just `_changes.yml` that gets compilet into a `snippets/changes.md`
- and into a RSS file that goes in the build.
- This RSS them can be linked as a `rel` element in the HTML, along with
- a regular link like "Follow updates in this book".
+ * [ ] How to cite, by using ~~`@projectName`~~ an example in the PDF
+ frontmatter.
* [ ] Localization:
- * [ ] Make sure to properly localized the build date string.
+ * [ ] Make sure to properly localize the build date string.
* [ ] Setup a PO-file workflow for translating the structure and templates?
* [ ] Formats:
* [ ] Fix the EPUB output:
@@ -69,12 +62,17 @@
* [ ] Suport for a `BASE_URL` environment variable?
It would be applied as a template variable in `%%base_url%%` placeholers,
allowing the compile material to have links among themselves.
- * [ ] Optionally add a small reference to the Bookup website in the book
- frontmatter?
+ * [ ] Add a small reference to the Bookup website in PDF book frontmatter.
+ * [ ] Add the lists of tables, images etc in the PDF table of contents.
## Documentation
* [ ] Improve the documentation.
+* [ ] Add that, with Bookup, books can be written and logged like another
+ coding project: good practices learned from computer programming can
+ be fed back into book writing.
+* [ ] Tell about _living books_, meant to be versioned, have feeds and an
+ archive, so others can properly follow updates and cite specific versions.
* [ ] Document the "Bookup Stack": which piece of software is at which level,
and used for what.
* [ ] Add a reference to: