Skip to main content
Version: 1.8.1

How to write the Website Content

In this page, we will explain all about the convention we use to write and generate the website content and the wiki content. Since the release of GAMA 1.7, with the new GAMA website, we have two contents:

  • The wiki content is hosted in github, witch directly interpret the markdown format of the files to display them in a proper way. This wiki, since it is a wiki, can be edited by any user. It is then, in constant changes.
  • The website content is the content of the real GAMA website. It is a verified and fixed version of the documentation (usually a re-generation of the website content is done when there is a new release of the software)



To generate automatically the documentation, the GAMA Git version is required. See Install Git version for more details.

Among all the GAMA plugins, only one is related to documentation generation:

  • msi.gama.documentation: it contains some useful java scripts to help you to write a correct documentation.

In addition, the folder containing the wiki files is required. In the GitHub architecture, the wiki documentation is stored in a separate Git repository A local clone of this repository should thus be created:

  1. Open the Git perspective:
  • Windows > Open Perspective > Other...
  • Choose Git
  1. Click on "Clone a Git repository"
  • In Source Git repository window:
    • Fill in the URI label with:
    • Other fields will be automatically filled in.
  • In Branch Selection windows,
    • check the master branch
    • Next
  • In Local Destination windows,
    • Choose the directory in which the gama Git repository has been cloned
    • Everything else should be unchecked
    • Finish
  1. In the Git perspective and the Git Repositories view, Right-Click on "Working Directory" inside the repository, and choose "Import projects"
  • In the Select a wizard to use for importing projects window:
    • "Import existing projects" should be checked
    • "Working Directory" should be selected
  • In Import Projects window:
    • Uncheck ยซ Search for nested project ยป
    • Check the project
    • Finish
  1. Go back to the Java perspective: a plugin should have been added. tree structureโ€‹

The "" plugin contains all the wiki content, and almost all the website content. It contains a folder content which contains the following folders:

  • Tutorials
    • LearnGAMLStepByStep: contains the linear documentation to learn about the concepts of GAML
    • Recipes: contains short pieces of documentation answering a specific problematic
    • Tutorials: contains applicative tutorials
  • References
    • ModelLibrary: contains the model library (only present in the website)
    • PlatformDocumentation: contains the documentation dealing with how to use the platform
    • GAMLReferences: contains GAML references
    • PluginDocumentation: contains the documentation of the additional plugins
  • Community
    • Projects: contains a presentation of the projects where GAMA is involved (only present in the website)
    • Training: contains a presentation of the training sessions organized by the GAMA team (only present in the website)
  • WikiOnly: contains the content only present in the wiki, and not in the website
    • DevelopingExtensions: contains explanations about how to extend the platform
  • resources: contains all the additional resources needed (images, pdf...)

For the rest of this document, the highest level of tree structure ("Tutorials"/"References"/"Community"/"WikiOnly") will be named as tabs. The level just under will be named as sections, and the level under will be named as sub-section. All this content is written using the markdown format. All the images resources are included in the resources/images folder. They are actually under different sub-folders. From the markdown page, you can call the resource with the relative path resource/images/sub_folder/image_name.png. If a section/sub-section contains one of several sub-division, then those sub-divisions will be stored in a folder with the name of the corresponding section/sub-section, and this section/sub-section folder will be associated with a markdown file with the same name (indeed, a section/sub-section has its own page). If a section/sub-section has no sub-division, then this section/sub-section is simply defined with a markdown file containing the content wanted.


Notice that there is some content which is present only in the wiki (the "WikiOnly" content), some content present only in the website (the model library, most of the community content...). In fact, the wiki tree structure is determined by the file Sidebar, while the website tree structure is determined by the file _WebsiteTreeStructure.

Good practices when writing markdown filesโ€‹


