Add inital commit

.github/workflows/publish.yml

@@ -0,0 +1,33 @@
+on:
+  workflow_dispatch:
+  push:
+    branches: main
+
+name: Quarto Render and Deploy to Netlify
+
+
+
+jobs:
+  build-deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4 
+
+      - name: Set up Quarto
+        uses: quarto-dev/quarto-actions/setup@v2
+
+      - name: Render English
+        run: quarto render ${{ inputs.path }} --profile english
+
+      - name: Render French
+        run: quarto render ${{ inputs.path }} --profile french
+
+      - name: Publish
+        uses: netlify/actions/cli@master
+        with:
+          args: deploy --dir=_site
+        env:
+          NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}
+          NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
+

.gitignore

@@ -0,0 +1,171 @@
+# Project-specific
+data/*
+**/*.txt
+**/*.csv
+_site/en/*
+_site/fr/*
+.quarto/*
+pictures/webpictures
+*.zip
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+/.quarto/

README.md

@@ -0,0 +1 @@
+For more information on the construction of this example, see: https://marioangst.com/en/blog/posts/multi-language-quarto

_quarto-english.yml

@@ -0,0 +1,21 @@
+project:
+  title: "Example multilingual site"
+  output-dir: ./_site/en
+
+website:
+  navbar:
+    left:
+      - href: about.qmd
+        text: About
+      - href: faqs.qmd
+        text: FAQs
+  body-header: |
+    <button onclick="window.location = location.href.replace('/en/','/fr/');" class="btn"> Français </button>
+
+lang: en
+
+format:
+  html:
+    theme: pulse
+    css: styles.css
+    toc: true

_quarto-french.yml

@@ -0,0 +1,22 @@
+project:
+  title: "Exemple de site multilingue"
+  output-dir: ./_site/fr
+
+website:
+  navbar:
+    left:
+      - href: about.qmd
+        text: À propos de ce site
+      - href: faqs.qmd
+        text: Questions fréquentes
+  body-header: |
+    <button onclick="window.location = location.href.replace('/fr/','/en/');" class="btn"> English </button>
+
+        
+lang: fr
+
+format:
+  html:
+    theme: pulse
+    css: styles.css
+    toc: true

_quarto.yml

@@ -0,0 +1,9 @@
+project:
+  type: website
+
+profile:
+  default: english
+  group: [english, french]
+
+execute:
+  freeze: auto

_site/_redirects

@@ -0,0 +1 @@
+/              /en/about

about.qmd

@@ -0,0 +1,15 @@
+---
+format: html
+---
+
+:::{.content-hidden unless-profile="english"}
+This is an example of a site with two different languages, based on the guide at: https://marioangst.com/en/blog/posts/multi-language-quarto/. 
+
+This is not the only way to build a multilingual Quarto site. There is also now babelquarto: https://docs.ropensci.org/babelquarto/. And you can also simply implement it through the sidebar. 
+:::
+
+:::{.content-hidden unless-profile="french"}
+Ceci est un site qui utilise deux langues différentes. L'implémentation suit le guide disponible sur : https://marioangst.com/en/blog/posts/multi-lingual-quarto/. 
+
+Ce n'est pas la seule façon de créer un site Quarto multilingue. Il existe aussi babelquarto : https://docs.ropensci.org/babelquarto/. Et vous pouvez aussi simplement l'implémenter via la barre latérale.
+:::

faqs.qmd

@@ -0,0 +1,17 @@
+---
+format: html
+---
+
+:::{.content-hidden unless-profile="english"}
+**What is this website?**
+
+It's an example of a Quarto website with two languages.  
+
+:::
+
+:::{.content-hidden unless-profile="french"}
+**Qu'est-ce que ce site ?**
+
+C'est un exemple d'un site Quarto en deux langues.
+
+:::

styles.css

@@ -0,0 +1,15 @@
+/* css styles */
+.btn {
+    background-color: darkgrey;
+    border: none;
+    color: white;
+    padding: 12px 16px;
+    font-size: 16px;
+    margin-bottom: 4px;
+    cursor: pointer;
+    float: right;
+  }
+  .btn:hover {
+    background-color: #1a7bd9;
+    color: white;
+  }