First step before replacing documentation by a markdown version.

[groud]

These are the first sources for the documentation. Writen with Markdown and compiled with Mkdocs.

A preview :

[Seneral]

Hey @groud, will you update this with the other pages? It looks amazing btw:)

[groud]

Well, I can do that. But is it really useful if we plan to put the whole documentation into the wiki repository ? I am still waiting for a decision from @Baste-RainGames about giving us right on this wiki repository (I have no idea about how to do that, btw :/ )

[Seneral]

We can do both since we can use MK for both, right? Additionally a standalone online documentation makes a good impression I think;) Also I could create the wiki pages, but only @Baste-RainGames can elect contributors, so if you could respond that'd be great;) I'm currently trying to install mkDocs

[groud]

If we can the put all MD files into the wiki repository with the compilation files (the mkdocs.yml file), I though we would keep only the compiled (i.e. html) files into the gh-pages branch and into the docs folder.

[Seneral]

Yup, sounds about right. On a side note, I seem unable to install mkDocs :( When the installation notes refer to a command (MKDocs, pip, ...) which console do I use? The normal cmd reports 'python' does not exist even when having it installed and the python console doesn't accept these commands either. I'm not that into python to get this :D EDIT: Ok I got why it didn't register python, I unselected to add it to the path on installation:)

[groud]

Normally it should work if you use cmd, but you can use powershell instead. If it does not work with 'python', try 'python.exe' instead.

Check your python version, the 3.5 one comes with pip, while the 2.* don't.

Pip commands should also be executed into cmd/powershell shells, not into the python's one.

[Seneral]

Yeah it does work now, just missed to add python to the path variable when installing. Only realized this as I tried the older 2.7.11 which actually explained what that does, I simply unchecked it in the first install because I though I didn't need it :'D It is looking really pretty. Though the theme your using is deprecated, it says... If you don't mind I'll experiment with it a bit:)

[groud]

Well, do not hesitate to checkout my branch, create a new branch from there, push your changes into your own fork, then create a pull request into my branch. ^^

[Seneral]

Yep good idea:) The changes are not yet committed so we should leave this open until we're happy with the page so far (of course it's a ongoing WIP) For me that means only the style to go;) Do you have any ideas/improvements?

[Seneral]

Maybe we can structure it a bit better, including subpages, etc. Not today though, atleast for me:)

[Seneral]

Also, any idea how we can remove the duplicate page link 'Node Editor Framework' and 'Home' to the index page?

[groud]

I merged the pull request. The check failed comes from travisCl, I was testing this module that can perform building tests when a pull request is made. :)

Actually I did not check the content yet, I do not know the Framework enough to have pertinent comments on the documentation ^^

[groud]

Double link removed. :)

[Seneral]

Oh misunderstood your previous post

Also, that was the reason I asked, removing this won't compile;)

[groud]

@Seneral , lol, this worked fine with another project. I'll fix this

[Seneral]

Sorry it will compile but the index.md page is completely left out.

[groud]

Well, I more or less fixed this... ^^

[Seneral]

Really good idea! That'll do:)

[Seneral]

Wait: this also hides the search field :O It is also the first element in a list:(

[Seneral]

Can you exclude classes from css? Then excluding 'navbar-right' should do it

[Seneral]

This css works:

ul.nav.navbar-nav:not(.navbar-right) li:first-child {
    display: none;
}

[groud]

Done.

[Seneral]

Cool