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 that branch into master and start migrating content, and/or creating different subdirectories for other websites (such as the plugin portal, for instance).

So, please, say yes or no to keep this path of work. Some other ideas would also we welcome.

Kind regards,
Antonio


[1]
https://github.com/apache/incubator-netbeans-website-cleanup

[2]
https://github.com/apache/incubator-netbeans-website/tree/multisite-test

We've used asciidoc, but Wade's script supports markdown and html as well. An example asciidoc file, as rendered by github, can be seen here:

https://github.com/apache/incubator-netbeans-website/blob/multisite-test/netbeans.apache.org/src/content/download/index.asciidoc

[3]
Neil's impressive SCSS organization is here:
https://github.com/apache/incubator-netbeans-website/tree/multisite-test/netbeans.apache.org/src/content/scss

(note: some low quality scss stuff in there is my fault, not Neil's)

[4]

Apache Navigation Links Policy
https://www.apache.org/foundation/marks/pmcs#navigation

Incubator Branding Guide
http://incubator.apache.org/guides/branding.html


---------------------------------------------------------------------
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



Reply via email to