[Koha-bugs] [Bug 26977] Update Koha Documentation to use absolute paths instead of relative ones

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26977

--- Comment #2 from Rex Barkdoll <rex at nicic.gov> ---
I understand, but I think what I'm asking for is to add more detailed
recommendations to the documentation. 

Throughout my (short) experience with Koha, there's been what feels like
disconnect between people who have been using Koha for a long time and people
who are new to it, by that I mean people who just know where stuff is based on
experience versus people looking for these things the first time. Admittedly,
this is an anecdotal assertion based on my experience and what I've identified
with in other users' posts on forums, but I feel like I have seen enough people
with growing pains to leverage the point.

I believe good documentation is written toward first-timers, and preferably is
written in crayon with neon signs pointing the way. Working at a library which
services technophobic users, most of our tutorials and guides are written so an
elementary school kid could follow along. Even so, our advanced users
appreciate that it's hard for them to miss anything and we've tried to
over-document to clear up any vague parts before they become and issue.

With Koha, I've had to go to multiple sources and 3rd-party documentation (like
Koha geek) to get answers and tutorials to things that really should have been
in the official documentation/manual (initial setup, importing a previous koha
database, setting up cron tasks, tutorials on XSLR modifications, detailed
guides on building reports, etc). What if Koha geek or other third-party
resources go away one day?

By no means should the documentation say "this is always where this file will
be found," but you could say:

"Depending on your installation method and OS, this files will most likely be
found in /usr/share/koha/... OR in /etc/koha/... You can also perform a simple
find search if they are not located in either of these directories."

I'm also not asking for the monumental task of changing every URL, just adding
a recommended location at the top of each section to point someone in the right
direction.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.