Ahhh, cmake and doxygen. The perfect combo to bitch about life for a
whole day...
-Edit (project)/buildtools/Cmake/DefinePackage.cmake, and add your
+Edit (project)/tools/cmake/DefinePackage.cmake, and add your
newly added page to the DOC_SOURCES. And bitch about these damn tools.
Don't forget to commit your page, so that you can get some git fun to
\section inside_doxygen_image Adding an image to the documentation
If you need to run a command (like fig2dev) to generate your image,
-edit buildtools/Cmake/GenerateDoc.cmake and add your command to the
+edit tools/cmake/GenerateDoc.cmake and add your command to the
doc target (grep for fig2dev in the file to see
where exactly). Don't forget to add the source of your image to the
archive somehow. You can add it to the list DOC_FIG of
-buildtools/Cmake/DefinePackage.cmake.
+tools/cmake/DefinePackage.cmake.
If your image is ready to use, put your png in doc/webcruft, and
register it to cmake by adding it to the DOC_IMG list of file
-buildtools/Cmake/DefinePackage.cmake so that it lands in the archive
+tools/cmake/DefinePackage.cmake so that it lands in the archive
distribution. It will also be copied automatically to the documentation.
\section inside_doxygen_website Working on the website
-Actually, the website is very different from doxygen. It uses a tool
-called jekyll to turn markup-formated text into nice static web pages.
-Jekyll is less annoying than doxygen since it's written in a scripting
-language: you can dynamically add (or change) parts of the tool to
-make it fit your needs. Get the sources, and start improving the
-website now (there is a README in the repo with more details).
+Our website is generated/exported via [orgmode](http://www.orgmode.org), a tool that we use to facilitate our reproducible research.
+
+Get the sources, and start improving the
+website now! (There is a README in the repo with more details,
+but it might be outdated. Contact us if you really want to help.)
@verbatim
git clone git://scm.gforge.inria.fr/simgrid/website.git
