On Mar 16, 6:57 pm, The Editor <[email protected]> wrote: > On 3/16/10, Markus <[email protected]> wrote: > > > On Mar 16, 1:29 pm, The Editor <[email protected]> wrote: > > > Yes, thoughts. solutions.snippets is almost invisible. It's just > > something there in the docs. One link under many. Not even the page > > itself tells you that you are invited to share your code. But it's > > part of a more general issue. I would really love to do two things: > > How about adding a second level link under docs entitled examples... > Go form there. > > I'd be willing to set it up...
I'd probably use: Information Documentation Code And create code.share. As 'code' is the common denominator of that section. Or, of course, 'blueprints' to strengthen the branding. > > 1) Take a copy of BoltWire.com and restructure it from scratch, make > > it dead simple to navigate and 100 % obvious where things are. Then > > post it to the list and see if it is good or terrible. > > This would be great, but I'd hate for you to spend that kind of time > on it. Why not just keep offering suggestions? I don't even mind > giving you additional edit access to the BoltWire site if you need it. Actually I started writing down suggestions and decided it took way too long to describe everything. Therefore it was more like a time- saving idea. Additional edit access (if needed) and prolonged stamps life would be good. My only concern is that there would temporarily be dead links and broken pages. That's why I initially thought of a copy. Yet, in that case one had to monitor changes on BoltWire.com to put them into the copy afterwards. Not sure what is the preferred way to do it. > Your suggestions are systematically excellent--and there's only a > couple pages I ever even really look at: home, downloads and the > roadmap. Appreciate your kind words. I have more felt like the spamming complainer on here when I noticed my current post frequency... > > 2) Go through every single system page of BoltWire and make the > > language as concise as possible. I could give you countless examples > > where the language is perfectly polite and coherent but too verbose. I > > bet that 90 % of all text, important or not, is only read by 1 % of > > the users. > > I really don't mind your editing of things at all. It was originally > designed as a wiki. We should make it one. I can increase the stamps > half life to a year or something. Make sure we have good working edit > notifications and encourage a team of contributors to post content. > The notifications might be important so those interested could follow > changes and respond if they thing some change was a bad idea... Here, I was talking (primarily) about the barn/system/pages which I would strip their verbosity off. Though some pages on BoltWire.com might need this as well. Maybe the site first, then the system pages. I'll let you decide. Either create a copy of the BoltWire.com field that I can mess up or give me the access rights to rename and edit the three main sections on the site or change your mind. :) Prolonged stamps life and the rotten links plugin would both make lots of sense. Markus -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
