Sections…

I loved sections! Textpattern has it right using sections. For those of you that are wordpress junkies, let me explain… In textpattern, a section is almost like it’s own little site within your site. When done right, sections in textpattern allow you to separate and manage all of the different content areas in the website. Each section, is assigned a stylesheet and template. You can of course use one set of css and templates for all sections, but you don’t have to.

All of the posts to the CMS are assigned to sections. So, in my old textpattern install – I would have posted this into the articles section. The post would also get the textpattern and website categories. The cool thing with sections – you can separate your content – truly separate it.

For ryanbarr.com I had a few sections in my textpattern install. I won’t go through each of them but I’ll talk about three of them, and why I miss them dearly…

1. Articles
2. Trading
3. Pictures

In my articles section, Megan and I put all of the “standard” fair content. Stuff about the family, any random thoughts etc… This was the area of the site that folks who know us and are interested in what we are doing could come to. On the navigation, we had a link to the Barr Family Blog and this was really just a link into the articles section.

The articles section of the site was setup without all of Ryan’s stock information. When a visitor clicked into the section homepage, the page was rendered using our standard theme, just without the business stuff. The same thing would happen when a visitor clicked into a posting in the section. However, the list of postings was also limited to the articles section! That means that folks interested in the family, but who don’t care about options aren’t stuck seeing all the posts I have about options etc…

The trading section was just the opposite. It was really my business, investing, options, iron condor playground. I put the papermoney trades in here, all of my random market commentary, and everything else to do with business in the trading section. Posts in here had the addition of stock quotes on the page, and targeted ads. it was pretty nice. I didn’t place ads or stock quotes in the articles section because they didn’t really fit.

Pictures, well it was just that pictures!

Certain sections were allowed to show on the homepage, and then once in the section you were really in a specific part of a total website. Quite nice really.

WordPress does not do this Or at least I haven’t yet figured out how to make wordpress do this without a ton of php hacking.

Making it work…

Since I decided to move to wordpress I had to make this work. In wordpress you have pages (static content), categories (posts), and tags (pages and posts) – alas, no sections.

Currently, ryanbarr.com is divided between really two, possibly three major topic areas.  The family area, the business area and the pictures area. Taking pictures out to there own part of the site was a snap using the Gallery and wordpress setup that I have running here.  Part one solved.

Breaking out family and business just didn’t seem possible.  So for the site we’ve taken a little different approach. Rather than using a ton of categories as most blogs tend to do, ryanbarr.com will only have a few categories, and we will make judicious use of tags.  Thankfully, wordpress now has native support for tags so that should help out a bit. A few pieces have been broken out into pages, that will also help as well.

The one thing with this setup that I’m not too happy about is the fact that wordpress doesn’t really support viewing posts by category.  You have the archive pages, which I am using, but once in an article, the segregation goes away.

I’ve also lost the ability to really support the “two” major rss feeds I used to send.  With the new setup, I can do rss feeds by category, author, tag etc.. however, I haven’t figured out how to send an rss feed for a group of categories.  If I could set this up, that would be perfect.  Until then, we’ve decided to just use the main rss feed only.  It will muddle the content a little bit, but it’s not horrible.

I’m still looking for a way to fix this, so if you know of something – post a comment please!

Importing Data

Now that Meg and I have decided on an organizational strategy, it’s time to bulk load some testing data so that I can make sure everything is working correctly.  Off to Manage -> Import…

First things first, the textpattern import into wordpress is broken.  It doesn’t take categories in correctly.  And please make sure that you change the name of your admin user before you do this import.   Here are the things to watch out for…

1. Categories do not import correctly.  They show up in the list without any problem, but the association of post -> category somehow gets lost in the shuffle.
2. When you import users, their password is reset.  Make sure you rename the admin account in either textpattern or wordpress before running the import script.  If you don’t you will be kicked out of the import and have to do a password reset… it is a pain.
3. Posts (articles) are imported in plain text, ie: textile.  If you don’t want to use textile in wordpress, this is a problem.  You will lose all of your formatting.
4. WordPress doesn’t have sections, sections do not get imported.  If you’ve used sections in textpattern they will be lost

To fix a couple of these annoying problems, I hacked my textpattern.php import file.  I’ll post a copy of it on this post, just note that it doesn’t work perfectly – it was a hack for my use and I don’t plan to support it.  Please use at your own risk. This script met my needs so I left it alone after that. Here are the things that I fixed/added.

