Open josecelano opened 7 months ago
We observed that an existing link to https://secure-git.guide/014_Sharing-GitHub-secrets-with-third-party-actions/ is now 404. It was referred to in our docs, and we verify our links with lychee linter. The link became https://secure-git.guide/013_Sharing-GitHub-secrets-with-third-party-actions, but we cannot assume all the internet would change the links they point to.
https://github.com/oxsecurity/megalinter/pull/3172 https://github.com/oxsecurity/megalinter/actions/runs/7052989650/job/19199178930#step:4:1018 https://github.com/oxsecurity/megalinter/actions/runs/7072922624/job/19260950110?pr=3172#step:4:1906
See https://secure-git.guide/#articles
- Articles markdown number prefixes do not match the number in the HTML list.
- There are some missing articles.
- The markdown file name does not match the article title.
cc @da2ce7 @grmbyrn should we remove the number prefix?
I think we should include an article slug and put meta info in the markdown file like in the Torrust website (for example https://raw.githubusercontent.com/torrust/torrust-website/develop/src/routes/(blog-article)/containerizing-rust-applications-best-practices/%2Bpage.md).
I think the problem comes from the Curated List of Resources post. It was number 7 but it had been removed the posts displayed on the website. I put it in at the bottom. I think it could be a good idea to follow something like the Torrust website and would be open to implementing it if that's what you would like to do.
In all cases, to not break all the links to your articles online, you might need to keep the old URLs, or at least redirect them to your new structure ;)
We should use permanent redirects for the old URI's.
See https://secure-git.guide/#articles
cc @da2ce7 @grmbyrn should we remove the number prefix?
I think we should include an article slug and put meta info in the markdown file like in the Torrust website (for example https://raw.githubusercontent.com/torrust/torrust-website/develop/src/routes/(blog-article)/containerizing-rust-applications-best-practices/%2Bpage.md).