There is a private repository and a public website.

A repository is a word usually used in a computer program writing context.

The definition on is : A repository is where you store your code and make changes to it. Your changes are tracked with version control.

For us, the repository is both the place where we store contents and information, but also where the programs to navigate through the contents are written.

In the repository, there are folders and files.

This is how the organisation looks like: gazette/
├── contexts/
│   ├── actors/
│   │  ├── atelier-cartographique/
│   │  └── …
│   ├── lists/
│   ├── methodology/
│   └── technologies/
├── lexicon/
├── multilingual-encounters/
├── programs/
└── sources/

In the folders, there are text files, mostly written in Markdown format, because its syntax is both convenient for us (as human beings) to read, but can also be processed easily by computer programs.

We have written some programs, stored in the programs folder, to build html pages based on some resources (markdown text files, images) from the other folders.
For example, this page is generated using the content of a text file, stored in the folder technologies/repository/

The resulting html is then styled using less or css declarations.

The repository, and all its versions, is stored on a physical server, from which we rent a space on to our neighbours and system infrastructure providers, tactic asbl.

We use git to track the changes. This allow us to work on the files from different computers. It also allows us to track all the changes that were made, and version them, but also to create new branches of development.

Il y avait quelque chose sur les graphes orientés acycliques, mais je ne me souviens plus comment faire le lien.

Et aussi cette manière de mettre ensemble plein de fils pour faire une corde.

Some words about how these web pages were made. How it all starts from folders and files, organized in a way that made sense for us.