[DISCUSS] Migrating to the New Incubator Website

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Migrating to the New Incubator Website

John D. Ament-2
All,

I'd like to start the process to move forward on a new incubator website.
Based on discussions in the past on list, I wanted to do the following:

- Roll out a new technology stack + repository
- Leave content in place, while we work later on content enhancements

For right now, I'm planning to leave the existing /projects and
/ip-clearance in place.  My hope is that we may not need them in the future.

The website staging area can be seen here:
https://incubator.apache.org/ngtest/
The git repository for the site can be seen here:
https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
(with
github mirror at https://github.com/apache/incubator/tree/jbake-site )

I'd like to get some final feedback on the layout and colors (not the
content).  I want to start tracking content enhancements in JIRA to help
come up with a backlog of areas of improvement for our incubator guides.

John
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

sebb-2-2
On 17 June 2017 at 13:35, John D. Ament <[hidden email]> wrote:
> All,
>
> I'd like to start the process to move forward on a new incubator website.
> Based on discussions in the past on list, I wanted to do the following:

I missed those, so some of my comments may be unnecessary ...

> - Roll out a new technology stack + repository

Is this going to be documented somewhere?

> - Leave content in place, while we work later on content enhancements
>
> For right now, I'm planning to leave the existing /projects and
> /ip-clearance in place.  My hope is that we may not need them in the future.

/projects files are currently referenced from lots of places.

This includes retired podling website urls which redirect to the
relevant projects/podling.html file.
These are set up as permanent redirects in .htaccess files.

The list of graduated and retired projects needs to be accessible.

> The website staging area can be seen here:
> https://incubator.apache.org/ngtest/
> The git repository for the site can be seen here:
> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
> (with
> github mirror at https://github.com/apache/incubator/tree/jbake-site )
>
> I'd like to get some final feedback on the layout and colors (not the
> content).

The layout and colours seem fine to me, but I was happy with the
present layout (which was redone not that long ago?)

All existing (major) URLs should continue to work to avoid
invalidating bookmarks.

> I want to start tracking content enhancements in JIRA to help
> come up with a backlog of areas of improvement for our incubator guides.
>
> John

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Raphael Bircher-2
In reply to this post by John D. Ament-2
Hi John

Am .06.2017, 14:35 Uhr, schrieb John D. Ament <[hidden email]>:

> All,
>
> I'd like to start the process to move forward on a new incubator website.
> Based on discussions in the past on list, I wanted to do the following:
>
> - Roll out a new technology stack + repository
> - Leave content in place, while we work later on content enhancements
>
> For right now, I'm planning to leave the existing /projects and
> /ip-clearance in place.  My hope is that we may not need them in the  
> future.
>
> The website staging area can be seen here:
> https://incubator.apache.org/ngtest/
1) When you think to add the navigation?
2) The code part has a syntax heightlighting. witch is not so nice if you  
have a simple text file. (a template for a E-mail for example.

Regards, Raphael


--
My introduction https://youtu.be/Ln4vly5sxYU

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Pierre Smits
From a UX point of view I would move the 'About The Apache Software
Foundation' to below the lists of codlings.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Sat, Jun 17, 2017 at 9:05 PM, Raphael Bircher <[hidden email]>
wrote:

> Hi John
>
> Am .06.2017, 14:35 Uhr, schrieb John D. Ament <[hidden email]>:
>
> All,
>>
>> I'd like to start the process to move forward on a new incubator website.
>> Based on discussions in the past on list, I wanted to do the following:
>>
>> - Roll out a new technology stack + repository
>> - Leave content in place, while we work later on content enhancements
>>
>> For right now, I'm planning to leave the existing /projects and
>> /ip-clearance in place.  My hope is that we may not need them in the
>> future.
>>
>> The website staging area can be seen here:
>> https://incubator.apache.org/ngtest/
>>
> 1) When you think to add the navigation?
> 2) The code part has a syntax heightlighting. witch is not so nice if you
> have a simple text file. (a template for a E-mail for example.
>
> Regards, Raphael
>
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

John D. Ament-2
In reply to this post by sebb-2-2
On Sat, Jun 17, 2017 at 8:53 AM sebb <[hidden email]> wrote:

> On 17 June 2017 at 13:35, John D. Ament <[hidden email]> wrote:
> > All,
> >
> > I'd like to start the process to move forward on a new incubator website.
> > Based on discussions in the past on list, I wanted to do the following:
>
> I missed those, so some of my comments may be unnecessary ...
>

Your input is never unnecessary Sebb :-)


