errose28 commented on PR #9979: URL: https://github.com/apache/ozone/pull/9979#issuecomment-4162889154
> this is a user doc. But since the code is still in feature branch, not merged back to master yet, I think maybe it's stay with ozone repo first. After the feature branch merge, we can submit a new patch for this for ozone-site repo, what do you think? A better option might be to raise a draft PR in ozone-site and merge it when the feature branch is merged here. The formatting supported for pages is a little different, so it is not always a copy/paste from one to the other. Docusaurus has callouts and mdx that could be helpful, for example. ozone-site also has stricter linting rules. > BTW, there is no auto sync between ozone repo and ozone-site repo for document now? For user docs we should probably delete docs and Hugo content from the Ozone repo to ensure all new user docs go to ozone-site. We have the previous docs [captured as Hugo builds](https://github.com/apache/ozone-site/tree/master/static/docs/1.4.1) in the [new website](https://ozone.apache.org/docs/1.4.1/) so removing them here would ensure they live on as read-only. The only sync process we may want to add would be for design docs. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
