You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Wade Chandler <wa...@apache.org> on 2017/02/20 18:39:59 UTC
Apache NetBeans (Incubating) Web Site Change Planning
All,
I suggest we setup a Wiki page to start to layout a plan for the Apache NetBeans (Incubating) web site. For instance, change the folder “bilder” to “images”, etc. But, too, to start to setup some formal research into which technology we will use along with a build to allow branding modifications without SED or something else horribly hard to use as we will have a static site. A site generator would come in extremely handy for this. I’m sure various other threads can spawn from this. Has anyone already setup a page for this? If not, I can go ahead and do that. From there we can formulate topics as well as point to and create JIRA tickets for us to take ownership and work on.
Thanks,
Wade
===================
Wade Chandler
e: consult@wadechandler.com
Re: Apache NetBeans (Incubating) Web Site Change Planning
Posted by Wade Chandler <wa...@apache.org>.
===================
Wade Chandler
e: consult@wadechandler.com
> On Feb 20, 2017, at 14:07, Geertjan Wielenga <ge...@googlemail.com> wrote:
>
> (and hey I bet we'll do
> some experimentation too at the NetBeans booth at DevNexus!)
That will certainly be good and fun! :-)
> and we should
> collect our findings and proposals on that child page.
Sounds good. I will set one up.
Thanks,
Wade
Re: Apache NetBeans (Incubating) Web Site Change Planning
Posted by Wade Chandler <wa...@apache.org>.
I set this child page up:
https://cwiki.apache.org/confluence/display/NETBEANS/New+NetBeans+Web+Site+Planning <https://cwiki.apache.org/confluence/display/NETBEANS/New+NetBeans+Web+Site+Planning>
I put a basic framework in place which we can fill in. In my opinion, the first priority is hashing out the “Interim Plan For Site Maintenance”. Perhaps myself or someone else can give some thought to this, and start a thread for that specific discussion.
Then in my opinion, the next priority would be “Tool Selection Criteria” to setup some priorities we see for tool capabilities and features. Then we can get into tool enumeration followed by some research. Then finally selection. We can follow that up with the site layout discussion. Then we can take things to the next level with a new site plan, and start to pic apart some of the content to be moved over etc. Again, these are my opinions on how this could work in a fairly organized and transparent fashion.
Thanks,
Wade
> On Feb 20, 2017, at 14:27, Wade Chandler <wa...@apache.org> wrote:
>
> Right, I’m not sure how much of that is out of date now considering the git sites plus github etc; I saw something about Apache CMS recently, but cannot remember the exact details. I will look for that email. I’m sure we’ll see some patterns by investigating the other Apache Git based projects site builds and tools.
>
> Thanks Gj,
>
> Wade
>
>
>
>> On Feb 20, 2017, at 14:15, Geertjan Wielenga <geertjan.wielenga@googlemail.com <ma...@googlemail.com>> wrote:
>>
>> Web Site Generation Tool
>>
>> The choice of tool used to generate the web site is left to the podling. If
>> you already have a tool that you are comfortable with, you can continue to
>> use it. If you do not, consider using the Apache CMS
>> <http://www.apache.org/dev/cmsref.html <http://www.apache.org/dev/cmsref.html>>.
>>
>> Regardless of which tool you use, the web site should be maintained in the
>> svn repository, and include the site generation tool as a binary file. This
>> simplifies the process of site generation and enables changes to the site
>> to be made by any committer. The generated site should also be checked into
>> svn. This allows the generated site to be relocated to any part of the
>> Apache site after incubation is complete.
>>
>> Since the site is independent of the code, it should exist high in the svn
>> repository, e.g. parallel to the trunk of the source tree.
>>
>> From: http://incubator.apache.org/guides/sites.html <http://incubator.apache.org/guides/sites.html>
>>
>>
>>
>> On Mon, Feb 20, 2017 at 8:07 PM, Geertjan Wielenga <
>> geertjan.wielenga@googlemail.com <ma...@googlemail.com>> wrote:
>>
>>> Yup, excellent. I'm going to experiment a bit too (and hey I bet we'll do
>>> some experimentation too at the NetBeans booth at DevNexus!) and we should
>>> collect our findings and proposals on that child page. I have the
>>> netbeans.org <http://netbeans.org/> website checked out and am trying to see how to make the new
>>> Apache site structure as close to the original as possible -- while a lot
>>> of the original site is simply historic and can be omitted, i.e., it's
>>> mostly a question of transferring feature pages and tutorials.
>>>
>>> Gj
>>>
>>> On Mon, Feb 20, 2017 at 7:43 PM, Wade Chandler <wadechandler@apache.org <ma...@apache.org>>
>>> wrote:
>>>
>>>> I imagine we could use this or a child page of it which Gj setup:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site <https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site> <
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site <https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site>>
>>>>
>>>> …probably a child page will be better?
>>>>
>>>> Wade
>>>>
>>>>
>>>>> On Feb 20, 2017, at 13:39, Wade Chandler <wadechandler@apache.org <ma...@apache.org>>
>>>> wrote:
>>>>>
>>>>> All,
>>>>>
>>>>> I suggest we setup a Wiki page to start to layout a plan for the Apache
>>>> NetBeans (Incubating) web site. For instance, change the folder “bilder” to
>>>> “images”, etc. But, too, to start to setup some formal research into which
>>>> technology we will use along with a build to allow branding modifications
>>>> without SED or something else horribly hard to use as we will have a static
>>>> site. A site generator would come in extremely handy for this. I’m sure
>>>> various other threads can spawn from this. Has anyone already setup a page
>>>> for this? If not, I can go ahead and do that. From there we can formulate
>>>> topics as well as point to and create JIRA tickets for us to take ownership
>>>> and work on.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Wade
>>>>>
>>>>>
>>>>> ===================
>>>>>
>>>>> Wade Chandler
>>>>> e: consult@wadechandler.com <ma...@wadechandler.com> <mailto:consult@wadechandler.com <ma...@wadechandler.com>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>
Re: Apache NetBeans (Incubating) Web Site Change Planning
Posted by Wade Chandler <wa...@apache.org>.
Right, I’m not sure how much of that is out of date now considering the git sites plus github etc; I saw something about Apache CMS recently, but cannot remember the exact details. I will look for that email. I’m sure we’ll see some patterns by investigating the other Apache Git based projects site builds and tools.
Thanks Gj,
Wade
> On Feb 20, 2017, at 14:15, Geertjan Wielenga <ge...@googlemail.com> wrote:
>
> Web Site Generation Tool
>
> The choice of tool used to generate the web site is left to the podling. If
> you already have a tool that you are comfortable with, you can continue to
> use it. If you do not, consider using the Apache CMS
> <http://www.apache.org/dev/cmsref.html>.
>
> Regardless of which tool you use, the web site should be maintained in the
> svn repository, and include the site generation tool as a binary file. This
> simplifies the process of site generation and enables changes to the site
> to be made by any committer. The generated site should also be checked into
> svn. This allows the generated site to be relocated to any part of the
> Apache site after incubation is complete.
>
> Since the site is independent of the code, it should exist high in the svn
> repository, e.g. parallel to the trunk of the source tree.
>
> From: http://incubator.apache.org/guides/sites.html
>
>
>
> On Mon, Feb 20, 2017 at 8:07 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
>> Yup, excellent. I'm going to experiment a bit too (and hey I bet we'll do
>> some experimentation too at the NetBeans booth at DevNexus!) and we should
>> collect our findings and proposals on that child page. I have the
>> netbeans.org website checked out and am trying to see how to make the new
>> Apache site structure as close to the original as possible -- while a lot
>> of the original site is simply historic and can be omitted, i.e., it's
>> mostly a question of transferring feature pages and tutorials.
>>
>> Gj
>>
>> On Mon, Feb 20, 2017 at 7:43 PM, Wade Chandler <wa...@apache.org>
>> wrote:
>>
>>> I imagine we could use this or a child page of it which Gj setup:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site <
>>> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site>
>>>
>>> …probably a child page will be better?
>>>
>>> Wade
>>>
>>>
>>>> On Feb 20, 2017, at 13:39, Wade Chandler <wa...@apache.org>
>>> wrote:
>>>>
>>>> All,
>>>>
>>>> I suggest we setup a Wiki page to start to layout a plan for the Apache
>>> NetBeans (Incubating) web site. For instance, change the folder “bilder” to
>>> “images”, etc. But, too, to start to setup some formal research into which
>>> technology we will use along with a build to allow branding modifications
>>> without SED or something else horribly hard to use as we will have a static
>>> site. A site generator would come in extremely handy for this. I’m sure
>>> various other threads can spawn from this. Has anyone already setup a page
>>> for this? If not, I can go ahead and do that. From there we can formulate
>>> topics as well as point to and create JIRA tickets for us to take ownership
>>> and work on.
>>>>
>>>> Thanks,
>>>>
>>>> Wade
>>>>
>>>>
>>>> ===================
>>>>
>>>> Wade Chandler
>>>> e: consult@wadechandler.com <ma...@wadechandler.com>
>>>>
>>>>
>>>>
>>>
>>>
>>
Re: Apache NetBeans (Incubating) Web Site Change Planning
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Web Site Generation Tool
The choice of tool used to generate the web site is left to the podling. If
you already have a tool that you are comfortable with, you can continue to
use it. If you do not, consider using the Apache CMS
<http://www.apache.org/dev/cmsref.html>.
Regardless of which tool you use, the web site should be maintained in the
svn repository, and include the site generation tool as a binary file. This
simplifies the process of site generation and enables changes to the site
to be made by any committer. The generated site should also be checked into
svn. This allows the generated site to be relocated to any part of the
Apache site after incubation is complete.
Since the site is independent of the code, it should exist high in the svn
repository, e.g. parallel to the trunk of the source tree.
From: http://incubator.apache.org/guides/sites.html
On Mon, Feb 20, 2017 at 8:07 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Yup, excellent. I'm going to experiment a bit too (and hey I bet we'll do
> some experimentation too at the NetBeans booth at DevNexus!) and we should
> collect our findings and proposals on that child page. I have the
> netbeans.org website checked out and am trying to see how to make the new
> Apache site structure as close to the original as possible -- while a lot
> of the original site is simply historic and can be omitted, i.e., it's
> mostly a question of transferring feature pages and tutorials.
>
> Gj
>
> On Mon, Feb 20, 2017 at 7:43 PM, Wade Chandler <wa...@apache.org>
> wrote:
>
>> I imagine we could use this or a child page of it which Gj setup:
>> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site <
>> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site>
>>
>> …probably a child page will be better?
>>
>> Wade
>>
>>
>> > On Feb 20, 2017, at 13:39, Wade Chandler <wa...@apache.org>
>> wrote:
>> >
>> > All,
>> >
>> > I suggest we setup a Wiki page to start to layout a plan for the Apache
>> NetBeans (Incubating) web site. For instance, change the folder “bilder” to
>> “images”, etc. But, too, to start to setup some formal research into which
>> technology we will use along with a build to allow branding modifications
>> without SED or something else horribly hard to use as we will have a static
>> site. A site generator would come in extremely handy for this. I’m sure
>> various other threads can spawn from this. Has anyone already setup a page
>> for this? If not, I can go ahead and do that. From there we can formulate
>> topics as well as point to and create JIRA tickets for us to take ownership
>> and work on.
>> >
>> > Thanks,
>> >
>> > Wade
>> >
>> >
>> > ===================
>> >
>> > Wade Chandler
>> > e: consult@wadechandler.com <ma...@wadechandler.com>
>> >
>> >
>> >
>>
>>
>
Re: Apache NetBeans (Incubating) Web Site Change Planning
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Yup, excellent. I'm going to experiment a bit too (and hey I bet we'll do
some experimentation too at the NetBeans booth at DevNexus!) and we should
collect our findings and proposals on that child page. I have the
netbeans.org website checked out and am trying to see how to make the new
Apache site structure as close to the original as possible -- while a lot
of the original site is simply historic and can be omitted, i.e., it's
mostly a question of transferring feature pages and tutorials.
Gj
On Mon, Feb 20, 2017 at 7:43 PM, Wade Chandler <wa...@apache.org>
wrote:
> I imagine we could use this or a child page of it which Gj setup:
> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site <
> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site>
>
> …probably a child page will be better?
>
> Wade
>
>
> > On Feb 20, 2017, at 13:39, Wade Chandler <wa...@apache.org>
> wrote:
> >
> > All,
> >
> > I suggest we setup a Wiki page to start to layout a plan for the Apache
> NetBeans (Incubating) web site. For instance, change the folder “bilder” to
> “images”, etc. But, too, to start to setup some formal research into which
> technology we will use along with a build to allow branding modifications
> without SED or something else horribly hard to use as we will have a static
> site. A site generator would come in extremely handy for this. I’m sure
> various other threads can spawn from this. Has anyone already setup a page
> for this? If not, I can go ahead and do that. From there we can formulate
> topics as well as point to and create JIRA tickets for us to take ownership
> and work on.
> >
> > Thanks,
> >
> > Wade
> >
> >
> > ===================
> >
> > Wade Chandler
> > e: consult@wadechandler.com <ma...@wadechandler.com>
> >
> >
> >
>
>
Re: Apache NetBeans (Incubating) Web Site Change Planning
Posted by Wade Chandler <wa...@apache.org>.
I imagine we could use this or a child page of it which Gj setup:
https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site <https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Site>
…probably a child page will be better?
Wade
> On Feb 20, 2017, at 13:39, Wade Chandler <wa...@apache.org> wrote:
>
> All,
>
> I suggest we setup a Wiki page to start to layout a plan for the Apache NetBeans (Incubating) web site. For instance, change the folder “bilder” to “images”, etc. But, too, to start to setup some formal research into which technology we will use along with a build to allow branding modifications without SED or something else horribly hard to use as we will have a static site. A site generator would come in extremely handy for this. I’m sure various other threads can spawn from this. Has anyone already setup a page for this? If not, I can go ahead and do that. From there we can formulate topics as well as point to and create JIRA tickets for us to take ownership and work on.
>
> Thanks,
>
> Wade
>
>
> ===================
>
> Wade Chandler
> e: consult@wadechandler.com <ma...@wadechandler.com>
>
>
>