Hi tison, +1
Thank you for driving this. The old "How to Publish the Curator Website"[1] is a mystery for me anyway. I am nervous about the process of site deployment. It will be great for CI to automate this. Only two concerns: * Javadoc is also hosted there. I think we should also migrate it. * The new website will be a separate repo ? Will we bypass jira for website update ? Personally, I am OK with this. We don't have to follow jira/pr as code repositories. [1]: https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-HowtoPublishtheCuratorWebsite Best, Kezhu Wang On Mon, Aug 14, 2023 at 3:06 PM Enrico Olivelli <eolive...@gmail.com> wrote: > > +1 > > Thanks > Enrico > > Il giorno lun 14 ago 2023 alle ore 08:55 tison <wander4...@gmail.com> > ha scritto: > > > > For your reference, the workflow and demo site can refer to - > > > > * https://github.com/apache/kvrocks-website > > * https://kvrocks.apache.org/ > > > > (while I don't like its homepage, other pages should be good) > > > > Best, > > tison. > > > > > > tison <wander4...@gmail.com> 于2023年8月14日周一 14:53写道： > > > > > 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 > > >
