Skip to content

[dash] Sidenav doesn't contain an entry for the bug-reports page #1628

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

Closed
chalin opened this issue Oct 31, 2018 · 8 comments
Closed

[dash] Sidenav doesn't contain an entry for the bug-reports page #1628

chalin opened this issue Oct 31, 2018 · 8 comments
Assignees
Labels
e1-hours Effort: < 8 hrs p1-high Major but not urgent concern: Resolve in months. Update each month.

Comments

@chalin
Copy link
Contributor

chalin commented Oct 31, 2018

This is the page: https://flutter-io-staging-1.firebaseapp.com/docs/resources/bug-reports

Should there be a corresponding entry in the sidenav?

@chalin chalin added the act.question Relates to issues that writers need SME help label Oct 31, 2018
@galeyang
Copy link
Contributor

galeyang commented Nov 1, 2018

@Sfshaza Do you know if we have multiple Contributing related pages like this? Do we need a place for all Contributing docs (like React)?

@sfshaza2
Copy link
Contributor

sfshaza2 commented Nov 1, 2018

This is a good page and I'd forgotten about it. I'd like to see this in the footer. File an issue, right in the footer. But if it has to go in the sidenav, I'd put it in resources.

In any case, it should be linked to from the community page, perhaps.

No, @galeyang, we have the contributing page, which is not displayed on the website, and the community page, which Daniel is working on.

@sfshaza2 sfshaza2 added the p1-high Major but not urgent concern: Resolve in months. Update each month. label Nov 1, 2018
@galeyang
Copy link
Contributor

galeyang commented Nov 1, 2018

I see. Thanks for the clarification!

@chalin
Copy link
Contributor Author

chalin commented Nov 1, 2018

This is a good page and I'd forgotten about it. I'd like to see this in the footer. File an issue, right in the footer.

We already have a page-specific "file an issue" button in the top-left corner of every page.

But if it has to go in the sidenav, I'd put it in resources.

Actually, come to think of it, we could place the page under /community, as in /community/bug-reports. We don't have to have the page appear in the sidenav, but it should be part of some nav (side- or main-nav).

Thoughts?

@sfshaza2
Copy link
Contributor

sfshaza2 commented Nov 1, 2018 via email

@sfshaza2
Copy link
Contributor

Still not there.

@sfshaza2 sfshaza2 added e1-hours Effort: < 8 hrs and removed act.question Relates to issues that writers need SME help labels Jan 30, 2019
@galeyang
Copy link
Contributor

We can probably add a link about the bug-report page to the community page where we invite people to request new features or report bugs.
image

@galeyang galeyang removed their assignment Sep 10, 2019
@parlough
Copy link
Member

parlough commented Jan 6, 2023

A link to this page in the sidenav was added under resources in #4378

@parlough parlough closed this as completed Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e1-hours Effort: < 8 hrs p1-high Major but not urgent concern: Resolve in months. Update each month.
Projects
None yet
Development

No branches or pull requests

4 participants