muralibasani commented on PR #856: URL: https://github.com/apache/kafka-site/pull/856#issuecomment-4412051437
> Yes I think something along these lines would work. Thanks for figuring it out. > > I'm wondering whether we should keep all existing versions as is, at least for now, and only start with the new scheme for newer versions. So we'd do the changes in the kafka repository instead. > > Also it seems the new process requires editing hugo.yaml for each release, could we invert the process to include mapping all existing versions, and not require changes for new releases? @mimaison new changes now handle only newer versions and no edits are required for hugo config going fwd. Added one excludeFiles config to skip empty stubs in 4.2. (if we don't need this config, need to delete those empty files and they only exist in content/4.2/generated) And for new releases: copy docs/ into content/en/<v>/ and images/javadoc into static/<v>/, catch-all will take care. Tested with a new version locally. -- 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]
