Web Page Audience Site Structure

This is a proposal for a new twiki.org site structure. Its content is derived from the Personas we created on WebPageAudience. Please see these topics for background information on the process. Work items are listed at TWikiOrgRenewalWorks2008ToDo.

High level site structure

These sections do not necessarily mean new webs. We can look at this the other way around: how can current Webs support the new structure?

• TWiki = About TWiki
  • About TWiki: general introduction and information how to deploy TWiki
  • Practical information: downloads, requirements, user documentation
  • 'System' information (installed plugins, technical details)
• Codev = Community & Development
  • Community pages: focus on contributing, who's who, learning TWiki (may contain current Blog)
  • Development pages: focus on programming; features
• Main = Users - only contains user pages
• Examples - new Applications web
• Plugins Extensions
  • XxxDev pages moved to Support, since most communication on extensions are support questions
• Support - should have clear linkage with DTO
• Sandbox - OK like it is. A link called "Try TWiki" would disappoint people coming here
  • Examples moved out to Examples web

Site structure in more detail

items in bold are menu items

• About TWiki
  • (link to News, Blog, etc)
  • What is TWiki?
    • Our Users
      • (Contains user quotes)
      • User Success Stories
    • Main Features
      • (link to Apps)
      • TWiki features by example
    • Compare
    • TWiki and Web 2.0
    • TWiki in the News
    • Download Cheat Sheet
    • TWiki Open Source Project (who runs this site?)
      • Roadmap
      • Contributing to TWiki
  • Considering TWiki
    • (link to Technical requirements), (link to Technical papers)
    • Integration with my Business
    • Cost, Maintenance and Support
      • (link to Support)
      • Getting Professional Support
    • Safety and Security
      • Security Notices
    • Introducing a Wiki in my Organization
  • Download
    • (link to Support), (link to WikiRing, TWIKI.NET), (link to Security Notices)
    • Latest Stable Release
    • Installer Versions
    • Known Problems
    • Older Versions
  • Documentation
    • (link to technical papers)
    • User Guide
    • Technical Requirements
    • Installation Instructions
    • Reference Manual
    • Technical Papers
    • Older Versions

Apps
(lists higlighted examples)

• Browse apps
  • (lists higlighted examples)
  • by name
  • by feature
  • by sector
  • by date
  • by company
  • by keyword
  • by (TWiki) release
• Add your app
• Request an app

Extensions
(point to extension support)

• Browse extensions
  • by name
  • by feature
  • by keyword
  • by (TWiki) release
• Developing extensions
• Discuss

Community

• News and Blog
• About the community
  • Who's who
  • TWiki Champions
  • User pages
  • Getting in contact
• Contribute to TWiki
  • How to contribute
  • Areas to contribute
  • Guidance
  • Getting code access
• Development
  • Vision and Timeline
  • Current Focus
  • Programming Reference
  • Programming Guidelines
    • Writing quality code
    • Writing quality docs
  • Code Repository
  • Feature Requests
  • Bugs
  • Development discussions

Support

• Tutorials
• Training materials
• Help with extensions
• Upgrading help
• Answers to questions
• Report a problem
• Getting professional support
• Offering professional support

Click trails of personas based on proposed site structure

Note that each page may address several personas. The page structure and text may support multiple user needs.

Industry Analyst

Picture	Name/Type/Occupation	Looking for	In format	Persuaded by
	Irma Andersen (33) Industry Analyst	Overview: what, how, who Comparison Usage News, trends	Cheatsheet News blurbs/blog posts User stories Pointers to other sites	Proof that TWiki addresses current needs (so I can recommend it to companies) A newsworthy story Great usage examples

Important to address persuasion arguments:

• Proof that TWiki addresses current needs (so I can recommend it to companies)
• A newsworthy story
• Great usage examples

Economic Buyer

Picture	Name/Type/Occupation	Looking for	In format	Persuaded by
	Eric Cedrof (48) Economic Buyer CEO	Confirmations, based on opinions of team members and snippets of information. How TWiki will improve the workgroups.	Structured, short documents. Management summary at the top, one subject per document. A mix of qualitative results (statements, experiences, stories) and numbers.	A tool that will solve his problem: better workgroup integration. Safe, mature and with support. Cheap to create and maintain.

