<div class="gmail_quote">On Wed, Dec 9, 2009 at 10:59 AM, Kito Mann <span dir="ltr"><<a href="mailto:kito.mann@virtua.com">kito.mann@virtua.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Two things:<br>
<br>
(1) Where should we place a link to o the AJAX JSF Matrix?<br>
(<a href="http://www.ajaxjsf.com/" target="_blank">http://www.ajaxjsf.com/</a>)? I'm going to continue talking to Thomas<br>
about integrating it with JSFCentral, but in the meantime, it'd be<br>
nice to have a link to it.<br></blockquote><div><br>I added a short blurb to the home page about the JSF ecosystem and included a link to this site. I was careful to say that it is not an official representation, but is nonetheless useful.<br>
<br>Btw, we don't have to have everything on the front page, I'm just adding information and we can reorg as needed. We can include some nested navigation to break it up. For instance, the related specifications section should likely be a subpage of Specification called "Related Specifications". Just haven't gotten to it yet (I've kind of flooded right now). (Anyone want to take it?)<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
(2) For the Getting Started section, I see two problems: (a) it only<br>
talks about JSF 2, and (b) it doesn't give you any info if you're not<br>
using Maven.</blockquote><div><br>Well, it does have a link to the download page for each project. If you aren't using Maven, you really can't get around just downloading the dist (we aren't getting into Ivy).<br>
<br>As for the JSF 2, yes, I think we should just promote JSF 2. They can find JSF 1.2 if they go to the implementation sites. Not saying we can't mention the version structure, but we don't want to provide Maven archetype info for anything but JSF 2.<br>
<br>Since this site is forward looking, we can't really promote starting 1.2 projects. That's really a step backwards. We just need to encourage the component libraries to get JSF 2 support out there so that we can just forget about JSF 1.2 (from an advocacy perspective).<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>