Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For discussion: Content updates for the Performance Team site #1226

Open
joemcgill opened this issue May 17, 2024 · 1 comment
Open

For discussion: Content updates for the Performance Team site #1226

joemcgill opened this issue May 17, 2024 · 1 comment
Assignees
Labels
Needs Discussion Anything that needs a discussion/agreement

Comments

@joemcgill
Copy link
Member

The Performance Team's site at https://make.wordpress.org/performance/ has been a great resource for us to publish evergreen content, like the yearly roadmap, our handbook — including articles about measuring performance, etc.

However, there are few updates I think we could try to make the site more useful.

  1. Change the front page: Like most team sites, this defaults to the latest posts on the team blog. However, we don't really use this feature since our meeting notes and other posts get published on the make/core site. Instead, I would propose that the front page be an intro into the purpose of the performance team, with some sections to promote our work—including the Performance Lab program, our roadmap, etc. This should be for an external audience but also point people to how they can get involved.
  2. Add a page that shares the purpose of the Performance Lab program: (I'm using the term "program" to be inclusive of all of our feature plugins, including the performance lab plugin that started the whole idea). There are times where it would be useful to send people to a landing page that gives an overview of what the Performance Lab program is, and list all of our feature plugins in one place. This would make for a much more useful link for the Author URI in our plugins (see Indicate plugins in list table which are installed by Performance Lab #1222).
  3. Move developer documentation: for contributing to the Performance Lab repo to markdown files in the repo itself, rather than maintaining that documentation in the handbook. Specifically, the getting started section, but it may also make sense to move the release process docs to the repo as well, as this would allow us to make updates to the docs in the same PRs where changes to the process are implemented (e.g., Improve readme command #1224).

I'd be happy to take on the work for these changes, but wanted to gather feedback before moving forward.

@joemcgill joemcgill added the Needs Discussion Anything that needs a discussion/agreement label May 17, 2024
@westonruter
Copy link
Member

Love this. At WordCamps we've directed people to that page but when I went there I didn't feel like it was very helpful at giving users an overview of what we're working on.

@joemcgill joemcgill self-assigned this May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Discussion Anything that needs a discussion/agreement
Projects
Status: Definition ✏️
Development

No branches or pull requests

2 participants