feat: migrate blog posts from ipynb/md to qmd format

- Update conda/dev.yaml for quarto support
- Update .makim.yaml to render qmd to md in pipeline
- Add scripts/convert-blog-posts-to-qmd.py
- Update CONTRIBUTING.md with qmd-first workflow

Fixes #255

Author: Shivampal157

.makim.yaml

@@ -6,16 +6,27 @@ groups:
         backend: bash
         run: |
           mkdir -p build
-          # Directory to search for .ipynb files
+          # Directory to search for blog sources
           export SEARCH_DIR="pages/blog"
 
-          # Find all .ipynb files, excluding .ipynb_checkpoints,
-          # and convert them to Markdown named 'index.md'
+          # 1) Convert legacy .ipynb posts to Markdown (for now)
+          #    This keeps existing notebook-based posts working while we
+          #    migrate everything to Quarto.
           find "$SEARCH_DIR" -path "*/.ipynb_checkpoints/*" -prune -o -name \
             "*.ipynb" -exec sh -c \
             'jupyter nbconvert --to markdown --template=theme/custom-markdown.tpl --output-dir "$(dirname "$0")" --output "index" "$0"' {} \;
 
-          # remove console colors from md files
+          # 2) Convert .qmd blog posts to Markdown using Quarto
+          #    This allows us to use .qmd as the single canonical format
+          #    while still feeding Markdown into MkDocs.
+          if command -v quarto >/dev/null 2>&1; then
+            find "$SEARCH_DIR" -name "*.qmd" -exec sh -c \
+              'quarto render "$0" --to gfm --output "$(dirname "$0")/$(basename "$0" .qmd).md"' {} \;
+          else
+            echo "[WW] Quarto is not available on PATH; .qmd files will not be rendered."
+          fi
+
+          # 3) Remove console colors from generated md files
           find "$SEARCH_DIR" -name \
             "index.md" -exec sh -c \
             'cat "$(dirname "$0")/index.md" | python scripts/clean-output.py > "$(dirname "$0")/temp_index.md" && mv "$(dirname "$0")/temp_index.md" "$(dirname "$0")/index.md"' {} \;

CONTRIBUTING.md

@@ -42,24 +42,22 @@ dependencies and activate it.
 
 ### Creating a New Blog Post
 
