-
Notifications
You must be signed in to change notification settings - Fork 70
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 catalog-info.yaml #17341
base: main
Are you sure you want to change the base?
Create catalog-info.yaml #17341
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not know all the specifics of what is required by CODE VA, but if nothing else these files should not interfere with CMS operation.
Alright, I had a chance to look at this PR - I think we need to decide if we want to flesh out the side-nav a bit more. Based on the current implementation, it would only show the README.md file and none of the other docs that are in that repo. Also, I think the Thoughts on this @timcosgrove or @EWashb ? |
@CoryTrimmUSDS I agree. It looks like your solution provides a much better user experience. |
FWIW 100% agree, sidenav was on my todo 😁 |
Created more extensive `mkdocs.yml` based on the Table of Contents in the main `README.md` file.
va/tests/status-error:
|
Description
Relates to #issueid. (or closes?)
Testing done
Screenshots
QA steps
What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?
As user uid with user_role
Definition of Done
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing
Is this PR blocked by another PR?
DO NOT MERGE
Does this PR need review from a Product Owner
Needs PO review
CMS user-facing announcement
Is an announcement needed to let editors know of this change?