In this most recent series of posts, I’ve introduced you to and demonstrated some of the fundamentals of the Textile text processor for the Textpattern CMS. Armed with these two tools, along with some of the ‘how to’ articles I’ve posted here, you should be in a position to install Textpattern to your Arvixe web hosting account and try them both out. I’ve written these articles as an introduction and/or primer for how Textile works, and while I don’t consider this a thorough tutorial series, it’s important that you know where to look should you want to find out more.
If you’re familiar with the Markdown text processor, you will likely spot some similarities between the two systems. Markdown and its derivatives are far more widely-deployed than Textile. In some respects, you can compare this Markdown vs Textile difference in availability across the Internet like WordPress vs Textpattern, although I don’t have figures to hand to back up this statement. One of the key take-aways from Markdown vs Textile is that both have their place, and although you may well come down on one side of the fence, it’s a useful skill to at least know about both and know where to get more information.
It shouldn’t be a surprise if I tell you the Arvixe blog runs on WordPress. I’m not sharing anything ultra-sensitive with this information, it’s trivial to find out what most blog sites are running. I use WordPress, and I use Textpattern. I use Textile, I use Markdown. I personally prefer the Textpattern and Textile combination because that’s what I’m most comfortable with. You won’t find any CMS jingoism from me, I’ve long since been done with the pettiness and name-calling when comparing platform/product/service since the PC vs Mac days. I haven’t yet found a situation where I personally would use WordPress over Textpattern, but I do actively recommend WordPress for some of my clients with broad needs.
If you’re using WordPress on your Arvixe site(s), and you’ll be among millions of other websites using it, then you can try out Textile without getting involved with Textpattern. I am somewhat biased in thinking that you might want to at least try Textpattern to see if it’s a good for you (or if you’re a good fit for it, if you will), but you can get Textile functionality in WordPress with a plugin, depending on the version you have installed. If you’re using Joomla, Drupal, Moveable Type or another self-hosted content management system, you can likely find a plugin or module to extend the core functionality to include Textile processing. If you’re handy with PHP and libraries, you could even snag the source and build something yourself.
Your Textile toolkit should include a bookmark to the Textile documentation and sandbox, the Textile Wikipedia page for a history lesson and the Textpattern support forum. Perhaps if the take-up of Textpattern users on Arvixe increases I’ll also be able to direct you to the as-yet-uncreated Textpattern forum in the Arvixe forum; in the meantime, if you have any questions or queries about anything I’ve covered regarding Textile, and any other facet of Textpattern, please leave a comment or get in touch with me and I’ll do my best to assist you.
That’s it for Textile education, the next time we meet I’ll be talking about the practicalities of managing your Textpattern when there’s more one person involved, specifically your users, everyone’s articles and comments left by readers. Thanks for reading, and I hope you’ll join me again.