diff --git a/.gitignore b/.gitignore
index 492a39b..4c46da2 100644
--- a/.gitignore
+++ b/.gitignore
@@ -15,3 +15,4 @@ vendor
.env-secret
.fake
*_files/
+.vscode/
\ No newline at end of file
diff --git a/.vscode/ltex.dictionary.en-US.txt b/.vscode/ltex.dictionary.en-US.txt
deleted file mode 100644
index d08bd3f..0000000
--- a/.vscode/ltex.dictionary.en-US.txt
+++ /dev/null
@@ -1 +0,0 @@
-Computo
diff --git a/.vscode/settings.json b/.vscode/settings.json
deleted file mode 100644
index a88d1a3..0000000
--- a/.vscode/settings.json
+++ /dev/null
@@ -1,78 +0,0 @@
-{
- "latex-workshop.latex.recipes": [
- {
- "name": "dvilualatex -> dvisvgm",
- "tools": [
- "dvilualatex",
- "dvisvgm",
- "clean"
- ]
- },
- {
- "name": "pdflatex (latexmk)",
- "tools": [
- "latexmk"
- ]
- }
- ],
- "latex-workshop.latex.tools": [
- {
- "name": "latexmk",
- "command": "latexmk",
- "args": [
- "-synctex=1",
- "-interaction=nonstopmode",
- "-file-line-error",
- "--recorder",
- "--pdf",
- "--enable-installer",
- "--shell-escape",
- "-output-directory=%OUTDIR%",
- "%DOC%"
- ],
- "env": {}
- },
- {
- "name": "dvilualatex",
- "command": "latexmk",
- "args": [
- "-interaction=nonstopmode",
- "-file-line-error",
- "--recorder",
- "--dvilua",
- "--enable-installer",
- "--output-format=dvi",
- "--shell-escape",
- "-output-directory=%OUTDIR%",
- "%DOC%"
- ],
- "env": {}
- },
- {
- "name": "dvisvgm",
- "command": "dvisvgm",
- "args": [
- "--colornames",
- "--grad-overlap",
- "--optimize",
- "--exact",
- "--clipjoin",
- "--font-format=woff",
- "%DOCFILE%"
- ],
- "env": {}
- },
- {
- "name": "clean",
- "command": "latexmk",
- "args": [
- "-C",
- "--shell-escape",
- "-output-directory=%OUTDIR%",
- "%DOC%"
- ],
- "env": {}
- }
- ],
- "quarto.render.renderOnSave": true
-}
\ No newline at end of file
diff --git a/assets/img/cc-by.svg b/assets/img/cc-by.svg
new file mode 100644
index 0000000..b349817
--- /dev/null
+++ b/assets/img/cc-by.svg
@@ -0,0 +1,54 @@
+
+
+
\ No newline at end of file
diff --git a/assets/img/doa.jpg b/assets/img/doa.jpg
new file mode 100644
index 0000000..0778789
Binary files /dev/null and b/assets/img/doa.jpg differ
diff --git a/assets/img/logo-sh.png b/assets/img/logo-sh.png
new file mode 100644
index 0000000..75ed969
Binary files /dev/null and b/assets/img/logo-sh.png differ
diff --git a/assets/img/open_access_logo.png b/assets/img/open_access_logo.png
new file mode 100644
index 0000000..331dc2e
Binary files /dev/null and b/assets/img/open_access_logo.png differ
diff --git a/site/about.qmd b/site/about.qmd
index 07374f6..b7b3b83 100644
--- a/site/about.qmd
+++ b/site/about.qmd
@@ -7,7 +7,7 @@ page-layout: article
---
-## Aims and scope
+## Aims and scientific scope
Computo has been created in the context of a reproducibility crisis in
science, which calls for higher standards in the publication of
@@ -32,27 +32,47 @@ The journal welcomes the following types of contributions:
Prospective authors willing to know whether their contribution falls into the scope of Computo are encouraged to contact the editor at . Please make sure to include the title and abstract of your work in your pre-submission enquiry.
:::
-## An open access journal with reproducible contributions
-
-Computo is free for readers and authors.
-It is an open access journal which means that all content is
-freely available without charge to the user or his/her institution.
-Users are allowed to read, download, copy, distribute, print,
-search, or link to the full texts of the articles, or use
-them for any other lawful purpose, without asking prior permission
-from the publisher or the author. This is in accordance with the
-Budapest Open Access Initiative (BOAI) definition of open access.
-
-The reproducibility of numerical results is a necessary condition for
-publication in Computo. In particular, submissions must include all
-necessary data (e.g. via Zenodo repositories) and code. For
-contributions featuring the implementation of methods/algorithms, the
-quality of the provided code is assessed during the review process.
-We accept contributions in the form of notebooks (e.g. Rmarkdown, or
-Jupyter).
-
-The reviews are open, i.e. visible to any reader after acceptance of
-the contribution. Reviewers may choose to remain anonymous or not.
+## An open journal
+
+### "Diamond" open access {height="30px"}
+
+Computo is free for both readers and authors and adheres to the **Diamond Open Access model**: it is an open access journal, meaning that all content is freely available without charge to users or their institutions.
+
+### Content published under CC-BY license {height="30px"}
+
+Computo articles are published under a **[CC-BY 4.0 license](https://creativecommons.org/licenses/by/4.0/)**: Computo readers are allowed to download, copy, distribute, print, search, or link to the full texts of the articles, or use them for any other lawful purpose, without asking prior permission from the publisher or the author. The only requirement is to credit the authors, indicate the sources, and specify whether any modifications have been made.
+
+The CC-BY license is therefore indicated on the published and readable versions of the articles, as well as in the git repositories distributing the source code of the articles and enabling the reproducibility of the analyses.
+
+The source code of each article is based on various software and programs whose licenses (typically MIT, GPL, etc.) are specified where the code for this software is distributed. The authors commit to using content that complies with the CC-BY license of the articles and, more generally, to promoting the dissemination of open-source software, crediting the authors and contributors.
+
+This is in accordance with the [Budapest Open Access Initiative (BOAI)](https://en.wikipedia.org/wiki/Budapest_Open_Access_Initiative) definition of open access, as well as the [DOAJ](https://en.wikipedia.org/wiki/Directory_of_Open_Access_Journals)’s definition of open access, to whom we have submitted an application.
+
+### Open reviews
+
+The reviews and the discussions they sparked between authors and their peers are open, i.e. visible to any reader after acceptance of the contribution. These reviews are published either as issues in the git repository associated with the publication, or directly available for consultation on [Open review](https://openreview.net/group?id=Computo).
+
+Note that Reviewers may choose to remain anonymous or not.
+
+## Reproducibility Policy
+
+### Numerical Reproducibility
+
+The issue of reproducibility is at the heart of the Computo project. Therefore, the reproducibility of numerical results is a necessary condition for publication in Computo. To this end, we rely on a combination of notebooks, literate programming, virtual environments, and continuous integration.
+
+Submissions must also include all necessary data (e.g., via Zenodo repositories) and code. For contributions featuring the implementation of methods or algorithms, the quality of the provided code is assessed during the review process.
+
+For interested readers, [more details are provided on this page](../blog/2023-07-04-what-reproducibility/index.html) about our expectations regarding reproducibility.
+
+### Medium- to Long-Term Preservation
+
+To ensure that all published information remains accessible and usable over time:
+
+- we tag every published article, including its virtual environment;
+- we regularly run the workflow of each published article to check its medium- and long-term reproducibility;
+- we archive all git repositories of published articles on [Software Heritage](https://www.softwareheritage.org/) {height="20px"}.
+
+We would also like to emphasize that publishing an article in Computo in no way prevents authors from depositing a version of their article (e.g., PDF) in an institutional repository (e.g., HAL or arXiv), which helps to preserve and disseminate scientific work and is fully in line with the journal's policy and spirit.
## Plagiarism policy