1. Added a Section import into the Categories import part of the script
2. Added a button to skip the user import, you can still import users if you want
3. Changed all of the posts to import the Body_html and Excerpt_html, that fixes the annoying little plain text thing
4. Made the section a category for the post

The only thing that I can see that still doesn’t work is the normal category assignment.  I looked at it, the code appeared to be correct, but still no dice.  Since I decided to get rid of my textpattern categories and redo things with tags, this was okay with me and I didn’t bother to fix it.

I’ve got data!

So now I’ve got data! Everything in the development instance is running pretty well.  I had to run the data import script a few times to get everything fixed, but after a bit of debugging we are good to go.

Now that I’ve got data… oh man, the site still needs work.

The vSlider3 theme is pretty cool, but it has a few goofy things that I wasn’t happy with.  In the next post I’ll run through the things that I tweaked in the vSlider theme to adjust the way that Gallery 2 works, as well as some of the things in wordpress.

Oh yeah, here is the import script (from wordpress 2.3.1):  download

For part two of “My Journey to WordPress” I’m going to talk about setup and configuration. I mentioned that my host does a simplified installation of both wordpress and gallery. It made the first part of this really, really easy. I literally, log into my administration web-panel, then click install.

After about 5-10 minutes I had emails in my inbox letting me know that the software was up and running. Excellent! I logged into wordpress, and it was setup in no time flat, gallery was a little more cumbersome, but still quite simple to setup really.

With the gallery setup, a few of the plugins needed additional configuration so they didn’t work right out of the box. But that was no big deal. Now that gallery and wordpress were both independently working, it was time to hook them together and then pass off the site.

To install the WPG2 plugin, just download, unzip, ftp/ssh/sftp/whatever the files over to your wordpress plugins directory. After installing, enable the plugin then head over the to the WPG2 tab in the admin interface.

General configuration of the WPG2 was pretty straight forward. The URL rewrites section gave me a little bit of trouble, so make sure to enable and disable it in Gallery first. Then try it in WPG2. You’ll also need to download two additional Gallery plugins per the WPG2 docs. That process was very straightforward in the Gallery admin panel, click on plugins then the second tab , download, activate, enjoy.

Now the trouble begins…

I had this great setup all ready to go, Gallery 2 integrated with wordpress! It was perfect. I clicked on the WPG2 page and saw this horrible theme that didn’t fit into wordpress at all! Uh-oh

I figured that I must have missed something. Being the a developer type, and a guy, I didn’t bother to read the instructions, I just stared clicking and watching the error messages. So I figured, what the heck, let’s see what the docs have to say. A quick google for WPG2 takes me to the old plugin homepage, put luckily there was a link to the “new” homepage via wordpress.org. On the homepage I see a quickstart guide – perfect! Or not…

The quickstart said to to exactly what I did! I’ve got wordpress and gallery integrated, heck I can even use the snazzy gallery picker while writing my articles… but the page looks horrible!

I figure that it must be a theme thing or something, so now it is time to go and figure that one out. Back to google. I did a quick search for “wpg2 wordpress theme” and came up with a few interesting hits.

• The first a site with a bunch of modified wordpress themes that are “optimized” for gallery… I have no idea what that means, it wasn’t in the quickstart… I didn’t realize you needed to optimize for this integration… Bookmark it, comeback later.
• Next, that old help forum… it rules in the google search so be careful! Just a bunch of php nonsense. I don’t know php – and I don’t want to know it! That is what I loved about textpattern… wordpress is beginning to piss me off.
• Next, another site from the old forum… Didn’t they move all of this stuff?!!? Wait!! Something that might be useful!
  

Before you begin

• – if you need to modify the header.php file of the WordPress theme to suite your needs, try to do this before proceeding
  - it’s recommended that you use a Gallery2 theme which is optimized for WordPress integration, like the WordPressEmbedded Gallery2 Theme for Gallery 2.1 or the WordPress Gallery2 Theme for Gallery 2.0.x.

Aha! There is some sort of wordpress embdeded Gallery 2 theme. That makes sense… Since I’m using a version of Gallery 2 that is above 2.1 that might just be the ticket. Download, install.