Each markdown files has to start with a title in the markdown format (like # title). This is this title which will be displayed in the tree structure of the website.

Even if the repository how have a more complexe tree structure, you don't have to (and you must not !) speficy the relative or absolute path to the target page, just naming the page will work : [text_displayed](the_name_of_the_md_file)

As already said in the previous paragraph, images have to be in an "resources/images/folder_name" folder next to your md file, so that you can write the relative path more easily.

Insert Metadatasโ€‹

Metadatas in content files are written as comments, with the following syntax:

[//]: # (name_of_the_medatada|value_of_the_metadata)

Medatadas are not displayed in the wiki and the website content. For the website generation, metadatas are used in order to build the database, most of all to manage the search engine, and the learning graph.

Here is the list of metadata we use in the content files:

  • keyword : will write an invisible anchor in this exact place in the website. When the user will do a research about this word, he can access directly to this anchor.

  • startConcept/endConcept : used to delimit a concept. The value of those two metadatas is the name of the concept. All the concepts are listed in the file "DependencyGraph", in the content folder in your wiki repository.


The value of the keyword has to have this structure : keyword_category_keyword_name (indeed, several keywords can have the same name ! The type of the keyword has to be specified). Here is the list of the several keyword categories : concept, operator, statement, species, architecture, type, constant and skill. Example of metadata : [//]: # (keyword|concept_3D), or [//]: # (keyword|operator_int).


The value of the keyword have to be one of the values defined in the file learningConcept.xml.

Notice that a concept in the meaning of keyword is not the same as a concept (or learning concept) in the learning graph! Please read the part concerning the database to learn more about it.

Website generation workflowโ€‹

This part is not implemented yet, it is under construction.


The gama.documentation pluginโ€‹

This plugin is used to generate GAML documentation automatically in the markdown format, and copy paste the content to the wiki folder. The plugin is also used to generate the model library in the markdown format, with the source code, a quick description, and an image (screenshot). In the same time, the plugin generates a html page (an "abstract") and put it directly in the model folder (in order to be loaded directly from GAMA).

The documentation plugin contains also 2 other scripts which helps to create content:


The learningGraphDatabaseGenerator script is used to generate the "nodesDatabase.js" file, which is read to visualize the learning graph. This script needs the "learningGraph.xml" file as input. Each learning concepts has an id, a name, a very short description, a position (position in x and y in %, between 0 and 1. This value is then multiplied by the coeff in the learningGraphDatabaseGenerator), and a list of prerequisite learning concepts. A category of learning concept (also defined in the learningGraph.xml file) has an id, a position (position in x and y), a position for the hallow (position in x and y of the big circle displayed when a category is selected), a size for the hallow, a color, a name, and the list of learningConcept associated.


The modelLibraryGenerator script is used to generate all the markdown files of the model library. This script

  • Parse all the models of the model library, and build an "input" xml file for a headless execution (this file is deleted at the end of the execution).
    • By default, this will ask to execute all the experiments for each model, and take a screenshot of the 10th cycle for each display.
    • You can change this default behavior by changing the file "modelScreenshot.xml", in the wiki repo (see description below)
  • Execute the headless
  • Copy-paste all the generated images in the write folder, with the write names.
  • Browse a second time all the models, build the md file, including the screenshot computed from the headless execution, and analyzing the header of each model to extract the title, author and tags. Each md files respects the following format : path_from_model_with_underscore_instead_of_slash_without_strange_char + ".md". (ex : "Features/3D/3D Visualization/models/3D camera and trajectories.gaml" becomes "".)

Format of the xml file to "tune up" the screenshot generation :

<experiment id="name_of_the_file_without_extention"+" "+"model_name"+" "+"experiment_name">
<display name="display_name_1" cycle_number="number_of_the_cycle_for_the_screenshot"/>
<display name="display_name_2" cycle_number="number_of_the_cycle_for_the_screenshot"/>


The repositoryโ€‹

This repository contains in on hand the content auto generated by the documentation plugin, and in the other hand a handmade content. All the content is in the markdown format, organized through a specific tree structure, sometime containing metadatas.

The website repositoryโ€‹

This repository contains:

  • A copy of the content of the wiki repo (copy/pasted manually to freeze a specific commit of the wiki)
  • A Database management system
  • A script used to interpret the metadatas from the content, in order to load the database
  • Some pages which are not in the wiki repo, and some heavy resources (such as videos)

Website databaseโ€‹



A keyword is a keyword that can be used for search, either manually (the user enters the wanted keyword in the searchbar of the website) or automatically (through the search tab in the navigation panel) A keyword in attached with a category (among the following names : concept, type, operator, statement, species, architecture, constant, action, attribute, skill, facet).

  • A keyword that is a concept can be linked with other keywords (ex : the keyword "BDI" will be linked with the keywords "eval_when", "get_priority"...)
  • A keyword that is a facet is linked to a statement or a species keyword (ex : the keyword "torus" will be linked with the keyword "global").
  • A keyword that is an action or an attribute is linked either to a skill keyword (if it is actually an action or an attribute of a skill), an architecture keyword (if it is an action or a behavior of an architecture), or a species keyword (if it is a built-in action or attribute).
  • A keyword that is a statement can be linked to an architecture.

A keyword is composed of:

  • id (unique id)
  • name (the word which is searched by the user)
  • idCategory (id of the category)

A cagegory is composed of:

  • id (unique id)
  • name (the name of the category)



Another database is used to join an alias to an existing keyword. Ex: the word "alias" will be changed as "die".

An alias is composed of:

  • id (unique id)
  • name (name of the alias. ex : "kill")
  • attachedKeywordName (name of the keyword attached. ex : "die")

Note that an alias does not know the id of the keyword, but only the name of the attached keyword(s). Indeed, the alias "integer" will give the keyword name "int", but several keywords correspond to the keyword name "int" (it can be the type "int", or the cast operator "int")



A webpage can be either a page of the model library, a page of the gaml reference, or an other page of the documentation.

A webpage is composed of:

  • id (unique id)
  • name (name of the webpage)
  • webpageCategory (the name of the category of the webpage, a value among modelPage, docPage, gamlRefPage_).

The tables webpage and keyword are linked through an association table. This association table contains also an anchor (an anchor has a unique value) to the wanted page.


Note that only the keywords which have the category concept, species, type, operator, skill and constant can be attached to a webpage.

The keywords which have the category action, attribute and facet forward to the attached keyword.

The keywords which have the category statement are attached to a webpage only if they are not attached to another keyword. If they are attached to another keyword (an architecture keyword), then the statement keyword forward to the attached keyword.


LearningConcept is used to build the learning graph (notice that a "learning concept" and a "keyword concept" is not the same thing !)

A LearningConcept is composed with:

  • id (unique id)
  • name (name of the learning concept)

A LearningConcept is linked to a webpage through an association table. This table is composed also with two anchors that are used to delimit the position of the learning concept in a page (the beginning position and the ending position).

A LearningConcept can be associated to other LearningConcepts through an association table, used to spefify the "prerequisite concepts".


Loading the Databaseโ€‹

The database is loaded from a gathering of independent files. Some of those files are handmade written, other are generated automatically.

Role of the documentation generation script in the construction of the databaseโ€‹

As explained in the explication of the documentation generation pages, the documentation generation script is used to generate the gaml references and the model library pages (in the markdown format with metadatas), but also to build two files category.txt and keyword.xml.

The file category.txt is a very simple file, listing the different keyword categories. This file will be used to build the Category table.

Format of the file:

concept, type, statement, species, architecture, operator, skill, constant, action, attribute, facet

The file keyword.xml is an xml file that contains all the possible keywords (all except some keywords written manually directly in the documentation pages). The GAML words can be found directly using the code of GAMA. The concept words can be found using the code of GAMA (thanks to the tag "category") and also by using the tags in the header of the model files. This xml file will be used to build the Keyword and the AssociationKeywordCategory tables.

Format of the file:

<keyword id:keywordname_keywordcategory>

Note that:

  • The list associatedKeywordList contains only one element for the facet keywords, one of no element for the action or attribute keywords (none when the action/attribute is a built-in), several or no elements for the concept keywords, and none for the other type of keywords.

  • The id is built with the value of the attribute "name" and with the value of the attribute "category" for every keywords except the statement, facet, action and attribute keywords, which need also the value of the associatedKeyword linked. Ex : the id of the facet "torus" will be "facet_torus_statement_global".

Preparation of the repository before the generation of the databaseโ€‹

After the generation of the markdown content in the wiki repository, two other files have to be built manually: the files alias.txt and learningConcept.xml.

The alias.txt file contains all the connexions between alias and keyword name. It will be used to build the Alias table.

Format of the file :


The learningConcept.xml file is used to list the learning concepts, and to connect them to their prerequisite concepts. It will be used to build the LearningConcept and the AssociationLearningConcept tables.

Format of the file :

<learningConcept id:learningConceptName>

Note that the value of the attribute "name" can be used as an unique id.

Role of the website content generation script in the construction of the databaseโ€‹

After copy-paste the content to the website folder, a script is used to build the database and to generate website content.

The Category, Alias, LearningConcept and AssociationLearningConcept tables are loaded easily from the files category.txt, alias.txt, and learningConcept.xml.

The Keyword and AssociationKeywordCategory tables are loaded from the keyword.xml file. Note that those two tables are not entirely loaded yet, because other keywords can be presents in the header of other files.

The markdown files are converted one by one into html format.

  • When a metadata startConcept/endConcept is found (syntax : [//]: # (beginAnchor|name_of_learning_concept)), the metadata is replaced with an anchor in the page (with an unique id), and the AssociationWebpageConcept table is updated.
  • When a metadata keyword is found (syntax : [//]: # (keyword|name_of_keyword_category_name_of_keyword)), the metadata is replaced with an anchor in the page (with an unique id), and the AssociationWebpageKeyword table is updated (the Keyword and AssociationKeywordCategory are updated if the keyword does not exist yet in the table).

Manage concepts keywordsโ€‹

ALL the concepts must be declared in the "IConcept" java class. If you want to add a new concept, please check before if your the concept you want to add cannot be remplaced by one of the existing concept. If it is the case, you can add your word as if it was an alias, pointing to the existing concept. Note that all the alias are listed in the alias.txt file. If you realy think that the concept has to be added, please add it to the IConcept file, and also to (one or several) of the lists CONCEPTS_NOT_FOR_GAML_REF, CONCEPTS_NOT_FOR_MODEL_LIBRARY, CONCEPTS_DEDICATED_TO_SYNTAX in the ConceptManager class if needed.

Most of the keywords of the website (used for the search) are managed automatically. But the "concepts" keywords have to be (partially) hand-made managed. You can add the concepts with 3 differents methods :

In the Documentationโ€‹

"Documentation" here designs all the content manually written in the wiki. All those pages can contain "concepts" through the metadata format :

[//]: # (keyword|concept_name_of_concept)

You can either :

  • place those metadatas anywhere in the page if you want to point directly in this part of the page if the user makes a search
  • place those metadatas above the title : doing this, the "automatic search" (left navigation panel) will be made with this concept. You have to be really sure this concept is the main concept of the page to place it there.

In the Model libraryโ€‹

Directly from the gaml files of the model library, you can add the concept you want through the "Tags" in the header of the model.

Exemple :

* Name: 3D Display model of differents shapes and a special Object
* Author:
* Description: Model presenting a 3D display of differents shapes (pyramid, cone, cylinder, sphere and a teapot object) to represent the same agents but with
* different aspects. Five experiments are possible, one for each of the shapes presented previously. In each experiment, the agents move to create a big circle but flee
* from their closest neighbor.
* Tags: 3d, shape, neighbors

Note that if you don't want this model to have a page in the website, you can name it starting with the character _.

In the GAML Referencesโ€‹

You can add a concept to a gaml word by using the syntax concept = { IConcept.MY_CONCEPT }.

Exemple :

@operator(value = "flip",
concept = { IConcept.RANDOM }

The following text has been automatically generated from "mainCheckConcepts"

__ last update : 2020/06/19 14:26:08

List of concepts to use for model library (except Syntax):

3d, agent_location, agent_movement, algorithm, architecture, asc, batch, bdi, camera, chart, clustering, color, communication, comodel, comparison, csv, database, date, dem, dgs, diffusion, dxf, edge, elevation, equation, fipa, fsm, geometry, gis, gml, graph, graph_weight, graphic, grid, gui, headless, hydrology, image, inheritance, inspector, light, load_file, math, mirror, monitor, multi_criteria, multi_level, multi_simulation, neighbors, network, nil, node, obj, obstacle, osm, overlay, physics_engine, r, raster, regression, save_file, scheduler, serialize, shape, shapefile, shortest_path, skill, sound, spatial_computation, spatial_relation, spatial_transformation, sport, statistic, svg, system, task_based, test, text, texture, tif, topology, transport, txt, xml

List of concepts to use exclusively in Syntax models:

arithmetic, attribute, cast, condition, container, filter, list, logical, loop, map, matrix, string, ternary

List of concepts to use for GAML worlds:

3d, action, agent_location, agent_movement, algorithm, architecture, arithmetic, asc, attribute, batch, bdi, behavior, camera, cast, chart, clustering, color, communication, comodel, comparison, condition, constant, container, csv, cycle, database, date, dem, dgs, diffusion, dimension, display, dxf, edge, elevation, equation, experiment, file, filter, fipa, fsm, geometry, gis, gml, graph, graph_weight, graphic, graphic_unit, grid, gui, headless, hydrology, image, inspector, length_unit, light, list, load_file, logical, loop, map, math, matrix, mirror, monitor, multi_criteria, multi_level, multi_simulation, neighbors, network, nil, node, obj, obstacle, optimization, osm, overlay, parameter, physics_engine, point, r, random, random_operator, raster, regression, save_file, scheduler, serialize, shape, shapefile, shortest_path, skill, sound, spatial_computation, spatial_relation, spatial_transformation, species, statistic, string, surface_unit, svg, system, task_based, ternary, test, text, texture, tif, time, time_unit, topology, transport, txt, type, volume_unit, weight_unit, xml

Concept namein Docin GAML Refin Model LibTOTAL