<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 3, 2014 at 2:45 PM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Hylke<br>
<br>
I guess we had a different approach here:<br>
- You want to revisit our librairies split to fit in the web site restructure.<br>
- I want to fit the actual libraries split into your new web site, making adjustment to web site design.<br>
<br>
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:<br>
<br>
*********<br>
Core - Server: nope, just an example<br>
---<br>
Core - Client iOS: <a href="https://github.com/aerogear/aerogear-ios" target="_blank">https://github.com/aerogear/aerogear-ios</a><br>
Core - Client JS: <a href="https://github.com/aerogear/aerogear-js" target="_blank">https://github.com/aerogear/aerogear-js</a><br>
Core - Client Android: <a href="https://github.com/aerogear/aerogear-android" target="_blank">https://github.com/aerogear/aerogear-android</a><br>
Core - Client Cordova: n/a<br>
*********<br>
Push - UnifiedPush Server: <a href="https://github.com/aerogear/aerogear-unifiedpush-server" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server</a><br>
Push - UnifiedPush Server Java Sender API: <a href="https://github.com/aerogear/aerogear-unifiedpush-java-client" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-java-client</a><br>
Push - UnifiedPush Server Node Sender API (JS): <a href="https://github.com/aerogear/aerogear-unifiedpush-nodejs-client" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-nodejs-client</a><br>
Push - SimplePush Server: <a href="https://github.com/aerogear/aerogear-simplepush-server" target="_blank">https://github.com/aerogear/aerogear-simplepush-server</a><br>
Push - SimplePush Server Java Sender API: <a href="https://github.com/aerogear/aerogear-simplepush-java-client" target="_blank">https://github.com/aerogear/aerogear-simplepush-java-client</a><br>
Push - SimplePush Server Node Sender API (JS): <a href="https://github.com/aerogear/aerogear-simplepush-node-client" target="_blank">https://github.com/aerogear/aerogear-simplepush-node-client</a><br>
---<br>
Push - Client iOS: UnifiedPush.Registration: <a href="https://github.com/aerogear/aerogear-push-ios-registration" target="_blank">https://github.com/aerogear/aerogear-push-ios-registration</a><br>
Push - Client JS: UnifiedPush.Registration: n/a<br></blockquote><div>Actually, we have this in the JS core repo. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Push - Client Android: UnifiedPush.Registration:<br>
Push - Client Cordova: UnifiedPush.Registration: <a href="https://github.com/aerogear/aerogear-pushplugin-cordova" target="_blank">https://github.com/aerogear/aerogear-pushplugin-cordova</a><br>
---<br>
Push - Client iOS: SimpledPush: n/a<br>
Push - Client JS: SimplePush: JS core repo<br>
Push - Client Android: SimplePush: n/a<br>
Push - Client Cordova: SimplePush: n/a - nothing yet<br>
*********<br>
Security - Server Shiro Adapter: <a href="https://github.com/aerogear/aerogear-security-shiro" target="_blank">https://github.com/aerogear/aerogear-security-shiro</a><br>
Security - Server PicketLink Adapter: <a href="https://github.com/aerogear/aerogear-security-picketlink" target="_blank">https://github.com/aerogear/aerogear-security-picketlink</a><br>
Security - Server Hawk Adapter: <a href="https://github.com/aerogear/aerogear-security-hawk" target="_blank">https://github.com/aerogear/aerogear-security-hawk</a><br>
Security - Server Crypto: <a href="https://github.com/aerogear/aerogear-crypto-java" target="_blank">https://github.com/aerogear/aerogear-crypto-java</a><br>
---<br>
Security - Client iOS Security.OTP: <a href="https://github.com/aerogear/aerogear-otp-ios" target="_blank">https://github.com/aerogear/aerogear-otp-ios</a><br>
Security - Client JS Security.OTP: <a href="https://github.com/aerogear/aerogear-otp-java" target="_blank">https://github.com/aerogear/aerogear-otp-java</a><br>
Security - Client Android Security.OTP: <a href="https://github.com/aerogear/aerogear-otp-js" target="_blank">https://github.com/aerogear/aerogear-otp-js</a><br>
Security - Client Cordova Security.OTP: <a href="https://github.com/aerogear/aerogear-otp-cordova" target="_blank">https://github.com/aerogear/aerogear-otp-cordova</a><br>
---<br>
Security - Client iOS Security.Crypto: <a href="https://github.com/aerogear/aerogear-crypto-ios" target="_blank">https://github.com/aerogear/aerogear-crypto-ios</a><br>
Security - Client JS Security.Crypto: <a href="https://github.com/aerogear/aerogear-crypto-java" target="_blank">https://github.com/aerogear/aerogear-crypto-java</a><br>
Security - Client Android Security.Crypto: JS core repo<br>
Security - Client Cordova Security.Crypto: <a href="https://github.com/aerogear/aerogear-crypto-cordova" target="_blank">https://github.com/aerogear/aerogear-crypto-cordova</a><br>
*********<br>
Note: that JavaScript libraries although not splitted into different repos still offer fine grained libraries with the Custom build feature.<br>
I didn’t know where to put: <a href="https://github.com/aerogear/aerogear-geo-cordova" target="_blank">https://github.com/aerogear/aerogear-geo-cordova</a>.<br>
<br>
@all, feel free to correct if I missed some repo.<br>
<br>
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.<br>
<br>
++<br>
<span class="HOEnZb"><font color="#888888">Corinne<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 03 Mar 2014, at 13:03, Hylke Bons <<a href="mailto:hbons@redhat.com">hbons@redhat.com</a>> wrote:<br>
<br>
> Hello,<br>
><br>
> Can we hold a larger high level discussion about the project's package<br>
> organisation and splits? I really think this is needed before we can<br>
> actually come up with a good design for this.<br>
><br>
> Otherwise I'm afraid we'll end up with inconsistent and confusing pages,<br>
> not a whole lot better than our current download pages.<br>
><br>
> I've already written down some of my thoughts on this:<br>
> <a href="http://oksoclap.com/p/AeroGearModuleUntangling" target="_blank">http://oksoclap.com/p/AeroGearModuleUntangling</a><br>
><br>
> What I can do right now is mock up the flow from the download page to<br>
> the different platform client setup pages.<br>
><br>
> Hylke<br>
><br>
><br>
> On 03/03/2014 11:17, Corinne Krych wrote:<br>
>> Hello All,<br>
>><br>
>> 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].<br>
>><br>
>> 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].<br>
>><br>
>> 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.<br>
>><br>
>> 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].<br>
>><br>
>> @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?<br>
>><br>
>> wdyt?<br>
>><br>
>> ++<br>
>> Corinne<br>
>> [1] <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365</a><br>
>> [2] <a href="https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png" target="_blank">https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png</a><br>
>> [3] <a href="http://aerogear.org/download/" target="_blank">http://aerogear.org/download/</a><br>
>> [4] <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html</a><br>
>> [5] <a href="http://aerogear.org/download/custom/" target="_blank">http://aerogear.org/download/custom/</a><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div></div>