Skip to content

Markdown guide #6581

@mike-j-thomas

Description

@mike-j-thomas

Goal

Have a simple guide for Fleet-flavoured Markdown that lives in the handbook.

How

  • Create a separate file, markdown.md, in the Digital Experience folder of the handbook (awaiting successful merge of Website: Add support for multiple levels in the handbook #6524 before this can be created).
  • Compile a list of all Markdown syntax that is supported by fleetdm.com and document it in the handbook. Ask @eashaw if you are unsure about any of the syntax:

Suggested structure for the guide:

  • Headers
    • h1
    • h2
    • h3
    • h4
  • Emphasis
    • Bold
    • Italic
    • Bold italic
    • Strikethrough
  • Lists
    • Ordered
    • Unordered
    • Sub-list items
  • Links
    • Inline links
    • Relative links
    • mailto links (good to have, but have a note saying that we NEVER use it. We don't want our email getting spammed.)
  • Image
    • Image syntax
    • Image caption (* in the line directly under the image. See this example)
  • Code and syntax highlighting
    • Inline code
    • Code block
    • Code block with syntax highlighting
  • Tables
  • Notes & Tips (we use blockquote ">" syntax for this)
  • An actual blockquote (ask @eashaw if we support this)
  • Horizontal rule (---)
  • YouTube videos
  • Podcast (Check our podcast posts. It's just a code snippet in an iframe, copy/pasted from Apple's podcast page).

Examples

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
https://about.gitlab.com/handbook/markdown-guide/
https://www.markdownguide.org/basic-syntax/

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions