-
Notifications
You must be signed in to change notification settings - Fork 55
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
Change cni.dev version scheme #76
Comments
I think the folder method is probably the right choice; I don't see us localizing anytime soon, but we definitely will be cutting versions semi-frequently. |
Changing from a URL based to a folder based versioning scheme. Fixes: containernetworking#76 Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
[edit] comment moved to description. |
Changing from a URL based to a folder based versioning scheme. Fixes: containernetworking#76 Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
- Changing from a URL based to a folder based versioning scheme. - Add link checker command to Makefile - Updating navbar-version-selector's dropdown menu to link to the top level of a version if the specific file does not exist - Updating links throughout Fixes: containernetworking#76 Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
- Changing from a URL based to a folder based versioning scheme. - Add link checker command to Makefile - Updating navbar-version-selector's dropdown menu to link to the top level of a version if the specific file does not exist - Updating deprecation warning - Updating links throughout Fixes: containernetworking#76 Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
- Changing from a URL based to a folder based versioning scheme. - Add link checker command to Makefile - Updating navbar-version-selector's dropdown menu to link to the top level of a version if the specific file does not exist - Updating deprecation warning - Updating links throughout Contributes to: containernetworking#76 Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
- Changing from a URL based to a folder based versioning scheme. - Add link checker command to Makefile - Updating navbar-version-selector's dropdown menu to link to the top level of a version if the specific file does not exist - Updating deprecation warning - Updating links throughout Contributes to: containernetworking#76 Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
I don't have any analytics access -- do we know if people are visiting the previous versions now? I'm curious because we may want to change the feature branches that point to the new versions system instead of deleting them entirely -- turn them into redirects to preserve bookmarks. We maybe able to do this on the Netlify side so we don't have to maintain the feature branches here. |
- Changing from a URL based to a folder based versioning scheme. - Moving from 3 digit to 2 digit version number scheme - Add link checker command to Makefile - Updating navbar-version-selector's dropdown menu to link to the top level of a version if the specific file does not exist - Updating deprecation warning - Updating links throughout Contributes to: containernetworking#76 Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
Now that PR #80 has been merged in, we can bring down the Netlify sites, and delete the feature branches for the versions. Netlify sites that need to be brought down:
@zacharysarah, @caniszczyk, @squeed, I don't have the Netlify admin permissions to delete these sites, and suspending them isn't an option. Who is the best person to bring down these sites? |
@squeed as the feature branches for the versions are protected, I'm not able to delete them. Feature branches to be deleted:
|
the sites should be deleted :) |
I've been researching a fair amount on how to do versioning in hugo, and think that the URL scheme I set up for cni.dev is probably not the best method for this site.
A folder method of versioning cni.dev may be better for the following reasons:
A con I can think of for this method, for a site of this size, is that once you start adding languages/localizations navigation becomes more complex.
Once PR #80 is merged in, then we can:
The text was updated successfully, but these errors were encountered: