I've given up on building the old site since I failed several times. I've create two issues to track the progress of migrating the old site to Antora.
* Make an inventory of old site https://issues.apache.org/jira/browse/JAMES-3301 * Migrate the content https://issues.apache.org/jira/browse/JAMES-3302 Please help out with the inventory and if you have ideas with the content. I'll migrate what I can, we can sort them after. I've migrated the markdown files for ADR and src/site/markdown using kramdown . I have found a migration from XDOC/APT -> DocBook -> AsciiDoc , but did not try it yet. See my code here: https://github.com/apache/james-project/pull/234 . Feedback is welcomed. We might not get gradle soon since migration is stalling but I think we can get the website. IMO it is a smaller enterprise and with a bit more immediate impact. Regards, La 09.07.2020 20:09, Eugen Stan a scris: > Hello Benoit, > > I've added the list since you missed to include it. > > Thanks for the reply. I missed this information and asked again in my > second email. > > I think we can work in this thread and ignore the other. > > See my reply inline: > > La 08.07.2020 09:33, Tellier Benoit a scris: >> Le 06/07/2020 à 14:17, Eugen Stan a écrit : >>> Hello David, >>> >>> Thanks for the guide. >>> >>> I think we can work on a branch on top of >>> https://github.com/apache/james-site/tree/asf-site >>> >>> >>> @Benoit: Regarding https://issues.apache.org/jira/browse/JAMES-3226 . >>> >>> What is the current process of deploying the james-site ? >>> >> Instructions can be found here: >> >> https://github.com/apache/james-project#how-to-build-and-publish-the-website >> >> >> - Build the homepage (using jekyll) ( james-project/src/homepage ) >> >> Commands could be extracted from the dockerfile: >> >> https://github.com/apache/james-project/tree/master/dockerfiles/site/homepage > Using docker to build the hompage is ok I guess. > > I would push a pre-built image instead of always building it. > > I do think we should move the all the site information to james-site > project. > > We can have the code there and use orphan branches for publishing the > website. > > We can drop and remake those branches to keep the repo slim. > > It's good to know that the site is generated and we can drop asf-site > when we need to. > > > Moving to Antora I guess we should decide if we want to maintain a > separate homepage using Jekill or port things to Antora. > > I like simple things and dropping an extra tool makes sense. > > We do have to figure out what will be the porting effort. > > I wonder what everyone else thinks about this. (Hint for everyone to > speak their mind). > > I've managed to build the homepage. > >> - Build the (mvn) documentation site (james-project/src/site ) >> >> Which is slow... >> >> Commands could be extracted from the dockerfile: >> >> https://github.com/apache/james-project/tree/master/dockerfiles/site/website >> >> I do run them without docker. > I failed to build the site using docker. Any ideas (did not have time to > investigate yet) ? > > ---- > > [ERROR] [ERROR] Could not find the selected project in the reactor: > mpt/antlib @ > [ERROR] Could not find the selected project in the reactor: mpt/antlib > -> [Help 1] > > ---- > >> Then specify the output (or copy it) to james-site project, commit & >> push. (I said it was dirty) >> >> Note that there is often (always) a synchronisation issue: changes are >> not applied. I raised the point with the infra (can't recall the ticket) >> and their proposal solution is to do a dummy one line commit (pushed >> separately) after the site modification, which immediatly makes the >> changes visible. >> >> This answers your question? > Yes, it answers my questions. Thank you. > > My proposal so far is to: > > 1. Figure out if we can leverage Antora for the homepage as well (I > believe we can, but I need to check). > > This will simplify our build setup. > > 2. Prepare a new website on james-site and migrate the existing content > there. > > I hope we get to do a community push on this. It's not sexy but I think > we can convert the existing pages to Asciidoc. > > Migrating the content is important - not all of it is relevant but a lot > is IMO. > >>> I'll work on a branch and try to automate that or parts of that. >> +1 <3 today it is painful. >>> My goal is to also incorporate antora into the mix. >> +1 I would love to have it as a subfolder of current website until we >> can fully switch to it. > I agree. > > >>> I've created this to track work on it >>> https://github.com/apache/james-site/pull/1 . >>> >>> We can discuss there for specific technical aspects. >> I had a read, it sounds good to me. >> >> Regards, >> >> Benoit >> -- Eugen Stan +40720 898 747 / netdava.com
<<attachment: eugen_stan.vcf>>
signature.asc
Description: OpenPGP digital signature
