Article
A bit about Textpattern Content Management
Feb 25, 09:39 PM | Birdie | 5 Comments
Back to BlogI mentioned a bit about Textpattern in my last post, but i’m going to go into a bit more detail here about how it works and how it can be used to power all kinds of sites.
I have spent some time over the last couple of months learning to use Textpattern, an open-source content management system. Originally I first looked at it purely as a blogging solution, which is it’s primary purpose, but it turns out that, unlike most of the other blog systems, Textpattern was capable of running a full website and not just the blog areas.
Another reason I went with Textpattern was the Textpattern Solutions book which was meant to get me up and running quickly. Unfortunately I found the book frustrating more than anything else, mainly due to the lack of step-by-step tutorials. It gives a good overview of the system and how it works, and it’s useful as a reference, but the tutorial aspect was a let down. I see others have had the same issue.
How Textpattern Works
The Textpattern system works through a combination of standard HTML & CSS, Sections, Pages and Forms. Essentially the process is to design the pages as per usual and then import them into Textpattern, creating Sections and Pages as needed. Sections are top level divisions, so www.mysite.com/about is the url for the about section. Pages could also be called Templates, as they perform the same function by providing the layout, so the about section uses the about_template page.
The flexibility of Textpattern comes from the Forms. “Forms” is a bit confusing at first, because it doesn’t refer to actual text-input form elements, as you would find on a Contact form for example. Instead, it refers to automated functions within Textpattern that allow you to create content areas on your site, which are populated depending on the section you place the form in.
It’s the relationship between Sections & Forms that is the hardest to get your head around, and it took a few evenings of frustrating trial & error before I felt comfortable creating automated functions. With perseverance though, it eventually clicked and once it does it all seems very simple.
Organizing Content in Textpattern
All the content managed by the Textpattern system is contained within Articles. Apparently this is to do with the history of Textpattern, which was originally based on the working structure of an off-line publication, such as a newspaper or magazine. This becomes very apparent when you see the User Profiles Textpattern uses, which include Publisher, Copy Editor, Staff Writer and Designer.
An article contains a Title, Body Copy and Excerpt by default, and more content, such as an image or URL, can be added through Advanced Options or by using Textile mark up. Textile is a simple markup language used by a variety of web apps which i’m quite fond of, but I think it’s an unnecessary complication for client sites so i’ll be installing a plug-in to add WYSIWYG text editing instead.
Interactive Elements
Because the system is so flexible, it’s possible to use Textpattern for all sorts of sites. The bird.ie site would be a classic ‘static’ site, which is all taken care of fairly simply, but i’ve also installed Textpattern to control a flash video portfolio (launching soon). Because it doesn’t rely on templates, any content can be included through judicious use of Forms.
Final Thoughts
I think Textpattern is great, and I am very pleased with it’s flexibility and power, but it won’t quite replace the services of a good developer on some projects. The system is perfect for straightforward content management on text-based sites, such as B2B sites, brochureware and blogs, and it can be pushed into more complex content management when needed, but I don’t think the interface is intuitive to other non-text based or image heavy content.
This stems from the history of the system, and also impacts on the default look and feel of the CMS, which is fairly bland. However it is possible to re-skin the system using CSS and a bit of hacking, so a Birdie themed redesign could be in the works if I find the time.
Overall I have very few complaints. Textpattern suits my needs, and the general needs of most business websites, so i’m delighted to be able to offer Textpattern powered content managed websites as part of the Birdie service, and I am looking forward to getting my teeth into a few projects with it.
Back to BlogComment on this post
That is true, it’s quite simple to install static pages into a Textpattern set up without making any modifications. I find that useful for adding pages to this site – because I know HTML it’s easy for me to just edit the raw markup if I need to make a small change.
For clients who don’t understand HTML it is relatively straightforward to switch the page content to Textpattern articles as they are needed, or as budget becomes available. Thanks for commenting Markus!
Very informative article. Glad to have stumbled upon your blog.
Thanks, good post.
It’s a really good article for me, Must admit that you are one of the best bloggers I ever saw.Thanks for posting this informative article and share with me.
I liked the ‘being confused’ parts as these are not obvious anymore after the TXP logic once ‘clicked’.
For very simple single pages you won’t even need forms or articles because you can design a ‘one section=one page’ website.
But of course you will want to have a header and a footer form at least. BUT you can start to transfer a static site to TXP by importing (read copy&paste) the static HTML markup (and the CSS) into Textpattern. Dynamic refinements may follow later.
I am doing this right now with a nine section static site. The advantage is that you won’t have to do the logic redesign for a dynamic page from scratch but you can start with ‘static’ pages and add variables as you like and when you like (and as the budget allows it).
Example: This website transfers from static to dynamic: Record studio in Hamburg. Progress will follow as the client budget allows it.