<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Last Friday, while in Boston, we ran a few dozen people through our "Getting Started Tutorial" - a hands-on lab<div><a href="http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/">http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/</a></div><div><br></div><div>I made several notes on "gotchas" that students struggled with and one of them was forge's "list-commands".</div><div><br></div><div>In the tutorial, we instruct the student to use the "entity" command and one student said "hey, this list-commands is broken, entity is not listed".</div><div><br></div><div>and my immediate response was "yes, list-commands rarely tells me what I want" and the students response was "then how do I know what Forge offers me" and my response was "you have to read a document, like this tutorial we provided". </div><div><br></div><div>The light-bulb turns on - we must have a usability problem :-)</div><div><br></div><div>At this time, People mostly wish to use Forge to:</div><div>- new project</div><div>- new entity (with bean validations)</div><div>- rest endpoints</div><div>- jsf scaffolding</div><div>- reverse engineer a database</div><div><br></div><div>So, we need a better list-commands and better docs that "list out the commands". Based on current "docs", Forge only does a few things - <a href="https://docs.jboss.org/author/display/FORGE/Samples">https://docs.jboss.org/author/display/FORGE/Samples</a> :-)</div><div> </div></body></html>