<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
All,<br>
<br>
I added the archetypes info on Stacks page. <br>
<br>
I tried 3 different approaches to show the Archetypes:<br>
<br>
- Archetypes on another page (information became diffuse)<br>
- Tree Table (too confusing, polluted)<br>
- Overlay (actual - I liked that)<br>
<br>
I took a link to
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Archetype/">http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Archetype/</a>
on Archetype info<br>
<br>
Please, consider another review at <a
href="http://site-jdf.rhcloud.com/stack/stacks/">http://site-jdf.rhcloud.com/stack/stacks/</a><br>
<br>
<br>
<pre class="moz-signature" cols="72">Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
</pre>
<br>
Em 25-07-2012 17:21, Rafael Benevides escreveu:
<blockquote cite="mid:50105542.9030705@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Thanks for your tips Pete. It was really awesome<br>
<br>
New release - with your commits rebased :) - to review<br>
<br>
<a moz-do-not-send="true"
href="http://localhost:4242/stack/runtimes/">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</a><a moz-do-not-send="true"
href="http://site-jdf.rhcloud.com/stack/boms/">http://site-jdf.rhcloud.com/stack/boms/</a>
<pre class="moz-signature" cols="72">Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
</pre>
<br>
Em 25-07-2012 07:26, Pete Muir escreveu:
<blockquote
cite="mid:1F805878-F41B-4727-96F2-B50772C53E19@redhat.com"
type="cite">
<pre wrap="">On <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://site-jdf.rhcloud.com/stack/boms/">http://site-jdf.rhcloud.com/stack/boms/</a>
* the code samplle indentation is probably wrong, I think it should just be left aligned.
* You have a trailing full stop in the code sample
* Maybe we should experiment with a table for the layout, rather than the accordion? not sure.
* the "Description:" is probably redundant, the layout of the page makes it obvious that it's a description ;-)
* maybe we should make the Usage h3 or h4, it's a bit distracting right now
* We've lost the info on plugins needing to be copied in from the BOMs readmes
On <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://site-jdf.rhcloud.com/stack/runtimes/">http://site-jdf.rhcloud.com/stack/runtimes/</a>
* I would prefer to present this all in one table, rather than multiple tabs by type
* We should present newest server first, not last (descending order)
* Normally the code name of the server goes in parentheses
* Links to BOMs should open the right accordion/tab
* I wonder if we should call it "Suggested Runtime" "Suggested BOM", "Suggested Archetype"
* Download URL isn't a URL, it's a link. Suggest you change to "Download" and then use one of the glyphicons for in the table
* I would like to be able to expand a row, and see all the available BOMs and archetypes, and also all available versions of said BOMs and archetypes
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://site-jdf.rhcloud.com/stack/plugin-jdf/">http://site-jdf.rhcloud.com/stack/plugin-jdf/</a>
* Something has gone wrong with the markdown, links aren't being correctly created
* I'll send a pull with some suggested changes to the README source
On 25 Jul 2012, at 02:24, Rafael Benevides wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi ALL
After digging the awestruct/ruby/haml world I update the JDF site to read the jboss-stack yaml file
So I created a new section named JBoss Stacks that's what we have been calling it.
This new section contains:
- The JBoss boms (from yaml file - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/jboss-jdf/jdf-stack/blob/Beta2/stacks.yaml">https://github.com/jboss-jdf/jdf-stack/blob/Beta2/stacks.yaml</a>)
- The Runtime matrix (Major Releases, Minor Releases and some Runtime data - also read from yaml file)
- A page about JDF plugin (from README.md)
- PLANED: Archetypes data
This new section is at <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://site-jdf.rhcloud.com/stack/boms/">http://site-jdf.rhcloud.com/stack/boms/</a> - I'll thank for any review and just to know: My designer skill is terrible :p
P.S: Pete Muir heard something about "JBoss Stacks" is an overloaded name. I don't think that we should change it but if someone have any name idea, it will be welcome.
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
_______________________________________________
jdf-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jdf-dev@lists.jboss.org">jdf-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jdf-dev">https://lists.jboss.org/mailman/listinfo/jdf-dev</a>
</pre>
</blockquote>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jdf-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jdf-dev@lists.jboss.org">jdf-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jdf-dev">https://lists.jboss.org/mailman/listinfo/jdf-dev</a>
</pre>
</blockquote>
</body>
</html>