Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#73 Today 13:30:02
Re: RFC: Textpattern 5 ideas & feature requests
Markdown as default text converter on new installations, Textile for existing installations.
Controversial, yes…but Markdown has the edge for legibility and is more widely-known. Textile can handle more complex layouts, so it’s there when needed. From a purely PR point of view, if a new Textpattern user already knows some Markdown, the barrier to learning & adoption is lower.
Offline
#74 Today 16:01:47
Re: RFC: Textpattern 5 ideas & feature requests
gaekwad wrote #340156:
Markdown as default text converter on new installations, Textile for existing installations.
Controversial, yes…but Markdown has the edge for legibility and is more widely-known. Textile can handle more complex layouts, so it’s there when needed. From a purely PR point of view, if a new Textpattern user already knows some Markdown, the barrier to learning & adoption is lower.
That is indeed very controversial! I wouldn’t have it as a default but as a preference which could be set during installation.
The articles should of course maintain the option to select between leave text untouched, convert linebreaks, textile, and markdown, but I’m not sure as to how much we will bloat the db.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
#75 Today 21:40:42
Re: RFC: Textpattern 5 ideas & feature requests
gaekwad wrote #340156:
Markdown as default text converter on new installations, Textile for existing installations.
I like it. But concur with Yiannis that I’d prefer to offer a choice during installation.
I did actualy have a go (aaaages ago) at merging wet_textfilter_markdown into core. Got 98% of the way there but hit a roadblock and can’t for the life of me remember what it was now. It seems like it’d be trivial, and not much code.
colak wrote #340162:
I’m not sure as to how much we will bloat the db.
No more bloat than Textile would. In terms of filesystem space, it’s another file in /vendors.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline