As you can see, there is Need for that: ➢ This PR adds support for Gulp task runner. Using Gulp / node.js tools for building frontend assets is a standard practice today. It offers more packages than Gradle and it will be easier to find new frontend developers.
It is not only my opinion and BTW, I wasn’t the author of the PR 😉. So I’m for merge and there is someone else who wants to work on it, if this changes. Cheers Chris Von: Antonio Gesendet: Montag, 15. Juli 2019 20:59 An: dev@netbeans.apache.org Betreff: Re: AW: website build system: moving to node/npm? Thanks, Chris! So let's await for those "frontend guys" with "> 10 years" of experience to build a "common frontend stack" so they can "work on the page" with "VuePress, Nuxt, Hugo or Hexo". Meanwhile let's stick with the "guys working on that page" (no matter whether backend or frontend) and let's close PR#375 [1]. As Geertjan suggested, "If it ain't broke, don't fix it...". Thanks again & kind regards, Antonio [1] https://github.com/apache/netbeans-website/pull/375 El 15/7/19 a las 15:30, Christian Lenz escribió: > We only need frontend guys working on that page and there are a lot of > frontend guys out there. There is Nothing half baked. Look at Github what > they have use a more common frontend stack. For me as a frontend developer > for > 10 Years, it is farly not Java or JBake or JVM whatever. This is not a > common frontend stack and the case why I didn’t work on the page is exactly > that using of the stack. > > We don’t Need Java backend guys working on that page. Just a couple of > frontend guys and I guess david will aslo help here and me too. > > My proposals are: VuePress, Nuxt, Hugo or Hexo. My 2 cents. > > > Cheers > > Chris > > > > Von: Neil C Smith > Gesendet: Montag, 15. Juli 2019 12:50 > An: dev > Cc: Apache NetBeans > Betreff: Re: website build system: moving to node/npm? > > On Mon, 15 Jul 2019 at 11:07, Geertjan Wielenga <geert...@apache.org> wrote: >> >> If it ain't broke, don't fix it... >> >> And do we expect lots of people to work on the site just because we switch >> from Gradle to Gulp? Do we need lots of people working on the site, >> especially since everything's working fine the way it is? > > Switching to an equally bespoke and arcane build system in Gulp, no. > Moving to a popular static generator ( https://www.staticgen.com/ ) > and using it in a somewhat standard fashion (which we're not with > JBake as I recall) might be a good move to reduce technical debt. > > If we did stay JVM, then Orchid might be worth looking into, as it > claims both to support JBake configuration and the additional things > we're doing in the custom build process?! > > If someone has a proposal for a JS (or other) SSG that can do the full > job of what we have now in a standard way then I think it's strongly > worth considering. But it needs to be a complete plan. At my old > company I did take a brief look at Gatsby, but in the end mostly made > use of Jekyll due to the better (at the time) client-side CMS options > - or in other words, there are always other considerations in play! > :-) > > Best wishes, > > Neil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
