Skip to content

use GitHub Flavored Markdown #526

Open
@SethTisue

Description

@SethTisue

over at https://github.com/scala/scala.github.com/blob/master/_config.yml we have:

markdown: kramdown
kramdown:
  input: GFM

it would be great to standardize on the same thing here. for multiple reasons:

  1. GitHub Flavored Markdown is IMO what our contributors are likeliest to expect
  2. it's confusing and error-prone for contributors anytime the two sites have technical differences (and makes it harder to move content between the two sites)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions