What do people want on an OfficialSite?
- Personas
- For the average joe
- For developers
- For web designers
- For non-technical publishers and content creators
- For vendors of products that might create or consume Atom or support the Atom API
- For journalists and other members of the press
- Discussion
Personas
For the average joe
-
The joy of syndication: real stories
-
What is it?
-
How do I use it?
-
Why?
-
Demo / Tutorial
-
Glossary
-
News subscriptions (email and Atom)
-
Major news (once in a blue moon)
For developers
-
Introduction and fast-forward to what Atom really is
-
Technical Glossary
-
Specs and other documentation
-
Community
-
Technical Support
-
Wall of Credit
-
News subscriptions
-
Major news
-
File format updates
-
API updates
-
discussion and blog
For web designers
-
How users think about syndication
-
Graphic resources
-
Advanced techniques: XSLT and other cool tips
-
News subscriptions
-
Design updates
-
The design blog
For non-technical publishers and content creators
-
What Atom is and why you should care
-
How hard and costly is it to support Atom?
-
How is Atom used?
-
Publication case study
-
Intranet case study
-
Government case study
-
Issues and concerns
-
Atom vs. RSS
-
News subscriptions
-
Major news
-
The manager's blog
-
Where to go for help (consultants and advisors)
For vendors of products that might create or consume Atom or support the Atom API
-
Potential vendors
-
Why support Atom? And other FAQs
-
Advantages of registering to be Atom-Friendly
-
Now Supporting
-
Registration form
-
Directory of Atom-friendly products and services
-
News subscriptions
-
Changes to your profile
-
Inquiries about your product
-
Changes to the program
For journalists and other members of the press
-
Contacts and bios
-
FAQ
-
Photos and videos
-
Contact form
-
News release archive
-
Endorsements and other quotes
-
Atom seen in the news
-
Stats: Latest estimates on the number of Atom feeds, posts, users
Discussion
Specs and other documentation [AsbjornUlsberg] Needs to be extremely simple laid out, and as "all-at-the-same-place" as possible. Extarnal linkage, new page designs to get familiar with, and not to mention (text-only) specifications, are as scary as Emacs is to a Visual Studio developer. Sam Ruby has some ideas on this which is materialized in e.g. the Survival guide to i18n (although I find the title a bit too "scary"