> For the complete documentation index, see [llms.txt](https://stephanosterburg.gitbook.io/scrapbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephanosterburg.gitbook.io/scrapbook/thought/blog/markdown.md).

# markdown

## Making text collapsible:

```
# A collapsible section with markdown
<details>
  <summary>Click to expand!</summary>
  
  ## Heading
  1. A numbered
  2. list
     * With some
     * Sub bullets
</details>

```

[**https://github.com/github/jekyll-commonmark-ghpages#installation**](https://github.com/github/jekyll-commonmark-ghpages#installation)

**Important:** to get it to work on GitHub Pages we need to add the following to the `Gemfile`:

```
group :jekyll_plugins do
  gem 'jekyll-commonmark-ghpages'
end
```

and modify your `_config.yml` to use **CommonMarkGhPages** as your Markdown converter:

```
markdown: CommonMarkGhPages
```

This processor is currently in testing for use in GitHub Pages.

To specify extensions and options for use in converting Markdown to HTML, supply options to the Markdown converter:

```
commonmark:
  options: ["SMART", "FOOTNOTES"]
  extensions: ["strikethrough", "autolink", "table", "tagfi
```

[CommonMark](https://commonmark.org/): One of our major goals is to [strongly specify Markdown](https://spec.commonmark.org/), and to eliminate the many old inconsistencies and ambiguities that made using Markdown so difficult.

**NOTE**: Unfortunately this brakes some of the latex and some html implementation in the blog. Maybe over Xmas.

{% embed url="<https://spec.commonmark.org/0.29/>" %}

## &#x20;Open link in new tab

```
<a href="https://stackoverflow.com" target="_blank">stackoverflow</a>
```

## Testing

{% embed url="<https://johnmacfarlane.net/babelmark2/>" %}

{% embed url="<https://dillinger.io/>" %}

{% embed url="<https://stackedit.io/app#>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://stephanosterburg.gitbook.io/scrapbook/thought/blog/markdown.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.