typical software project consists of source code
that is stored in revision control and compiled with
`make` and `gcc`, an ikiwiki-based wiki is stored as
-human editable source in a revision control system,
+human-editable source in a revision control system,
and built into HTML using ikiwiki.
Ikiwiki uses your revision control system to track
HTML files from source wiki files. This example builds
a wiki for an imaginary software project. The wiki
source files used in this example are available in the
-[[examples/softwaresite]] section of ikiwiki's documentation.
+[[examples/softwaresite|examples/softwaresite]] section
+of ikiwiki's documentation.
wiki$ ls
Makefile bugs.mdwn doc/ download.mdwn news/
grouping, tags are better for categorizing issues
as bugs, wishlist items, security issues, patches,
or whatever other categories are useful. Bugs can
-be tagged "moreinfo", "done" "unreproducible",
-or "moreinfo", etc, to document different stages of
+be tagged "moreinfo", "done", "unreproducible",
+etc, to document different stages of
their lifecycle. A developer can take ownership of a
bug by tagging it with something like "owner/Joey".