<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://jdsalaro.com</id>
  <title>Jayson Salazar Rodriguez | @jdsalaro | Blog - Posts tagged sphinx</title>
  <updated>2025-12-26T16:36:53.745568+00:00</updated>
  <link href="https://jdsalaro.com"/>
  <link href="https://jdsalaro.com/blog/tag/sphinx/atom.xml" rel="self"/>
  <generator uri="https://ablog.readthedocs.io/" version="0.11.4.post1">ABlog</generator>
  <subtitle>@jdsalaro</subtitle>
  <entry>
    <id>https://jdsalaro.com/cheatsheet/sphinx-myst-markdown/</id>
    <title>MySt and Markdown for Sphinx Cheatsheet</title>
    <updated>2023-07-12T00:00:00+00:00</updated>
    <author>
      <name>Jayson Salazar Rodriguez</name>
    </author>
    <content type="html">&lt;p class="ablog-post-excerpt"&gt;&lt;p&gt;I’ve never been a fan of Re-StructuredText, but most importantly I’m new to MySt, which leads to a lot of googling and painstaking trial-and-error while writing. Although my preferred references are the &lt;a class="reference external" href="https://jupyterbook.org/en/stable/reference/cheatsheet.html"&gt;Jupyter Book MyST Cheatsheet&lt;/a&gt;, the &lt;a class="reference external" href="https://sphinx-book-theme.readthedocs.io/en/stable"&gt;Sphinx Book Theme Documentation&lt;/a&gt;, and the &lt;a class="reference external" href="https://myst-parser.readthedocs.io/en/latest/syntax"&gt;MyST Parser Reference&lt;/a&gt;, they are way too extensive, sometimes incorrect, and I don’t really use every directive or variant thereof. Therefore, I’ll use this post to gather the bits of the syntax and snippets I use the most.&lt;/p&gt;
&lt;/p&gt;

    &lt;script type="text/x-thebe-config"&gt;
    {
        requestKernel: true,
        binderOptions: {
            repo: "binder-examples/jupyter-stacks-datascience",
            ref: "master",
        },
        codeMirrorConfig: {
            theme: "abcdef",
            mode: "python"
        },
        kernelOptions: {
            name: "python3",
            path: "./blog/tag"
        },
        predefinedOutput: true
    }
    &lt;/script&gt;
    &lt;script&gt;kernelName = 'python3'&lt;/script&gt;</content>
    <link href="https://jdsalaro.com/cheatsheet/sphinx-myst-markdown/" rel="alternate"/>
    <summary>I’ve never been a fan of Re-StructuredText, but most importantly I’m new to MySt, which leads to a lot of googling and painstaking trial-and-error while writing. Although my preferred references are the Jupyter Book MyST Cheatsheet, the Sphinx Book Theme Documentation, and the MyST Parser Reference, they are way too extensive, sometimes incorrect, and I don’t really use every directive or variant thereof. Therefore, I’ll use this post to gather the bits of the syntax and snippets I use the most.</summary>
    <category term="blogging" label="blogging"/>
    <category term="highlight" label="highlight"/>
    <category term="myst" label="myst"/>
    <category term="sphinx" label="sphinx"/>
    <category term="technology" label="technology"/>
    <published>2023-07-12T00:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://jdsalaro.com/howto/sphinx-load-environment-pickle/</id>
    <title>Load Sphinx environment.pickle and List all Labels</title>
    <updated>2023-07-10T00:00:00+00:00</updated>
    <author>
      <name>Jayson Salazar Rodriguez</name>
    </author>
    <content type="html">&lt;p class="ablog-post-excerpt"&gt;&lt;p&gt;In order to come up with a reliable and standardized way of referring to document sections and document it in &lt;a class="reference internal" href="../../../cheatsheet/sphinx-myst-markdown/"&gt;&lt;span class="doc"&gt;MySt and Markdown for Sphinx Cheatsheet&lt;/span&gt;&lt;/a&gt;, I went down a pretty deep rabbit hole of Sphinx label manipulations.&lt;/p&gt;
&lt;/p&gt;

    &lt;script type="text/x-thebe-config"&gt;
    {
        requestKernel: true,
        binderOptions: {
            repo: "binder-examples/jupyter-stacks-datascience",
            ref: "master",
        },
        codeMirrorConfig: {
            theme: "abcdef",
            mode: "python"
        },
        kernelOptions: {
            name: "python3",
            path: "./blog/tag"
        },
        predefinedOutput: true
    }
    &lt;/script&gt;
    &lt;script&gt;kernelName = 'python3'&lt;/script&gt;</content>
    <link href="https://jdsalaro.com/howto/sphinx-load-environment-pickle/" rel="alternate"/>
    <summary>In order to come up with a reliable and standardized way of referring to document sections and document it in /cheatsheet/sphinx-myst-markdown, I went down a pretty deep rabbit hole of Sphinx label manipulations.</summary>
    <category term="sphinx" label="sphinx"/>
    <published>2023-07-10T00:00:00+00:00</published>
  </entry>
</feed>
