Migrate user-guide functionality to make it version controllable

[janhalen]

After at very short talk with @sobuos yesterday, we identified the wish to be able to version control the user-guide. This needs to be broken down into tasks offcource, lets use this issue as the top-level issue to communicate and break this initiative down into smaller bits..

When theres an actionable task identified, we can create these as sub-issues to this "umbrella" issue (or epic if we talk agile)

@andreasDroid: Any first takes on this?

[janhalen]

My general design idea would be something along the lines of:

1. Convert the text and illustrations into markdown and keep it in a repo in the os2fleetoptimiser organisation on GitHub,
2. Find a suitable static page generator, that is a balance between nice UI/UX and its ability to be automated and play nice with markdown.
3. Serve the content with GitHub pages from the selected repo.

Lots of options and possibilities, but lets break it further down.

[andreasDroid]

@janhalen , yes this can be handled in MD in a separate repository, but I guess that would also imply the task of maintaining the user guide is moved away from @sobuos ?

[janhalen]

Hmm yes, at least @sobuos would need to change the way the maintenance is done!

We could support this with training from our central resources in OS2.

[andreasDroid]

That's fine with me. We will move the user guide to another repo in this organisation.
I can make the conversion from the current format to MD.
Along the way, I guess it would be nice for @sobuos to be able to update it directly in the user guide repo.

[janhalen]

@andreasDroid & @sobuos

Ok.. we need to discuss what priority this has, I have made some preliminary research on a more user-frindly "CMS" like way to keep the guide updated while retaining the transparency and traceability of storing the data in a git repo.

If this is prioritized, lets discuss possible solutions with the goal of

1. Making it fast and easy to implement, and sufficiently easy to use
2. Discuss the potential for making it a template other os2 products can use.

If we implement the solution with sharability in mind from the start, less work will need to be done for making it generic via templating. Making it a template and donating it back to a central os2 repository, would make it likely that the central os2 secretariat can support the work financially.

But.. lets talk about it.

[sobuos]

@janhalen let's discuss it next time i'm in the office. That will be next week on March 26.