I don't think that the Hugo version is particularly important. I'm using 0.68.3 locally and it works just fine. I filed [1] to enquire.
Did I answer all your questions? [1] https://github.com/EclipseFdn/hugo-eclipsefdn-website-boilerplate/issues/1 On Tue, Mar 30, 2021 at 3:42 AM Jonah Graham <[email protected]> wrote: > Hi Wim/all, > > This is great - and on behalf of the CDT team I am closely following > because we will probably do the same for the CDT project. > > Some notes based on my experimentation with what you provided: > > - I didn't understand step 2 about "process can be tested locally" at > first. The link provided was to Jenkins stuff ( > #how-to-build-my-projects-website-with-jenkins > <https://github.com/EclipseFdn/hugo-eclipsefdn-website-boilerplate#how-to-build-my-projects-website-with-jenkins>) > which I assume is out of scope for "local" builds. > - It turns out that the anchor in the link was probably wrong as your repo > [1] has a good getting started for the new repo (s/eclipse/wimjongman/ in > the git clone line until it is promoted to eclipse's github org) > - On the build machine hugo 0.81.0 is used (as documented on the wiki[2]) > - but the 0.80.0 version that is available as a snap in Ubuntu seems to > work fine. If there is a minimum or suggested version that may be good to > have in the readme too? Especially for those of us new to the Hugo > technology[3] > - If using snap (and you are new to snap installs) make sure you clone the > repo into somewhere in your home directory or you get errors when running > hugo (like Error: open /var/lib/snapd/void: permission denied) > > [1] > https://github.com/wimjongman/platform-web/tree/staging/#getting-started > [2] > https://wiki.eclipse.org/Jenkins#How_to_build_my_project.27s_website_with_Jenkins.3F > [3] https://gohugo.io/ > > Thanks Wim! > > Jonah > > ~~~ > Jonah Graham > Kichwa Coders > www.kichwacoders.com > > > On Mon, 29 Mar 2021 at 17:22, Wim Jongman <[email protected]> wrote: > >> It took a long struggle but our webmasters did it and we now have a very >> easy website process. >> >> 1. We just edit some markdown files e.g. [1] >> 2. The whole process can be tested locally to make sure the changes are >> ok [2] >> 3. The build converts the website to static HTML and pushes it to the >> main server [3] >> >> I have converted the main page from php/html to markdown [1] >> >> ## RESULT >> old: https://www.eclipse.org/eclipse >> new https://staging.eclipse.org/eclipse >> >> Cheers, Wim >> >> [1] https://github.com/wimjongman/platform-web/tree/staging/content >> [2] >> https://github.com/EclipseFdn/hugo-eclipsefdn-website-boilerplate#how-to-build-my-projects-website-with-jenkins >> [3] >> https://ci.eclipse.org/platform/view/Other/job/TEMP_WEBSITE_DEPLOYMENT/ >> >> _______________________________________________ >> platform-dev mailing list >> [email protected] >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/platform-dev >> > _______________________________________________ > platform-dev mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev >
_______________________________________________ platform-dev mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
