If you have built a product or a study with Open Terms Archive, we would love to reference it in the public showcase!
This is a good way for you to gain more visibility, but it is also a very important contribution to Open Terms Archive. Doing so helps the Core team make connections between similar reusers and raise funds for maintaining the ecosystem alive and adding features to the software.
Referencing your reuse is fast and easy. Follow the instructions below and contact us if you encounter any problem!
Create a YAML file in the data/reuses/
folder, in snake case. For example, if your reuse is called “Research on the impact on human rights”, you would create a file named research-on-the-impact-on-human-rights.yml
.
Fill in that file with information following the template below:
title: # in both languages, 50 characters max
en: Research on the impact on human rights
fr: Recherche sur l'impact sur les droits humains # deepl.com can be used for automated translation
author: # in both languages, 50 characters max
en: Lab-LEX, University of Brest
fr: Lab-LEX, Université de Brest
description: # in both languages, 150 characters max
en: Research paper on the impact on human rights of the evolution of social media terms of use.
fr: Papier de recherche sur l'impact sur les droits de l’homme de l’évolution des conditions d’utilisation des réseaux sociaux. # deepl.com can be used for automated translation
website: https://grsomedia.wordpress.com/2023/10/10/publication-du-rapport-les-conditions-dutilisation-des-reseaux-sociaux-et-leur-impact-sur-les-droits-de-lhomme/ # prefer HTTPS over HTTP
Add an image in the PNG format to the assets/images/reuses/
folder, with the same name as the .yml
file. For example: research-on-the-impact-on-human-rights.png
.
The file should be in 529 × 310 pixels. To ensure fast loading and minimise the environmental impact of the Open Terms Archive website, the maximum allowed picture weight is 400 kB.
It is strongly recommended to use an image compression tool such as ImageOptim to reduce the image weight. Choosing “lossy” settings at 90% quality will usually yield over 50% compression gains.
If you need to use different illustrations depending on the language of the site, you can do so by adding a suffix to the name of your image file. Supported suffix values are en
and fr
and it must be preceded by a -
. For example: research-on-the-impact-on-human-rights-fr.png
.
Add an image in PNG format to the content/<current_section>/
folder where <current_section> is the folder in which the given page resides. Name the file with the sanitizedtitle of the page for which you want to configure the Open Graph image. The extension must be .png
(all lowercase).
We follow the GitHub Flow: all code contributions are submitted via a pull request towards the main
branch.
Opening a Pull Request means you want that code to be merged. If you want to only discuss it, send a link to your branch along with your questions through whichever communication channel you prefer.
All pull requests must be reviewed by at least one person who is not their original author.
To help reviewers, make sure to describe your pull request with a clear text explanation of your changes.
We strive to follow this recommendation to write our commit messages, which contains the following rules:
- Separate subject from body with a blank line.
- Limit the subject line to 50 characters.
- Capitalize the subject line.
- Do not end the subject line with a period.
- Use the imperative mood in the subject line.
- Wrap the body at 72 characters.
- Use the body to explain what and why vs. how.
We add this additional rule:
- Do not rely on GitHub issue reference numbers in commit messages, as we have no guarantee the host system and its autolinking will be stable in time. Make sure the context is self-explanatory. If an external reference is given, use its full URL.
Use BEM methodology to create reusable components and facilitate code sharing.
We acknowledge the efforts of our contributors by listing them on our website. Depending on whether the contributor has a GitHub account, the process for adding them differs slightly.
This is made possible by the use of the All Contributors bot, that enables adding a contributor with a comment on an issue or pull request, without writing code. To do this, please use the dedicated issue on this repository and write a comment with a command like:
@all-contributors please add @<username> for <contributions>
If the contributor does not have a GitHub account, the repository files will need to be manually updated:
-
Edit the
.all-contributorsrc
file at the root of this repository by adding the contributor's details in the following format within the contributors array:{ ..., "contributors": [ { "name": "<contributor_name>", "profile": "<contributor_website>", "contributions": ["<type_of_contribution>"] } ] }
-
Add a contributor's picture in the
assets/images/contributors/
folder which respects the following constraints:- Square format, 420x420 pixels.
- Optimized JPEG format (you can use tools like Image Optim for optimization).
- Filename should be a slugified version of the contributor's name with a
.jpg
extension (e.g.,contributor-name.jpg
).
To add more contribution types to an existing contributor, you can either edit the .all-contributorsrc
file directly or use the All Contributors bot by posting a comment in the format:
@all-contributors please add @<already_listed_contributor> for <new_contribution_type>