Okay, so now gallery has a new theme. It’s pretty boring, but what the heck, I haven’t seen it in wordpress yet. That site at the Gallery 2 old forum mentioned something about the header.php file… Whatever, lets see what we get

Not good… Okay, so it’s not totally plug and play. This is becoming painfully obvious. And what happened to the quick start, this isn’t feeling so quick now!

Stop! I’m working on my friends site… this isn’t going to work. The site looks like crap, I’m hacking a live version and this just isn’t good… Detour. Reset my development instance of ryanbarr.com. Install of the the files from my host, re-configure and walk through the steps I’ve taken so far… a while later… Resume, on my development instance of my personal site.

Now you see how I got roped into this whole mess… Since I’m already working on it to figure it all out…

Next step, lets try hooking into the “bookmarked” link I found earlier. I download a few of the “optimized” themes, activate and suddenly all is well in the world. The blog, and the gallery are working perfectly together – but why? I realize that I have no idea why this is suddenly working, the quick start guide wasn’t so quick and now I’m lost. Okay, time to read some more.

Back to the official homepage of the plugin. Under WPG2 Operations I finally find a few pieces of what I’m looking for. But it is sparse to and sort of fragmented. Again, no mention of this elusive Gallery 2 theme I found while googling, the only thing close was a page that was “under construction,” it linked back to the place I found my Galley 2 theme… So I guess if you look hard enough it is there, not not obvious.

Well, At this point I’m still a little lost, and don’t really have any desire to learn php (I do happen to know about 13 other programming/scripting languages, so i guess another one can’t hurt). What I really want it a customizable theme that doesn’t require me to re-do all of the work I just did in textpattern!

The support forums… Lets see, click, click, click, there we go… Found them! The support forums are located here. There are three options, if your looking for help with themes etc… go to WPG2 CSS/Layout Support. Don’t bother with the other areas, they will help if you have other integration issues

The forums are excellent! The guys that work the plugins seem to have answered all of the questions quickly and I was able to find what I needed… My theme vSlider3 this particular theme seemed to have it all. Customization, integration into gallery, options, configuration, no php required! Download, install!

Why didn’t I start at the support forums… Oh yeah, they are buried in the google results! That will work itself out with time…

Now I’ve installed vSlider3 and have a working site! Excellent!

Okay… now that this is all working, lets see about getting all of our content back into wordpress like it was in textpattern. Off to the admin panel, manage -> import -> textpattern -> oh crap.

In my next installment… Read about the joys of importing data from textpattern, and what I did about sections… What do you mean wordpress doesn’t have sections?!?!?!

Wow…

I never thought I would do this, but I’ve dumped textpattern. It actually came about rather quickly and I’m quite happy after doing it. Just a few weeks ago, Megan and I began the process of re-vamping the website. She really wanted to start blogging some more, and well, I needed to stop slacking off and start really blogging again. We talked about the options and figured that a re-design of ryanbarr.com was the way to go. It’s been quite a journey. One that I’ll probably split over a few posts so that this one isn’t obscenely long!

Anyhow, here is the story… I started off by completely re-doing the site in textpattern. I nabbed a pretty nice theme from textplates.com, and then dove in. After working out with Megan how we should manage the whole site, we decided to move a ton of content around (which of course wreaked havoc on my google placements) and totally reset the way a bunch of things were handled. I installed a ton of new textpattern plug-ins to try and make the administration a little more user friendly and even wrote a few myself to handle some stock quote functionality I was looking for. After spending a few weekends working on it, we finally had it ready to go.

Then a good friend of mine asked me to help her setup a new website – michellerenephotography.com.

My response: No problem! I’d be happy to help you out. Lets get a domain setup, I’ve got a great host that you can work with etc…

Then the kicker… “We’ll you know, it’s a photography site. I’d really like to have some serious image management. Really, I’d like it to be a gallery first, then a blog second.”

Serious image management?

I wasn’t quite sure how to approach it. I’ve been using textpattern for quite some time, and have built quite a few client sites using it. Textpattern is a great CMS, but serious image management is not it’s strong point. So, like any good open source kinda guy I went in search of an existing project. I happened to stumble upon a project called Gallery 2, and a wordpress plug-in called WPG2. Interesting… a full image management studio with pre-existing integration into wordpress. This could be worth a try.

The only hangup that I had was, well… I’d never used wordpress, and the last time I looked at it customization and theme’s were all handled through php hacks. Not nearly as elegant a design as textpattern.

