<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><blockquote type="cite"><br><font color="#b18cfe">@Hylke see my comments below</font><br><blockquote type="cite"><br>On 24 Jan 2014, at 19:08, Hylke Bons <<a href="mailto:hbons@redhat.com">hbons@redhat.com</a>> wrote:<br><br><blockquote type="cite">Hey,<br><br>On 24/01/2014 14:58, Corinne Krych wrote:<br><blockquote type="cite">Hello All,<br><br>I’ve being working on sass branch [1], the same branch Erik-Jan did its initial work.<br>Here is more feedback on our site redesign<br><br>1. Example page with each language code snippet<br>It’s a good idea, to show the unified aspect of our libs. Having a short snippet code is great, however it’s not possible to fit the detailed example we alreday have in our documentation. Rather than simplifying and not going into details, I think we could have a main page like [2] which give the definition + each snippet. Below the code snipet I’ve added a link:<br>Read more on Pipes on Android / Pipes on iOS / Paging on Web<br>which points to detailled page.<br><br>I think we should keep this documetation. It goes deeper in the sample code as opposed to snippet which is not necessarly complete code. One think that we could do is use code sample extracted from our cookbook recipe. So we can point to the repository for the full app code.<br><br>@Hylke Do you have a better idea than just a simple link? I think it’s not visual enough. And what should be the layout of the detailled example page?<br></blockquote><br>The [2] link is on localhost. :)<br><br>How about we try it out for Pipes and see how it goes? Yes, we probably <br>would need to move some stuff out to other sections, but that's ok. <br>We'll have a better ideas what to do with the "excess" docs once we try <br>any simplify the multiple documents into one.<br><br>Here's the idea for the scopes I had:<br><br>- Examples => High level overview of AeroGear concepts and code snippets <br>about how they're used. Not neccesarily big programmes.<br>- Documentation<br> - Getting started => Download and setup<br> - API Browser => just a link to the full API overview<br>- Guides: We can go more all out here. Tutorials, example projects, more <br>complex configurations, etc. Basically everything else that doesn't fall <br>into the above categories. :)<br><br>I know it's a lot of work... I do think it's the best way to go. I'd be <br>happy to help out on this too, though I've absolutely no clue on the <br>topic, but that may actually be a good thing for explaining stuff to <br>people new to the concepts. :)<br><br></blockquote><br><font color="#b18cfe">Actually if you setup the sass batch link[1], you run your environment and then you go to link[2] loclhost as it’s running on our instance, you will see i’ve tried it out for Pipes. In order to do it i needed to split the documentation for iOS/Android (I haven’t done completely JS part). with this exercice what i understand is:<br>1. the first view should contain code snippet with shows the unified aspect of client lib. those sippet are not complete code, it should be simplified.<br>2. this simplified view is not enough for a developer. Selecting his platform tab, he will be redirected to android for ex complete description on Pipes. Ideally this description is based on a cookbook exemple.<br>3. if the developer want to test it himself he’ll have the option to download the complete sample code (github link to cookbook repo) and just run it<br><br>So the explantion goes through 3 layers from 1)high level description (cross platform), 2) detailled explanation linked to a platform to 3) sample code implementation (obvious linked to a platform).<br><br>My question is How to make the transition from 1) to 2) ? See picture below<br><br></font></blockquote></blockquote><div><br></div><div><br></div><div><a href="https://www.dropbox.com/s/tz25vzu8doh6jkk/agorg2.png">https://www.dropbox.com/s/tz25vzu8doh6jkk/agorg2.png</a></div><div><br></div><br><blockquote type="cite"><br><br><blockquote type="cite"><br><blockquote type="cite"><br><blockquote type="cite"><br><br>5. Dracula theme vs White theme<br>If you uncomment [3] you can have a white theme. A shame that with Dracula theme we loose the AeroGear blue and orange logo...<br>@Hylke for the dracula theme we need AG logo in each of the 3 colors.<br></blockquote>Yes, I'll send you those. Don't worry about the theming too much, as we <br>haven't really discussed that yet. The "Dracula" theme was more of an <br>example of how we can use colours to mark different sections of the <br>project/site. So if you'd like to see things different, let me know! :)<br><br><blockquote type="cite">5. Menu<br>@Hylke you said you want to remove the actual menu, but what do you propose to navigate between topic: Core/Security/Push/Sync<br></blockquote>I've actually added it back in the mockup (see the other email on the <br>thread). It was more of a time thing that I hadn't added it yet. It's <br>back now.<br><br>Hylke<br>_______________________________________________<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></blockquote><br></blockquote><br></body></html>