<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hey Corinne,<br>
      <br>
      I've updated the mockup with a "platform specific example" page
      (on the far right):<br>
<a class="moz-txt-link-freetext" href="https://github.com/hbons/aerogear-design/blob/master/website-restructure/aerogear-project.png">https://github.com/hbons/aerogear-design/blob/master/website-restructure/aerogear-project.png</a><br>
      <br>
      Played with a lot of ideas for the transition, but your original
      idea in as implemented in the proof of concept seems to work best,
      so I just tweaked the style and wording of the links a little bit.
      These should go at the end of a section that talks a bout a high
      level concept, so people will read the secion first before getting
      into the language details.<br>
      <br>
      Let me know if that works.<br>
      <br>
      Hylke<br>
      <br>
      On 11/02/2014 12:55, Corinne Krych wrote:<br>
    </div>
    <blockquote
cite="mid:CAL8vO=dJb=yp9ZXO=cdYZWuA1jGak+o9FP=r+UKg=S6Rws4uMw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <p class="">Hello Hylke,</p>
        <p class="">We already discussed it in this thread [1], but I
          rather have the question in its own dedicated thread.</p>
        <p class="">Atm, the mockup defines 3 pages/layers: HOME, GET
          IT, and EXMAPLE page. I think we&#8217;re missing a PLATFORM EXAMPLE
          page. This page wil explain in more details with the user
          prefered platform how to deal with AG Core Pipe etc&#8230; Idally
          this page will have a github cookbook repo assiciated to it.
          We have cookbook for the 3 plaforms: android, iOS, JS so far
          and we also have demo repo. A crossrefence table like this one
          [2] could also be useful.</p>
        <p class="">An example page with high level concept and
          definition illustrated with code snippet is good. But not
          enough. Besides, atm we have an extensive documentation that
          goes in much more details and i really think we should keep
          this level of details.</p>
        <p class="">My question is: How do me transition from EXAMPLE to
          PALTFORM EXAMPLE? Does it make sense to you? wdyt?<br>
        </p>
        <p class="">Last time I did a hackengarten on AeroGear, people
          told me: Woah, you&#8217;ve got such a great documentation,
          explaining step by step. And I told them wait until we&#8217;ve got
          our killer revamp ;)</p>
        <p class="">++</p>
        <p class="">Corinne</p>
        <p class=""><span class="">[1] <a moz-do-not-send="true"
href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Fwd-Website-restructure-td5837.html"><span
                class="">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Fwd-Website-restructure-td5837.html</span></a></span></p>
        <p class=""><span class="">[2] <a moz-do-not-send="true"
href="https://github.com/aerogear/aerogear-ios-cookbook/blob/master/README.md"><span
                class="">https://github.com/aerogear/aerogear-ios-cookbook/blob/master/README.md</span></a></span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
    </blockquote>
    <br>
  </body>
</html>