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

Create feature pages for every feature #611

Open
3 tasks
mxkaske opened this issue Jan 30, 2024 · 3 comments
Open
3 tasks

Create feature pages for every feature #611

mxkaske opened this issue Jan 30, 2024 · 3 comments
Labels
👥 Core Team Prioritized for core team 🚧 Informations missing Not enough to start with

Comments

@mxkaske
Copy link
Member

mxkaske commented Jan 30, 2024

Description

To better showcase our features, we want to have a /feature/[name] path with more details. It will also improve our SEO. Our three main pillars are:

Monitoring

  • continuous monitoring
  • custom requests
  • response header / message (on error) / timing phases
  • speed checker playground
  • ...

Status Page

  • tracker
  • status report
  • status subscribers
  • ...

Incident

  • notification if >50% of the regions fail at a speficic cron timestamp
  • notification channels
  • ...

Design is missing, but using our bento box design including the Shell and grid will help to easily come up with some ideas. We should use screenshots to showcase the dashboard

Also, we can have some shared components for every feature placed probably more at the bottom of the page.

Note

Will be edited over time!

TODO:

  • create a /features/[slug] page
  • create new components (tbd)
  • write copy
@mxkaske mxkaske added 👥 Core Team Prioritized for core team 🚧 Informations missing Not enough to start with labels Jan 30, 2024
@skushagra9
Copy link
Contributor

I am interested to work on this, please assign me

@mxkaske
Copy link
Member Author

mxkaske commented Jan 31, 2024

Hey @skushagra9! Thanks for your interest.

Please read the labels carefully, as well as the description. Not everything has been defined yet, so it is not ready to be worked on. Also this will most likely taken by the core team.

We have started to migrate from a more private project management tool Linear to GitHub project, which will then be fully public. It's a first experiment and we are figuring out how to combine tickets for contributions.

Cheers.

@skushagra9
Copy link
Contributor

Okay, got it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👥 Core Team Prioritized for core team 🚧 Informations missing Not enough to start with
Projects
Status: No status
Development

No branches or pull requests

2 participants