Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Understanding the extended Markdown some outliners use

Open
#223 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
markdown
Domain
tooling

Research direction

Start by finding an outliner that supports OPML import and uses Markdown as its native format. Import the linked states.opml example into that app, save or export it as Markdown, and post the result in this issue; completion means documenting how the content and outline structure are represented.

Written by the indexing model from the issue text.

Description

I understand that some outliners use an extended form of Markdown to save their outlines.

I'm interested in knowing exactly what this format is, because -- if it's easy to support as an export and import format in Drummer, then I want to do it. But first we have to understand what it is.

A good first step would be to do this:

  1. Find an outliner that supports OPML import, whose native file format is Markdown.

  2. Import our states.opml example into this app.

  3. Save/export it as Markdown.

  4. Post it here as a comment.

Why use states.opml? Because we know what's "content" and what's structure in the example. When I get an example where the text is about the format it's an example of, it gets confusing quickly. I know "Montana" and "Chicago" aren't part of the file structure. See how that works?

Everyone but silo-builders wins if our products interop.

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.