>
> > - Roll out a new technology stack + repository
>
> Is this going to be documented somewhere?
>

Yes, I think it'll be useful to include a README (a new norm?) on how it
works + create the equivalent of
https://incubator.apache.org/ngtest/guides/website.html for the new git
repo + jbake, plus docs on how the jenkins job works (over CMS)


>
> > - Leave content in place, while we work later on content enhancements
> >
> > For right now, I'm planning to leave the existing /projects and
> > /ip-clearance in place.  My hope is that we may not need them in the
> future.
>
> /projects files are currently referenced from lots of places.
>

ACK.  I have no intention of dropping /projects anytime soon, at least not
until Whimsy can handle all of these use cases.


>
> This includes retired podling website urls which redirect to the
> relevant projects/podling.html file.
> These are set up as permanent redirects in .htaccess files.
>

I'm wondering if this can just show a 404 page after a while?  For TLPs we
show an attic notice, but podlings may have never gotten through a release.


>
> The list of graduated and retired projects needs to be accessible.
>

While we provide this service today, I'm wondering what the use case is for
it?  Is it just to see that after they've graduated they had everything
done?


>
> > The website staging area can be seen here:
> > https://incubator.apache.org/ngtest/
> > The git repository for the site can be seen here:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
> > (with
> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
> >
> > I'd like to get some final feedback on the layout and colors (not the
> > content).
>
> The layout and colours seem fine to me, but I was happy with the
> present layout (which was redone not that long ago?)
>

It has to be ~ 6 years, at least, the incubator website looks the same as
when I first got here.


>
> All existing (major) URLs should continue to work to avoid
> invalidating bookmarks.
>

Sure, I'm assuming you'd be OK with a .htaccess doing redirects?  Just note
at some point we will be moving content around.


>
> > I want to start tracking content enhancements in JIRA to help
> > come up with a backlog of areas of improvement for our incubator guides.
> >
> > John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

John D. Ament-2
In reply to this post by Raphael Bircher-2
On Sat, Jun 17, 2017 at 3:05 PM Raphael Bircher <[hidden email]>
wrote:

> Hi John
>
> Am .06.2017, 14:35 Uhr, schrieb John D. Ament <[hidden email]>:
>
> > All,
> >
> > I'd like to start the process to move forward on a new incubator website.
> > Based on discussions in the past on list, I wanted to do the following:
> >
> > - Roll out a new technology stack + repository
> > - Leave content in place, while we work later on content enhancements
> >
> > For right now, I'm planning to leave the existing /projects and
> > /ip-clearance in place.  My hope is that we may not need them in the
> > future.
> >
> > The website staging area can be seen here:
> > https://incubator.apache.org/ngtest/
> 1) When you think to add the navigation?
>

Which navigation?  There's a header on top, similar to the top level www.


