From: Vincent Balat <vincent.balat@univ-paris-diderot.fr>
To: caml-list@inria.fr
Cc: Wojciech Meyer <wojciech.meyer@gmail.com>
Subject: Re: [Caml-list] OCaml wiki
Date: Fri, 21 Dec 2012 17:20:36 +0100 [thread overview]
Message-ID: <201212211720.37298.vincent.balat@univ-paris-diderot.fr> (raw)
In-Reply-To: <wf38z0iacc.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3648 bytes --]
Hi,
We have been using our home-made (Eliom based) wiki for years on
http://ocsigen.org and http://www.pps.univ-paris-diderot.fr and it is probably
a good candidate for ocaml.org. The project is called Ocsimore (see
http://ocsigen.org/ocsimore ).
You can test it on page:
https://ocsigen.org/sandboxwiki/
Log in with user "test", password "test".
and see the manual for the syntax here:
https://ocsigen.org/ocsimore/dev/manual/wiki
This wiki is somewhat different from all others, but has very interesting
features that may be useful for ocaml.org:
* you can mix static pages and wiki pages: if the static page is present, it
will be sent, otherwise the wiki page is displayed. It is possible for example
to keep the current web site and add progressively new pages using the wiki.
* you can create several wikis on the website, corresponding to different
rights. For example http://ocsigen.org/devarea/ is a wiki restricted to
ocsigen's developers.
* There is no default page container, and no default stylesheet: each wiki
has its own container, common to every page of the wiki, that is itself
written using wiki syntax. Editing the container requires special rights.
* CSS are also edited online (by the users who have the right for this)
* You can create CSS for the whole wiki or specific CSS for some pages
* The base component of the wiki is not the page, but the "wikibox"
Each page (and each wikibox) can contain several wikiboxes, and a wikibox may
appear on several pages
* Each wikibox can be given specific rights (read/write/see history/change
CSS...)
* Each wikibox may itself be a container. For example if you want a menu
common to several pages.
* The wiki syntax is following the wikicreole standard, with some additions.
The goal is to have most the possibilities offered by HTML. All the pages from
the websites mentioned above are written with this syntax.
* It is possible to write extensions to the wiki syntax. For exemple we have
<<code language="ocaml"| ... >> to display OCaml with syntax highlighting.
Ocsimore also has a forum module (for messages/comments) but it is still beta.
Ocsimore is conceived to be extensible and very customisable (even if it
requires to understand a complex piece of code). It has very powerful right
managements.
We never announced/released Ocsimore yet because there are still a lot of work
to do to improve user friendliness. But things improved a lot in the past
months and OCaml developers (and ocaml.org admins) can probably cope with it).
We will release version 1 soon.
Vincent [for the Ocsigen team]
> Hi,
>
> These days ocaml.org is a great resource and starting point for the
> community and people interested in learning OCaml. It would be great
> however if we have a collective wiki for OCaml too. Not being here at
> any rate competitive and just complementary.
>
> It could cover:
> - using core toolchain
> - tooling like Oasis, OPAM, ocamlfind, ocamlbuild etc.
> - type system tricks
> - small projects with good code examples
> - tools settings, emacs & vim configuration snippets
> etc.
>
> it should be searchable, and fairly centralised.
>
> What kind of wiki engine we would like to use?
>
> I'd just opt either for oddmuse, mediawiki perhaps with some movement
> towards custom one based on Ocsigen and Eliom, but here I don't have any
> strong opinions, feel free to propose anything else.
>
> Separate issue is storage and server etc., I'd happily organise/discuss
> these things, once we know the details :-)
>
> I'm open for any ideas and people joining up with the effort.
>
> Thanks,
>
> -Wojciech
[-- Attachment #2: Type: text/html, Size: 15420 bytes --]
next prev parent reply other threads:[~2012-12-21 16:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 23:15 Wojciech Meyer
2012-12-20 23:19 ` Malcolm Matalka
2012-12-20 23:22 ` Anil Madhavapeddy
2012-12-20 23:31 ` Benedikt Meurer
2012-12-20 23:34 ` Anil Madhavapeddy
2012-12-20 23:38 ` Malcolm Matalka
2012-12-20 23:50 ` Wojciech Meyer
2012-12-21 2:49 ` Ashish Agarwal
2012-12-21 8:37 ` Philippe Veber
2012-12-21 9:13 ` Fermin Reig
2012-12-21 9:39 ` Philippe Veber
2012-12-21 13:05 ` Wojciech Meyer
2012-12-21 13:31 ` Adrien
2012-12-21 16:39 ` Ashish Agarwal
2012-12-21 15:33 ` Siraaj Khandkar
2012-12-21 17:52 ` Siraaj Khandkar
2012-12-21 13:00 ` Hezekiah M. Carty
2012-12-21 1:31 ` [Caml-list] OCaml search into libraries for ocaml.org Francois Berenger
2012-12-21 2:57 ` Ashish Agarwal
2012-12-21 7:34 ` forum
2012-12-21 15:31 ` Leo White
2012-12-21 19:57 ` AW: " Gerd Stolpmann
2012-12-21 20:22 ` Török Edwin
2012-12-21 20:34 ` AW: " Gerd Stolpmann
2012-12-21 20:37 ` Edgar Friendly
2012-12-21 20:41 ` AW: " Gerd Stolpmann
2012-12-21 20:48 ` Library install standards (was: Re: AW: AW: AW: [Caml-list] OCaml search into libraries for ocaml.org) Edgar Friendly
2012-12-21 20:59 ` [Caml-list] Re: Library install standards Török Edwin
2012-12-21 23:47 ` AW: " Gerd Stolpmann
2012-12-21 16:20 ` Vincent Balat [this message]
2012-12-21 16:45 ` [Caml-list] OCaml wiki Ashish Agarwal
2012-12-23 14:53 ` Vincent Balat
2012-12-25 1:14 ` Ashish Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201212211720.37298.vincent.balat@univ-paris-diderot.fr \
--to=vincent.balat@univ-paris-diderot.fr \
--cc=caml-list@inria.fr \
--cc=wojciech.meyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).