-1. **Prepare the Blog Post:**
+1. **Prepare the Blog Post (Quarto-first workflow):**
 
    - Navigate to `pages/blog` and create a new folder with a slugified version
      of your blog post's title. Use
      [https://slugify.online/](https://slugify.online/) to generate a slug.
-   - Inside this folder, create your blog post file:
-     - For Markdown: `index.md`
-     - For Jupyter Notebooks: `index.ipynb` (use Jupyter Lab to create this
-       directly)
+   - Inside this folder, create your blog post as a **Quarto document**:
+     - `index.qmd`
 
 2. **Include a Header Image:**
    - Place a header image (either `header.png` or `header.jpg`) in your blog
      post folder. Make sure the image is under a free license.
 
 ### Metadata and Formatting
 
-- **Markdown Posts:** Add a metadata block at the beginning of your `index.md`
-  file:
+- **Quarto (`.qmd`) Posts:** Add a metadata block at the beginning of your
+  `index.qmd` file:
 
   ```markdown
   ---
@@ -75,8 +73,21 @@ dependencies and activate it.
   ---
   ```
 
-- **Jupyter Notebook Posts:** The first cell of your `index.ipynb` should be in
-  `raw` mode containing the same metadata as above.
+  The body of the file uses standard Markdown plus any Quarto features you
+  need (code chunks, figures, etc.). During the build, `makim pages.build`
+  will render `index.qmd` to `index.md` using Quarto so that MkDocs can
+  consume the generated Markdown.
+
+- **Legacy Jupyter Notebook Posts (optional / for migration only):**  
+  Existing posts may still be stored as `index.ipynb`. To migrate them to
+  Quarto, run:
+
+  ```bash
+  python scripts/convert-blog-posts-to-qmd.py
+  ```
+
+  This will generate corresponding `index.qmd` files, which you can then edit
+  directly. New posts should **not** be authored as notebooks; prefer `.qmd`.
 
 3. **Building and Viewing:**
    - If using a Jupyter Notebook, run `makim pages.build` to convert the
@@ -89,6 +100,8 @@ dependencies and activate it.
 Before submitting your blog post:
 
 - Ensure all files are added to your repository.
+- For new or migrated posts, confirm that `index.qmd` exists and that
+  `makim pages.build` successfully generates the corresponding `index.md`.
 - Submit a pull request to the main `opensciencelabs.github.io` repository for
   review.
 

conda/dev.yaml

@@ -7,3 +7,4 @@ dependencies:
   - pip
   - poetry
   - nodejs
+  

pages/blog/artbox-what-is-it-how-to-collaborete/index.qmd

@@ -0,0 +1,230 @@
+---
+title: "ArtBox: What is it and how to collaborate?"
+slug: artbox-what-is-it-how-to-collaborete
+date: 2024-04-02
+authors: ["Daniela Iglesias Rocabado"]
+tags: [open-source, art, python, multimedia processing]
+categories: [python]
+description: |
+  ArtBox is a tool set for handling multimedia files with a bunch of useful functions.
+thumbnail: "/header.jpg"
+template: "blog-post.html"
+---
+# How to use it?
+
+## What is ArtBox?
+
+ArtBox is a versatile tool set designed for efficient multimedia file handling, offering a range of valuable functions to enhance your multimedia processing experience.
+
+
+Key features of ArtBox include capabilities for text-to-audio conversion, YouTube video downloading, musical composition from notes, audio removal from video clips, audio extraction, and merging audio with video files. These functionalities position ArtBox as a pivotal tool for multimedia enthusiasts, content creators, and anyone in need of efficient multimedia processing solutions.
+
+
+### Installation
+
+ArtBox relies on certain dependencies that may not function optimally on your machine. To ensure a smooth installation process, it is recommended to create a conda/mamba environment and install ArtBox within that environment.
+
+```bash
+$ mamba create --name artbox "python>=3.8.1,<3.12" pygobject pip
+```
+
+The command is creating a conda environment named "artbox" with Python version 3.8.1 or later, and includes the pygobject and pip packages in the environment. This is useful for setting up an isolated environment for a specific project or application, ensuring compatibility and reproducibility of the software stack.
+
+```bash
+$ conda activate artbox
+```
+
+To prevent dependency conflicts, please install the numpy library using the following command:
+
+```bash
+$ pip install "numpy>=1.20"
+```
+
+The `conda activate artbox` command is used to activate the "artbox" conda environment, ensuring that subsequent commands or scripts run within this isolated environment. Activation modifies the system's `PATH` to prioritize the "artbox" environment, allowing for the use of specific Python versions and packages associated with the project, thus maintaining a clean and reproducible development or execution environment.
+
+
+```python
+$ !mamba install -q -y -c conda-forge pygobject pip
+```
+
+
+```python
+$ !pip install -q artbox
+```
+
+The `pip install artbox` command is used to install the Python package named "artbox" using the pip package manager. This command fetches the "artbox" package from the Python Package Index (PyPI) and installs it into the currently active Python environment. The `pip install` command is commonly used to add external packages or libraries to a Python environment, expanding its functionality for a particular project or application.
+
+## Examples of Artbox usage.
+For the following examples, create the a temporary folder for artbox:
+
+
+```python
+$ mkdir /tmp/artbox
+```
+
+### Convert text to audio
+
+By default, the `artbox voice` uses
+[`edge-tts`](https://pypi.org/project/edge-tts/) engine, but you can also
+specify [`gtts`](https://github.com/pndurette/gTTS) with the flag
+`--engine gtts`.
+
+
+```python
+$ echo "Are you ready to join Link and Zelda in fighting off this unprecedented threat to Hyrule?" > /tmp/artbox/text.md
+$ artbox speech from-text \
+    --title artbox \
+    --input-path /tmp/artbox/text.md \
+    --output-path /tmp/artbox/speech.mp3 \
+    --engine edge-tts
+```
+
+If you need to generate the audio for different language, you can use the flag
+`--lang`:
+
+
+```python
+$ echo "Bom dia, mundo!" > /tmp/artbox/text.md
+$ artbox speech from-text \
+    --title artbox \
+    --input-path /tmp/artbox/text.md \
+    --output-path /tmp/artbox/speech.mp3 \
+    --lang pt
+```
+
+If you are using `edge-tts` engine (the default one), you can also specify the
+locale for the language, for example:
+
+
+```python
+$ echo "Are you ready to join Link and Zelda in fighting off this unprecedented threat to Hyrule?" > /tmp/artbox/text.md
+$ artbox speech from-text \
+    --title artbox \
+    --input-path /tmp/artbox/text.md \
+    --output-path /tmp/artbox/speech.mp3 \
+    --engine edge-tts \
+    --lang en-IN
+```
+
+Additionally, if you are using edge-tts, you can specify `--rate`, `--volume`, and  `--pitch`, for example:
+
+
+```python
+$ echo "Do you want some coffee?" > /tmp/artbox/text.md
+$ artbox speech from-text \
+    --title artbox \
+    --input-path /tmp/artbox/text.md \
+    --output-path /tmp/artbox/speech.mp3 \
+    --engine edge-tts \
+    --lang en \
+    --rate +10% \
+    --volume -10% \
+    --pitch -5Hz
+```
+
+### Convert audio to text
+ArtBox uses `speechrecognition` to convert from audio to text. Currently, ArtBox just support the google engine.
+
+For this example, let's first create our audio:
+
+
+```python
+$ echo "Are you ready to join Link and Zelda in fighting off this unprecedented threat to Hyrule?" > /tmp/artbox/text.md
+$ artbox speech from-text \
+    --title artbox \
+    --input-path /tmp/artbox/text.md \
+    --output-path /tmp/artbox/speech.mp3 \
+    --engine edge-tts
+```
+
+Now we can convert it back to text:
+
+
+```python
+$ artbox speech to-text \
+    --input-path /tmp/artbox/speech.mp3 \
+    --output-path /tmp/artbox/text-from-speech.md \
+    --lang en
+```
+
+### Download a youtube video
+
+If you want to download videos from the youtube, you can use the following
+command:
+
+
+```python
+$ artbox youtube download \
+    --url https://www.youtube.com/watch?v=zw47_q9wbBE \
+    --output-path /tmp/artbox/
+```
+
+The command above downloads the video using a random resolution. If you want a specific resolution, use the flat `--resolution`:
+
+
+```python
+$ artbox youtube download \
+    --url https://www.youtube.com/watch?v=zw47_q9wbBE \
+    --output-path /tmp/artbox/ \
+    --resolution 360p
+```
+
+### Remove the audio from a video
+
+First, download the youtube video `https://www.youtube.com/watch?v=zw47_q9wbBE`, as explained before.
+
+Next, run the following command:
+
+
+```python
+$ artbox video remove-audio \
+  --input-path "/tmp/artbox/The Legend of Zelda Breath of the Wild - Nintendo Switch Presentation 2017 Trailer.mp4" \
+  --output-path /tmp/artbox/botw.mp4
+```
+
+### Extract the audio from a video
+
+First, download the youtube video `https://www.youtube.com/watch?v=zw47_q9wbBE`, 
+as explained before.
+
+Next, run the following command:
+
+
+```python
+$ artbox video extract-audio \
+  --input-path "/tmp/artbox/The Legend of Zelda Breath of the Wild - Nintendo Switch Presentation 2017 Trailer.mp4" \
+  --output-path /tmp/artbox/botw-audio.mp3
+```
+
+### Combine audio and video files
+
+First, execute the previous steps:
+
+- Download a youtube video
+- Remove the audio from a video
+- Extract the audio from a video
+
+Next, run the following command:
+
+
+```python
+$ artbox video combine-video-and-audio \
+  --video-path /tmp/artbox/botw.mp4 \
+  --audio-path /tmp/artbox/botw-audio.mp3 \
+  --output-path /tmp/artbox/botw-combined.mp4
+```
+
+## Additional dependencies
+
+If you want to use Python to play your audio files, you can install `playsound`:
+
+
+```python
+$ pip wheel --use-pep517 "playsound (==1.3.0)"
+```
+
+### Demo Video
+
+For a better explanation of the facilities and usage, please watch to the following video.
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/sITnMuZTNAw?si=goPrd2BhPxy7Fqku" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

pages/blog/avances-scicookie-grant-2024/index.qmd

@@ -0,0 +1,36 @@
+---
+title: "Implementaciones recientes en SciCookie gracias a la subvención de la PSF"
+slug: avances-scicookie-grant-2024
+date: 2024-06-21
+authors: ["Yurely Camacho"]
+tags: [psf, osl, scicookie, subvención, grant, comunidad, colaboración, desarrollo]
+categories: [código abierto, desarrollo de software, python]
+description: |
+  Descripción de las mejoras y tareas realizadas en SciCookie gracias a la subvención de la PSF.
+thumbnail: "/header.png"
+template: "blog-post.html"
+---
+
+Como mencionamos en el post anterior [SciCookie recibe nueva subvención de PSF para mejoras y crecimiento](https://opensciencelabs.org/blog/scicookie-recibe-nueva-subvencion-de-psf-para-mejoras-crecimiento/), en enero de 2024 la PSF aprobó nuestra solicitud de subvención. Esto nos ha permitido implementar una serie de mejoras significativas en SciCookie. A continuación, presentamos los avances y tareas realizadas.
+
+<!-- TEASER_END -->
+
+Se han incorporado nuevas opciones de herramientas a la plantilla, incluyendo los códigos de conducta (CoC) de Python (adaptado) y de NumFOCUS. También se ha añadido soporte para prettier como una opción de linter, proporcionando más flexibilidad a los usuarios.
+
+![Nuevas opciones de CoC](scr1.png)
+
+En cuanto a la estructura de la herramienta, se han realizado varias optimizaciones. Se implementó una opción condicional para las preguntas de uso de herramientas en el proyecto (`depends_on`) y se corrigió la indentación en algunos archivos de configuración para mejorar la legibilidad. Además, se unificaron estos archivos según las distintas opciones de sistemas de construcción (*build systems*) para evitar la repetición innecesaria de código y texto. También se creó un ejemplo para la opción de Interfaz de línea de comandos (CLI) como base del contenido de ese archivo.
+
+En el ámbito de la documentación, se ha automatizado el proceso de mover archivos de configuración a la raíz del proyecto, manteniendo una estructura ordenada. La selección del motor de documentación sphinx se ha dividido en `sphinx-rst` y `sphinx-md(myst)` para ofrecer opciones específicas. Se ha generado la documentación de la API para estas opciones, añadido `quarto` como un motor de documentación adicional, y se han incorporado distintos temas para cada motor de documentación disponible en la plantilla.
+
+![Nuevas opciones de documentación](scr2.png)
+
+Se ha iniciado comunicación con Leah Wasser, directora ejecutiva de pyOpenSci, quien ha revisado directamente el uso de SciCookie para las necesidades de pyOpenSci como plantilla de proyectos para recomendar a su comunidad. A partir de sus revisiones y sugerencias, se ha mejorado SciCookie para cumplir con sus principales expectativas. Leah también ha comenzado la creación de un perfil (conjunto de configuraciones por defecto) específico para pyOpenSci en [SciCookie](https://github.com/osl-incubator/scicookie/pull/273). Debido a sus prioridades y cronograma, este trabajo aún está en progreso.
+
+Con estos avances, SciCookie se presenta como una herramienta más completa y adaptable a diversas necesidades. Continuaremos trabajando para ofrecer mejoras a la comunidad de código abierto.
+
+Puedes consultar nuestro post [Collaborating and learning from SciCookie](https://opensciencelabs.org/blog/scicookie-collaborating-and-learning/) para más información sobre la herramienta.
+
+Mantente atento a futuras actualizaciones sobre SciCookie en próximos posts.
+
+Elementos gráficos de la portada fueron extraídos de [Job illustrations by Storyset](https://storyset.com/job)