GitXplorerGitXplorer
f

koding-wiki

public
6 stars
1 forks
0 issues

Commits

List of commits on branch master.
Unverified
eeee159821fb976b2f27d47d4256e84d64e8472e

Update index.md

ffatih committed 12 years ago
Unverified
39017758f461d5bcc324ab8cce1045fdbb2836c0

Merge pull request #1 from gbataille/master

ffatih committed 12 years ago
Unverified
1758c641758006db4a92669cc79d9a391060f635

Fixing the erroneous usage of the selectOptions parameters for

ggbataille committed 12 years ago
Unverified
c2a3acf5e521eba3d83be8652b9271c9b6af986b

Fix styling

ffatih committed 12 years ago
Unverified
c0dfe30255f0c6a0816830b5906718d3ed31334f

style improvements

ffatih committed 12 years ago
Unverified
3c48df33862d10b0ec20d679f0ea0174b609db6f

Fix italics

ffatih committed 12 years ago

README

The README file for this repository.

Koding source docs

This repo is using markdoc and the static files are hosted at: arslan.koding.com/docs

Please read further if you want to contribute or deploy the wiki on your local machine.

How to contribute and deploy Koding Wiki?

This wiki is based on simple, markdown powered engine called markdoc. The best part about markdoc is that there are no db or any fancy input forms. Just bare plain markdown files.

## How to create(deploy) the Wiki?

We use markdoc to generate static files(install it via pip install markdoc ). These are useful if we want to serve them. But you can always serve the whole wiki from your own machine with the following command(in the koding-wiki folder):

markdoc build 
markdoc serve

Now you can read all the docs on you localhost via http://127.0.0.1:8008

Rembember that all our doc files are markdown files. It means you can just dig around and open them your self.

## How do I contribute?

It's very easy. Just add a markdown file(i.e. foo.md) to a related folder (like client or backend). After adding the file modify the related index file (i.e. backend/index.md) and add a new line with the new file name:

* [new foo document](/backend/foo.md)

Or just examine the wiki folder. You'll see that it has an simple structue.

## Why do we change the index.md everytime we add a new file?

Because in the future there will be lots of files. It's very easy to miss or lost in those files. This is common problem amongst all wiki platforms.

Thus the easiest way to handle is to just add a simple line to the related sections index.md file. Markdoc is can generate an automatic list of all files, however its ugly and doesn't provide much info. The best way is to a maintain seperate index (home) files for each section.

## I have more questions...

Sent an email to fatih at koding dot com