Closed muscariello closed 2 years ago
I am in the process of also enabling the push of the docs to S3. Shall we use the S3 link instead?
@sknat @msardara we could also use S3 as landing pages but it requires additional work.
I did not update the HICN summary page yet.
I am in the process of also enabling the push of the docs to S3. Shall we use the S3 link instead?
Sounds good :)
@msardara I remove the redirect to 22.06 as readthedocs includes a side bar with all releases built from there. Hence #123 just updates links to the latest release. The summary page points to a redirect to readthedocs. When we have S3 ready we just need to update that redirect. We need to decided if we want to keep all previous doc releases. In that case we need to update the summary page.
Once we push on s3 it makes sense to keep all the releases. I think we will get the links in this form:
https://s3-docs.fd.io/hicn/22.02 https://s3-docs.fd.io/hicn/22.06 ...
That we just need to append in the summary page.
In theory yes. In practice there need to be real updates on the docs :-)
@edwarnicke we may want to wait https://gerrit.fd.io/r/c/ci-management/+/36010 is merged and double check the landing page on S3. In that case I'll update this PR with S3 for good.
@edwarnicke, @muscariello apologies for tagging over here directly. I'm redirecting from here & I just wanted to know the exact repo where LFN participants can potentially contribute?
I'm confused between FDio/site
& FDio/hicn
😅
Also, I do want to connect to Dave & Maciek and discuss about my proposal for LFN'23 application, but the slack invite link to the community isn't working (refer to: #140). I'd be highly obliged if anyone of you can guide me forward :)
Thanks!
We have moved the documentation landing page to https://hicn.readthedocs.io/en/latest/ which is automatically built by the readthedocs platform.
The platforms builds docs from all tags found in https://github.com/FDio/hicn starting from tag 22.02 e.g. https://hicn.readthedocs.io/en/v22.02-rc0/