-
Notifications
You must be signed in to change notification settings - Fork 2.6k
frameless-node-template link resolves in 404 #14629
Comments
I think it was asked to be hidden during the academy or something like that. |
I like the idea of Tuxedo |
cc @nukemandan Gatekeeping that content broke the Substrate docs and people noticed immediately. By making content closed we are preventing people from learning Substrate. |
As discussed internal to the PBA, this needed to happen for this moment because this repo was build for PBA to use as a graded assignment in full or in part. All graded assignments we must keep private by policy for now because we don't want solutions to leak (primarily). As it is presently unclear what aspects are to be gradaed from this repo, it needed to be hidden till those aspects are removed completely. Word from our director on this issue:
So after the PBA we can work to bring back this in some form. 😀 |
Also @JoshOrndorff if you read your own student roster, you will find all people in this issue are in now, or have been at the Academy. |
Thanks for replying so swiftly. :) |
I think this highlights a larger issue where we are unaware when doc links become broken, which really should be avoided. @kianenigma maybe you have already considered such tools in your docs overhaul effort, but it seems we should add something like a CI job that runs a tool like https://github.com/deadlinks/cargo-deadlinks ? |
The PBA3 assignment is over and I've made the repo in question public again. It will remain public henceforth as far as I'm in control of it. |
Glad to see this resolved; But, I'd still leave this open to introduce a link checker for external links to our repo. |
Yea its quite annoying. Added paritytech/polkadot-sdk#134 and paritytech/polkadot-sdk#993. |
substrate/src/lib.rs
Line 75 in ac9c1c2
Hey @kianenigma ,
It looks like the
frameless-node-template
has been removed recently.Should this link be replaced with the Tuxedo repository or is the node-template available somewhere else?
The text was updated successfully, but these errors were encountered: