[DRAFT] UI redesign
Pre-merge checklist
If you work at Sentry, you're able to merge your own PR without review, but please don't unless there's a good reason.
- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs
- [ ] PR was reviewed and approved by a member of the Sentry docs team
Description of changes
a wip branch to implement the new design
related #9369
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| sentry-docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | May 7, 2024 1:27pm |
@a-hariti this is a good first step!
Here are some changes we'd need to make in order of priority:
-
we would like to see an option of the platform dropdown that has both the languages and the frameworks as in this image:
-
we want to get rid of the separate product nav and move it so that it lives persistently even when users choose their SDK. (As a next step we'll need to reorganize the folder structure of the product docs, but we can do that a bit later.)
-
Python frameworks currently live in the "integration" section of docs, we'd need to make sure they are also visible in the dropdown.
-
Would like to see an option where there are 2 dropdown selectors, one for language and another for framework:
-
We don't need to worry about this right now, but of course we'd also need to update the colors/font styles etc. to reflect the new design:
Can the nested dropdown and two drop downs (for platforms & guides) coexist @lizokm ?
@a-hariti I don't think it makes sense for the nested dropdown and the two drop downs (for platforms & guides) to coexist. It should be one or the other.
Also, I resolved a conflict that may have led to more conflicts in the sidenav. Are you able to see the previews?
Yes, I can see the previews.
Thank you. I think you accidentally left a foreign string during the conflict resolution 🙊, I'll take care of it
Bundle Report
Changes will increase total bundle size by 629.32kB :arrow_up:
| Bundle name | Size | Change |
|---|---|---|
| sentry-docs-server | 7.42MB | 259.74kB :arrow_up: |
| sentry-docs-edge-server | 456.19kB | 13.27kB :arrow_up: |
| sentry-docs-client | 6.2MB | 356.32kB :arrow_up: |
@lizokm should the python integrations be converted to guides in the docs or should we just change to the way they are represented in the UI?
The second option will add some hardcoded logic for python in the code base
@stephanie-anderson @antonpirker would love your thoughts here: should the python integrations be converted to guides in the docs or should we just change to the way they are represented in the UI?
The second option will add some hardcoded logic for python in the code base
Deployment failed with the following error:
Could not parse File as JSON: vercel.json
You must have Developer access to commit code to Sentry on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes.
Learn more: https://vercel.com/docs/concepts/teams/roles-and-permissions#enterprise-team-account-roles
Deployment failed with the following error:
Redirect at index 1 has segment ":__UN_NAMED_SEGMENT__" in `destination` property but not in `source` or `has` property.
Learn More: https://vercel.link/invalid-route-destination-segment