<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 17, 2012, at 4:34 PM, Deepali Khushraj wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true">Here's one suggestion for organizing docs, including the one on OTP.</div></div></blockquote><div><br></div><div>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.</div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true"><br></div><div apple-content-edited="true">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. </div><div apple-content-edited="true"><br></div><div apple-content-edited="true">Attached is a snapshot of what I mean. </div><div apple-content-edited="true"><br></div><div apple-content-edited="true"><span><AG-Docs-Structure.jpg></span></div><div apple-content-edited="true"><br></div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br><div><div>On Dec 17, 2012, at 2:45 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Mon, Dec 17, 2012 at 8:39 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:<br><blockquote type="cite">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<br>client stuff or all server stuff on the home page.<br></blockquote><br>You mean a bundle of all things ? E.g. for client you get ALL of iOS,<br>all of Android, all of JS - in one bundle?<br>If so, feels weird<br><br><blockquote type="cite">The download page could have each individual thing listed I guess since that is all that's on that page.<br></blockquote><br>Being more concrete:<br><a href="http://aerogear.org/download/">http://aerogear.org/download/</a><br><br>A few options I can think of (I am not a designer, nor an ergonomics expert):<br>* add the OTP to the "AeroGear Security"<br>* add OTP to the platforms (e.g. OTP.js to JS, otp-ios to iOS etc)<br><br>-M<br><br><blockquote type="cite"><br>On Dec 17, 2012, at 1:34 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br><br><blockquote type="cite">Hi,<br><br>with the new OTP bits, we need to add them to the downloads.<br><br>Here are two thoguhts:<br><br>* Downloads: (Simple category, hopefully)<br><br><a href="http://aerogear.org/download/">http://aerogear.org/download/</a> contains a "AeroGear Security" section -<br>I am fine in adding OTP (iOS, Android/Java, JS) to there.<br><br>* Homepage: (not sure if that's simple)<br><br><a href="http://aerogear.org/">http://aerogear.org</a> I don't mind adding a new section "AeroGear<br>Security" (or "Mobile Security" ) on the homepage - but... perhaps<br>that's a bit too much?<br>Not sure.<br><br><br>Let me know where we should put the OTP download links<br><br><br>Greetings,<br>Matthias<br><br>--<br>Matthias Wessendorf<br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote><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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote><br><br><br>-- <br>Matthias Wessendorf<br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></blockquote></div><br></div>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote></div><br></body></html>