> 2) The code part has a syntax heightlighting. witch is not so nice if you
> have a simple text file. (a template for a E-mail for example.
>

Yeah, hm.  I think that's because I'm using asciidoctor's [source] instead
of [literal] but will check.



>
> Regards, Raphael
>
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

John D. Ament-2
In reply to this post by Pierre Smits
On Sat, Jun 17, 2017 at 3:51 PM Pierre Smits <[hidden email]> wrote:

> From a UX point of view I would move the 'About The Apache Software
> Foundation' to below the lists of codlings.
>

Hmmm ok.  I'm not sure the text is relevant, and i'm not sure how much
people will scroll through the list of podlings (I included it to simply
mirror existing behavior).  I do think the whole header area needs a bit
more work.


>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Sat, Jun 17, 2017 at 9:05 PM, Raphael Bircher <[hidden email]
> >
> wrote:
>
> > Hi John
> >
> > Am .06.2017, 14:35 Uhr, schrieb John D. Ament <[hidden email]>:
> >
> > All,
> >>
> >> I'd like to start the process to move forward on a new incubator
> website.
> >> Based on discussions in the past on list, I wanted to do the following:
> >>
> >> - Roll out a new technology stack + repository
> >> - Leave content in place, while we work later on content enhancements
> >>
> >> For right now, I'm planning to leave the existing /projects and
> >> /ip-clearance in place.  My hope is that we may not need them in the
> >> future.
> >>
> >> The website staging area can be seen here:
> >> https://incubator.apache.org/ngtest/
> >>
> > 1) When you think to add the navigation?
> > 2) The code part has a syntax heightlighting. witch is not so nice if you
> > have a simple text file. (a template for a E-mail for example.
> >
> > Regards, Raphael
> >
> >
> > --
> > My introduction https://youtu.be/Ln4vly5sxYU
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

sebb-2-2
In reply to this post by John D. Ament-2
On 17 June 2017 at 21:42, John D. Ament <[hidden email]> wrote:
> On Sat, Jun 17, 2017 at 8:53 AM sebb <[hidden email]> wrote:
>
>> On 17 June 2017 at 13:35, John D. Ament <[hidden email]> wrote:
>> > All,
>> >
>> > I'd like to start the process to move forward on a new incubator website.
>> > Based on discussions in the past on list, I wanted to do the following:
>>

...

>> This includes retired podling website urls which redirect to the
>> relevant projects/podling.html file.
>> These are set up as permanent redirects in .htaccess files.
>>
>
> I'm wondering if this can just show a 404 page after a while?  For TLPs we
> show an attic notice, but podlings may have never gotten through a release.

I think it's important that the general public can find out what
happened to a podling.
They might be interested in the code.

>
>>
>> The list of graduated and retired projects needs to be accessible.
>>
>
> While we provide this service today, I'm wondering what the use case is for
> it?  Is it just to see that after they've graduated they had everything
> done?

Again so that the general public can find out what happened to a
podling they might be interested in.

Or indeed to find some software that covers an area they are interested in.
If the podling retired, the code is potentially still available for
others to use.
But they need to be able to find it.

There may be other uses.

It's really annoying when such information disappears.
We should not force users to rely on the Internet Archive.

>
>>
>> > The website staging area can be seen here:
>> > https://incubator.apache.org/ngtest/
>> > The git repository for the site can be seen here:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
>> > (with
>> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
>> >
>> > I'd like to get some final feedback on the layout and colors (not the
>> > content).
>>
>> The layout and colours seem fine to me, but I was happy with the
>> present layout (which was redone not that long ago?)
>>
>
> It has to be ~ 6 years, at least, the incubator website looks the same as
> when I first got here.

Time flies ...

>
>>
>> All existing (major) URLs should continue to work to avoid
>> invalidating bookmarks.
>>
>
> Sure, I'm assuming you'd be OK with a .htaccess doing redirects?  Just note
> at some point we will be moving content around.

I guess redirects are OK, but better would be not to move things.

>
>>
>> > I want to start tracking content enhancements in JIRA to help
>> > come up with a backlog of areas of improvement for our incubator guides.
>> >
>> > John
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Bertrand Delacretaz
In reply to this post by John D. Ament-2
Hi,

On Sat, Jun 17, 2017 at 2:35 PM, John D. Ament <[hidden email]> wrote:
> ...The git repository for the site can be seen here:
> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site ...

Just one detail, I'm also working on converting the Sling site to
JBake [1] and like the Tamaya podling website did I have included
JBake in a ./bin folder to make it easier for everybody to use the
same version.

-Bertrand

[1] https://issues.apache.org/jira/browse/SLING-6955 - repo will be at
https://git-wip-us.apache.org/repos/asf?p=sling-sling-site.git soon

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

John D. Ament-2
On Mon, Jun 19, 2017 at 7:15 AM Bertrand Delacretaz <
[hidden email]> wrote:

> Hi,
>
> On Sat, Jun 17, 2017 at 2:35 PM, John D. Ament <[hidden email]>
> wrote:
> > ...The git repository for the site can be seen here:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
> ...
>
> Just one detail, I'm also working on converting the Sling site to
> JBake [1] and like the Tamaya podling website did I have included
> JBake in a ./bin folder to make it easier for everybody to use the
> same version.
>
>
I ended up working with Gav to get 2.5.1 installed on jenkins slaves,
buildbot slaves are coming next.  Not sure if that's of interest to you.
The Tamaya guys are who introduced me to JBake.


> -Bertrand
>
> [1] https://issues.apache.org/jira/browse/SLING-6955 - repo will be at
> https://git-wip-us.apache.org/repos/asf?p=sling-sling-site.git soon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Bertrand Delacretaz
On Mon, Jun 19, 2017 at 2:04 PM, John D. Ament <[hidden email]> wrote:
> On Mon, Jun 19, 2017 at 7:15 AM Bertrand Delacretaz <
> [hidden email]> wrote:
>>...I have included
>> JBake in a ./bin folder to make it easier for everybody to use the
>> same version...

> I ended up working with Gav to get 2.5.1 installed on jenkins slaves,
> buildbot slaves are coming next.  Not sure if that's of interest to you...

Jenkins maybe, but the idea for me is to make it easy for contributors
to run the website generation locally for creating content.

Anyway that was just a suggestion, and it looks like we're following
the same example anyway ;-)

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Suneel Marthi
In reply to this post by John D. Ament-2
FWIW, the Apache OpenNLP project recently moved to a new website using
JBake - http://opennlp.apache.org