I was a little more than skeptical, but I figured what the heck.  It’s her site and  if I can get her started I’m sure she can finish it off.  So, after a bit more research, I was ready to install. Given that michellrenephotography.com is a brand new site, I put the tools up and started hacking away.

My host does a cool quick install of both wordpress and gallery2 so we were off to the races quickly.  I got the two systems up and running, did a bit of quick configuration and then went about getting the plug-in working.  That is when I realized that there was no way on earth she was going to get this all figured out without some serious help.  Permissions, themes, configuration, ssh, linux and a ton of other things that are way to geeky for her to understand.  Well, I figured I’d better dig in…

As I worked on getting things working, I found that wordpress had evolved quite a bit since the last time I took a look.  Quite frankly, I was  downright impressed with it!  I’ll walk through my challenges and learning through this hole process over the next few posts…

Stay tuned to hear about the configuration and setup of the WPG2 plug-in.  The core of the blog/gallery setup that runs ryanbarr.com

Wow! Its been a while since I wrote my last textpattern basics article, and life has been quite busy! Well, its back to basics time! So lets talk page forms. Page forms are the heart of each section in a textpattern site. Generally speaking the page form controls what will actually show up on the page.

There are quite a few tags that you can use in a page form, and they do a ton of work! All of the tags mentioned in textpattern basics – part 2 can be used in a page form, along with some key tags to actually show articles…

<txp:article />

The article tag will show one or many articles, depending on how you have it configured. Some of the key attributes that you need to use and understand are form, listform and sortby. The form attribute specifies which article form to use when displaying a single article. The listform attribute specifies when article form to use when displaying a list of articles and of course sortby tells textpattern how to sort the output!

<txp:article_custom />

This tag will do the same as article, just with more options. You still need to use the key attributes from the article tag, but there are a few other key attributes to look out for. The section attribute will let you return articles from specific sections, regardless of where you are in the website, the same is true of the category attribute, but instead of sections it uses categories.

<txp:output_form />

One of the most important tags! This will call a regular form typically a form of type misc and output the form results into the page. This allows you to modularize your code, generally speaking, that’s a good thing!

There are plenty of other tags that you can use in a page form, however I try to keep my page forms limited to tags that call other forms! For example most of my pages look something like this…


<txp:output_form form="DTD_head" />
</head>
<body>
<div id="container">
<txp:output_form form="header" />
<txp:output_form form="navigation" />
..Some article tags and maybe a few div tags etc...
<txp:output_form form="footer" />
</div>
</body>
</html>


That’s it… The pages are pretty simple, allowing the power to be handled by the other forms! I’ll dive into those in part 4, which I’ll be publishing in the next few weeks months, till then – good luck and drop a few comments if you have a question.

Update: I’ve been slammed with buying property, my job and investing in the market. I’ll publish the next segment in my textpattern series soon!

In my last article textpattern basics – part 1 I reviewed some of the basic concepts in textpattern. As promised, this article will dive a bit deeper into sections, and I’ll start to peel the onion on page forms.

Sections
First off – I’m going to give credit to Thame at erratic wisdom and quote some of his tutorial. Then I’ll dive into my read on sections and try to elaborate a bit..

Textpattern Sections are by far the most misused aspect of Textpattern and I am often guilty of employing them when they are entirely unnecessary. Textpattern sections are strong content and presentation dividers and are powerful enough to create different blogs or web sites from the same installation.
Separate sections should only be used if you are trying to:

• Create ?static? pages ? Tutorial
• Create different ?blogs? with entirely different layouts and styles
• Manage archives

Sections should not be used solely for content division; there are categories for that purpose as well as other external tagging services
erratic wisdom: Textpattern Sections

I think that pretty much puts sums up what sections are. They are your first line of content separation, and should by used for that and that alone. Sections create “mini websites”. They are not just for “other content” – use a category for that! Sections allow you to create complete and totally different areas of your website. Take for example how I employed them here at ryanbarr.com. I have 10 sections—ten sections you might say… let me run them down.

