Hi, As asked by Michael, I had a quick look at your current setup, your pain points and what can be done to improve your experience. I just proposed one little PR to go step by step: https://github.com/apache/httpcomponents-website/pull/4
With that setup, building and deploying the main site is just "mvn site-deploy". As explain in the PR comment: "Once this step is ok from a developer point of view, run on his local machine, next step will be to configure a Jenkins job to do mvn site-deploy automatically when updating source content: from there, many little improvements can be done (testing Markdown and/or Asciidoc source instead of apt, improving site.xml, reworking the skin to add the "edit" icon in breadcrumb, ...)" On the question of "piecing together content of multiple releases into a single web site", this is the next step that will improve performance but requires some structure change (and 1 infra task done by infra): IMHO, we should discuss that once the previous non-invasive steps are working, then you start having a better confidence based on better experience. once 1 dev is able to rebuild and publish from his computer with "mvn site-deploy", I can provide you a few light improvements to see the site evolve with the new setup: just tell me once it works and you are ready to try next steps Regards, Hervé On 2020/10/26 18:13:19, Michael Osipov <[email protected]> wrote: > Am 2020-10-25 um 23:06 schrieb Oleg Kalnichevski: > > On Sun, 2020-10-25 at 19:49 +0100, Michael Osipov wrote: > >> Am 2020-10-25 um 16:15 schrieb Gary Gregory: > >>> On Sun, Oct 25, 2020 at 5:30 AM Michael Osipov <[email protected] > >>>> wrote: > >>> > >>>> Am 2020-10-19 um 19:12 schrieb Oleg Kalnichevski: > >>>>> Folks > >>>>> > >>>>> I personally think that our project web site is an absolute > >>>>> disgrace. > >>>>> The terrible quality of our web site really hurts the project. > >>>>> > >>>>> Last time we discussed the subject I swore to not touch the > >>>>> retched > >>>>> thing unless absolutely necessary for release publishing. > >>>>> > >>>>> Do we want to revisit the issue or shall we keep things as they > >>>>> stand? > >>>> > >>>> I have received to valuable answers on [email protected] > >>>> > >>>> 1. > >>>> > >>>> http://mail-archives.apache.org/mod_mbox/maven-dev/202010.mbox/%3C3CE5F2BA-3683-4024-9D4D-CA402AC9ABDC%40gmail.com%3E > >>>> 2. > >>>> > >>>> http://mail-archives.apache.org/mod_mbox/maven-dev/202010.mbox/%3C5401179.DvuYhMxLoT%40giga%3E > >>>> > >>>> This is really good. If no one beats me, I will dive into this in > >>>> November and will play around with it in a seperate deploy path > >>>> hopefully not breaking the current site. > >>>> > >>> > > > > Sounds good to me. I am still unsure how exactly you want to piece > > together content of multiple releases into a single web site using > > Maven Site plugin alone. > > This does work for Maven because we have 100 components hooked into the > site tree. I am quite sure this will work here too. Let me try and we'll > see in Nov. > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