Topic / Interest	Possible click trail
General overview of TWiki (Economic Buyer Point of View - to be elaborated)	WhatIsTWiki
TWiki Usage (In which ways is TWiki being used? To what use? In which environments? In which markets?)	WhatIsTWiki > OurUsers
User Success Stories	-- pages will be too long; preferably quotes; see for example http://twiki.net/customers.html --
Safety	SafetyAndSecurity > Safety
Costs, maintenance and support	ConsideringTWiki > CostMaintainanceAndSupport
Getting Professional Support	Support > GettingProfessionalSupport
Example Applications	-- won't go searching for real examples; a list of applications names with small pictures works better --

Important to address persuasion arguments:

• A tool that will solve his problem: better workgroup integration.
• Safe, mature and with support.
• Cheap to create and maintain.

Note:

• This person will not do the research himself. He needs to be persuaded by others.
• Structured, short documents. Management summary at the top, one subject per page.
• A mix of qualitative results (statements, experiences, stories) and numbers.

Infrastructure Buyer

Important to address persuasion arguments:

• Low cost (read: easy)
• Easy to install and maintain
• Secure

End User

Picture	Name/Type/Occupation	Looking for	In format	Persuaded by
	Ellen Uster (29) Tester / End User Senior at Communication and 'end user'	Compact introduction to TWiki: what does it do, how does it help. How does it fit in the Web2.0 landscape? Examples usage in other companies How support has been arranged How TWiki can be introduced in the organization	Concise introduction, complete. Written by humans for humans. User stories Pointers to support (how is this first impression?) Stories about introducing TWiki in the organization	Great usage examples Evaluation help Summarizing pros and cons to use with my report

Note:

• Concise introduction, complete. Written by humans for humans.
• Summarizing pros and cons to use with my report

Important to address persuasion arguments:

• Great usage examples
• Evaluation help

Potential Contributor

Picture	Name/Type/Occupation	Looking for	In format	Persuaded by
	Lasse Poven (24) Potential contributor Information management student	How to things work here, who is in control. A way to contribute with something significant. People to address, to connect to. A community center. Guidance, tips and advice.	Introduction to TWiki and twiki.org. Who runs what. Overview of areas to contribute. A place to discuss contributions. Pointers to people. Who is online? Faces.	Being wanted. Applying ideas that will be used by thousands of people.

Removed (too developer oriented):

Current Contributor

Picture	Name/Type/Occupation	Looking for	In format	Persuaded by
	Johan Curbain (32) Current contributor Independent consultant	Programming guidelines for core and plugins Programming reference Contributor centered information Contact with other contributors	Quality documents about/around programming (quick lookup) Contributor center	Being able to work efficiently Working with high quality code and docs Human touch

Wiki Champion

Picture	Name/Type/Occupation	Looking for	In format	Persuaded by
	Turan Chamer (31) The wiki champion Works in a IT company	How-to information (currently dispersed in TWiki, Codev and Support) Solution for upgrade problem Plugin version info: which one works in which version Training info Broad concepts as Security Ready-made TWiki apps. How to share TWiki apps. Sharing with other TWiki champions (to meet in person)	Central place for how-to information All issues reported by upgrading Plugins: clear TWiki version info, or alternative downloads for older versions Training material (note that current introductions are not focussed on bringing the concepts first) Repository of TWiki apps TWiki champion center	Grabbing great TWiki apps Painless upgrades, or being fully prepared Good training/tutorial material for users

-- Contributors: ArthurClemens, CarloSchulz - 25,27 Jan 2008

Discussion

Okay. So how does the site structure address the audience. What are is the most probable click trail for each type of visitor according to his needs/questions?

-- MichaelDaum - 13 Nov 2007

That's our next task. Mapping our personas to this site structure and see if we can easily address their needs or if we need to adapt this structure a bit further.

see the outcome of the discussion in TWikiMarketingMeeting2007x11x12 for a little bit more detail

-- CarloSchulz - 13 Nov 2007

I added some of the addressed personas. Not finished yet, though. Will continue tomorrow

-- CarloSchulz - 26 Nov 2007

Excellent work. What is the next step?

How can I help?

-- KennethLavrsen - 25 Jan 2008

That is indeed good work and I'm just adding a comment about the "Community" section.

Could other folks perhaps have a look at this page and tell me if you are as impressed with it as I am? For one thing it uses the phrase "get involved" rather than "community" which is far more active but also its so simple to see what's going on in the Ubuntu community. As I've said on other pages, I think there's a lot we can learn from their project.

-- MichaelCorbett - 25 Jan 2008

I already started with an overview of possible click trails for each persona from WebPageAudience. Will finish and publish today so we can talk about the next steps. There is really some work to do

-- CarloSchulz - 25 Jan 2008

MichaelCorbett: good input on the wording. Sounds defintely more attracting than just TWikiCommuninty... We need more trigger words like this!

-- CarloSchulz - 25 Jan 2008

There may be a difference between the words that are used to link (trigger words) and the actual page names.

-- ArthurClemens - 25 Jan 2008

Excellent work. I have refactored the click paths.

BTW I find it very hard to get an overview of the site structure with that Flash map.

-- ArthurClemens - 26 Jan 2008

I would like to create an overview now of the most important pages (besides the homepage) and the different perspectives on them regarding the persona motivations.

-- ArthurClemens - 27 Jan 2008

I have updated the site structure at #DetailedStructure.

-- ArthurClemens - 25 Feb 2008

What about her: Got it from Content Critical by Gerry McGovern. Anybody read his book?

-- MichaelDaum - 09 Mar 2008

"About TWiki > TWiki Open Source Project" and "Community > Development" are somewhat ambiguous. There's "Roadmap" on the former, however I'd expect "Roadmap" under the latter. I am not sure if the term "Considering TWiki" is that obvious of a choice for decision makers. What other wordings do we have? I don't get the overall site structure from the bullet lists above.

-- MichaelDaum - 03 Aug 2008

I have seen the "site structure" above as having more to do with navigation, menus, and content presentation than actual site structure (i.e., webs). I think the beginning of the topic actually says that. I do think that it might make a lot of sense to organize topics and webs based on the proposed presentation model. It would help a lot with the "everything-useful-is-in-codev-but-good-luck-finding-it" syndrome of the current TWiki. But, as more a presentation model, it seems likely that a few topics will likely find their way to inclusion in more than one grouping. The examples you give, Michael, seem like they might fit that description.

About TWiki > Open Source Project is a description (an About) of the who and how of TWiki. It borrows Roadmap from Community > Development and Contributing to TWiki from Community > Contribute to TWiki. I think there's a natural interest among those asking "What is TWiki" in those two items. That said, I do think that Roadmap does belong in Community > Development.

Does Considering TWiki just need a question mark? To me, it would make it more clear and connect it with the item before it, What Is TWiki?

-- DavidWolfe - 03 Aug 2008

Site structure is the structure of the site. It does not matter how you implement it, i.e. if you map a navigation onto TWiki's webs and subwebs. That's a rather crude web to (mis)use webs anyway, and even does not work out if the same content is reachable via multiple navigation paths.

Roadmap: where else if not under Development does it belong? Well, and Development is under Community right now.

In any case, a navigation structure should avoid as much as possible ambiguity and be as predictable as possible.

There seem to be more ambiguities. Maybe that's only because I can't see how the above high level site structure and the other detailed site structures come together. Can someone please create one single nested bullet list showing the navigation tree, please?

-- MichaelDaum - 03 Aug 2008

There is an inconsistency in the model: The first bulleted list says that Main will contain the user pages, but the second one list it under "Community".

There is something that is nagging me about this structure, but I could not put my finger on it.

-- RafaelAlvarez - 04 Aug 2008

I need to update the lists, because some things have changed underway. The 'real' high level structure is at the bottom of WebPageAudience. After that we have tried to fit the new groups into the existing web structure. Main web is still a bit problematic. It is not really used that actively on this site.

-- ArthurClemens - 04 Aug 2008