On Mon, Jun 19, 2017 at 2:04 PM, John D. Ament <[hidden email]>
wrote:

> On Mon, Jun 19, 2017 at 7:15 AM Bertrand Delacretaz <
> [hidden email]> wrote:
>
> > Hi,
> >
> > On Sat, Jun 17, 2017 at 2:35 PM, John D. Ament <[hidden email]>
> > wrote:
> > > ...The git repository for the site can be seen here:
> > >
> > https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
> shortlog;h=refs/heads/jbake-site
> > ...
> >
> > Just one detail, I'm also working on converting the Sling site to
> > JBake [1] and like the Tamaya podling website did I have included
> > JBake in a ./bin folder to make it easier for everybody to use the
> > same version.
> >
> >
> I ended up working with Gav to get 2.5.1 installed on jenkins slaves,
> buildbot slaves are coming next.  Not sure if that's of interest to you.
> The Tamaya guys are who introduced me to JBake.
>
>
> > -Bertrand
> >
> > [1] https://issues.apache.org/jira/browse/SLING-6955 - repo will be at
> > https://git-wip-us.apache.org/repos/asf?p=sling-sling-site.git soon
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Raphael Bircher-2
In reply to this post by Bertrand Delacretaz
Hi all

Am .06.2017, 14:07 Uhr, schrieb Bertrand Delacretaz  
<[hidden email]>:

> On Mon, Jun 19, 2017 at 2:04 PM, John D. Ament <[hidden email]>  
> wrote:
>> On Mon, Jun 19, 2017 at 7:15 AM Bertrand Delacretaz <
>> [hidden email]> wrote:
>>> ...I have included
>>> JBake in a ./bin folder to make it easier for everybody to use the
>>> same version...
>
>> I ended up working with Gav to get 2.5.1 installed on jenkins slaves,
>> buildbot slaves are coming next.  Not sure if that's of interest to  
>> you...
That would be great.
>
> Jenkins maybe, but the idea for me is to make it easy for contributors
> to run the website generation locally for creating content.
For my point of view, an automated build is better. Else you need to  
install the tools every time first. If you jest have a small improvement,  
you maybe don't do the change.

Regards, Raphael

--
My introduction https://youtu.be/Ln4vly5sxYU

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Ted Dunning
On Mon, Jun 19, 2017 at 8:56 AM, Raphael Bircher <[hidden email]>
wrote:

> Jenkins maybe, but the idea for me is to make it easy for contributors
>> to run the website generation locally for creating content.
>>
> For my point of view, an automated build is better. Else you need to
> install the tools every time first. If you jest have a small improvement,
> you maybe don't do the change.
>

Automated is required. No doubt.

But local running is very, very handy for anything larger than typo
correction.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Greg Stein-4
On Mon, Jun 19, 2017 at 9:42 AM, Ted Dunning <[hidden email]> wrote:

> On Mon, Jun 19, 2017 at 8:56 AM, Raphael Bircher <[hidden email]
> >
> wrote:
>
> > Jenkins maybe, but the idea for me is to make it easy for contributors
> >> to run the website generation locally for creating content.
> >>
> > For my point of view, an automated build is better. Else you need to
> > install the tools every time first. If you jest have a small improvement,
> > you maybe don't do the change.
> >
>
> Automated is required. No doubt.
>
> But local running is very, very handy for anything larger than typo
> correction.
>

Infra and some others have been using Pelican to generate content. It
provides a local server to check your changes before you commit/push them.
We have both git and svn repositories, feeding into buildbots to generate
the site from the Markdown content.

Cheers,
-g
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Patrick Hunt-3
In reply to this post by John D. Ament-2
On Sat, Jun 17, 2017 at 5:35 AM, John D. Ament <[hidden email]>
wrote:

> All,
>
> I'd like to start the process to move forward on a new incubator website.
> Based on discussions in the past on list, I wanted to do the following:
>
> - Roll out a new technology stack + repository
> - Leave content in place, while we work later on content enhancements
>
> For right now, I'm planning to leave the existing /projects and
> /ip-clearance in place.  My hope is that we may not need them in the
> future.
>
> The website staging area can be seen here:
> https://incubator.apache.org/ngtest/
> The git repository for the site can be seen here:
> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
> shortlog;h=refs/heads/jbake-site
> (with
> github mirror at https://github.com/apache/incubator/tree/jbake-site )
>
> I'd like to get some final feedback on the layout and colors (not the
> content).  I want to start tracking content enhancements in JIRA to help
> come up with a backlog of areas of improvement for our incubator guides.
>
>
I'm very familiar with the old layout, so this may be coloring my feedback.
However I find the new layout to be less usable than previous. In
particular the drop downs lack structure. I think it would be better to
focus on "solutions" e.g. "bootstrapping a new podling" along with assoc
docs, or "graduating a podingling" etc... - basically focus around the
lifecycle of podling rather than a big long list of "guides". Additionally
it's hard to find things with the new layout, I used to use the browser
"search" feature to narrow down to a particular doc. Now I need to click on
each of the drop downs to find the content I'm looking for. Additionally
things like wiki/faq/etc... - can't find them at all.

Patrick


> John
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

Ted Dunning
I like the idea of focusing around the podling life-cycle.



On Thu, Jun 22, 2017 at 9:49 AM, Patrick Hunt <[hidden email]> wrote:

> On Sat, Jun 17, 2017 at 5:35 AM, John D. Ament <[hidden email]>
> wrote:
>
> > All,
> >
> > I'd like to start the process to move forward on a new incubator website.
> > Based on discussions in the past on list, I wanted to do the following:
> >
> > - Roll out a new technology stack + repository
> > - Leave content in place, while we work later on content enhancements
> >
> > For right now, I'm planning to leave the existing /projects and
> > /ip-clearance in place.  My hope is that we may not need them in the
> > future.
> >
> > The website staging area can be seen here:
> > https://incubator.apache.org/ngtest/
> > The git repository for the site can be seen here:
> > https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
> > shortlog;h=refs/heads/jbake-site
> > (with
> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
> >
> > I'd like to get some final feedback on the layout and colors (not the
> > content).  I want to start tracking content enhancements in JIRA to help
> > come up with a backlog of areas of improvement for our incubator guides.
> >
> >
> I'm very familiar with the old layout, so this may be coloring my feedback.
> However I find the new layout to be less usable than previous. In
> particular the drop downs lack structure. I think it would be better to
> focus on "solutions" e.g. "bootstrapping a new podling" along with assoc
> docs, or "graduating a podingling" etc... - basically focus around the
> lifecycle of podling rather than a big long list of "guides". Additionally
> it's hard to find things with the new layout, I used to use the browser
> "search" feature to narrow down to a particular doc. Now I need to click on
> each of the drop downs to find the content I'm looking for. Additionally
> things like wiki/faq/etc... - can't find them at all.
>
> Patrick
>
>
> > John
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

John D. Ament-2
In reply to this post by Patrick Hunt-3
On Thu, Jun 22, 2017 at 12:50 PM Patrick Hunt <[hidden email]> wrote:

