diff --git a/www/contribute/producing-an-ebook-step-by-step.php b/www/contribute/producing-an-ebook-step-by-step.php index 26f6e1a2..d87770eb 100644 --- a/www/contribute/producing-an-ebook-step-by-step.php +++ b/www/contribute/producing-an-ebook-step-by-step.php @@ -18,34 +18,36 @@ require_once('Core.php');

If you commingle editorial changes with other changes in your commits, we’ll be forced to ask you to rebase your repository to tease them out. This is very difficult and you’ll get frustrated—so please make sure to keep editorial commits separate!

If your working directory contains a mix of changes and you only want to commit some of them, git add --patch is a useful way to only commit parts of a file.

-
- Table of Contents -

Set up the Standard Ebooks toolset and make sure it’s up-to-date

-

Select an ebook to produce

-

Locate page scans of your book online

-

Create a Standard Ebooks epub skeleton

-

Do a rough cleanup of the source text and perform the first commit

-

Split the source text at logical divisions

-

Clean up the source text and perform the second commit

-

Typogrify the source text and perform the corresponding commit(s)

-

Check for transcription errors

-

Convert footnotes to endnotes

-

Add a list of illustrations

-

Converting British quotation to American quotation

-

Add semantics

-

Modernize spelling and hyphenation

-

Check for consistent diacritics

-

Check for consistent dashes

-

Set <title> elements

-

Build the manifest and spine

-

Build the table of contents

-

Clean and lint

-

Build and proofread, proofread, proofread!

-

Create the cover image

-

Complete content.opf

-

Complete the imprint and colophon

-

Final checks

-

Initial publication

+
+ Table of Contents +
    +
  1. Set up the Standard Ebooks toolset and make sure it’s up-to-date

  2. +
  3. Select an ebook to produce

  4. +
  5. Locate page scans of your book online

  6. +
  7. Create a Standard Ebooks epub skeleton

  8. +
  9. Do a rough cleanup of the source text and perform the first commit

  10. +
  11. Split the source text at logical divisions

  12. +
  13. Clean up the source text and perform the second commit

  14. +
  15. Typogrify the source text and perform the corresponding commit(s)

  16. +
  17. Check for transcription errors

  18. +
  19. Convert footnotes to endnotes

  20. +
  21. Add a list of illustrations

  22. +
  23. Converting British quotation to American quotation

  24. +
  25. Add semantics

  26. +
  27. Modernize spelling and hyphenation

  28. +
  29. Check for consistent diacritics

  30. +
  31. Check for consistent dashes

  32. +
  33. Set <title> elements

  34. +
  35. Build the manifest and spine

  36. +
  37. Build the table of contents

  38. +
  39. Clean and lint

  40. +
  41. Build and proofread, proofread, proofread!

  42. +
  43. Create the cover image

  44. +
  45. Complete content.opf

  46. +
  47. Complete the imprint and colophon

  48. +
  49. Final checks

  50. +
  51. Initial publication

  52. +
  1. @@ -541,7 +543,7 @@ proceed to seal up my confession, I bring the life of that unhappy Henry Jekyll

    The manifest is already in the correct order and doesn’t need to be edited. The spine, however, will have to be reordered to be in the correct reading order. Once you’ve done that, commit!

    git commit -am "Add manifest and spine"
  2. -

    Build the table of contents

    +

    Build the table of contents

    With the spine in the right order, we can now build the table of contents.

    The table of contents is a structured document that lets the reader easily navigate the book. In a Standard Ebook, it’s stored outside of the readable text directory with the assumption that the reading system will parse it and display a navigable representation for the user.

    Use se build-toc to generate a table of contents for this ebook.

    diff --git a/www/css/manual.css b/www/css/manual.css index 572ea18e..a3904c9a 100644 --- a/www/css/manual.css +++ b/www/css/manual.css @@ -329,7 +329,7 @@ code.full .utf{ } .step-by-step-guide details{ - padding: 1.0em 0; + padding: 1rem 0; list-style-type: none; counter-reset: toc 0; } @@ -346,14 +346,6 @@ code.full .utf{ list-style-position: outside; } -.step-by-step-guide details p { - counter-increment: toc 1; -} - -.step-by-step-guide details p::before{ - content: counter(toc) ". "; -} - .alert p.warning{ font-size: 2rem; font-weight: bold;