CompEvol
BEAST 2 Manual
Snippet from a comment on issue #95 where this proposal was made:
"It would be really helpful to have an actual official BEAST 2 manual. I can't believe I only just thought of this. It summarizes the vague feeling of discontent I've always had with the documentation: there's heaps of it, and it's nicely written, but it's scattered across multiple blog posts and web pages so it's very difficult to navigate. Having a single source for the documentation of the core aspects of BEAST would be awesome. (The book is brilliant, IMO the value there is all of the biological and mathematical context it contains. What I'm talking about is a much shorter technical document/webpage organized according to subject matter.)"
This reminds me of https://xkcd.com/927/.
The beast2.org site could be the go-to site, and would have been if it did not use a system that discourages contribution (because it keeps on mangling content). That is one of the reasons information gets shattered across tutorials, user group posts, package web pages, the taming the beast site, etc. Adding a 'manual' just adds another place to search for info (and point of maintenance). What would be the scope of the manual that would not fit a page of the beast2.org site (which by now is out of date in places and could benefit from some reorganisation)?
Manual = Organised, complete and without redundancy. The act of creating something that has a contents and a beginning and end is rather important to create a useful resource.
On 23/02/2017, at 8:17 AM, Remco Bouckaert [email protected] wrote:
This reminds me of https://xkcd.com/927/.
The beast2.org site could be the go-to site, and would have been if it did not use a system that discourages contribution (because it keeps on mangling content). That is one of the reasons information gets shattered across tutorials, user group posts, package web pages, the taming the beast site, etc. Adding a 'manual' just adds another place to search for info (and point of maintenance). What would be the scope of the manual that would not fit a page of the beast2.org site (which by now is out of date in places and could benefit from some reorganisation)?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I share your general concern, Remco. The goal would be to reorganize the existing information on the website into a structured and indexed form (aka a manual), rather than to provide yet another source of documentation. (I'd want this to be part of the solution rather than the problem!)