> On Sat, Jun 17, 2017 at 5:35 AM, John D. Ament <[hidden email]>
> wrote:
>
> > All,
> >
> > I'd like to start the process to move forward on a new incubator website.
> > Based on discussions in the past on list, I wanted to do the following:
> >
> > - Roll out a new technology stack + repository
> > - Leave content in place, while we work later on content enhancements
> >
> > For right now, I'm planning to leave the existing /projects and
> > /ip-clearance in place.  My hope is that we may not need them in the
> > future.
> >
> > The website staging area can be seen here:
> > https://incubator.apache.org/ngtest/
> > The git repository for the site can be seen here:
> > https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
> > shortlog;h=refs/heads/jbake-site
> > (with
> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
> >
> > I'd like to get some final feedback on the layout and colors (not the
> > content).  I want to start tracking content enhancements in JIRA to help
> > come up with a backlog of areas of improvement for our incubator guides.
> >
> >
> I'm very familiar with the old layout, so this may be coloring my feedback.
> However I find the new layout to be less usable than previous. In
> particular the drop downs lack structure. I think it would be better to
> focus on "solutions" e.g. "bootstrapping a new podling" along with assoc
> docs, or "graduating a podingling" etc... - basically focus around the
> lifecycle of podling rather than a big long list of "guides". Additionally
> it's hard to find things with the new layout, I used to use the browser
> "search" feature to narrow down to a particular doc. Now I need to click on
> each of the drop downs to find the content I'm looking for. Additionally
> things like wiki/faq/etc... - can't find them at all.
>
>
Hi Patrick,

Thanks for the input.  I've started to add it to the new version, let me
know your thoughts.  There's still a few areas to tweak, but definitely
keep it coming.

I have to still add a link to google search.

John


> Patrick
>
>
> > John
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Migrating to the New Incubator Website

John D. Ament-2
It seems the discussion has died down.  I'm going to plan to finalize the
last few parts, make the jenkins job also build the legacy bits and move to
the new site sometime next week.

I'll drop a mail when I have the last of it staged and ready to go.

John

On Sat, Jun 24, 2017 at 10:27 AM John D. Ament <[hidden email]>
wrote:

> On Thu, Jun 22, 2017 at 12:50 PM Patrick Hunt <[hidden email]> wrote:
>
>> On Sat, Jun 17, 2017 at 5:35 AM, John D. Ament <[hidden email]>
>> wrote:
>>
>> > All,
>> >
>> > I'd like to start the process to move forward on a new incubator
>> website.
>> > Based on discussions in the past on list, I wanted to do the following:
>> >
>> > - Roll out a new technology stack + repository
>> > - Leave content in place, while we work later on content enhancements
>> >
>> > For right now, I'm planning to leave the existing /projects and
>> > /ip-clearance in place.  My hope is that we may not need them in the
>> > future.
>> >
>> > The website staging area can be seen here:
>> > https://incubator.apache.org/ngtest/
>> > The git repository for the site can be seen here:
>> > https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
>> > shortlog;h=refs/heads/jbake-site
>> > (with
>> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
>> >
>> > I'd like to get some final feedback on the layout and colors (not the
>> > content).  I want to start tracking content enhancements in JIRA to help
>> > come up with a backlog of areas of improvement for our incubator guides.
>> >
>> >
>> I'm very familiar with the old layout, so this may be coloring my
>> feedback.
>> However I find the new layout to be less usable than previous. In
>> particular the drop downs lack structure. I think it would be better to
>> focus on "solutions" e.g. "bootstrapping a new podling" along with assoc
>> docs, or "graduating a podingling" etc... - basically focus around the
>> lifecycle of podling rather than a big long list of "guides". Additionally
>> it's hard to find things with the new layout, I used to use the browser
>> "search" feature to narrow down to a particular doc. Now I need to click
>> on
>> each of the drop downs to find the content I'm looking for. Additionally
>> things like wiki/faq/etc... - can't find them at all.
>>
>>
> Hi Patrick,
>
> Thanks for the input.  I've started to add it to the new version, let me
> know your thoughts.  There's still a few areas to tweak, but definitely
> keep it coming.
>
> I have to still add a link to google search.
>
> John
>
>
>> Patrick
>>
>>
>> > John
>> >
>>
>