Delete navigator?

Jump to: navigation, search

It seems to me that we should delete the navigator at the top of this page. Although Help:Workgroup charter is an output of the WE Workgroup, it seems like it should stand on its own. I'm just wondering how users who come upon this page and know nothing or little about the WE Workgroups workgroup will interpret the navigator.

But it does make sense for the navigator at WE Workgroups to include this page but then this page doesn't have the navigator, so it doesn't seem like it's connected. I don't have any experience in this kind of thing.

Thoughts? Other suggestions?

ASnieckus (talk)18:36, 30 July 2009

Hi Alison,

Having the boilerplate the Help:Namespace as a community resource is the right place in the wiki -- In its new location, I agree that the navigation template doesn't make sense anymore more on this page. I vote for deleting the navigation template on the top of the page.

We can also create an input box which will preload the boilerplate headings (with shortened version of the instructions -- and tips). We could lauch the input box from both the Boilerplate page in the help section and the policy page for workgroups. This will help folk get started and promote consistency across Workgroup charters.

Haven't checked yet -- did you Move the page (which keeps other pages which were linking to the Charter Boiler plate in tact with the move.) -- if not, well need to check the other workgroups who may have linked to this page and rectify the links.)

Under the references section I propose that for historical reasons -- we provide a link to the charter for developing the resource.

Looking good so far!

Mackiwg (talk)22:56, 31 July 2009

"We can also create an input box which will preload..."

The input box idea to preload the charter boilerplate is a good idea. I saw the discussion on this in the proposed boilerplate style guide. Maybe the creation of the inputbox will be a job for WE Workgroups once we've completed everything currently on our plate.

"...did you Move the page..."

I did *Move* the page and revised the more important links, e.g., in the Workgroup guidelines, to go directly to the help page. As you know I don't have much experience working in wikis (only the 1000 edits I've done here on WE; seems like a lot, but I still have a pretty narrow wiki-editing skillset and incomplete wiki concept map). I had to muster up some courage :P

"...provide a link to the charter for developing the resource."

I had been thinking to create a statement of some sort to note that this boilerplate was created and is maintained by WE Workgroups. I'll put something in.

Yeah, I'm pretty happy with the result. The use of the boilerplate in the two workgroup start-ups provided great feedback.

ASnieckus (talk)00:40, 1 August 2009

Hi Alison,

We've been very fortunate in having at least three workgroups to trial the charter -- a great model for developing process guidelines.

I'm pretty impressed with your wiki skills --- 1000 edits represents a considerable amount of time and effort in WE. Yeah -- we'll look at the input box with preload text once we have the other stuff done. Its not too hard to set up -- perhaps I'll get a little free time over the weekend to take a peek at this :-)

Cheers Wayne

Mackiwg (talk)01:30, 1 August 2009
 
 

This is on a slight tangent...

If the intention of this page is to be used as a boilerplate then all the other information on it should be removed or placed in tags. The intent of a boilerplate is to be used with the {{subst:}} function which works just like template wiki syntax (including the use of inclusion tags inside the boilerplate), but instead takes all of the content and literally places or substitutes it into the page you want it in.

If you want it to be used as an inputbox preload, than nothing but exactly what you want in the content page should be in the boilerplate. Inclusion tags do not work with the inputbox extension, unfortunately, so that is not a solution.

My suggestion is that all of your rationale should be a part of the policy, or at this stage, the policy draft. This includes the resources and examples and such. If that sort of information is already in there, then I think the redundancy is unecessary. So in relation to this conversation, I agree that the nav box shouldn't go in the main page, but you could put it in the header of the talk page. That's what I did with the inputbox preload for the style guideline suggestions.

Jesse Groppi (talk)22:19, 3 August 2009

Jesse,

Thanks for your explanations (here and in the discussion on the proposed boilerplate style guide page). As you probably guessed, I didn't understand the prior discussions at the boilerplate style guide page on how a boilerplate can be used. I appreciate your taking the time to explain in more detail. I like the idea of putting the navigator and also some of the supporting info in the header on the talk page.

ASnieckus (talk)00:22, 6 August 2009

I'm glad I could help. You guys are doing a great job getting this policy set up!

Jesse Groppi (talk)00:54, 6 August 2009

Thanks. We've set some pretty tight deadlines for ourselves, so things are moving along.

ASnieckus (talk)02:07, 6 August 2009