Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
When we started this, and Chris did his icon, we had the NetBeans cube; both the blue solid and the red empty sides versions. NB has had those cube icons for decades at this point. Webpack, at the time of his drawing, had a cube in a translucent cube. But, did have the hexgon outline. Has anyone see the latest Webpack logo? It seems to differ only in color, as they have added boldness and contrast to the internal cube lines. I think it would be fair to afford some time for some modification because of this. Just some ideas: Some extra depth to the layer around the cube could relate to the pieces from "Fits the pieces together" as well as "into a new dimension". Maybe even adding some tilt to the hexagon to give it a distinct shadow. Wade On Feb 26, 2018 06:06, "Antonio"wrote: > Hi Chris, all, > > The situation with the logo is that there was a voting at [1] somewhere in > 2016, the most voted logo is not the one with colors, so using the one you > suggest (with colors) instead of the most voted one does not seem to be > very Apache compliant, as it would be against a voting result. > > Also in late 2017 we opened an Apache NetBeans logo contest at [2], which > has not been closed yet. There has been a submission in early february 2018 > (i.e., a few days ago) from Junichi (see [3]), which is also pretty cool, > IMHO, and also deserves our consideration. > > To end up the logo discussion once and for all I propose: > > - Announcing closing the contest within a few days. > - Announce a voting in the mailing list, as per the Apache way. > > I know this is probably lots of bureaucracy, but that's how things are > expected to work in this Apache world, AFAIK (and please correct me if I'm > wrong). > > Kind regards, > Antonio > > [1] > https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo > > [2] > https://issues.apache.org/jira/browse/NETBEANS-145 > > [3] > https://issues.apache.org/jira/secure/attachment/12909573/ap > ache-netbeans-logo.png > > Forwarded Message > Subject: AW: Merged to master (was Re: A NetBeans website proposal) > Date: Mon, 26 Feb 2018 10:58:53 +0100 > From: Christian Lenz > Reply-To: dev@netbeans.incubator.apache.org > To: dev@netbeans.incubator.apache.org > > I would like to Change the logo to the SVG file, because it scales better > and we don’t have any Problems with Retina and whatever, as you can see it > here: http://netbeans.apache.org/. I added the SVG too. > > > Cheers > > Chris > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
T-Shirts (was Fwd: Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal)))
Talking of which, the ASF Swag site http://apacheswag.com/ Has no Apache NetBeans T-Shirts yet!! :-( Forwarded Message Subject: Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal)) Date: Tue, 27 Feb 2018 10:58:11 + From: Neil C SmithReply-To: dev@netbeans.incubator.apache.org To: dev@netbeans.incubator.apache.org On Tue, 27 Feb 2018 at 10:40 Antonio wrote: I like that "Powered by NetBeans..." logo idea! Yes, particularly on a T-shirt! ;-) Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
On Tue, 27 Feb 2018 at 10:40 Antoniowrote: > I like that "Powered by NetBeans..." logo idea! > Yes, particularly on a T-shirt! ;-) Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
I like that "Powered by NetBeans..." logo idea! Thanks, Bertrand, Antonio On 27/02/18 10:31, Bertrand Delacretaz wrote: On Mon, Feb 26, 2018 at 5:20 PM, Eduard Karel de Jongwrote: ...The next discussion and a subsequent vote should be on the elements that we want to present in the typography... Note also https://www.apache.org/foundation/marks/pmcs which has a (small) section on logos and graphics policy. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
On Mon, Feb 26, 2018 at 5:20 PM, Eduard Karel de Jongwrote: > ...The next discussion and a subsequent vote should be on the elements that we > want to present in the typography... Note also https://www.apache.org/foundation/marks/pmcs which has a (small) section on logos and graphics policy. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
Indeed, the icon without typgraphy should be the item to vote upon this time. The next discussion and a subsequent vote should be on the elements that we want to present in the typography, for instance: -the word "apache" -the feather -a 'badge' with "IDE" (with a possible alternate badge for the framework, like "AFW". An other question is if the words "Net" and "Beans" should be with distinct typography. Cheers Eduard Antonio wrote: I'd say the icon without the typography. Cheers, Antonio On 26/02/18 12:16, Neil C Smith wrote: On Mon, 26 Feb 2018 at 11:06 Antoniowrote: To end up the logo discussion once and for all I propose: - Announcing closing the contest within a few days. - Announce a voting in the mailing list, as per the Apache way. Sounds good! Can we also clarify what we mean by logo though? Are we at this stage literally looking for the replacement for the cube icon, without any text / typography? Because currently the blue logo has 6 or 8 votes depending on what we mean. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
Indeed, the icon without typgraphy should be the item to vote upon this time. The next discussion and a subsequent vote should be on the elements that we want to present in the typography, for instance: -the word "apache" -the feather -a 'badge' with "IDE" (with a possible alternate badge for the framework, like "AFW". An other question is if the words "Net" and "Beans" should be with distinct typography. Cheers Eduard Antonio wrote: I'd say the icon without the typography. Cheers, Antonio On 26/02/18 12:16, Neil C Smith wrote: On Mon, 26 Feb 2018 at 11:06 Antoniowrote: To end up the logo discussion once and for all I propose: - Announcing closing the contest within a few days. - Announce a voting in the mailing list, as per the Apache way. Sounds good! Can we also clarify what we mean by logo though? Are we at this stage literally looking for the replacement for the cube icon, without any text / typography? Because currently the blue logo has 6 or 8 votes depending on what we mean. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Merged to master (was Re: A NetBeans website proposal)
On Mon, 26 Feb 2018 at 13:27 Peter Steelewrote: > Apologies if i may have missed it, but where in the > incubator-netbeans-website github repository is the delete/clean code in > build.gradle? > I have no idea! Maybe one for Wade. What I do know is that clean deletes the build dir, so the assets get removed. Maybe we need to explicitly clean up the asset dirs too? Seems possibly related to comments here https://github.com/gradle/gradle/issues/1168 Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Merged to master (was Re: A NetBeans website proposal)
Apologies if i may have missed it, but where in the incubator-netbeans-website github repository is the delete/clean code in build.gradle? On 26 Feb 2018 11:52, "Neil C Smith"wrote: > On Mon, 26 Feb 2018 at 11:38 Peter Steele wrote: > > > Although the easiest way is to actually move the clean code from the > > scripts to gradle because gradle will then have a complete view on things > > > > Everything is already gradle though! > > Best wishes, > > Neil > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >
Re: Merged to master (was Re: A NetBeans website proposal)
On Mon, 26 Feb 2018 at 11:38 Peter Steelewrote: > Although the easiest way is to actually move the clean code from the > scripts to gradle because gradle will then have a complete view on things > Everything is already gradle though! Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Merged to master (was Re: A NetBeans website proposal)
It could be that because you have cleaned them outside of gradle, gradle still thinks they are there and they haven't changed. The .gradle/caches contains the cached data, you can tell gradle to refresh the dependencies using ./gradle build --refresh-dependencies. Although the easiest way is to actually move the clean code from the scripts to gradle because gradle will then have a complete view on things On 26 Feb 2018 11:07, "Neil C Smith"wrote: On Mon, 26 Feb 2018 at 10:57 Peter Steele wrote: > Gradle clean basically cleans the build directory used in java compilation. > In the task compileContentSass for instance you source from $contentDir and > write to $generatedAssetDir and these are not part of the java eco system. > > What you should do is create a new task which deletes all the directories > you use and then do a clean.dependsOn(myCleanTask) so that is is run when > clean is run. > Thanks! Wade's build scripts do clean out all the generated files, presumably because they're under /build anyway? However, the sass plugin still thinks it's up-to-date. I'm assuming we need to link the sass plugin into clean somehow, but the problem appears to be more than just deleting the output directories, because they already are deleted? Unless it's the way that they're deleted that matters? Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
On Mon, 26 Feb 2018 at 11:24 Antoniowrote: > I'd say the icon without the typography. > Agreed, so +1 from me to that and your schedule. Given the necessarily short schedule, etc., and as we find our feet at Apache, it might be good to keep in mind that any decision could get reviewed around either next major release or when we become a top-level project - ie. it's not a vote on something that will be fixed for all eternity! ;-) Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
I'd say the icon without the typography. Cheers, Antonio On 26/02/18 12:16, Neil C Smith wrote: On Mon, 26 Feb 2018 at 11:06 Antoniowrote: To end up the logo discussion once and for all I propose: - Announcing closing the contest within a few days. - Announce a voting in the mailing list, as per the Apache way. Sounds good! Can we also clarify what we mean by logo though? Are we at this stage literally looking for the replacement for the cube icon, without any text / typography? Because currently the blue logo has 6 or 8 votes depending on what we mean. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
Hi again, So, to keep things moving, shall we announce closing the contest by, say, until March the 1st? And start the voting during March 2nd, 3rd and 4th? Or is that too fast? ;-) Cheers, Antonio On 26/02/18 12:09, Geertjan Wielenga wrote: That sounds good. Thanks for persevering with this, Antonio. Gj On Mon, Feb 26, 2018 at 12:06 PM, Antoniowrote: Hi Chris, all, The situation with the logo is that there was a voting at [1] somewhere in 2016, the most voted logo is not the one with colors, so using the one you suggest (with colors) instead of the most voted one does not seem to be very Apache compliant, as it would be against a voting result. Also in late 2017 we opened an Apache NetBeans logo contest at [2], which has not been closed yet. There has been a submission in early february 2018 (i.e., a few days ago) from Junichi (see [3]), which is also pretty cool, IMHO, and also deserves our consideration. To end up the logo discussion once and for all I propose: - Announcing closing the contest within a few days. - Announce a voting in the mailing list, as per the Apache way. I know this is probably lots of bureaucracy, but that's how things are expected to work in this Apache world, AFAIK (and please correct me if I'm wrong). Kind regards, Antonio [1] https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo [2] https://issues.apache.org/jira/browse/NETBEANS-145 [3] https://issues.apache.org/jira/secure/attachment/12909573/ apache-netbeans-logo.png Forwarded Message Subject: AW: Merged to master (was Re: A NetBeans website proposal) Date: Mon, 26 Feb 2018 10:58:53 +0100 From: Christian Lenz Reply-To: dev@netbeans.incubator.apache.org To: dev@netbeans.incubator.apache.org I would like to Change the logo to the SVG file, because it scales better and we don’t have any Problems with Retina and whatever, as you can see it here: http://netbeans.apache.org/. I added the SVG too. Cheers Chris - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
On Mon, 26 Feb 2018 at 11:06 Antoniowrote: > To end up the logo discussion once and for all I propose: > > - Announcing closing the contest within a few days. > - Announce a voting in the mailing list, as per the Apache way. > Sounds good! Can we also clarify what we mean by logo though? Are we at this stage literally looking for the replacement for the cube icon, without any text / typography? Because currently the blue logo has 6 or 8 votes depending on what we mean. Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
That sounds good. Thanks for persevering with this, Antonio. Gj On Mon, Feb 26, 2018 at 12:06 PM, Antoniowrote: > Hi Chris, all, > > The situation with the logo is that there was a voting at [1] somewhere in > 2016, the most voted logo is not the one with colors, so using the one you > suggest (with colors) instead of the most voted one does not seem to be > very Apache compliant, as it would be against a voting result. > > Also in late 2017 we opened an Apache NetBeans logo contest at [2], which > has not been closed yet. There has been a submission in early february 2018 > (i.e., a few days ago) from Junichi (see [3]), which is also pretty cool, > IMHO, and also deserves our consideration. > > To end up the logo discussion once and for all I propose: > > - Announcing closing the contest within a few days. > - Announce a voting in the mailing list, as per the Apache way. > > I know this is probably lots of bureaucracy, but that's how things are > expected to work in this Apache world, AFAIK (and please correct me if I'm > wrong). > > Kind regards, > Antonio > > [1] > https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo > > [2] > https://issues.apache.org/jira/browse/NETBEANS-145 > > [3] > https://issues.apache.org/jira/secure/attachment/12909573/ > apache-netbeans-logo.png > > Forwarded Message > Subject: AW: Merged to master (was Re: A NetBeans website proposal) > Date: Mon, 26 Feb 2018 10:58:53 +0100 > From: Christian Lenz > Reply-To: dev@netbeans.incubator.apache.org > To: dev@netbeans.incubator.apache.org > > I would like to Change the logo to the SVG file, because it scales better > and we don’t have any Problems with Retina and whatever, as you can see it > here: http://netbeans.apache.org/. I added the SVG too. > > > Cheers > > Chris > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Merged to master (was Re: A NetBeans website proposal)
On Mon, 26 Feb 2018 at 10:57 Peter Steelewrote: > Gradle clean basically cleans the build directory used in java compilation. > In the task compileContentSass for instance you source from $contentDir and > write to $generatedAssetDir and these are not part of the java eco system. > > What you should do is create a new task which deletes all the directories > you use and then do a clean.dependsOn(myCleanTask) so that is is run when > clean is run. > Thanks! Wade's build scripts do clean out all the generated files, presumably because they're under /build anyway? However, the sass plugin still thinks it's up-to-date. I'm assuming we need to link the sass plugin into clean somehow, but the problem appears to be more than just deleting the output directories, because they already are deleted? Unless it's the way that they're deleted that matters? Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))
Hi Chris, all, The situation with the logo is that there was a voting at [1] somewhere in 2016, the most voted logo is not the one with colors, so using the one you suggest (with colors) instead of the most voted one does not seem to be very Apache compliant, as it would be against a voting result. Also in late 2017 we opened an Apache NetBeans logo contest at [2], which has not been closed yet. There has been a submission in early february 2018 (i.e., a few days ago) from Junichi (see [3]), which is also pretty cool, IMHO, and also deserves our consideration. To end up the logo discussion once and for all I propose: - Announcing closing the contest within a few days. - Announce a voting in the mailing list, as per the Apache way. I know this is probably lots of bureaucracy, but that's how things are expected to work in this Apache world, AFAIK (and please correct me if I'm wrong). Kind regards, Antonio [1] https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo [2] https://issues.apache.org/jira/browse/NETBEANS-145 [3] https://issues.apache.org/jira/secure/attachment/12909573/apache-netbeans-logo.png Forwarded Message Subject: AW: Merged to master (was Re: A NetBeans website proposal) Date: Mon, 26 Feb 2018 10:58:53 +0100 From: Christian LenzReply-To: dev@netbeans.incubator.apache.org To: dev@netbeans.incubator.apache.org I would like to Change the logo to the SVG file, because it scales better and we don’t have any Problems with Retina and whatever, as you can see it here: http://netbeans.apache.org/. I added the SVG too. Cheers Chris - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Merged to master (was Re: A NetBeans website proposal)
Gradle clean basically cleans the build directory used in java compilation. In the task compileContentSass for instance you source from $contentDir and write to $generatedAssetDir and these are not part of the java eco system. What you should do is create a new task which deletes all the directories you use and then do a clean.dependsOn(myCleanTask) so that is is run when clean is run. Another thing is noticed was you have a task to stop and start tomcat, there is a nice plugin on github (bmuschko/gradle-tomcat-plugin) which allows you to redeploy core easily. On 26 Feb 2018 10:42, "Neil C Smith"wrote: > On Mon, 26 Feb 2018 at 07:54 Antonio wrote: > > > This has now been merged to master, we think we comply with ASF's > > podling website requirements. > > > Woot! :-) > > Some other enhancements & to-dos as seen in the thread & elsewhere: > > ... > > - The README at > > > > https://github.com/apache/incubator-netbeans-website/ > tree/master/netbeans.apache.org > > explains how Wade's script work, how to run a preview site yourself, etc. > > > > > Note (for others) that you might need to run these commands to get the > correct output - > > ./gradlew clean > ./gradlew preprocessContent --rerun-tasks > ./gradlew bake > > One other useful task would be for someone who understands Gradle better > than Antonio or I to have a look at why the build (or sass plugin in > particular) is incorrectly caching even after cleaning. > > Best wishes, > > Neil > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >
Re: Merged to master (was Re: A NetBeans website proposal)
On Mon, 26 Feb 2018 at 07:54 Antoniowrote: > This has now been merged to master, we think we comply with ASF's > podling website requirements. Woot! :-) Some other enhancements & to-dos as seen in the thread & elsewhere: > ... > - The README at > > https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org > explains how Wade's script work, how to run a preview site yourself, etc. > > Note (for others) that you might need to run these commands to get the correct output - ./gradlew clean ./gradlew preprocessContent --rerun-tasks ./gradlew bake One other useful task would be for someone who understands Gradle better than Antonio or I to have a look at why the build (or sass plugin in particular) is incorrectly caching even after cleaning. Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
AW: Merged to master (was Re: A NetBeans website proposal)
I would like to Change the logo to the SVG file, because it scales better and we don’t have any Problems with Retina and whatever, as you can see it here: http://netbeans.apache.org/. I added the SVG too. Cheers Chris Von: Antonio Gesendet: Montag, 26. Februar 2018 08:54 An: dev@netbeans.incubator.apache.org Betreff: Merged to master (was Re: A NetBeans website proposal) Hi all, This has now been merged to master, we think we comply with ASF's podling website requirements. Feel free to submit PRs as you see fit. I've uploaded the bits at https://netbeans.vieiro.net temporarily, to verify that the "see this page in github" links work properly. This won't track master, and may dissappear within a few days. Thanks all involved and those giving comments and ideas. Have fun, Antonio == Main goals As Geertjan outlined in the mailing list thread the main goals for the netbeans.apache.org website are, in order of importance: 1- Have a proper IDE features page. 2- Port the IDE tutorials. 3- Have a platform specific page. Some other enhancements & to-dos as seen in the thread & elsewhere: - Improve image visualization (lightbox, for instance). - Add proper retina images (including the NetBeans logo). - The wiki pages should be reviewed, after review the bottom of the page should contain the review date. == Going live AFAIK the website won't go live until we update the content to the "asf-site" branch (i.e., until we copy the generated HTML into that branch), as I think this branch is currently connected with the web server through Apache's gitpubsub. I'll try to find out the details. == netbeans.apache.org help materials - The README at https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org explains how Wade's script work, how to run a preview site yourself, etc. - The templates directory README https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org/src/content/templates has information about building templates as "Groovy Server Pages" files, as well as the initial templates we're using. - The scss directory at https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org/src/content/scss Contains the initial SCSS files from Foundation adapted to netbeans. Other useful links: - jbake http://jbake.org/docs/2.5.1/ - foundation 6 for sites https://foundation.zurb.com/sites/docs/ - for those using asciidoc the AsciiDoc Writer's Guide at https://asciidoctor.org/docs/asciidoc-writers-guide/ == bits.netbeans.org The ant script at bits.netbeans.org needs some love to properly generate NetBeans javadoc files + arch stuff (properly tagged with release information, etc.). The directory structure from current "bits.netbeans.org" does not match the existing one. AFAIK we haven't set up a webserver for this domain, I imagine we can do this later on (probably using gitpubsub too in another "api" branch). On 23/02/18 08:19, Antonio wrote: > Hi all, > > Wade, Tim, Neil, Jirka, Geertjan and I have been doing some experiments > regarding the NetBeans website. > > As you probably know, the current NetBeans website comprises many > different webs: we have "bits.netbeans.org" for APIs, "netbeans.org" for > main content, "plugins.netbeans.org" for the Plugin Portal, > "wiki.netbeans.org" for the wiki, and there're a few more subdomains. > > The current "netbeans.org" website is quite big. As you already know, > Wade consolidated it in github's > "apache/incubator-netbeans-website-cleanup" [1] repo, and added a Gradle > build system that uses JBake to generate static content, where content > is markdown/asciidoc/html with some additional files. > > As the migration is going to take time, and will require Oracle > reviewing IP clearance for the content, we thought we could start a > simpler "netbeans.apache.org" website that uses the same Wade's scripts. > We then could add content gradually, as Oracle passes the IP clearance > procedures. > > So we came out with a basic "multisite-test" _branch_ at Github's > "incubator-netbeans-website" [2]. > > The idea of this branch is to be able to consolidate different NetBeans > subdomains as different directories (currently "bits.netbeans.org" and > "netbeans.apache.org"), and create scripts for generating _static_ > content for those different websites. Currently we have: > > - bits.netbeans.org > Currently builds the javadoc from sources. > > - netbeans.apache.org > - Has some basic content from current Confluence pages. > - As posted to the list in december we chose the Foundation 6 > framework as a, well, foundation, and Neil modified it with some proper > SCSS structure [3] to fit our needs. > - We've also added the wiki pages. We may set up a different repo > for these in the future, though. > - We've uploaded the result of this static site to > https://netbeans.vieiro.net for you to see live (note: the "see this
Merged to master (was Re: A NetBeans website proposal)
Hi all, This has now been merged to master, we think we comply with ASF's podling website requirements. Feel free to submit PRs as you see fit. I've uploaded the bits at https://netbeans.vieiro.net temporarily, to verify that the "see this page in github" links work properly. This won't track master, and may dissappear within a few days. Thanks all involved and those giving comments and ideas. Have fun, Antonio == Main goals As Geertjan outlined in the mailing list thread the main goals for the netbeans.apache.org website are, in order of importance: 1- Have a proper IDE features page. 2- Port the IDE tutorials. 3- Have a platform specific page. Some other enhancements & to-dos as seen in the thread & elsewhere: - Improve image visualization (lightbox, for instance). - Add proper retina images (including the NetBeans logo). - The wiki pages should be reviewed, after review the bottom of the page should contain the review date. == Going live AFAIK the website won't go live until we update the content to the "asf-site" branch (i.e., until we copy the generated HTML into that branch), as I think this branch is currently connected with the web server through Apache's gitpubsub. I'll try to find out the details. == netbeans.apache.org help materials - The README at https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org explains how Wade's script work, how to run a preview site yourself, etc. - The templates directory README https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org/src/content/templates has information about building templates as "Groovy Server Pages" files, as well as the initial templates we're using. - The scss directory at https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org/src/content/scss Contains the initial SCSS files from Foundation adapted to netbeans. Other useful links: - jbake http://jbake.org/docs/2.5.1/ - foundation 6 for sites https://foundation.zurb.com/sites/docs/ - for those using asciidoc the AsciiDoc Writer's Guide at https://asciidoctor.org/docs/asciidoc-writers-guide/ == bits.netbeans.org The ant script at bits.netbeans.org needs some love to properly generate NetBeans javadoc files + arch stuff (properly tagged with release information, etc.). The directory structure from current "bits.netbeans.org" does not match the existing one. AFAIK we haven't set up a webserver for this domain, I imagine we can do this later on (probably using gitpubsub too in another "api" branch). On 23/02/18 08:19, Antonio wrote: Hi all, Wade, Tim, Neil, Jirka, Geertjan and I have been doing some experiments regarding the NetBeans website. As you probably know, the current NetBeans website comprises many different webs: we have "bits.netbeans.org" for APIs, "netbeans.org" for main content, "plugins.netbeans.org" for the Plugin Portal, "wiki.netbeans.org" for the wiki, and there're a few more subdomains. The current "netbeans.org" website is quite big. As you already know, Wade consolidated it in github's "apache/incubator-netbeans-website-cleanup" [1] repo, and added a Gradle build system that uses JBake to generate static content, where content is markdown/asciidoc/html with some additional files. As the migration is going to take time, and will require Oracle reviewing IP clearance for the content, we thought we could start a simpler "netbeans.apache.org" website that uses the same Wade's scripts. We then could add content gradually, as Oracle passes the IP clearance procedures. So we came out with a basic "multisite-test" _branch_ at Github's "incubator-netbeans-website" [2]. The idea of this branch is to be able to consolidate different NetBeans subdomains as different directories (currently "bits.netbeans.org" and "netbeans.apache.org"), and create scripts for generating _static_ content for those different websites. Currently we have: - bits.netbeans.org Currently builds the javadoc from sources. - netbeans.apache.org - Has some basic content from current Confluence pages. - As posted to the list in december we chose the Foundation 6 framework as a, well, foundation, and Neil modified it with some proper SCSS structure [3] to fit our needs. - We've also added the wiki pages. We may set up a different repo for these in the future, though. - We've uploaded the result of this static site to https://netbeans.vieiro.net for you to see live (note: the "see this page in github" won't work until/if this branch merges to master). So to summarize, the objectives are: 1. Have all NetBeans websites in a single repo, with different folders for each. Maybe we want to share stuff among them in the future. 2. Have some scripts to build static content for those websites. 3. For web sites, make them comply with Apache's guidelines for web sites [4] If you think the idea is good enough then we may merge