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

Project and organization settings overview page #321

Open
ericholscher opened this issue Mar 28, 2024 · 6 comments · May be fixed by readthedocs/readthedocs.org#12021
Open

Project and organization settings overview page #321

ericholscher opened this issue Mar 28, 2024 · 6 comments · May be fixed by readthedocs/readthedocs.org#12021
Assignees
Labels
Improvement Minor improvement to code

Comments

@ericholscher
Copy link
Member

When you click on Settings for a project, it should show you an overview of important things, instead of a list of random fields you don't want to change. I'm imagining something like:

  • Pageview & search analytics graphs
  • Toggles for PR builds, Privacy level
  • Links to ~5 most important settings pages as big UI buttons (Redirects, Domains, Integrations, etc.)
@agjohnson
Copy link
Contributor

I would maybe point to other form pages instead of duplicating form for toggling PR builds or setting project privacy level. A nice CTA would be a good addition for at least PR builds -- project privacy level is sort of a confusing setting though.

Another piece of data I'd like to start surfacing to users on this type of page is a monthly build time total for a project. We've also talked about this piece of data for subscription/organization level too.

@ericholscher
Copy link
Member Author

ericholscher commented Mar 28, 2024

Yea, build time would be a great "top-line" metric. I think the ads dashboards could be a good start, which are using inline metabase.

Screenshot 2024-03-28 at 12 52 56 PM

I could see:

  • Graph of builds, build time
  • KPIs of "Pageviews", "404s" and similar.

@agjohnson
Copy link
Contributor

A daily view could be really nice yeah. I also mostly want a place to start communicating "this project builds too often/takes too long/etc". There might be a way to do both with a daily graph, and it would look really nice in the dashboard too.

If we have an upper bound in mind, I was originally thinking a simple progress bar would be rather helpful -- a percentage view of average global/individual project monthly build time, total possible project monthly build time, or subscription month build time.

@ericholscher
Copy link
Member Author

Yea, I think a similar view on the organization settings page is probably a great additions step for any kind of larger billing stuff 💯

@agjohnson
Copy link
Contributor

Also, it might make sense to move the delete project form to the overview page as well. It's at the bottom of "Settings" now, so not super discoverable. It could make more sense at a more generic page like "Overview". This is what Github does too, with the "General" settings view.

@humitos humitos added the Improvement Minor improvement to code label Apr 8, 2024
@agjohnson
Copy link
Contributor

We talked briefly on this, it seems like a really awesome upgrade to the settings view so work we'd want to jump into. Namely, this feels like a great place to do feature marketing, and a later version of this can be adding new features -- metrics views and graphs/etc.

The primary initial focus would be more like marketing and helpful links for important features and focusing on onboarding instead of new features.

@agjohnson agjohnson added this to the New dashboard features milestone Jul 17, 2024
@humitos humitos changed the title Settings overview page Project and organization settings overview page Sep 12, 2024
@ericholscher ericholscher self-assigned this Feb 12, 2025
@ericholscher ericholscher moved this from Planned to In progress in 📍Roadmap Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Minor improvement to code
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

3 participants