1. about – basically my about page. I don’t want content from there to be syndicated and I don’t want it on the front page.
2. archivescat – this is for the archives page by category. I’m using a section because it allows flexibility to re-style it if needed and provides a solid division from other content. I’ll dive into this a bit more when talking about forms later in the series
3. archivesmonth – see archivescat; but monthly
4. article – this is were all of my “articles” go. anything that is regular content to the website gets dropped in this section.
5. contact – the contact form. It has its own page due to the different layout of the page
6. disclaimer – my disclaimer. I added this because I started to talk about investing and options and wanted to cover my butt. Again, this isn’t syndicated but you can search it.
7. family – my wife own little section Okay, not really. This section is a bit like article, but its specifically for our “family” stuff. The family content goes here because we always have the most recent family article on the home page, and because eventually if we want to style it differently we can.
8. links – for the links – again this section is used to change the output form used
9. pictures – all of our photo galleries use the pictures section. The content for these is substantially different and the layout is totally different than a regular article. I have pictures associated and all of that good stuff. So a new section was required.
10. search – again, just like the archives pages, search has its own layout so I gave it a section.

As you can see, most of these are pretty straight forward. Some come from the design I had up by Stuart, and some are due to my own hacking and customization. I think that generally each one is required to get the feel I was looking for. Notice that there is not an investing section, or a wedding pictures section or anything like that. All of that content is categorized using categories not sections. The only slight exception to this rule is the family category; however, those articles are treated differently and are not in with the regular article lists. Because of those differences, I chose a new section.

In my list of sections, I referred to syndication, homepage, search and some other stuff. Basically, as of textpattern 4.0.3 there are eight options that you can setup for each section. They are as follows:

• Section name: The name of the section – used in your code and in the admin gui.
• Section title: The title used for display purposes
• Uses page: What “page form” to use when in this section. More on this later
• Uses style: What “style” to use when in this section. Again, more later
• Selected by default?: Convenience feature for the admin gui
• On front page?: Should content from this section show up when on the “front page” or in the default section
• Syndicate?: Should articles in this section show up in your RSS or Atom feeds
• Include in site search?: Should these articles be searchable

Some of these items, like name and title are used in code. Some define outputs and some define where content goes… If you have different needs for your content, then you probably need different sections!

So, when your actually writing code – how do you handle sections… First off textpattern comes with a few out of the box tags that are helpful.

<txp:if_section name="[section name here]"> - Determine if we are in a section.
<txp:page_title /> - The title of this section
<txp:if_article_section /> - Conditional output to be used in an article form.
<txp:section_list /> - Shows a list of sections (navigation anyone??)


And to make it even better, I like to use some of the great plugin’s at rDS and Johan Nilsson to enhance what you can do with sections; take a look at glx_if and ob1_title. If those won’t fit what your looking to do, don’t’ forget the textpattern resources website!

Page Forms

Well, this article has already become quite long, so I’ll just “start” to peel the onion on this and go into more detail in the next article. I view page forms as your “starting” point for display. Each section has an associated page form – and textpattern installs three by default.

1. default – the default form – used by most sections
2. archive – used by articles (in the default install)
3. error_default – used for reporting error pages

Each of these forms allows you to define how the page should be displayed. The rules for where articles go, how links are handled and what not are all in this form. Remember that each section is associated to one page form, so in theory, you can have a page form for each section if you wanted to!

I’ll go into more detail in my next article. Let me know if you have any questions or comments, I’m always happy to discuss it. If your looking forward to the next article – grab my feed Thanks!

I’ve been writing about my switch to textpattern for the past week or so and have been playing around quite with the functionality and design of this site. After using a temp design by Stuart I finally got around to setting something up on my own. After getting it all setup on my Powerbook G4 in Safari and Firefox I went live and boom! sure enough it looks like crap in IE.

I should have known that a few things wouldn’t work right, but I didn’t expect to see it that messed up. So here are the things that I saw right away.

1. PNG graphics are totally messed up. The rendering of transparent backgrounds in .gif’s isn’t the best thing on the planet so I opted for .png’s. But the .png graphics looked horrible!
2. CSS  – My styles were totally messed up! Borders look horrible in IE. They look great on my mac, but oh my, on a PC it’s a disaster! The colors don’t render correctly (that’s my fault for not using web safe colors), the nav bar just flat didn’t work and thats just the beginning!
3. The nifty rounded corner script I’m using didn’t work correctly on the main content window
4. Spacing and margins are messed up..
5. The list goes on!

