Skip to content
vic

ooc-lang/the-ooc-language

:blue_book: The definitive manual on the ooc programming language

ooc-lang/the-ooc-language.json
{
"createdAt": "2010-08-08T22:21:14Z",
"defaultBranch": "master",
"description": ":blue_book: The definitive manual on the ooc programming language",
"fullName": "ooc-lang/the-ooc-language",
"homepage": "http://ooc-lang.org/",
"language": "Makefile",
"name": "the-ooc-language",
"pushedAt": "2014-12-20T17:44:44Z",
"stargazersCount": 49,
"topics": [],
"updatedAt": "2024-11-24T16:05:51Z",
"url": "https://github.com/ooc-lang/the-ooc-language"
}

404: Not Found# the ooc language

In progress, send feedback to amos@lockfree.ch and mention ‘ooc’ in the subject.

Thanks a lot =)

Amos Wenger aka @nddrylliog

Easy,

$ make

will generate a single-page, HTML version of the documentation.

Then,

$ make publish

will switch to the gh-pages branch, commit the modifications and push the commits to origin (which may be your forked repository).

  1. Figure out how to order the sections.
  2. Merge branch ‘mdoc’ into ‘master’ in a way that will let us generate both versions of the documentation with a single Makefile.
  3. Profit !