Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 2005-12-20 11:32:27
- Kosmo
- Member
- Registered: 2005-10-06
- Posts: 22
Re: A way to handle articles as pages
Actually, the problem from the beginning wasn’t the article, or the content of the article, or how the contect was presented.
TXP has about a million ways to manipulate the content, but not even a single way to manipulate my navigation. A problem that 99% CMS’ have.
But I guess that I have to code the navigation by hand because it isn’t generated automatically in any way.
Offline
#14 2005-12-20 22:33:35
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: A way to handle articles as pages
Kosmo:
“…but the TXP information and manuals are way too scattered to be useful for your average user that doesn’t have time to go through several different sites and articles to gather information.”
Uh, there is only one site. In fact, the tag list page is insanely helpful.
There probably is a way to get what you want, and without doing it by hand, but I don’t really know what the look you’re after is. In fact, I don’t think anyone else does either, so we’re stuck with wild guesses. Can you describe how you want your section to look/behave?
Offline
Re: A way to handle articles as pages
<blockquote>Uh, there is only one site.</blockquote>
Well, to be fair, <a href=“http://www.textpattern.com/faq/”>the FAQ</a> is hosted elsewhere.
And I’m with Mary—examples and/or in-depth descriptions would be a big help.
Offline
#16 2005-12-21 09:42:52
- marknumberm
- Member
- From: Minneapolis
- Registered: 2005-11-29
- Posts: 46
Re: A way to handle articles as pages
I agree with Mary that the tag list page is a very helpful way to dive in and start learning textpattern. Just choose a few at random and start reading them. It’s oddly fun…
The FAQ and some other things handle pretty well the quesitons that lots of people have in common. (How do I make a static page, for example.) And the thing about examples and in-depth descriptions is that once you get beyond the most basic level, not very many people are trying to do exactly the same thing.
So an in-depth description about what I’m trying to do with textpattern probably won’t help you because you’re trying to do something different. I might still write a tutorial or some documentation on what I end up putting together, but it might be better housed somewhere on my site, or briefly written up on this forum.
Just some thoughts…
Offline