So here what I did… I added a designed for Firefox and Safari at the bottom of the page, fixed the nav and decided to vent about it on the home page! I’ll get around to making a few things look better in ie over the next couple of days, but I’m not about to redesign the whole thing! I guess that’s a good lesson to us “programmer” types, design is harder than it looks! I’ll probably switch to regular borders and do a few other cosmetic changes, but beyond that switch to Firefox or better yet, Get A Mac!

As promised in my article moving to textpattern I’m going to go over some code and concepts used on this site. This site is run using textpattern, currently I’m on version 4.0.3; if this changes you can see the version at the bottom of this page. I’ll start my series of articles by going over some textpattern basics and linking out to some great resources. Hopefully you will find this tutorial helpful!

Resources

• Textpattern
• Textpattern Forums
• Textpattern Resources
• Textbook
• Into to Textpattern

Basics

Okay lets start with the basics.  Textpattern is a CMS, its much more than a simple blog! It uses a bunch of different concepts and methodologies to organize information and create web-pages. Textpattern allows you to enter and store, text (articles), images, files and links. It also allows you to create and manage your website presentation using styles, pages, forms and sections. Each piece of content(articles, images files and links) can be associated to a category. All of these things together allow you to create a very robust website, and if the out of the box tools aren’t good enough, you can always use plugins! For this article, I’ll focus in on Sections and Categories.

Textpattern uses two major organizational structures to move store and organize textual information. These two structures are Sections and Article Categories. For the rest of this article, I’ll refer to Article Categories as Categories.

In my opinion Sections are a key part of textpattern organization. Sections are used to “section” off articles from other articles. These sections basically create big holding tanks that articles are placed into. When browsing a section such as my www.ryanbarr.com/portfolio textpattern basically limits the <txp:article/> tag to only articles that are in that section. This is a really important concept; so let me phrase it another way. When browsing a section, textpattern attempts to limit the information presented to articles that are in that section. As a side note you can show content from another section if you want to by using a tag like <txp:article_custom /> or some other really cool plugins.

Categories on the other hand allow you to categorize your information. Categories have nothing to do with sections. Any article can be placed in any category So for example, on this site if you go to the investing category page you will see all of the articles that are in the investing category. It doesn’t matter what section these articles are in, only the category matters. This allows you to have any information that is related, no matter want section it is in placed together.

The basic difference between categories and sections is pretty important and needs to be understood (in my opinion) to really get a good handle of textpattern. Hopefully this makes sense, if not, drop me a few comments and I’ll try to clear it up! Next time I’ll dive into Sections a little deeper and start to discuss Page forms.

I’ve spent the last ten plus years of my life writing code for the web. I started with the Microsoft set of tools, ASP and Access. Oh those were the days… well maybe not! I can still remember being in high school spending hours down in the basement working on website after website; writing horrible spaghetti code that was impossible to maintain. After a while I moved along into the ranks of a “professional developer”, starting out again with the Microsoft set of tools and after a few years there I again migrated to the world of Java.

For the last five or six yeas I’ve been maintaining a bunch of websites written in a bunch of different languages and its been driving me nuts! So, a while back I started looking for a better way to build sites, something that will let me focus on getting a functional website created in a short amount of time that will also allow my customers (and me) ease of maintenance. Well, I’ve found it!

This site was recreated in about a day’s worth of time from a home grown “pile of ASP and SQL Server code” to textpattern; and I couldn’t be happier. Textpattern is a great tool, it’s a bit confusing when you start, but once you get the hang of it, it’s awesome! I’ve already re-built a couple of client websites using textpattern and have been working on doing more and more as the days go by.

How can you beat it, its open source, well maintained, extensible and quite simple to use once you figure it out. Now don’t get me wrong here, I’m no php guru, but after spending a couple of days playing with textpattern, I’m already in hacking and tweaking plugin’s all over the place. The tool is flexible, performs really well, and so far the administrative functions have been nothing but helpful for my clients.

I’ll spend a little bit of time over the next few weeks posting some of the code used to build this site; as well as some snippets from a few others. I’ll also spend some time writing about the different aspects of the tool as I understand them… Hopefully all of this information will be helpful to others that are working on moving to this awesome tool! But until then, its back to my next textpattern project; a complete rebuild for my church’s website. It will be XHMTL and fully CSS compliant, and built in textpattern. I’m excited, its going to look great, work great and be much easier for the staff to update on a consistent basis! What are you waiting for, check out textpattern for yourself!