search

readthedocs / website

The Read the Docs community website
16 stars 6 forks source link

Content: add subproduct pages for user personas #43

Open agjohnson opened 2 years ago

agjohnson commented 2 years ago

We discussed branching off of the product page with several subproduct pages -- for developers, technical writers, management or operations, etc. We'll come back to these pages next, but it might help to start outlining what content these pages will have and what personas we feel are important to write for.

agjohnson commented 1 year ago

cc @ericholscher

This issue hasn't been thought out much yet, but these pages could be a chance to index and group feature listings and also get a bit more opinionated on SEO focus. The current features/workflow overview page is more for explaining RTD to users and might not drive traffic all very well.

Maybe general feature content is more important, or perhaps there isn't a whole lot of value overall in these types of pages too.

Any thoughts on if this seems worthwhile, or where we would start if it is? Perhaps with the operational/management type focus? We could be better about providing that narrative of all of our hosting features coming together for projects -- analytics, search, auth, etc.

ericholscher commented 1 year ago

@agjohnson aye -- definitely another good option. I've generally seen these called like "Solutions" pages or similar. I think Enterprise is probably a good place to start, perhaps? But agreed the "Management value" is another good place to sell our value.

agjohnson commented 1 year ago

"Solutions" is much better :+1: That will make for nice navigation structure on the top navigation -- "Solutions -> [For enterprise, For engineering teams, ...]"

Enterprise is definitely a overview page we could use. I know we usually struggle with selling the benefits of an enterprise level plan too, so maybe a more generally useful page is easier to start with too. But, both certainly work.