[
https://issues.apache.org/jira/browse/KAFKA-20541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079099#comment-18079099
]
ASF GitHub Bot commented on KAFKA-20541:
----------------------------------------
mimaison commented on PR #856:
URL: https://github.com/apache/kafka-site/pull/856#issuecomment-4397857586
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?
> Duplicate generated folder in kafka-site
> ----------------------------------------
>
> Key: KAFKA-20541
> URL: https://issues.apache.org/jira/browse/KAFKA-20541
> Project: Kafka
> Issue Type: Bug
> Components: website
> Reporter: Mickael Maison
> Assignee: Muralidhar Basani
> Priority: Major
>
> We have the generated content under both:
> - content/en/<VERSION>
> - static/<VERSION>
> For example:
> https://github.com/apache/kafka-site/tree/markdown/content/en/42/generated
> https://github.com/apache/kafka-site/tree/markdown/static/42/generated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
