[aerogear-dev] [ag.org revamp] GET IT page structure

Mon Mar 3 09:18:39 EST 2014

On 03 Mar 2014, at 15:13, Hylke Bons <hbons at redhat.com> wrote:

> Thanks Corinne and Sebastien for the list, that's useful to have.
> 
> "- You want to revisit our librairies split to fit in the web site restructure."
> 
> 
> No, the website mockups are just one example how things can be 
> structured. It makes many assumptions, some of which may not be possible 
> right now. It doesn't neccesarily have to be according the the mockups.
> 
> I _do_ want revisit the libraries split, because there are 
> inconsistencies and no website redesign is going to fix them.

With the list provided i think it’s doable. Where do you think there is a problem? Let’s be more specific.

>  I need 
> your help to find out where the problems lie, and if we can't do it this 
> way, let's find another one, but the current situation is problematic if 
> we want to implement anything coherent.
> 
> Thanks,
> 
> Hylke
> 
> 
> On 03/03/2014 13:54, Corinne Krych wrote:
>> Thanks Sebi for the correction!
>> ++
>> Corinne
>> On 03 Mar 2014, at 14:51, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>> 
>>> 
>>> 
>>> On Mon, Mar 3, 2014 at 2:45 PM, Corinne Krych <corinnekrych at gmail.com> wrote:
>>> Hello Hylke
>>> 
>>> I guess we had a different approach here:
>>> - You want to revisit our librairies split to fit in the web site restructure.
>>> - I want to fit the actual libraries split into your new web site, making adjustment to web site design.
>>> 
>>> Let me detail out libraries a bit more. Here is a list of existing split with matching gh repo (when available) that we can use as a starting point for our GET IT page:
>>> 
>>> *********
>>> Core - Server: nope, just an example
>>> ---
>>> Core - Client iOS: https://github.com/aerogear/aerogear-ios
>>> Core - Client JS: https://github.com/aerogear/aerogear-js
>>> Core - Client Android: https://github.com/aerogear/aerogear-android
>>> Core - Client Cordova: n/a
>>> *********
>>> Push - UnifiedPush Server: https://github.com/aerogear/aerogear-unifiedpush-server
>>> Push - UnifiedPush Server Java Sender API: https://github.com/aerogear/aerogear-unifiedpush-java-client
>>> Push - UnifiedPush Server Node Sender API (JS): https://github.com/aerogear/aerogear-unifiedpush-nodejs-client
>>> Push - SimplePush Server: https://github.com/aerogear/aerogear-simplepush-server
>>> Push - SimplePush Server Java Sender API: https://github.com/aerogear/aerogear-simplepush-java-client
>>> Push - SimplePush Server Node Sender API (JS): https://github.com/aerogear/aerogear-simplepush-node-client
>>> ---
>>> Push - Client iOS: UnifiedPush.Registration: https://github.com/aerogear/aerogear-push-ios-registration
>>> Push - Client JS: UnifiedPush.Registration: n/a
>>> Actually, we have this in the JS core repo.
>>> Push - Client Android: UnifiedPush.Registration:
>>> Push - Client Cordova: UnifiedPush.Registration:  https://github.com/aerogear/aerogear-pushplugin-cordova
>>> ---
>>> Push - Client iOS: SimpledPush: n/a
>>> Push - Client JS: SimplePush: JS core repo
>>> Push - Client Android: SimplePush: n/a
>>> Push - Client Cordova: SimplePush: n/a - nothing yet
>>> *********
>>> Security - Server Shiro Adapter: https://github.com/aerogear/aerogear-security-shiro
>>> Security - Server PicketLink Adapter: https://github.com/aerogear/aerogear-security-picketlink
>>> Security - Server Hawk Adapter: https://github.com/aerogear/aerogear-security-hawk
>>> Security - Server Crypto: https://github.com/aerogear/aerogear-crypto-java
>>> ---
>>> Security - Client iOS Security.OTP: https://github.com/aerogear/aerogear-otp-ios
>>> Security - Client JS Security.OTP: https://github.com/aerogear/aerogear-otp-java
>>> Security - Client Android Security.OTP: https://github.com/aerogear/aerogear-otp-js
>>> Security - Client Cordova Security.OTP: https://github.com/aerogear/aerogear-otp-cordova
>>> ---
>>> Security - Client iOS Security.Crypto: https://github.com/aerogear/aerogear-crypto-ios
>>> Security - Client JS Security.Crypto: https://github.com/aerogear/aerogear-crypto-java
>>> Security - Client Android Security.Crypto: JS core repo
>>> Security - Client Cordova Security.Crypto: https://github.com/aerogear/aerogear-crypto-cordova
>>> *********
>>> Note: that JavaScript libraries although not splitted into different repos still offer fine grained libraries with the Custom build feature.
>>> I didn’t know where to put: https://github.com/aerogear/aerogear-geo-cordova.
>>> 
>>> @all, feel free to correct if I missed some repo.
>>> 
>>> As you can see we have something that we could fit in our GET IT page. I’m convinced though, that a PLATFORM GET IT page (which would provide a PLATFORM view) will be really useful.
>>> 
>>> ++
>>> Corinne
>>> 
>>> On 03 Mar 2014, at 13:03, Hylke Bons <hbons at redhat.com> wrote:
>>> 
>>>> Hello,
>>>> 
>>>> Can we hold a larger high level discussion about the project's package
>>>> organisation and splits? I really think this is needed before we can
>>>> actually come up with a good design for this.
>>>> 
>>>> Otherwise I'm afraid we'll end up with inconsistent and confusing pages,
>>>> not a whole lot better than our current download pages.
>>>> 
>>>> I've already written down some of my thoughts on this:
>>>> http://oksoclap.com/p/AeroGearModuleUntangling
>>>> 
>>>> What I can do right now is mock up the flow from the download page to
>>>> the different platform client setup pages.
>>>> 
>>>> Hylke
>>>> 
>>>> 
>>>> On 03/03/2014 11:17, Corinne Krych wrote:
>>>>> Hello All,
>>>>> 
>>>>> Following Hylke’s thread on web site restructure [1], I’d like to start a new thread to discuss GET IT pages in the mockup section [2]. Those pages will replace the “get started” page on the current web site [3].
>>>>> 
>>>>> As Hylke said it, we don’t necesseraly have a the same split of libraries in the differents platforms. Some thing to carry on working on; for example in iOS, we do have a thread opened for iOS small libs [4].
>>>>> 
>>>>> To make an initial working GET IT page, we could have a list of libraries per features but we also need a link to a PLATFORM GET IT page.
>>>>> 
>>>>> The PLATFORM GET IT page, it’s similar to the PLATFORM EXAMPLES page where we need a view per platform. We should have a iOS GET IT which split between sever/client and displays all libraries with code color for different features. For JavaScript this page will contain the custom builder tool [5].
>>>>> 
>>>>> @hbons How can we make the transition from GET IT to PLATFORM GET IT page? shall we add a link from HOME page to PLATFORM GET IT page?
>>>>> 
>>>>> wdyt?
>>>>> 
>>>>> ++
>>>>> Corinne
>>>>> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365
>>>>> [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png
>>>>> [3] http://aerogear.org/download/
>>>>> [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html
>>>>> [5] http://aerogear.org/download/custom/
>>>>> _______________________________________________
>>>>> 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
>>> 
>>> _______________________________________________
>>> 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
>> 
>> _______________________________________________
>> 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