A proposal, and a question: I’m hoping to experiment with adding some “boilerplate” presentations for projects, and then reach out to those projects to engage with volunteers to write actual content for the presentations. The initial goal is a “elevator pitch” slide deck for each, with:
* What is it? * Ok, what does that actually mean? (Example of how one might use it in the real world, possibly with a user reference * Tech stack diagram, or other simple illustration of how the thing works * “Get involved” slide with website, mailing list, etc. etc Now the question: I’ve added Accumulo, Airavata, and ActiveMQ (Not sent a PR yet, since the network situation where I am is … challenging.) and it’s immediately obvious that the “Presentation” menu item is going to get way out of hand, really fast, if I have any success with this. So I need a pointer on how to correctly subdivide that menu into alpha submenus. Does the directory structure have to reflect the submenu structure? That is, do I have to modify the directory structure where the presentations live? Do I have to modify each pom file to reflect that directory structure? Or is there a simpler, or at least more desired, way to handle this restructuring? — Rich Bowen [email protected]
