Tom Schraitle

Moved from https://sourceforge.net/p/doccookbook/tickets/26/ --- Write a colophon explaining how this book is/was produced; which tools, fonts, etc. are used

## Problem The book needs a decent index, maybe created semi-automatically. ## Solution The book contains an index with the following properties: * [ ] primary indexterm about (stylesheet) parameters...

Moved from https://sourceforge.net/p/doccookbook/tickets/29/ --- Implement syntax highlighting in online output for screen or programlisting. Useful links: * http://alexgorbatchev.com/SyntaxHighlighter/ * http://softwaremaniacs.org/soft/highlight/en/ * http://code.google.com/p/google-code-prettify/

## Problem User would like to leave a comment for a specific page. ## Possible Solutions * Create infrastructure to enable users to insert comments for each paragraphs, similar to...

## Problem As a showcase, use assemblies in the future ## Expected behaviour * The main file is an assembly file * The tool chain is adapted to produce the...

## Problem The project and book name is a bit cheasy. ## Solution Rename it to "DocBook Style Guide: Best Practices for Authors and Developers" ## Checklist * [ ]...

## Problem Although DocBook does not enforce how you create your project, it could be helpful to give some information about the "things around DocBook". ## Solution Some ideas that...

**Is your feature request related to a problem? Please describe.** The current look of my HTML pages are a bit... boring. Furthermore, it should be readable on smartphones and desktop...

**Is your feature request related to a problem? Please describe.** Missing `sitemap.xml` to improve Google SEO results. **Describe the solution you'd like** Add a `sitemap.xml`. **Additional context** * To split...

## Problem Maybe it's worth to think about creating a specific GitHub domain dedicated to this project. Related to #19 ## Solution With a domain, it could be easier to...