Triggers for this work are: - https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject.org/thread/TQERUXSDITSUZH2RNPADAFKKWETNE46F/ - https://pagure.io/fedora-infrastructure/issue/6397
Make Fedora resources / assets easier for anyone to locate via search engines by engaging in search engine optimization (SEO) for our user-facing web presence.
In order to conduct SEO properly, we'll need to come up with an inventory of those things we want to ensure come up in the results - what are the terms / keywords of interest, and what pages do we want to appear prominently for each? A suggested approach to determining this is as follows:
Create a task list of things we want our target audience (https://fedoraproject.org/wiki/Workstation/Workstation_PRD#Target_Audience is a good one to go with) to be able to do with the website(s). (marketing team, websites team, design team)
Test the tasks in the task list with our current sites against a representative sampling of our target audience; see what users search for / how they approach it and note it. (design team)
Use the data collected in testing to develop the inventory of keywords to optimize, creating a matrix of keywords to the Fedora URLs we would like to promote for each keyword. (marketing team)
For this ticket, we should work to come up with the task list noted in #1 above.
This is a straw man. Let's discuss :)
(copied from https://fedoraproject.org/wiki/Workstation/Workstation_PRD#Target_Audience)
Programming Environment: web languages and tools, open source databases, IDE, Compilers, debug tools, performance monitoring
Desktop apps should be sufficient to make this system the user's only computer. Users should not be required to be familiar with the terminal or to use the terminal for essential tasks, including software development.
Engineering/CS student who needs a personal system for software classwork and personal projects. Software class work may require particular tool chain versions. Tries out new versions of open source applications when released. Uses computer to play games. Ability to play 3D games from commercial publishers distributing games for Linux. Multiple developer environments i.e. school standard for class work, latest tools for personal use.
Personal development system for an independent software developer doing contract work or developing apps for a new opportunity.
Desktop Apps: Up to date desktop with email client, browser, productivity suite, messaging, and a complete set of desktop apps and utilities. Desktop apps should be sufficient to make this system the developer's only computer.
Generally a single development environment with the latest web development tools.
Easy to configure Virtual Machines for testing software.
Software developer working on an individual project or coordinated small team. DevOps.
Generally a single development environment with the latest web development tools. Easy to configure Virtual Machines for testing software.
Testing in local VMs and on dedicated testing systems.
Software developer working on a large, coordinated project in a large organization.
Support for enterprise login. Multiple developer environments i.e. current project and maintenance work on older projects. Testing typically on a target system in a testing lab.
While our focus is on creating a top-class developer workstation, our developer focus will not compromise the aforementioned goal to be a polished and user friendly system that appeals to a wide general audience. In fact, many of the changes and improvements we expect to implement for developers will be equally beneficial to other user segments. For instance our plans around multi-screen handling and improved terminal functionality should also be highly beneficial to a system administrator. Or the work we are doing to provide a high performance graphics workstation would be useful to people who want a Linux gaming PC. Or a student who just wants a system with a productivity suite to write papers will of course get benefit from the fact that we do ship a good productivity suite. We welcome feedback and requests from all our users and will consider accommodating it when possible.
Thanks -- this is great!
We should also include https://fedoraproject.org/wiki/Atomic/PRD#Target_Market_.2F_Audience (and ask Atomic WG to expand on that if it's not sufficient for this purpose) and also https://fedoraproject.org/wiki/Server/Product_Requirements_Document#User_Profiles.2C_Primary_Use_Cases_and_Goals (but that probably also needs a post-Modularity refresh).
We also have target audiences for the project which are different from the target audiences for the editions.
@mattdm the project wide audience i could find is marked out of date, can you confirm its the latest or if there's another one we should be looking at? https://fedoraproject.org/wiki/User_base
I dont know that server personas need a refresh bc of a tech change - user problems are presumably the same
@mattdm ping
@duffy In the new mission, the project target audience is "software developers and community members" — that is, people building the platform and people building on the platform. Then, various approved subprojects (like the editions) have their own target audiences (which are generally expected to be more user-focused).
@mattdm is there a specific canonical reference where that can be found and referred to?
The mission and foundations page will be at:
https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html
as soon as that moves from staging, where it is live now.
Further detail seems appropriate for the marketing strategy document (issue #262), which I hope to make time to work on in early November. (With more people than just me.)
Metadata Update from @bt0dotninja: - Issue marked as depending on: #262
Metadata Update from @x3mboy: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.