Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation #30

Open
l-arnold opened this issue Sep 10, 2015 · 7 comments
Open

Documentation #30

l-arnold opened this issue Sep 10, 2015 · 7 comments

Comments

@l-arnold
Copy link
Owner

There is a fair bit of information we should Impart.

Thinking that this may be a "moving" subject, can we have a WIKI?
I otherwise propse we build it into the Documentation system with in var/www here
(see port https://Server:12324)

@JedMeister
Copy link
Collaborator

Oops probably should have posted here...

Git repos have wikis too (as it seems you've already realised!); although IMO keeping it as a text file in the docs dir is better in the longer term...

FWIW Alon and I were talking about this the other day and thinking that we might move all appliance specific docs to a docs dir within each appliance's build code (like you have in Odoo). That way the docs can be tracked over time and relevant to each release. Currently the TurnKey appliance build code is tagged with the release version so generally speaking viewing the docs at that tag point will give the docs relevant to that version...

@l-arnold
Copy link
Owner Author

I have built first Drafts of 4 Documents in the Root Docs File now.
Should be enough to get folks started. Some Art would be nice but we are not writing HTML there.

@l-arnold
Copy link
Owner Author

I would like a "web driven" but easy to navigate system for "internal/external" documentation.
Best to use Dreamweaver? Should some sort of internal wiki (very lightweight) be integrated?

Thinking out loud as is too often the case.

@DocCyblade
Copy link
Collaborator

Thinking out loud as well... Is there not a apache2 module that would convert RST(Restructured Text) or MD(Mark Down) files to HTML? Like GIT does? This way you could just store them in text format MD or RST and have apache serve them up as is. No need to know HTML. The pages would be basic but really thats all you need any way.

@JedMeister
Copy link
Collaborator

Thinking out loud as well... Is there not a apache2 module that would convert RST(Restructured Text) or MD(Mark Down) files to HTML? Like GIT does? This way you could just store them in text format MD or RST and have apache serve them up as is. No need to know HTML. The pages would be basic but really thats all you need any way.

If there isn't there should be!

[update]
Not quite an Apache module but might be of value?:
http://linux.die.net/man/1/markdown

@l-arnold
Copy link
Owner Author

yeah. I was thinking that too. It seems thate perhaps Odoo supports it. For sure Git supports it.

I threw some in there and if people want to read them nice they can go to the GitHub home for the files. One solution for now.

@l-arnold
Copy link
Owner Author

Docs (somewhat Stranded) in "dev" branch until we get Dev Branch booting into Odoo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants