feature wishlists

[jonschlinkert]

from jonschlinkert/remarked#12 (comment)

• Citations
• Definition lists Add support for description lists markedjs/marked#254
• Footnotes
• Abbreviations https://michelf.ca/projects/php-markdown/extra/#abbr
• To-do lists: To do lists markedjs/marked#107
• Macros (see Consideration of a "Macro" standard for Markdown. remarked#9)
  • blocks (with open/close marks or open + indent content)
  • inline (no convention about format).
• Source maps? Feature Request: Source maps commonmark/commonmark-spec#57
• Typographical features: Implement markdown extra features markedjs/marked#27. Macros should be able to handle these

---

upd by @puzrin:

No questions! No discussions! Only feature name + link to details. This issue is used by devs to keep archtecture in sync with possible needs. If you wish to discuss any feature - just create new a ticket.

[puzrin]

• Footnotes
• Macros (see Consideration of a "Macro" standard for Markdown. remarked#9)
  • blocks (with open/close marks or open + indent content)
  • inline (no convention about format).
• HTML (inline only - tags will be autoclosed at the end of block, if no closing pair found)

[puzrin]

• Source maps? Feature Request: Source maps commonmark/commonmark-spec#57

[puzrin]

• table of content (toc)

[howardroark]

Would it make sense to make a ticket for each feature request with a proper label and make this ticket a milestone? Or at least add a link next to each "todo"?

I'd love to talk about things like Footnotes (which I feel is an excellent idea).

[puzrin]

This thread is to understand the situation in general, and check, that all features can be implemented with new archtecture. Please, don't make discusstions here. Only name of feature + link to details if exists.

If you need to discuss feature details - just create a separate issue.

[howardroark]

• meta-data support for YAML front matter markedjs/marked#485

Jekyll has a great thing called front-matter which makes it a sane process to use Markdown files as the structure of a document. It's basically a format for adding data that is meant for a template engine that runs later. It could be a project of it's own, but the idea of returning content+meta in one swoop is very interesting.

[puzrin]

(?) From multimarkdown https://rawgit.com/fletcher/human-markdown-reference/master/index.html

• citations
• definition lists

[jonschlinkert]

@puzrin I'm going to consolidate the ideas in the op, obviously feel free to continue editing that list

[puzrin]

ok

[puzrin]

Marked two html-related features for remove. First one because working on/off mode for html, second - because not needed (with html off output is correct, with html on need external sanitizer).

@jonschlinkert , if no objections - cleanup first message

[jonschlinkert]

done

[szelga]

image dimensions: http://stackoverflow.com/a/21242579

[jonschlinkert]

huh, yeah image dimensions is an interesting one. I like that

[puzrin]

There are maruku syntax for defining any attributes. I'm not sure, that it's good idea to make exclusion specially for images.

I'd recommend to discuss it first at http://talk.commonmark.org/ , if you wish to include it to core. Or you can rewrite image rendering fn and extract this info from title, if you can't wait.

[jonschlinkert]

yeah, I was thinking it would be interesting for a plugin or extension, not core

[jonschlinkert]

maybe we should create an issue titled "plugin ideas" where we can add these, so we/users can add to those or create the plugins. also might be a good way to educate users on what is good for core versus a plugin - by way of example...

[puzrin]

Create a memo page in wiki, to avoid infinite tickets.

[jonschlinkert]

so, create a page in the wiki, where no one looks, to avoid users creating more tickets? (e.g. users will create tickets and we'll tell them to look at the wiki? instead of having one ticket that keeps users from creating more?). not sure that makes sense

[puzrin]

You try to create ticket for solving problem that not yet happened :)

[puzrin]

Removed toc - in 1.4.0 can be done with plugin easy. The same for Emojy.

@jonschlinkert were can i see detailed examples for citations ?

[jonschlinkert]

I'll look around for examples. I can't remember where I saw them.

[tcoopman]

metadata?

Metadata must be placed at the top of the document – there can be no white-spaces before – and it ends with the first empty line. Each entry is composed of key and values, separated by a colon (:).

There are plenty of keys supported, some of the most common being Title, Author, Date, Copyright, Keywords and Email.

http://bywordapp.com/markdown/guide.html

[puzrin]

metadata?

It's not in CommonMark spec. Only discussed, with unclear future http://talk.commonmark.org/t/metadata-in-documents/721

It's better to parse metadata in external module now or write appropriate plugin.

[tcoopman]

It's better to parse metadata in external module now or write appropriate plugin.

I have written a plugin a the moment. Except for the fact that there aren't any docs yet, it was nice and easy. Nice work on remarkable (I will use it on my blog)

[puzrin]

@jonschlinkert i think, we can close this ticket and create separate issues for rules, that are really needed. No need to keep infinite issues, which have no strict conditions to close.

[puzrin]

Closed. Create separate tickets or just write plugins. The most complicated things are already done.

[jonschlinkert]

Sorry, when I read the email from the last message on here I thought you closed this already. 👍

[anaran]

github task list support is not implemented yet, right?

It's kind of hard to follow the situation about them.

[felixSchl]

Yeah what's the story about githab task lists, is this still on the radar?