Add better navigation
diff --git a/content/fop/dev/design/index.mdtext b/content/fop/dev/design/index.mdtext
index b6a6da7..5da1dd1 100644
--- a/content/fop/dev/design/index.mdtext
+++ b/content/fop/dev/design/index.mdtext
@@ -4,11 +4,31 @@
<note>The articles in this section pertain mainly to the *redesign* or *main* line of development. The redesign is mainly focusing on parts of the layout process (converting the FO tree into the Area Tree). Therefore other (non-layout) sections in this document are probably largely accurate for the maintenance branch, but should be used with care in that context.</note>
+## Topics
+
+- [Areas](areas.html)
+- [Breakpos](breakpos.html)
+- [Embedding](embedding.html)
+- [Extending](extending.html)
+- [Fotree](fotree.html)
+- [Images](images.html)
+- [Layout](layout.html)
+- [Optimise](optimise.html)
+- [Parsing](parsing.html)
+- [Pdf-library](pdf-library.html)
+- [Properties](properties.html)
+- [Renderers](renderers.html)
+- [Startup](startup.html)
+- [Svg](svg.html)
+- [Useragent](useragent.html)
+
## The Black Box View { #black-box}
From a user's standpoint, Apache™ FOP is a black box that an xml file as input, performs some magic, then creates the desired output:
-<caption>Apache™ FOP from a User's Standpoint</caption>| Process | Result |
+<caption>Apache™ FOP from a User's Standpoint</caption>
+
+| Process | Result |
|---------|--------|
| . | XSL-FO document |
| FOP | Output: PDF, Postscript, Print, etc. |
@@ -37,7 +57,9 @@
With our design goals outlined, we'll now open the Black Box and look at the major processes inside. FOP has adopted the basic structure of the XSL-FO standard itself as a convenient model for the major processes in FOP. The Result in each row is the input for the next.
-<caption>FOP's Big Picture Design</caption>| Process | Process Result/Input for Next | Notes |
+<caption>FOP's Big Picture Design</caption>
+
+| Process | Process Result/Input for Next | Notes |
|---------|-------------------------------|-------|
| . | XSL-FO document | . |
| [Parsing](parsing.html) | [FO Tree](fotree.html) | . |
diff --git a/content/fop/dev/index.mdtext b/content/fop/dev/index.mdtext
index 4445d49..708fe97 100644
--- a/content/fop/dev/index.mdtext
+++ b/content/fop/dev/index.mdtext
@@ -9,6 +9,20 @@
For basic and user information on FOP, please visit the [Apache™ FOP homepage](http://xml.apache.org/fop).
+## Topics
+
+- [Design](design)
+- [Conventions](conventions.html)
+- [Doc](doc.html)
+- [Extensions](extensions.html)
+- [Faq](faq.html)
+- [Implement](implement.html)
+- [Release](release.html)
+- [Rtflib](rtflib.html)
+- [Svg](svg.html)
+- [Testing](testing.html)
+- [Tools](tools.html)
+
## Development { #lines}
The main development happens on "FOP Main".
diff --git a/content/fop/dev/svg.mdtext b/content/fop/dev/svg.mdtext
index 8e5c145..a2f17a0 100644
--- a/content/fop/dev/svg.mdtext
+++ b/content/fop/dev/svg.mdtext
@@ -9,7 +9,9 @@
These examples illustrate a number of issues relating to conversion to PDF:
-<caption>SVG to PDF examples</caption>| | svg file | png file | pdf result |
+<caption>SVG to PDF examples</caption>
+
+| | svg file | png file | pdf result |
|--|----------|----------|------------|
| images | [images.svg](svg/images.svg) | [images.png](svg/images.png) | [images.pdf](svg/images.pdf) |
| svg linking | [link.svg](svg/link.svg) | [link.png](svg/link.png) | [link.pdf](svg/link.pdf) |
@@ -21,7 +23,9 @@
<note>You will need Acrobat 5.0 to see transparency.</note>
-<caption>XSL:FO to PDF examples</caption>| | fo file | pdf result |
+<caption>XSL:FO to PDF examples</caption>
+
+| | fo file | pdf result |
|--|---------|------------|
| embedding svg | [embedding.fo](fo/embedding.fo) | [embedding.fo.pdf](fo/embedding.fo.pdf) |
diff --git a/content/fop/dev/testing.mdtext b/content/fop/dev/testing.mdtext
index 4dc33a8..b0752cf 100644
--- a/content/fop/dev/testing.mdtext
+++ b/content/fop/dev/testing.mdtext
@@ -5,7 +5,7 @@
## "Build" Testing { #build}
-Apache™ projects use an automated build tool called "jenkins" to create nightly builds from the SVN repository. Jenkins sends "nag" messages if the build fails. This can be considered a sort of basic test of the build process. To view the most recent logs of the jenkins builds:
+Apache™ projects use an automated build tool called "jenkins" to create nightly builds from the Git repository. Jenkins sends "nag" messages if the build fails. This can be considered a sort of basic test of the build process. To view the most recent logs of the jenkins builds:
- [Jenkins build for main](https://builds.apache.org/view/X/view/XmlGraphics/)
