Skip to content

Pivot to Markdown as universal file format #84

@erikhofer

Description

@erikhofer

Advantages:

  • Items can be browsed on Sites like GitHub and GitLab as is
  • Editing of files outside of scope42 can be done with any Markdown editor
  • markdownlint can be applied easily
  • Enables Markdown processing with things like remark

Disadvantages:

  • Parsing is harder to implement and propably needs to become more tolerant
  • Files can not be processed with simple YAML tooling anymore, it basically can only be done with our libraries, if you need the model
  • [Proposal] Improve file names #29 would become impossible because it would break links
  • This is not sufficient for exporting. The Markdown needs to be processed if things like scripting are used.

Additional considerations

  • We may want to stick with YAML for a 1.0.0 and decide on this later. An automatic migration is trivial because we need Model->Markdown serializer anyways.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions