Tiki Community Audience and Objectives

This is a working page as part of Tiki Community 2021 Navigation Revamp

There are three parts here:

1. Who is the audience?
2. What can this audience gain from Tiki?
3. What Tiki can gain from this audience?

1.1. Someone evaluating Tiki

Someone that can decide his organisation needs Tiki or to be comforted in choosing Tiki.

To do a good job here, we need more granularity because there are so many variants.

Profile of person

• enterprise vs freelancer vs non profit vs government ...
• sysadmin vs developer vs entrepreneur vs manager vs graphic artist vs technical writer vs generalist...

Type of project

For own project vs a tool to deploy and help others vs a tool to build a service

What is person looking for?

• Is the person here for the mission? or the features? or both?
• A community project to avoid vendor lock-in
• A community project to participate in?
• To pay a vendor and have something that "just works"

c) For himself or for someone having the task of using Tiki (someone else chose for him)

Examples of questions to answer

• What problem(s) does Tiki solve?
• Who uses it?
  • Social proof
  • Inspiration (case studies)
  • Awards
• How rich it is ? (themes, web-components, ...)
• What solutions it fits the best (examples, working sites, etc.)
• How does it do it?
• How does it compare to other solutions?
  • (We should be very subtle )
    • Can you elaborate? What does this mean? And why?
• Who supports it?

1.2. Tiki site admin

This assumes Tiki already been chosen, and now a power user (Not a developer) is managing it

• How to install, ideally with a 1-click installer
• Where to host?
• How to get support? (free vs paid)
• How to report a bug?
• Custom theme
  • How can I make one?
  • How can I commission a specialist to convert a theme to Tiki?

What can site admin gain from Tiki?

• Leveraging Tiki better by learning from others
• Participate to the future of Tiki

What Tiki can gain from site admin?

• More feedback and volunteers to manage the project

1.3. New developer

This assumes Tiki already been chosen, and now a developer is involved. Knows how to code and we want to make it easy to turn into active contributor

• Where is source code?
• Where is Docker?
• How to make a merge request

What can new devs gain from Tiki?

• Can commit code directly in the core
• Work opportunities
• Participate to the future of Tiki

What Tiki can gain from new devs?

• Commits
• Help with development process (releases, etc)