31 December 2012
Don’t watch. It will be ready…soon(ish).
Don’t watch. It will be ready…soon(ish).
It seems that there might still be some problem with the way this new version of Textpattern is assigning the date and time to each new article.
The latest suspicion is that a plugin might be causing the problem.
This is a test post to see if the problem persists.
EDIT: This article posted correctly with the date and time assigned properly. This edit will determine whether the date and time can be updated correctly after editing an article.
Two recent articles initially posted out of order on this weblog. Only after resetting the date/time for the article was I able to move them to the top of the weblog.
The articles each carried the proper article number indicating that Textpattern assigned precisely the right sequence.
This is simply a test to see if this article appears at the top of the weblog when I press publish.
After an afternoon and evening of updating sites to Textpattern 4.0.4, there’s much to be pleased about. Four websites updated without any tweaking at all. Those happened in a matter of minutes. Exploring the new feature set and improvements took a bit longer.
The developers, testers and all the contributors have done a fantastic job of improving the product while protecting sites built with prior versions.
Built into the new version is Textile 2.0. It fixes the problems associated with multi-paragraph blockquotes and a host of other difficulties.
There isn’t a tutorial for Textpattern. There’s a wiki for documentation and there are some new help screens for the fields that make up the heart of the system. Unfortunately, some of those help screens contain typos and spelling errors which can be distracting.
There are still some challenges for a rookie who wants to take the software from download to a styled site with minimal frustration. I suspect there will be a renewed effort to help those of us who are not site designers and software developers now that 4.0.4 is out.
With so many content management systems available, these notes about documentation, tutorials and help screens are the only things that prevent Textpattern from competing with and surpassing Blogger or LiveJournal or TypePad or other “starter” systems. Before raising anyone’s ire, let me add that Textpattern isn’t really a competitor to those entry-level blogging tools.
Textpattern clearly goes well beyond basic blogging software in capabilities and power. It’s the initial start that can be a little tough for those of us not steeped in deep site design and software development knowledge. A tutorial that takes you from software download through installation to theme and template implementation for both a basic weblog and a basic web site would open the product up to a new realm of users.
Unfortunately, any mention of these kinds of things is often met with a write-it-yourself comment in Textpattern’s support forum. However, it is that very forum which is the ultimate documentation and resource for virtually any challenge one faces with Textpattern. The folks there are a savvy bunch and helpful.
To undertake the list of small improvements planned for this website, two approaches are available. One involves taking each individual improvement into the forum, asking a question and implementing the change. A second approach involves finding a Textpattern designer/developer who can optimize the installation of Textpattern, rid it of unnecessary plugins and ready the site for its next 4500 articles.
One’s knowledge is enriched with the first way. The results come quicker with the second approach. Either way, Textpattern is clearly capable of taking any type of web site from back-of-the-napkin to thousands of pages of content. It’s all a matter of just how deeply involved with the workings of your site you want to be.
This is a call for the right kind of CSS instruction for people who are just getting their start with web design.
Modern arguments about any subject usually contain some elements of truth from both sides. Except in those (often political) debates where one side knowingly distorts the position of the opponent, the tidbits of truth can serve as a perfect starting point for a real education.
There was a CSS rant. Then, there was a CSS training offer. “What would those two days of training cost…?”Now, what is there for the more pedestrian users of CSS? While there were some misguided conclusions in Dvorak’s article, there were also elements of truth. CSS can be very frustrating when one is left to some sort of self-taught methodology. Standards bodies don’t provide the kinds of answers that work-a-day CSS users need in spite of protestations to the contrary.
If experts can’t agree, what are those of us on the outside supposed to do? Books about CSS sometimes use valuable chapters explaining table-based layouts before declaring those techniques to be wrong. What we need is a video of Molly’s two-day training session. Better yet, we need An Event Apart focused on those of us who want answers like the ones Molly promises to Dvorak.
The question is this, “what would those two days of training cost if they were provided to an audience of about ten or twelve interested designers?”