Thanks for your replies! > Javadoc is also hosted there. I think we should also migrate it.
Yes. I know how to implement that :P > The new website will be a separate repo? This is actually an open issue, and I ask for a separate repo so that I can later create it on demand or not. The benefit of a separate repo is that we don't mix up code and have a separate focus when building CICD workflows. Also, people who can improve the site or code accordingly. The benefit of a mono repo is that contributors can update code and docs simultaneously. And thus we don't need to "remember" to update the website correspondingly. Either of them should be able to work well with Curator's bias. In projects I mentor, Kvrocks uses separate repos and contributors are actively update both of the repos, while OpenDAL uses a mono repo and it can deploy well also. Flink and InLong, where I'm a committer in, use a mixed solution that hosts a separate site repo while partially copying docs from the main repo, which is too complex for Curator IMO. I personally like separate code of the website from core logic. > Will we bypass jira for website update Not always. flink-web[1] as an example can sometimes associate a commit with a JIRA ticket. I suggest we don't require it but also don't forbid it. Best, tison. [1] https://github.com/apache/flink-web Jordan Zimmerman <[email protected]> 于2023年8月14日周一 23:59写道： > OK with me. > > > On Aug 14, 2023, at 7:53 AM, tison <[email protected]> wrote: > > > > Hi, > > > > I'm building a Docusaurus-based website for Curator these days, whose > first > > version will be almost identical to the current one. > > > > With a Git-based workflow and Docusaurus-based website framework, we (or > at > > least I) can reduce the maintenance burden for understanding and > performing > > SVN commands & maven + confluence-based site (e.g., we have some broken > > links list on[1] and I don't want to learn that tech stack for resolving > > it). > > > > Thus, I'd propose creating curator-site Git repo to host the code, and > I'll > > later put all things up to publish the new site. > > > > What do you think? > > > > Best, > > tison. > > > > [1] https://curator.apache.org/releases.html > >
