I’m starting this thread to have a conversation about what we need for documentation in OH 2. My goals with this conversation is to brainstorm and identify what needs to be done, what can be started now verses waiting for OH 2 to mature some more, and perhaps create a high level outline. If this co…

[image] Kai: No, that’s not it! ESH is a framework and OH2 a solution built with it. You can read my blog where I tried to explain it. Well I clearly didn’t go back on the blog far enough. Thanks for the link. So basically ESH is much (but not all) of what we would call “core” on OH 1. And wh…

I like it. I would suggest that focus be initially placed on bulleted points in a tree like structure. We can then build out the sections and points over time and provide more detail, context, etc., as well as periodically change the structure as feedback is integrated.

Ok, so we all agree that we like it - now it only must be done :slightly_smiling: With more on more functionality being added to OH2, I think it is now really time to get some better documentation out of the door (and to aggregate it to a single place). Is any of you volunteering to work on the in…

I so desperately want to take the lead on this but realistically, if I did, I would not be able to keep up with any sort release deadline. It would be far better if someone who can devote the time necessary to devote to it would take the lead. This isn’t something I can do from my phone during five …

I am also not able to keep up with any deadline and therefore we hardly ever set any deadlines :slightly_smiling: - I prefer to have things moving forward instead of creating schedules, which then cannot be met because nobody eventually does the work. Hence moving slowly is definitely better than s…

[image] rlkoshak: However, if no one steps up, I will do what I can. I think from the time I have known you in this forum you would simply be the best for this task … the explanations you are giving in your posts are always extremely valuable and even more important: everybody is able to unde…

Note that the discussion is currently not about the content, but the technical infrastructure, which indeed cannot be done in 5minute breaks on a phone… I agree with you that @rikoshak is actually the better fit for working on the documentation content.

I’m actually a developer and am comfortable setting up the infrastructure as well so if noone else steps up I have the skills to do that as well.

I didn’t mean to say that you are lacking the skills for the technical parts! Just wanted to express how important you will be for the content side of things afterwards as well :sunglasses:

[image] rlkoshak: However, if no one steps up, I will do what I can. It just won’t be fast. Jekyll does indeed look to be pretty easy to work with, particularly if you are used to a SW dev workflow. How are things going? :slightly_smiling:

openHAB Community

OH 2 Documentation

Setup, Configuration and Use Runtime

Kai (Kai Kreuzer) June 1, 2016, 3:38pm 26

FTR: I close this topic as it is continued here.