• Separate content by audience
• Provide cross-linking where beneficial
• Provide global searching (and searching within current book?)

Example: See Sitka's Evergreen Training Manual for staff-focused documentation.

QUESTION: Should these be two separate books?

1. See Evergreen Developer Overview
2. Evergreen Community (where to get help)
3. Software Installation
4. Migrating from a legacy system
5. Migrating Patron Data
6. System Configuration and Customization
7. NEW SECTION: System Administration from the shell (how to restart clark, run helper scripts, etc.)
   1. See Support Scripts
8. Creating a new skin
9. TPAC Configuration and Customization
10. Authentication Proxy
11. SIP administration
12. Apache administration (phonelist.pm, rewrite, access handler)
13. NEW SECTION: Reports for Sys Admins
    1. See Adding Data Sources to Reporter
14. NEW SECTION: Understanding Permissions (naming conventions, troubleshooting tips, working with permission groups)
    1. See Describing your people
    2. See User and Group Permissions
15. NEW SECTION: Optimizing your server
    1. See Optimizing the performance of your Evergreen server
    2. Ask sys admins for more recommendations (e.g. for Apache, memcached, OS)
16. Developer Resources
17. Handy SQL queries (taken from random_magic_spells)
18. The db schema

1. Evergreen Community (where to get help)
2. Installing the Staff Client
3. System Administration From the Staff Client: overview
4. Describing your organization
5. Describing your people
6. Library Settings Editor
7. Acquisitions Administration
8. Booking Administration
9. Cataloging Administration
   1. Authorities Administration
   2. Z39.50 Administration
10. Circulation Administration
    1. Borrowing items: who, what, for how long
    2. Hard due dates
    3. Accepting Credit Card Payments
       1. Stripe
       2. NEW SECTION: Paypal/Authorize.net/etc.
11. Holds Administration
12. OPAC Customization
13. Reports Module

1. Evergreen Community (where to get help)
2. Using the Staff Client
3. Circulation
4. Reports (as relates to their needs)
5. Using the Public Access Catalog (as relates to their workflows, and for helping patrons)

1. Evergreen Community (where to get help)
2. Using the Staff Client
3. Cataloging
4. Reports (as relates to their needs)
5. Using the Public Access Catalog (as relates to their workflows)

1. Evergreen Community (where to get help)
2. Using the Staff Client
3. Acquisitions
4. Reports (as relates to their needs)
5. Using the Public Access Catalog (as relates to their workflows)

1. Evergreen Community (where to get help)
2. Using the Staff Client
3. Serials
4. Reports (as relates to their needs)
5. Using the Public Access Catalog (as relates to their workflows)

- Where do details about permissions live? Stuff like this section is gold for troubleshooting permissions issues, but would it live in the cataloger's manual with other documentation of batch import? In the staff sysadmin's manual in a little tiny section of its own?