Snarkdown roadmap ?

Hey !

Cool project ! Thanks for sharing this, really.

@developit, after going through the code, I found some irregularities (PR submitted) but I don't know to which extend you will accept PR or what aspects of Markdown are you willing to support Vs the `1kb` claim.
I know you are by definition a "zero-calories-coder" (yeah it's brand new term, my present :P ) [#Preact (3kb)](https://github.com/developit/preact/) , but where do you want to go with snarkdown ?

In my opinion, I totally buy the 1kb assertion (this one aspect lead me here in the first place), however I would like to be able to freely extend functionalities. My personal goal, for my project would be o basically match with [markdown-it](https://markdown-it.github.io/).
This means support for GFM tables (I see a [PR](https://github.com/developit/snarkdown/pull/18) is pending), I recently [added strikethrough](https://github.com/developit/snarkdown/pull/32), I also see there is a slight problem regarding images that do not support the Alt attribute (a PR on that might move stuff around as it implies adding a new catching group to links regex...), I think I can add subscript and superscript, and custom containers (which is out of commonMarks specs but I find it useful to add basic styling) would basically be 200 bytes to implement...
Now, in your opinion, when should we include all of this into snarkdown, and when it should be out: how to implement it ?

Indireclty, my question is two fold:
1. is there some roadmap you wish to implement ?
2. to balance lightweight code Vs features : could you guide us toward a kind of plugin implementation that would extend the 1kb if needed ?

Thanks for reading

Commencez par examiner la discussion existante et les PR référencées #18 et #32, puis comparez le périmètre demandé avec markdown-it et l’objectif de 1kb de Snarkdown. Le travail est terminé lorsque l’orientation du projet est clarifiée : les fonctionnalités Markdown prises en charge, les critères d’acceptation pour les ajouts et la question de savoir si l’extensibilité devrait utiliser une approche par plugin.

Rédigé par le modèle d'indexation à partir du texte de l'issue.