docs site version name (label) display in url and also in dropdown of versions

[devopstoday11]

explained the issue here -
https://www.loom.com/share/79a5434464b24c87a29a34305178acb8
@tfsojon

Currently for the latest version of docs - the URL is like this https://docs.intelops.ai/1.0.0/compage/1-docs-structure/
For the latest version docs only - the URL should have the version name in it instead of the version number, something like this https://docs.intelops.ai/latest/compage/1-docs-structure/

label parameter I explained in the video - new parameters to use for latest version doc in .md file : -
version_name: "latest"
display_version_name: "true"

[devopstoday11]

@tfsojon

[tfsojon]

Sorry I forget to respond, but started working on it form morning

[tfsojon]

@devopstoday11 website issue fixed.
but this one quite unusual to implement in Hugo also on our doc-system. I already spend 2+ hrs to figure this out with Hugo's function.
We can not do this without changing the folder name (like 1.0.0 to latest). but it also need lot more fixes across the site.

The main problem you mention is url issue from social media.
I hope I got another solution. Will implement by tomorrow.

[tfsojon]

Now we have to update the latestDocVersion in two places

1. in config.toml - https://github.com/tfsojon/external-docs/blob/chandu/config.toml#L40
2. in netlify.toml - https://github.com/tfsojon/external-docs/blob/chandu/netlify.toml#L11
   

check this url - https://tf-intelops-docs.netlify.app/1.0.1/compage/6-contribution/
if you are in latest version of doc and click on copy-icon, it will copy the link with latest name

and try that copied link in a new tab.

intelops-docs.mp4

[tfsojon]

@devopstoday11 did you checked this?

[devopstoday11]

@devopstoday11 did you checked this?

sorry, I just checked this. Please resubmit PR to chandu branch. I want to check in my local before merging to main branch. @tfsojon

[tfsojon]

@devopstoday11 Submitted new PR. sorry for the previous PR.

[devopstoday11]

@tfsojon
I observed one issue in the docs site.
When you are inside a particular topic related documentation, and when you click on the version drop down and select a version it is taking me to docs site home page instead of staying within the same page where I am currently.
When I change the version, I should still be within the same topic related documentation but related to whatever the version number I selected. Don't necessarily need to be on same exact page, but should be routed to same topic's first page instead of routing to docs site home page.

https://loom.com/share/59c66ba7a05d43bab23c072de52fa8c5

[tfsojon]

Ok, will do something with this.

[tfsojon]

@tfsojon I observed one issue in the docs site. When you are inside a particular topic related documentation...

https://loom.com/share/59c66ba7a05d43bab23c072de52fa8c5

@devopstoday11 updated - https://tf-intelops-docs.netlify.app/1.0.0/compage/3-installation/

[devopstoday11]

@tfsojon , yes that is what I wanted. Awesome. Thank you.

[devopstoday11]

@tfsojon @tfsumon ,
need modifications to the versioning feature in the Docs site.
Currently, the version (for example 1.0.0) is common for every topic. That is causing some conflicts to manage the versions properly for each topic independently. I think each topic should have it's own version.

This is how topics are arranged currently in the Docs site code base -
content > version-number > topic
Need to change this to -
content > topic-name > version numbers (folders for each version e.g: 1.0.0 , 1.0.1 , 1.0.2 , 1.0.3 , etc.)

So in the UI when the docs site is launched, there is no need to have a single global version for all topics, which is what currently is. We a visitor clicks on a certain topic and when the relevant Topic's documentation page is opened, there that Topic's version should be should in the drop down (latest, 1.0.1, 1.0.0, etc.).
When you make this new update to the versioning feature, make sure the "latest in the URL" launches the latest version which was developed by @tfsojon as mentioned in this comment. So, basically, the same "latest" functionality should be available independently for each topic since that is the change I asked for the actual versioning too.