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

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

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(a)redhat.com&gt; 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-s... >> [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/... >> [3] http://aerogear.org/download/ >> [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6... >> [5] http://aerogear.org/download/custom/ >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev