Writing About Textpattern
by Destry Wion :: published 29 January 06
Since publishing the first article, Understanding Textpattern Building Blocks, of my anticipated two article series on Textpattern building blocks, I have been contacted a number of times about the possibility of producing a single document that explains how to build a basic Textpattern site. Although I can appreciate people’s frustrations here, a single article about building a Web site based on Textpattern is a tall order, for a couple of reasons.
First, there is no one way to build a Textpattern site, even a basic one, so any attempt to write an end-to-end process like such is not really practical as it could lead people astray from what they may really want to achieve. For example, one article might appeal to a certain audience with Weblog needs, but another group of people might want something entirely different, like a photoblog or a business site. The bottom line is you can’t write a single article that would be general enough for all interests yet still cover complete site design.
Second, and despite the first, producing such an article would require three assets if the article was to have real worth: 1) it would require a writer with in-depth understanding of Textpattern to ensure the most fundamental, core concepts were communicated, 2) the writer would need to have a LOT of time on her/his hands, and 3) the writer must know how to write well and with respect to a given target audience. All of these assets are huge, and while many in the Textpattern community may have a couple of them (though certainly not the same two), very few (perhaps none) actually have all three.
Note: What the Textpattern community does have is a fair number of designers and developers, like myself, who know how to build a variety of Textpattern sites, which for them is often much easier than writing about how to do it. Hence, for a negotiated fee you can have a Textpattern site built for you, with accompanying user documentation, which will likely be better for you in the end, or at least get you to the end much quicker.
In fairness to the many folks out there who have written on behalf of Textpattern, there is lots of good information available that can help guide a newcomer through the basic steps of site creation. To be sure, there isn’t a single document that says it all, but rather many articles covering many facets of Textpattern. In addition to the three authoritative documentation sources I’ve mentioned before—again, the Textpattern Support Forum, the Textpattern FAQ, and TextBook—there is also the Textpattern Resources site, which for the most part is a search portal for various Textpattern articles posted on Weblogs around the world. If one spends enough time hunting, they’ll be able to put many pieces of the Textpattern puzzle together.
With that last thought in mind, one thing an aspiring writer for Textpattern could do is attempt to write an outline of the steps required to build a given site type, where insteading of filling in all the sectional details themselves, they simply provide a short list of links for any given section topic that points to the best existing articles available on the subject. Developing a complete walk-through document in such a manner would achieve a number of things:
- It would be somewhat easier to prepare (theoretically) should any writer take up the activity.
- It would provide the 1-2-3 instructions in context to the process that a single article would provide.
- It would save newcomers having to conduct time-consuming searches for disparate articles on their own.
- It would lay significant foundation for the writer (or perhaps another) to produce a complete, concise and consistantly written article later, for which there is seemingly still great demand for.
As I sit here and reflect on this, the obvious response comes up: start such an outline in TextBook. In fact, that road has been tried before and didn’t get very far. The problem there, is that it relies on the whims of the community, and as TextBook has proven, contributions of any kind are slow in coming. No, to be sure, what an effort like this would require is a single, good writer who has the necessary time, insight and focused dedication to put such a document together.
Note: As you come to perhaps know Textpattern better, please consider making your own contributions to TextBook. No one person will ever be able to write everything about Texpattern. Good documentation will eventually be realized by the collective efforts of the user community, and that means you as much as the next person.
My advice for newcomers to Textpattern is to make use of the authoritative resources I mentioned before, start your own document collecting activities as you need for the given site functions and features you desire to have (printing articles and keeping them in a notebook is one very effective method), and tinker with things on your own. If you are not too concerned with having a custom interface or custom functionality, you might consider using one of the growing number of Textpattern themes (or skins) that are available, each of which should come with it’s own limited set of instructions for getting it implemented. A good place to look for the available themes is TextGarden. Otherwise, one must resign themselves to a little patience as existing documentation resources like TextBook gradually improve, and they certainly will.
Having said all that, however, I will be writing individual articles from time to time that are meant to build upon one another conceptually, and you can consider Understanding Textpattern Building Blocks as the first of that effort. The next article in the building block series, Textpattern Building Block Mechanics, will be published soon. Stay tuned.
Latest Ten Articles
- Finally Pro-MacBooked 6 April 07
Six months later than expected, and on the eve of the new Apple Leopards, I am nevertheless a happy owner of the MacBook Pro, and it feels good.
- What Makes a Good Web Accessibility Guide for the Business? 2 April 07
With pressure mounting on web developers and companies alike to provide quality eAccessibility products and services, it makes good business sense for companies to have their own eAccessibility guidelines to help ensure development objectives are being met in efficient and cost-effective ways. However, just knowing guidelines are needed is one thing, producing and integrating them into a development workflow is something else. What breadth and depth of information should they cover? How should they be written and structured for maximum understanding? What format provides the best utility? Seemingly, the preparation of eAccessibility guidelines is not a fundamental task, the considerations are many.
- Main Points Delivered at the First European eAccessibility Forum14 March 07
I’m not exactly punctual on this one, but making a long story short, here are the main points as I took them from the eAccessibility Forum held in Paris nearly 6 weeks ago…already.
- In Paris for the First European eAccessibility Forum27 January 07
It’s going to be a whirlwind trip on the train, but should be interesting nonetheless.
- Lose Readers by Moving Themes?14 January 07
We hear about free Weblog themes all the time, and see the same ones all over the Web, but it’s not often you read about someone moving a personal theme from one self-owned domain to another, or the implications of doing so.
- Book Reviews Coming to Wion18 November 06
Reading and writing is my kind of chocolate, and when it comes to book reviews, everybody wins. I hope you’ll find them helpful. Stay tuned.
- A Core Textpattern Technique Addressing Internationalization Interests14 November 06
This article presents a core Txp technique for managing internationalization efforts, and three methods of use are described: 1) multilingual publishing within site, 2) collaborative international publishing between individuals, and 3) an alternate approach to #2 that essentially takes a community slant.
- Textpattern Building Block Mechanics30 May 06
Here is the second article in a two-article series about Textpattern building blocks. If you missed the first article, Understanding Textpattern Building Blocks, you might check it out too.
- Heatmap Presentation of Eye-tracking Data17 May 06
Isotopic heatmaps of eye-tracking sessions are easier too see and understand; hence, great slide material for stakeholder presentations (management, clients, and so forth).
- IE Conditional Comments: Where Have They Been?19 April 06
Conditional comments have been with us for years and largely unknown, but with the coming of IE 7 they may be the swan song that’s about to go platinum.
