See ocsigen.org/src/site_ocsimore.ml

See ocsigen.org/src/site_ocsimore.ml

Use some continuous integration service to:

• Generate HTML files
• Update and push other repositories' gh-page branches

• Links
• code
• concept
• table of content
• etc.

In the current state of the project, extensions are compiled into ohow.byte alongwith the compiler.
Thus, if some HOW user needs to add a custom wikicréole extension, they will need to edit the sources of the project and re-compile it.

It would be better if instead, the user could use an opam library, say How_ext which provides the necessary OCaml interfaces and parsers for building an extension. The user would then compile its extension alone, and when they run ohow, the binary dynamically links to itself the user extension (probably a .cmo) and the magic happens...

Btw we could externalize the Ocsigen-specific extensions out of this project.

Example: <a_api text="text" version="dev" | fun

Should it by default:

• refer to the current project?
• refer to the current subproject when used inside an api wiki?
• trigger an error?
• etc.

Rename files, too?
EDIT: not just intro -> index

• Detect dead links
• Copy images to the output directory

It's very difficult to work on pages and see the result locally.

See ocsigen.org/src/site_ocsimore.ml

See ocsigen.org/src/site_ocsimore.ml

We should read them from the opam file, instead of duplicating them in .merlin and _tags.

Mimic ocsigen.org/src/site_doc_menu.eliom

It didn't typecheck :/

Requires the <<content>> extension tag to be implemented.

http://ocsigen.org/howto

manpage and README

We could support arbitrary function calls (stored as templates in separate files, by default in the root directory), evaluating arguments by rendering them first.

In $DATA/concept.wiki:

<<div class="concept"| __<<title>>__: <<content>> >>

In eliom/manual/intro.wiki:

<<concept name="Multi-tier"|Multi-tier programming allows a lot of fancy things.>>

<<a_api | fun>> must be equivalent to <<a_api subproject="default_subproject" | fun>>.

See ocsigen.org/src/site_ocsimore.ml

Hello @ghuysmans ,
I see only the last version of each project. Is it on purpose?
Is it easy to change this to have all the versions?
Thanks!
Vincent

On GitHub Pages: https://ocsigen.github.io/project/version/manual/wiki
Local: file:///home/path/to/project/version/manual/wiki.html

Client-side? Js_of_ocaml?