On Dec 17, 2012, at 4:34 PM, Deepali Khushraj wrote:
Here's one suggestion for organizing docs, including the one on OTP.
Since we're talking about OTP download, and not general docs, this should have it's own thread. I don't want to go too far off topic - but I do agree our doc page could get styled more like the others.
It would be good if the developer could easily find relevant docs based on the mobile app type or backend technology being used. All domain specific docs could go in a common area.
Attached is a snapshot of what I mean.
<AG-Docs-Structure.jpg>
On Mon, Dec 17, 2012 at 8:39 PM, Kris Borchers <kris@redhat.com> wrote:
I would say no new section on either page. The security section on both pages could be divided internally to server and client sections. Even then, I would only want to see a single download of all
client stuff or all server stuff on the home page.
You mean a bundle of all things ? E.g. for client you get ALL of iOS,
all of Android, all of JS - in one bundle?
If so, feels weird
The download page could have each individual thing listed I guess since that is all that's on that page.
Being more concrete:
http://aerogear.org/download/
A few options I can think of (I am not a designer, nor an ergonomics expert):
* add the OTP to the "AeroGear Security"
* add OTP to the platforms (e.g. OTP.js to JS, otp-ios to iOS etc)
-M
On Dec 17, 2012, at 1:34 PM, Matthias Wessendorf <matzew@apache.org> wrote:
Hi,
with the new OTP bits, we need to add them to the downloads.
Here are two thoguhts:
* Downloads: (Simple category, hopefully)
http://aerogear.org/download/ contains a "AeroGear Security" section -
I am fine in adding OTP (iOS, Android/Java, JS) to there.
* Homepage: (not sure if that's simple)
http://aerogear.org I don't mind adding a new section "AeroGear
Security" (or "Mobile Security" ) on the homepage - but... perhaps
that's a bit too much?
Not sure.
Let me know where we should put the OTP download links
Greetings,
Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev