Any opinions? Advantages? Disadvantages?
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
October 24, 2007 12:02pm
Subscribe [6]#1 / Oct 24, 2007 12:02pm
Any opinions? Advantages? Disadvantages?
#2 / Oct 24, 2007 12:23pm
I think overall Markdown is written more efficiently. Certain types of text with Textile can cause a bottleneck. I’m sure that’s probably the case conversely as well, but I’ve seen it a number of times with Textile.
#3 / Oct 24, 2007 1:03pm
My preference is Markdown. I think it’s much more readable, and my clients like it better than textile.
But, YMMV.
#4 / Oct 24, 2007 3:17pm
A vote for Markdown here, I’ve been able to “sell” it to several clients, even decidedly “non-geek” clients.
#5 / Oct 24, 2007 8:15pm
Ditto Markdown. Chairman Gruber knows what he’s about.
#6 / Oct 25, 2007 2:04pm
Thanks! I was leaning towards Markdown. Is there still no plugin wysiwyg editor for the wiki?
#7 / Oct 25, 2007 2:16pm
Thanks! I was leaning towards Markdown. Is there still no plugin wysiwyg editor for the wiki?
Patrick has used Xinha, and Phoebe has an extension to use the YUI wysiwyg editor with the wiki.
#8 / Oct 26, 2007 10:59am
I like Markdown a lot, but I like having the ability to add classes with Textile. And being able to quickly and easily add a table is convenient for clients. I think Textile is a little more powerful than Markdown in terms of control. Both have their +/- but I prefer Textile.
#9 / Oct 26, 2007 2:20pm
Wow.. I really need to look into Markdown. I’ve implemented Textile in my site mainly because I started my first CMS’d personal site using Textpattern. Shortly after that I switched my entire team over to BaseCamp for our collaborative project management. That grew into us also implementing textile in our home-built CMS (we wanted it so bad we wrote an ASP class to support textile since one didn’t exist).
Now that I’m building out my own EE sites I’ve just used textile since it’s what I know. I’ll have to go take a look at markdown to see if that’ll be easier for non-technical folks to grasp…
#10 / Oct 26, 2007 2:25pm
Replying to my one post…
It appears as though at a basic level, Textile has better support for cleaner, more semantic code.
If I want a third level heading with a specific ID and class, all I need to do is this:
h3(#idhere classhere anotherClassHere). This is My Heading
Ordered lists auto renumber so you only need to do this:
# first item
# second item
# third item
When you want to add another item in the middle, you don’t have to go renumber any items that follow.
Abbreviations? These are fairly simple IMO(In my Opinion).
My biggest gripe with Textile 1.0 is the lack of support for dictionary lists… that’s something I use a lot when creating semantic markup and something sorely missed…