TxP.com home page

zero · 2008-09-20 18:09:46

Jonathan, after my initial shock at the disappearance of so many words, I now like what you’ve done. Direct, to the point, no fluff.

Kevin, I only foresee a few features listed on the home page, the rest available at a click (but still on the front page). Features are also available here which you can see is arranged quite differently with different headings. I see this one as the basis for the inner page. The wording is different from features on the front page, with just a few similarities, so no duplicate content but twice the seo, findability and persuasiveness, imho.

Last edited by zero (2008-09-20 18:14:21)

jstubbs · 2008-09-20 18:13:19

Bloke wrote:

Nice work. Might I suggest using the word ‘arrange’ instead of ‘presentation’? The reason being that the other initial words in bold are more things you can do with it, whereas ‘presentation’ is like a feature of the system. So if you then read the words down the list one by one, they are all action-based and roll off the tongue nicely. Of course, ‘arrange’ might not be the right word either, so if anyone has anything better, fire away.

Made another couple changes in line with your comments – Content becomes Publish while Presentation becomes Present.

Better?

jstubbs · 2008-09-20 18:16:23

zero wrote:

Jonathan, after my initial shock at the disappearance of so many words, I now like what you’ve done. Direct, to the point, no fluff.

Peter, that was the purpose – partly because the direction was unclear, but also because Textpattern is about elegance and simplicity, and the wording and presentation should support that.

kvnmcwebn · 2008-09-20 18:17:27

one features page for each user target, thats as good a way as any to organize it.
Also: For a great overview of txp read page 124 of solutions.
-best
kevin

zero · 2008-09-20 18:19:08

Jonathan, when I first used breeze I wondered how well known it was internationally, so perhaps there’s something better for that (particulary as it will be part of the first content that is read).

Kevin, Bloke – for the record I don’t agree about a separate features page for each audience. The audiences are not so separate as that and the division is a bit artificial. That’s why I think it’s ok on the front page to give a focus, but to have to look at 3 separate features pages in order see all the features is not user friendly. The original feature list page (with appropriate updating) targets all users at once.

Last edited by zero (2008-09-20 18:26:46)

jstubbs · 2008-09-20 18:52:22

Peter, I removed “breeze” and replaced it with “simple and easy”. It is, so that should be fine for now.

For the record, I agree with Peter that only one Features page is required. How the features are presented on the front page is another matter altogether – it makes sense to directly address users who identify themselves as a publisher, developer or designer.

kvnmcwebn · 2008-09-20 19:48:07

*zero wrote: about a separate features page for each audience. The audiences are not so separate as that and the division is a bit artificial. That’s why I think it’s ok on the front page to give a focus, but to have to look at 3 separate features pages in order see all the features is not user friendly. The original feature list page (with appropriate updating) targets all users at once.*

to be honest that was my initial reaction as well, but then i thought if there was going to be a really long page of features than i would rather be able to find what i was looking for right away. But now that i think about it there would probably be a lot of overlap. right one page is enough.

maniqui · 2008-09-20 21:05:11

I would think it the other way: audiences are “naturally” separated: publishers != designers != developers. Sometimes those roles are all (or two of them) played by the same person. The “artificial” thing is to separate TxP features and list them under different audiences. Of course, there are some features that are more appealing for a particular audience, and that’s what we have to emphasize on homepage.
Then, there are a common set of features that are of common interest for all audiences.

So, regarding how to reflect/organize this on inner pages, I would suggest some ideas thay may be positive from a SEO POV.

first, to have a section named /features/, and its content could be:
- a little intro paragraph (a sticky article) with:
- a short list of interesting features aimed to any audience
- then, below, three subheadings+excerpts, doing the same separation than in homepage:
  - For web publishers, followed by a short paragraph and list of features of interest for web publishers
  - For web designers, idem
  - For web developers, idem

Those three subheadings+excerpt could be managed using 3 different TXP articles, which will allow us to:

