User talk:Ryan Lutz

> I am interested in making this information readily available in a straightforward manner but I don't want to step on any toes. Guess I'm looking for an introduction to the work online here.

Do a search on the wiki using terms related to your topic. This will give you some idea what's already then. Then, either add your material to existing pages (if appropriate) or create new ones. The wiki is generally open to new contributions. See Wiki instructions for some guidelines on how to work with the wiki. I'd be happy to answer any other questions you have either here in the wiki or by email at markjnorton (at) earthlink (dot) net. Mjn 05:03, 28 June 2011 (PDT)

-

On Wikinames, you mention "Sub-pages should be appended to the name with an underscore". My understanding is that sub-pages are formed using a slash. Thus "Steam Engine Build/Valve". It was explained to me that this was the common wiki media convention and should be applied consistently in the OSE wiki. Note also that I have applied this convention to MANY sub-pages. Changing the convention at this point would be burdensome. See Steam Engine/Index for a list of the many pages now associated with the project. Mjn 06:29, 18 July 2011 (PDT)

yeah i'm afraid the cakes already been baked on the / thing marks talking about --Dorkmo 10:03, 18 July 2011 (PDT)

-

> put correct templates on each piece of the GVCS including all sub-pages

I think we might need a bit more thought before we do something like this. The Steam Engine has over 50 wiki pages at this point, and growing weekly. Rather than putting the Product Template on all pages, I've been using a hierarchical navigation scheme. All build pages have a link to the Steam Engine Build Instructions page, which has the template on it. All pages have the Steam Engine category, which provides a quick link to an alphabetical listing of all steam engine pages. I also have a Steam Engine/Index page which organizes the wiki pages by category, which I personally find far more useful than an alphabetic list. Also note that have recommended a substantial change to the master product template - see Mark J Norton/GVCS Template It includes as major topics:  Overview (or Home), Research, Design, Specifications, Bill of Materials, Build Instructions, Development, and User Manual. I would hope that improvements to the GVCS documentation would be a dialog among the major contributors, rather than being done by fiat. Let me know if you'd like to discuss it further. Mjn 04:20, 26 July 2011 (CEST)

Re: all previous posts
I responded on your User:Talk page, Mark. Should I respond on this page? Forgive my lack of wiki etiquette, please.

On the Factor E Farm front, I have been running my template ideas by Marcin and he seems generally supportive of the direction. I am basically trying to put a user-friendly facade on the wiki to try and route users to the info they want quickly. Your GVCS Template is dead on... in fact all of those components are being utilized. See CEB_Press for an example. They may be a bit out of the order you have listed there, but everything is there within those 5 pages.

As for the 50+ pages on the Steam Engine, certainly those can be easily categorized and accessed through a navbar in subsections (i.e. Development)? We don't want to flood the average person with mountains of pages to sift through to find a simple answer, which seems to be the status quo.

If we can come to an agreement as far as where my proposed 5-header navbar infrastructure facade (Home, Development, BOM, Manufacturing, Manual) and the real content (your 50+ Steam Engine pages) come together, I think we will be near a breaking point. Ryan Lutz 11:48, 26 July 2011 (CEST)