For the wiki the only (current) format is plain text, which is the raw text
we see when editing a page. At first glance the usefulness of this feature may not be
apparent; however, there is one area that can really benefit.
Most applications ship with some sort of plain text documentation, whether it is
a version history, change log, or a basic 'read me' file. We can store and edit the
contents of these files within our wiki, gaining all the benefits the wiki provides but
we can still save them as plain text files when it is time to release.
Summary
In this chapter we have seen how Trac helps reduce the friction involved in creating
documentation. We discovered the basics of formatting text and looked at how to
edit and create new pages. In the next chapter we will continue our tour of Trac and
in particular will see how to use tickets to track our development tasks.
Tracking Our Tasks
Back in Chapter 1 we looked at the basics of task management and how it could help
us to manage our software development. There are many methods that can help us
track our tasks, but the good news is that what we need for developing software is
built right into Trac in the form of tickets.
Most developers, particularly those familiar with open-source projects, will be
familiar with the concept of bug trackers.
Pages:
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73