v01d commented on pull request #1501:
URL: https://github.com/apache/incubator-nuttx/pull/1501#issuecomment-674238029


   > > I wanted to check with you (maybe @btashton ?): I understand that the 
latest version of HTML docs is always on the Wiki, built from the repo, right? 
If so, I would include the deletion of all HTMLs and renaming of doc/ to 
Documentation/ in this PR. The wiki would then host the archived version of 
latest HTML docs. Does that sound correct? Or should we go about this another 
way? My intention is that with this PR, the new docs become the official docs 
and any other change which impacts documentation will already be done over 
these (and not HTMLs), thus the idea of removing them.
   > 
   > The docs on the wiki are for the latest release and it is a manual process 
to update them. The CI creates a minified inlined HTML file so that the wiki 
can render it, but it does not update anything. So short of it is that we can 
drop the doc CI step that already existed and add the one that exists in this 
PR that generates the HTML files as Artifacts. As I said earlier I will be 
happy to do the CI bit that connects this all to the website release.
   
   I see. But then if I drop the doc workflow, there will be no more artifacts 
generated for old docs (only for new ones) once this is merged. If the latest 
version is not on the wiki, maybe we should grab latest artifact from master 
for old docs y use that to update the wiki (or maybe as in the website itself, 
so that we can link to the archived version of the docs there). If that's what 
you had in mind, I will then remove the doc workflow, and leave the sphinx-docs 
(only building and creating the artifiact, removing the GH pages part).


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to