[aerogear-dev] Feature based landing page (and new UI)

[Matthias Wessendorf]

Andres,

to give some insights. The modules would list all of our modules, while
each of them contains more info on it, like:

https://aerogear.org/push/
https://aerogear.org/sync/

(yes, both are a bit different - but with the new UI, I am hoping to get
them unified)

On Wed, Jan 21, 2015 at 2:57 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> yeah! that would be awesome!
>
>
> On Wednesday, January 21, 2015, Andres Galante <agalante at redhat.com>
> wrote:
>
>> Should I add single "modules" pages for each module?
>>
>> ----- Original Message -----
>> From: "Matthias Wessendorf" <matzew at apache.org>
>> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
>> Sent: Tuesday, January 20, 2015 7:22:09 PM
>> Subject: Re: [aerogear-dev] Feature based landing page (and new UI)
>>
>>
>>
>> On Tue, Jan 20, 2015 at 9:58 PM, Corinne Krych < corinnekrych at gmail.com
>> > wrote:
>>
>>
>>
>> > On 20 Jan 2015, at 17:01, Matthias Wessendorf < matzew at apache.org >
>> wrote:
>> >
>> > Hi,
>> >
>> > for all of our different push offerings, we have a central landing page
>> ([1]), and soon that page will also list our work on the WebPush spec ([2])
>> > Since this model is quite handy, having a centralized landing page, I'd
>> propose we do that for other features, like OAuth2 and Sync as well.
>> >
>> >
>> > With the new design, the "feature" is more a module, which is fine. The
>> Screenshot of the modules page ([3]), we list all of our feature, or more
>> modules ;-)
>> > While for PUSH we have more than just one repo (UPS, SimplePush and now
>> WebPush + demos), I think the getting started should go to a 'feature' (or
>> module) landing page. For AeroGearPush that would be [1], or something
>> similar. Basically, on this "module landing page", I'd like to list all
>> relevant GH repos, link to JIRA and perhaps other resources.
>> >
>> > Any thoughts?
>> >
>> >
>> > Now, taking a different example, sync, we would list these repos:
>> >
>> > iOS:
>> > https://github.com/aerogear/aerogear-ios-sync
>> > https://github.com/aerogear/aerogear-ios-sync-client
>> > https://github.com/aerogear/aerogear-ios-sync-demo
>> >
>> > Android:
>> > https://github.com/aerogear/aerogear-android-sync
>> >
>> > JS:
>> > https://github.com/aerogear/aerogear-js (part of the lib)
>> > https://github.com/aerogear/aerogear-js-cookbook (a sync demo, based
>> on node)
>> >
>> > Sync-Server:
>> > https://github.com/aerogear/aerogear-sync-server
>> >
>> >
>> > + linking to the JIRAs tracked for the different Sync milestones
>> (currently the ones with the 'sync-1.0.0.alpha.1' label)
>> >
>>
>> Do you mean adding a fifth button “List of JIRA tickets" after “github
>> repo” or this JIRA button is only accessible via Doc->roadmap menu?
>>
>> I think it is a good thing to have another link, to all the upcoming
>> JIRAs from a 'feature' or 'modules' page. Users of the current bits may be
>> also interested, to some degree, into what's coming next.
>>
>> While a 'link' from Docs/Roadmaps is good as well.
>>
>> -M
>>
>>
>>
>>
>>
>> >
>> > When we have clear "module" entry or landing pages, it's easy for new
>> users, to get an understanding what it is all about. Instead of jump around
>> on the site (which is why we generally do the new site :-))
>> >
>> >
>> > Does that make sense ?
>> >
>> >
>> > -Matthias
>> >
>> > [1] https://aerogear.org/push/
>> > [2] https://github.com/aerogear/aerogear.org/pull/468
>> > [3]
>> https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Sent from Gmail Mobile
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150121/c36e55fb/attachment-0001.html