Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
[wiki] Welcome to Your Site!
What do you want to do next?
- Modify or even delete this article? The article list is the place to start.
- Change this site’s name, or modify the style of the URLs? It’s all up to your preferences.
- Get yourself acquainted with Textile, the humane web text generator which comes with Textpattern? The basics are simple. If you want to learn more about Textile, you can dig into an extensive manual later.
- Be guided through your Textpattern first steps by completing some basic tasks?
- Study the Textpattern Semantic Model?
- Add another user, or extend the capabilities with third party plugins you discovered from the central plugin directory at Textpattern Resources?
- Dive in and learn by trial and error? Then please note:
- When you write an article you assign it to a section of your site.
- Sections use a page template and a style as an output scaffold.
- Page templates use XHTML and Textpattern tags (like this:
<txp:article />) to build the markup.- Some Textpattern tags use forms, which are building blocks for reusable snippets of code and markup you may build and use at your discretion.
There are a host of Frequently Asked Questions to help you get started.
Textpattern tags, their attributes and values are as well explained as sampled at the Textbook Wiki, where you will also find valuable tips and tutorials.
If all else fails, there’s a whole crowd of friendly, helpful people over at the Textpattern support forum. Come and pay a visit!
Offline
Re: [wiki] Welcome to Your Site!
The immediate problems are that Textpattern First Steps has been deprecated and the Textpattern Semantic Model is still a work in progress, which doesn’t necessarily mean the work needs to be done here. But what else is there that might be updated/changed/improved?
Offline
Re: [wiki] Welcome to Your Site!
You mean when installing a new site, you see this dialogue and links, right? Yes, I’ve noticed it too, it’s two-sided problem. On one side there’s nobody on the “team” side of things who’s’ main objective is to look at content, messaging, etc from inside the machine out (which is really the devs’ territory, the machine). The other side of the problem is that there’s so much to tackle on the outside (e.g, user docs) that it’s hard to keep focused on any one problem area and get it caught up. E.g., I’m itching to get back to the FAQ audit and rewrite those buggers into the user docs where they should be, but I’m so dang busy with real life I can’t get to it yet. But I will!
Any case, keep pointing this stuff out, Michael. It’s needed to help bring attention to it. Good man.
Offline
Pages: 1