have three permlinks (individual articles) like this (please, think about better, richer URL-only-titles):
- /features/a-cms-for-web-designers (or better: /features/a-flexible-content-management-system-for-web-designers)
- /features/a-cms-for-web-publishers (or better: /features/a-easy-to-use-content-management-system-for-web-publishers)
- /features/a-cms-for-web-developers (or better: /features/an-extensible-content-management-system-for-web-developers)
this will allow us to create better content (an attractive excerpt, then a better body) and to aim better to each audience on a individual-article/permanent-link context without cluttering the /features/ section nor the homepage.
the usability/marketing/SEO benefits are immediate.
the SEO benefits will come from many factors:
- better/easier achievement of common SEO task, like having a good/great meta description for each audience (on its particular permalink, see above), so on a SERP, Textpattern will stand out better.
- better/deeper crawling of better/richer crafted content
- keyword rich / attractive / human-readable URLs that stand out even on SERPs.

@All: I’m pretty confident about this: we could easily (well, not easily, it’s a lot of effort, but it isn’t voodoo) dominate/influence organic SERP for relevant searches. We have Textpattern, the CMS that makes it easy to create better content, and makes it easy to do the SEO tasks (rah_metas and rah/jmd_sitemap are our friends here), so we let’s take advantage of this momentum we have gained and start building the f***ing d*mn thing right now.
I’m for the opinion that we don’t need to have the visual aspect defined to start working on some technical tasks as: install a new Textpattern on dev.textpattern.com, install the needed plugins, load the content, creating some basic mark-up, etc.

That’s one of the beautiful things of this create-a-website game using HTML+CSS+TXP: to separate the content from the presentation.

(sorry for my english)

Last edited by maniqui (2008-09-20 21:08:09)

redbot · 2008-09-21 03:01:52

Ehm, I know I’m too late but I would divide “present” in:

“organize” (unlimited sections and categories)
“style (or something similar)” (txp outputs standard-compliant tableless code etc etc …you decide how your site will look).
Of course this should be written better. I just wanted to say IMHO sections and categories are different from visual presentation (even if in in txp – wrongly – they’re under the same tab called “presentation”).
Obviously this is only my opinion.

jstubbs · 2008-09-21 08:15:27

I edited the promo space a little to add redbot’s suggestion, and also edited the other bullet points.

Bloke · 2008-09-21 08:31:39

jstubbs/redbot

Nice, reads well. Good job all.

maniqui

Cunning. I like the cut of your jib, as Mr Burns might say. Having three articles + a sticky on an article list ‘features’ page is a great idea for all the reasons you state and more. Four times the SEO and cuts down on scrolling through swathes of features without inconveniencing users too much.

It delivers a focused, targetted message but with enough “while you’re here it can also do this” on the same page to dangle the delicious carrot of enticement. And of course the individual features pages would also have “related articles” links (i.e. the excerpts) to the other features pages which means you don’t lose visibility of the features for all three of the arbitrary “roles” we have targeted.

I agree we have enough to start building the content, so let’s build.

Last edited by Bloke (2008-09-21 08:33:06)

zero · 2008-09-21 11:35:56

I’ve been working on the features. What you see on the Home page is a sentence with features common to all audiences at the top (nicely written by Jonathan) followed by the complete list of features for each of the 3 audiences. Note that the list is not all that long.

What you see on the Features page are the same features but worded differently so there is now no duplicate content. I’ve also rearranged them to suit what I think visitors will look for in a feature list – something relevant to them. Publishers, designers and developers are catered for but using different headings. Note that if the page is two columns all these features would be seen without scrolling, so it’s not like there’s lots to wade through. The headings should direct the eye too. (I’m open to different headings suggestions of course).

If anyone wants to split up the features page, please copy it here first and then rejig it, leaving what I’ve just done alone for the time being.

Textpattern CMS

Textpattern CMS support forum

#253 2008-09-20 18:09:46

Re: TxP.com home page

#254 2008-09-20 18:13:19

Re: TxP.com home page

#255 2008-09-20 18:16:23

Re: TxP.com home page

#256 2008-09-20 18:17:27

Re: TxP.com home page

#257 2008-09-20 18:19:08

Re: TxP.com home page

#258 2008-09-20 18:52:22

Re: TxP.com home page

#259 2008-09-20 19:48:07

Re: TxP.com home page

#260 2008-09-20 21:05:11

Re: TxP.com home page

#261 2008-09-21 03:01:52

Re: TxP.com home page

#262 2008-09-21 08:15:27

Re: TxP.com home page

#263 2008-09-21 08:31:39

Re: TxP.com home page

#264 2008-09-21 11:35:56

Re: TxP.com home page

Board footer