Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Understanding the extended Markdown some outliners use

未关闭
#223 11 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
markdown
领域
tooling

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
HTML
星标
134
派生
10
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

scripting/Scripting-News 的其他 Issue

查看 scripting/Scripting-News 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。