Closed brandtkeller closed 1 month ago
Name | Link |
---|---|
Latest commit | a69c8bc6b4804da0ca269239bd7831f52aac95a1 |
Latest deploy log | https://app.netlify.com/sites/tag-security/deploys/66344002ff89120008a1a41f |
Deploy Preview | https://deploy-preview-1245--tag-security.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Tagging @eddie-knight as it looks like they may have instituted the current state and I don't want to undo any work or plans.
Hey @brandtkeller, thanks for this. It does provide a good fix for https://github.com/cncf/tag-security/issues/1244.
I don't see any downsides to the Makefile iteration, and it moves us closer to refining the navbar content.
Closes #1244
Much more to do on the website - but this resolves a majority of the broken links identified in the linked issue.
I don't see support for utilization of a
root/
content directory in conjunction with the standardcontent/
directory for the website.Solution
Copy required files to the
website/content
directory in order to support resolving links from the homepage to other markdown files within the repository.Follow on work
Would be good to standardize the repository with what we intended to expose via the website. Rsync command was re-worked to essentially deny everything by default unless allowed.