Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2006-07-15 13:39:01
- Ray
- Member
- Registered: 2004-03-02
- Posts: 159
Large production site on Textpattern. Your thoughts.
Looking for input from the txp developers and hard core users.
Anyone know of a large production site using textpattern as the CMS?
I’m considering moving a potential client away from a rather expensive enterprise package and putting them on a Textpattern install. They’ve been around for 10 years, have just shy of 10,000 articles, aprox 50 sections (with another 20-30 sub-sections/directories), three primary editors and a couple dozen writers. They get about 800,000 page views per month. There will be NO need for any plugins.
Offline
Re: Large production site on Textpattern. Your thoughts.
Pageviews shouldn’t be a problem.
I have a site with about 2.500 (mostly long) articles on a shared hosting account and never had any issues (There’s also 2-3 dozen editors). IIRC I had some tests running last year with tens of thousands of messages, without any measurable difference to a resh, small site. And there is not reason why there should be (especially if you do not use plugins).
Sections shouldn’t be a problem. I don’t know how you did sub-sections, so I can’t comment on that.
All in all I don’t see anything that should stop you. Of course measuring and testing is a must, but IMHO you should go for it.
Offline
#3 2006-07-15 19:12:06
- Ray
- Member
- Registered: 2004-03-02
- Posts: 159
Re: Large production site on Textpattern. Your thoughts.
The sections and sub directories are going to be the major issue. Right now they have sub-directories going six deep. I’m hopeing they’ll consider reorganizing and consolidating all their content into maybe 70 sections and moving away from the sub/sub/sub-directories. This will of course require some Apache voodoo to satisfy the search rankings and bookmarks (Dear God help me) but it’s manageable.
My primary concern was… can Textpattern handle a site this size with a fairly steady amount of traffic. I think you’ve answered my question quite nicely. If there’s anything I should be considering please let me know. Thanks Sencer.
BTW… average word count per article is 740. So, the articles aren’t much of a problem. Graphics can be a bit intense (only in some sections) but again… it’s manageable.
Danke schön!
Offline
Re: Large production site on Textpattern. Your thoughts.
Would be interested in reading a regular report on this project, Ray, (monthly or so at your Web site) just to see how you tackle things and all. This is the terrain I think many other people have wondered at one time or another. I had a potential large project (link is now gone) once, but it never materialized. Still, you never know. ;)
Offline
Re: Large production site on Textpattern. Your thoughts.
Simple. Turn off logging. Your TXP install will be more efficient than Wordpress (and that currently handles a lot of traffic for many sites…)
Offline
Re: Large production site on Textpattern. Your thoughts.
Loging on or off has a negligable effect on performance.
Last time I tested (been a while) Textpattern handled high traffic better than Wordpress out of the box – of coure with caching plugins the serving of cached pages is similar across most systems.
Offline
#7 2006-07-27 12:50:31
- Murk
- Member
- Registered: 2006-07-22
- Posts: 12
Re: Large production site on Textpattern. Your thoughts.
I’ve successfully put together two small test sites on a local server to become familiar with Textpattern. I have two web projects and I’m trying to determine if TxP will make my life easier.
1. I want to put a 300 page cookbook online (we own the rights). Lots of static info, pages of recipes and we’d like to have blog on the main page, along with static info. This project looks doable in TxP.
2. We also own a legacy site (but still a PR7) from 1994 that has ten thousand or more pages, all static, hand-coded HTML. We want to convert this site over to TxP. Same plan — use TxP to add a blog to the existing static pages. The plan would be to add new weekly content via TxP first and slowly convert the legacy pages as time permits.
Looks like using ID tags might help organize the material for both sites.
My concerns:
The TxP interface for small sites is fine though the small fields are ludicrous—I just download Mary’s redesigned interface to see if it addresses that issue. But since this site has hundreds of sections and pages, my lists could become unmanageable. I assume categories will help but when we reach thousands of pages, I see myself doing a lot of scrolling through lists. Perhaps I missed something since I’m a newbie…
Also, as someone posted above, I must keep the current URLs on the legacy site due to indexing by search engines. The poster above talks about using Apache voodoo. Not being an American Indian or from Haiti, what kind of voodoo are they talking about? : )
Thanks,
Murk
Offline
Re: Large production site on Textpattern. Your thoughts.
You should try to move your legacy stuff and all new content into articles, not pages. Pages serve merely as “templates” for sections when displaying articles. If you need to create more than dozens of pages, you are probably doing thigs the wrong way. (I am using between 2 and 6 pages for sites that have thousands of entries).
But all your questions seem to be about migration, not so much about running large sites in general. A different/new topic will probably better for your needs.
Offline