-
Notifications
You must be signed in to change notification settings - Fork 89
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
Get feedback on current new go_refs page #2255
Comments
Will need @pgaudet feedback. |
@pgaudet also floated ToC pager, and then linking to individual pages. |
Decision: individual pages + ToC page |
Also, there needs to be a link tot SoT (somewhere), so users that want to search through everything can do so. @pgaudet , can you define whether to do this on each page, or just on the ToC. |
The source of truth (SoT) yaml file is an internal documentation, I propose to put a link in the wiki under the Annotation group documentation. OK ? |
|
@pgaudet @vanaukenk Noting that this is not yet the SoT and will not be until Patrick's go-ref project is completed. He will do a final sync to re-match things before switching over, but be aware that the old SOP is in place until that happens. |
Looks good to me. @pgaudet, do you have any feedback here? |
Looks good. I have one feature request : to have OBSOLETE refs in a separate section at the bottom. But if that's complicated we can drop it. Not a requirement for this work. Thanks, Pascale |
No that's not complicated at all, will do. |
This seems to be all done? Can this ticket be closed? |
Yes I'd say so |
As the new page assembly gets put together, we want to make sure that it is acceptable to users.
The text was updated successfully, but these errors were encountered: