Template talk:Talk header/Archive 3

Talk-Header on Meta-wiki user talkpage
Is it permitted for the talkheader code to be placed on my wikimedia "meta-wiki" user talkpage which would say this, the links i've changed because of it being on the wikimedia site and not wikipedia, but am i allowed to have it on, if so could you leave a message on my user talk via this Link which will lead to my userpage on meta-wiki.SKYNET X7000 (talk) 15:23, 21 December 2007 (UTC)

[template code removed]


 * The talkheader template, like everything else on Wikipedia, may be copied and used however you like, provided you comply with the terms of the GFDL. Reusing Wikipedia content has details.  •  I had to remove your template code from this page, as there was an unclosed element (I couldn't find which) that was grabbing everything else after it (like my comment, here.  You can retrieve the code from the page history (click edit to get the source; just don't save).  — DragonHawk (talk|hist) 20:29, 21 December 2007 (UTC)


 * Thanks. SKYNET X7000 (talk) 15:31, 22 December 2007 (UTC)

much less anything else
On the draft, Jake the Editor Man changed "This is not a forum for general discussion about the article's subject" to "This is not a forum for general discussion about the article's subject, much less anything else". While I agree with the sentiment, I believe past discussion (here, and at the TfDs) shows a clear consensus for keeping this template as concise as possible, and that addition would make that line long enough to almost always wrap. • I'm also not sure how productive it really would be to put it in, though that's just a comment, not an objection. • If people think I'm off-base in my interpretation of consensus, by all means add it to the draft again, and/or comment here. Thanks! — DragonHawk (talk|hist) 02:36, 3 January 2008 (UTC)

Please indent replies
Having been looking for a template to post on a messy article talk page frequented by loads of what I assume are IP newbies it's good to find this template. However it's missing a comment about indenting replies, such as Please indent replies using a colon -  -- John (Daytona2 ·  Talk ·  Contribs) 20:25, 14 January 2008 (UTC)


 * Hmmmm. I know where you're coming from on that.  I've toying around with the draft right now with some ideas for it.  My only concern is that there has been a lot of previous desire to keep this template concise and brief, i.e., covering only the bare minimum and letting links do the rest.  I'm not sure where indentation falls in that consensus.  I suspect it makes the template too wordy.  Information overload is a concern. — DragonHawk (talk|hist) 20:56, 14 January 2008 (UTC)

Suggesting move of "not a forum" message
If you take a look at the draft page, I moved the "not a forum" line inside the box, where a free line was already available. This way it doesn't heighten the box at all. Please check it out. Note that this line doesn't normally appear anywhere but on article talk pages, so I also added the text explicitly so it would appear on the draft page. Take a look at an article talk page (like Talk:I Am Legend (film) to see how it normally appears right now -- notice the extra line that currently gets created in the topmost section of the template. This change eliminates that extra line.  Equazcion •✗/C • 09:26, 1 Feb 2008 (UTC)


 * FYI: I think (I'm not sure) the reason that line originally got put up in the top section was that the left (white background) section of the template has longer sentences, and thus tends to wrap more and sooner. If you narrow your browser window down to 640x480 pixels, you'll see what I mean.  The white box gets unbalanced with text, leaving the middle and right sections with lots of extra whitespace ("tanspace"?).  I don't think it really matters much.  It might even be the Right Thing for what most people have for screens these days (I dunno).  But I figured I'd mention it, for posterity.  I also wanted to note that it's a good idea to test changes to this template (and similar templates) at a variety of window sizes.  There's lots of different screens out there in the world.  Cell phones and giant flat panels are not uncommon extremes. — DragonHawk (talk|hist) 20:52, 20 April 2008 (UTC)

Alignment
The Talkheader is centrally aligned. Is there an option somehow to left align it?

If not perhaps extend this template to have that option or create another template TalkheaderLeft and TalkheaderRight? ChessCreator (talk) 17:57, 13 March 2008 (UTC)


 * Pretty much all the WP:talk page templates are center-aligned. I don't think I've ever seen one left-aligned.  That said, I think you should be able to customize your user CSS to declare class "standard-talk" to have style "text-align: left" to see what you want for yourself.  See Help:User style for details on that.  — DragonHawk (talk|hist) 20:56, 20 April 2008 (UTC)

Please see my proposed change at VPR
I propose integrating an archive list into the talkheader template, the same way the Village pump header template does. See the discussion at village pump proposals (try to keep discussion centralized). Thanks.  Equazcion •✗/C • 21:14, 23 Mar 2008 (UTC)

editprotected

I don't think this is a particularly controversial edit, so unless there's some objection, please replace the current template code with the code at User:Equazcion/sandbox3. This will just place archive links in the template, if any archives exist under the current page. If no archive pages exist, nothing will change. Thanks. See here for an example of what the integrated archive links will look like.  Equazcion •✗/C • 02:08, 24 Mar 2008 (UTC)

Discussion here
OK, I have no problem with it per se, but it should be made as an opt-in, as per most template changes, so we don't have drastic changes cross-wiki. Also, for pages with extensive archives, it should be able to be turned off. -- Avi (talk) 22:32, 24 March 2008 (UTC)
 * I disagree with the opt-in part. I think it should be automatic. I stupidly didn't test this from article space, hence the display issue. Once it's tested there I think it should be implemented by default, but the opt-out option is a good idea.  Equazcion •✗/C • 22:38, 24 Mar 2008 (UTC)

Okay, I fixed the problem, and added the opt-out functionality. I created Talk:Test article as a temporary demonstration. The  parameter will hide the archive list. Let me know what you think.  Equazcion •✗/C • 23:09, 24 Mar 2008 (UTC)
 * I'm heading out now. I'm sorry for the trouble I caused via my stupidity -- I don't know what possessed me to assume this would work based only on a test in userspace. My apologies especially to Fuhghettaboutit, for making him implement my erroneous code. I rushed to get this implemented because I didn't think there would be much interest in discussing it, but if there is then great. Please let me know your thoughts/suggestions/etc. I still do think this should be implemented across-the-board rather than having to comb through miles of article talk pages to add a parameter. But of course that's up for discussion. Thanks again.  Equazcion •✗/C • 23:24, 24 Mar 2008 (UTC)
 * Nothing to be sorry about. You had good intentions; I had good intentions; we were both a bit rash; the ultimate result was no harm done I don't think, and it got more eyes on the issue.--Fuhghettaboutit (talk) 03:09, 25 March 2008 (UTC)

I've created a temporary template in the template namespace: talkheader4 (talkheaders 2 and 3 are redirects). I've begun placing this on a few talk pages that have lots of archive pages, to make for an adequate test. I figure this will be a good trial run, and eventually when the decision is made whether or not to implement the changes, we'll just redirect talkheader4 to the original talkheader. Take a look at some of the pages in this list to see what the changes look like live. I welcome any input.  Equazcion •✗/C • 03:05, 25 Mar 2008 (UTC)

Regarding opt-in vs. opt-out, unless there is good reason, I believe we try to make as minimal visible changes as possible when changing templates. This template must be on hundreds of thousands of pages, to change them all in one fell swoop is not appropriate, in my opinion. -- Avi (talk) 03:07, 25 March 2008 (UTC)
 * I think we can test this adequately enough prior to implementing it, enough that we can be certain it won't cause trouble across-the-board -- especially now that I'm doing the live testing via talkheader4. But I'm of course open to implementing this via an opt-in parameter, if that's what everyone else wants to do. And thanks for your remarks, Fuhghettaboutit :)  Equazcion •✗/C • 03:14, 25 Mar 2008 (UTC)
 * 77,394 at the last count. I like the archive display in general; what will happen, however, when Talk:Adolf Hitler gets a couple more archives? Will it wrap?  Or overflow? Happy‑melon 13:55, 25 March 2008 (UTC)
 * It should wrap. You can narrow your browser window to see what that'll look like.  Equazcion •✗/C • 14:11, 25 Mar 2008 (UTC)
 * This improvement is the sort of thing that can take a lot of effort to get right (which is why extensive testing is a good idea, of course), but which will have large savings in editor time, eventually. (Not having to add a new archive to an archive box, in itself, is a major savings.) I for one want to express my appreciation for the proposed change; simplification (in terms of what editors need to know and do, even at the cost of more complexity within a template) is almost always (in my opinion) a good thing. -- John Broughton (♫♫) 01:37, 27 March 2008 (UTC)

(<-)I saw you tested it on Talk:Circumcision as well, looks pretty good. -- Avi (talk) 15:07, 27 March 2008 (UTC)
 * (ec) Thanks. I've got talkheader4 on about 10 pages, you can see them via whatlinkshere.  Equazcion •✗/C • 11:14, 27 March 2008 (UTC-4)

Another reason opt-out is important is that there are certain pages where archives are aggregated by topic, and not chronology, so it would be confusing to have to alternate indexing schema on the same page. -- Avi (talk) 15:11, 27 March 2008 (UTC)
 * Well the entire archive portion of the template only shows up if the archives use the standard "Archive #" naming convention. If they use any other names, no links show up at all, so whatever linking templates already in use on the page would continue to function as the sole archive link index.  Equazcion •✗/C • 11:14, 27 March 2008 (UTC-4)

I understand that; however, sometimes the canonically-named archives are wikilinked to the archive boxes in a fashion other than by number, so the opt-out remains a necessary feature, I believe. Thanks. -- Avi (talk) 15:54, 27 March 2008 (UTC)
 * Certainly the feature should have an opt-out. I would like to see a demonstration on a page which has unusual archive naming, to show that it doesn't produce wierd displays.  Is there such an example? <b style="color:forestgreen;">Happy</b>‑<b style="color:darkorange;">melon</b> 15:59, 27 March 2008 (UTC)
 * Unusual archive names will produce no links. I don't have an example of that right now, but I can tell you what would happen is simply that the entire archive line would not be displayed. If I understand Avi's comment, he's concerned about duplicate links to the same numerically-named archives via differing link text, and that is a valid concern. In the interest of avoiding confusion, the opt-out is necessary (and is currently implemented via noarchive=yes). Melon, if you come across a page that has oddly-named archives, feel free to post talkheader4 there to see what'll happen. I don't know of any offhand to test this on. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 05:56, 28 Mar 2008 (UTC)
 * Yes, Equazcion, that was my concern and the "noarchive=yes" handles that admirably. -- Avi (talk) 15:55, 28 March 2008 (UTC)
 * If we want to test this further, perhaps a bot could be requested to replace talkheader with talkheader4 on some articles (20? 50? 100?). The talk/discussion pages of the most viewed articles might be a good place to select articles from, since most of those probably have robust archives. -- John Broughton  (♫♫) 17:06, 29 March 2008 (UTC)

← Thanks John -- I started using that list to post talkheader4 some more. HappyMelon might like to know that Talk:John McCain has non-standard archive names, and posting there shows that the archive line doesn't show up (which is good). <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗ /C • 17:47, 29 Mar 2008 (UTC)
 * I did some creative searching to find the talk pages with the most archives, and it's revealed a bug. It seems the archive list stops at 36. See Talk:George W. Bush and Wikipedia talk:WikiProject Opera. The archive list in this template is actually a separate template that already existed, archive list. Posting the archive list template alone makes the list go up to 39 and then stop (even though more archives still exist). I'm still trying to figure this one out. If anyone has any ideas let me know. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 02:10, 30 Mar 2008 (UTC)
 * This seems to be a problem with the archive list template. talk:Anarchism shows the 36 limit in a separate archive box as well. I've posted a question at the template talk page. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 02:28, 30 Mar 2008 (UTC)
 * archive list is fixed now thanks to User:Tra. Everything seems to work now. See Talk:George W. Bush for a pretty long archive list. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 17:42, 30 Mar 2008 (UTC)

Reality check
Past experience suggests that using  to generate a list of subpages might not be a very good idea. — CharlotteWebb 19:32, 2 April 2008 (UTC)
 * That's archive list you're talking about, and it's been rewritten to fix those problems, apparently. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 20:39, 2 Apr 2008 (UTC)
 * It doesn't "fix" the problems, just reducing the cost of using "archive list" (expressed as number of  calls) by a factor of roughly 25 for frequently archived pages. Adding this to talkheader would increase the overall number of uses by a much greater factor. So while fewer ifexist would be made per page-load, more would be made overall. Shrug. Seriously though, how many article talk pages have ever been archived? One percent? Maybe less. Checking for archives should be disabled by default. Or just use prefixindex by default, and allow talk pages to be manually switched to the more sophisticated method in the uncommon situation where more than 3 or 4 archives exist. — CharlotteWebb 21:30, 2 April 2008 (UTC)
 * archive list isn't called in every talkheader. There's a single ifexist to determine if an Archive 1 exists, and if it does, thenarchive list is called. This would only add a single new ifexist to all talk headers. To talk pages with archives, it would add the slough of archive list ifexist's, but presumably they would've already had it due to another archive listing template -- which will presumably be removed once this change is implemented, since this is meant to replace them all. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 22:34, 2 Apr 2008 (UTC)
 * I see what you mean, but this is still feature creep for talk pages which due to scarcity of comments have never been, and probably never will be, archived (the vast majority), but I give up. — CharlotteWebb 14:37, 3 April 2008 (UTC)
 * Feature creep? Never heard that one. If features are beneficial, who cares if there are a lot of them? Anyway: This automatically provides an archive box for pages that would've had one added manually anyway. All other pages without the box would continue not having one, with basically no additional page processing necessary. I don't see the downside, and I have doubts that you do at this point either. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 15:44, 3 Apr 2008 (UTC)
 * I agree, and I think this has been in discussion long enough for any serious flaws or opposition to surface. Shall I replace  with the contents of ?? <b style="color:forestgreen;">Happy</b>‑<b style="color:darkorange;">melon</b> 14:59, 5 April 2008 (UTC)
 * I've tested this in every conceivable talk space, and haven't seen any problems. No comments at VPR in the last 3 days. I think it's time. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 20:32, 8 Apr 2008 (UTC)
 * ✅ there goes the job queue! <b style="color:forestgreen;">Happy</b>‑<b style="color:darkorange;">melon</b> 21:21, 8 April 2008 (UTC)

Documentation
Equazcion, Perhaps you can add a note to the template documentation regarding the recent change. For example in what scenarios will archives be listed, where and how can they be turned off?. I'm currently interested why Talk:Scotland (for example) doesn't have them listed, while Talk:Adolf Hitler does and i've no desire to wade through that spaghetti of template code! Thanks/wangi (talk) 21:44, 8 April 2008 (UTC)
 * A change to such a widely-used template isn't instantaneous; The change was just made and needs time to propagate through about 80,000 pages. It'll probably be a while before all pages show the change. Talk:Scotland shows the archive list for me currently though. I'll make the necessary additions to the documentation now. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 21:53, 8 Apr 2008 (UTC)
 * Done. Let me know if there's anything I left out. <small style="font:bold 10px Arial;display:inline;border:#009 1px dashed;padding:1px 6px 2px 7px;white-space:nowrap"> Equazcion •✗/C • 22:02, 8 Apr 2008 (UTC)
 * Thanks for that, look complete/wangi (talk) 22:09, 8 April 2008 (UTC)

Namespace/sub-page issues
The namespace #switch produces non-intuitive results when used on a sub-page in "user talk" space, e.g. "This is MaryJo/Sandbox's talk page, where you can send messages and comments to MaryJo/Sandbox". Might want to split these apart with &#123;&#123;SUBPAGENAME&#125;&#125;, &#123;&#123;BASEPAGENAME&#125;&#125; and use them to write something that actually makes sense. — CharlotteWebb 19:32, 2 April 2008 (UTC)

Suggest adding "consensus" to template
This template has earned the respect of many editors for its calming, policy-based approach to editing and discussing articles. It has saved the day many times. One thing missing, though, is the injunction to editors to work at getting consensus for changes. WP:CON is one of the key behavioral policies. I would suggest adding the following to the template: "Editorial decisions are made by consensus." I could see adding this just below the first line that reads "This is the talk page for discussing improvements to the XYZ article." It could be preceded by the word "Note." What do you think? Sunray (talk) 14:23, 14 May 2008 (UTC)
 * Well, that didn't get much response yet. WP:CON puts it thus: "Consensus is Wikipedia's fundamental model for editorial decision-making." How could we best encourage editors to work towards consensus? What role could this template play in this? Sunray (talk) 23:29, 16 May 2008 (UTC)
 * This has large scope for creating confusion. It's easy for editors to get mislead with a single sentence about consensus. Many editors would take the suggested sentence 'Editorial decisions are made by consensus' with it's literal English meaning, and assume that consensus should be gathered before the first edit, instead of reading WP:CON which actually says make the first edit and only get consensus in the case of disagreement. So for this reason I suggest instead using WP:BRD as that would seem less likely to confuse. SunCreator (talk) 22:04, 19 May 2008 (UTC)
 * Yes, good point. One problem is that BRD is not policy. Perhaps we could use something close to your wording about getting consensus in the case of disagreement. Perhaps this wording:
 * Note: If there are disagreements, editorial decisions will be made by consensus. Sunray (talk) 05:50, 20 May 2008 (UTC)
 * To stress the negative 'disagreements' would in my opinion set the wrong tone on this template. WP:BRD is not a policy, but that's okay, neither is WP:AGF, WP:SIG and WP:NEWBIES which are referred to by this template already. SunCreator (talk) 09:02, 20 May 2008 (UTC)
 * I should have said "BRD is neither a policy nor a guideline." I meant it is not part of the WP policy base. But I agree that it would be best to not state the negative. However, getting consensus on talk pages is very important. Would you be able to propose an alternative that refers people to WP:CON? Sunray (talk) 22:53, 20 May 2008 (UTC)
 * Unfortunately it's not easy to use WP:CON in a nice way. Perhaps just state the nutshell text. "Consensus is Wikipedia's fundamental model for editorial decision-making." SunCreator (talk) 11:44, 21 May 2008 (UTC)
 * I like that. I'm mindful that it is just two of us talking here. How would we get such a change made? Sunray (talk) 15:44, 31 May 2008 (UTC)

Proposal to add "consensus" to talkheader
The recommended addition is:
 * "Consensus is Wikipedia's fundamental model for editorial decision-making."

This statement could be added in the top section of the box, just below: "This is the talk page for discussing improvements to the Template:Talkheader page."
 * - OR -

In the section with the white background, just above the statement: "Please sign and date your posts by typing four tildes ( ~ )."

Rationale
Many times new editors (and even some that have been around for awhile) are unaware of WP:CON and how it works. It would be helpful in curbing edit wars to be able to refer combatants to the consensus policy in a nutshell (the quote) as a groundrule for talk page discussion. In my experience, this is not a perfect solution since a bunch of editors can gang up to prevent reasonable changes. However, such situations are rarely problematic, and there are other remedies, such as RfC and the dispute resolution process if it does happen.

Because of the importance of consensus for peaceful and productive talk pages, I recommend this addition. Sunray (talk) 20:40, 8 June 2008 (UTC)


 * ❌ Consensus deals with the article itself. Talkheader is for advice on how to edit talk pages, and not for advice about how to deal with articles. Although consensus should be reached on the talk page, Talkheader isn't the right place for a message like this. Thanks, PeterSymonds (talk)  21:25, 8 June 2008 (UTC)


 * I certainly agree that consensus applies to editorial decisions about the articles. What is the process for making such decisions? Sunray (talk) 21:53, 8 June 2008 (UTC)


 * The banner statement at the top of the talkheader states: "This is the talk page for discussing improvements to the [article or project] page." It seems to me that the means of deciding on those improvements is consensus, per WP:CON. What am I missing here? Sunray (talk) 20:13, 14 June 2008 (UTC)

Link alternative
There's strong past consensus to keep this template as compact as possible, so I think adding more verbiage might be a bad call. As an alternative, how about turning the word "discussing" into a hyperlink to Consensus? My only concern then would be that the text is becoming over-linked. — DragonHawk (talk|hist) 03:51, 16 August 2008 (UTC)

"Below" instead of "under"
Shouldn't it say below instead of under? as in: "Put new text below old text." -- Alexf42 20:20, 20 July 2008 (UTC)
 * I think they're synonyms. But, aesthetically, "below" does sound a bit better to my mind.  — DragonHawk (talk|hist) 03:48, 16 August 2008 (UTC)

Collapse it
To make this less irritating, have it permanently collapsed.

<pre style="overflow: auto"> class="messagebox standard-talk collapsible collapsed"

Also, change <pre style="overflow: auto"> Click here to start a new topic.

to

<pre style="overflow: auto"> Click the New section tab to start a new topic.

This is educate new users on how to start new topics on talk pages without this annoying thing on it. LA @ 16:25, 14 August 2008 (UTC)


 * I doubt the first change is a good one. Is not the whole point of the template to be visible? And if/when it loses it's purpose (a warning at a talk page prone to attract new/unexperienced users) than it should be removed? Agree with the second proposed change. - Nabla (talk) 16:35, 14 August 2008 (UTC)
 * Hiding it defeats the purpose, I'm afraid. If it's that bothersome to you, you could add  to your user CSS to hide it from your own display. –  Luna Santin  (talk) 16:58, 14 August 2008 (UTC)
 * I have to agree that collapsing the template would defeat the purpose of it. Past discussions seem to indicate that, while not everybody likes this template, there is no consensus to get rid of it.  I did just add a section to the doc subpage about how to make it invisible in user CSS; hopefully that will help some people. — DragonHawk (talk|hist) 04:34, 16 August 2008 (UTC)

Not done. Please gain consensus for these changes. --- RockMFR 06:32, 15 August 2008 (UTC)


 * I do support the second change. Tell new users how to edit talk pages, don't do it automagicaly for them. - Nabla (talk) 18:59, 15 August 2008 (UTC)


 * I'm generally a fan of the "teach a man to fish" approach, so the idea appeals. Some concerns, though: • Not all WP:Skins have a "new section" tab.  It can be argued that if someone has changed their skin, they prolly know what a discussion page is for, but then again, it's easy to change preferences, and "Skins" is something many people are familiar with from other areas of computing.  • Bigger concern is that "New section tab" is not necessarily obvious.  Heck, many people have trouble finding the "Discussion" tab.  I believe that hyperlink was put in there because -- to be blunt -- there are a lot of clueless newbies out there, and it was thought better to try and at least help confine their damage to easily-identifiable section.  •  That said, to help give people an idea of how it would look, I've added the proposed change to the draft.  There may also be issues with the longer text wrapping on some screens. — DragonHawk (talk|hist) 04:52, 16 August 2008 (UTC)
 * I just checked all of the current skins, and most have New section or Post a comment. Its too bad that the parser function #skin is not installed since it would be great to have it in this instance. LA (T) @ 08:11, 16 August 2008 (UTC)


 * {|class="wikitable"

!Section name!!Skins
 * New section
 * Chick, Classic, Cologne Blue, Modern, Monobook, MySkin, Simple
 * Post a comment
 * N/A
 * Nostalgia
 * }
 * N/A
 * Nostalgia
 * }
 * }


 * PS. Well, they are all called the same thing now. LA (T) @ 10:17, 16 August 2008 (UTC)


 * Well, if nothing else, at least this discussion resulting in making the skins more consistent. :)  I've linkified the skin names in the handy table Lady Alenna posted, so people can easily preview this talk page with different skins, to get an idea of what we're talking about. — DragonHawk (talk|hist) 17:55, 17 August 2008 (UTC)


 * (fixed DragonHawk's link that was pointing to the "draft" article, not to *the* draft - I hope you don't mind). I think that may be a sensible compromise... giving the fish while also teaching how to fish. As to the line wrpping, given that those are actually two different things, one is about replying to an existant section, the other about creating a new one, why not split in 2 lines? Take a look at my edit to the draft - Nabla (talk) 03:43, 17 August 2008 (UTC)


 * The problem with adding another line is that it will grow the overall template box on article pages. There is a line that doesn't appear except when this template is used on an article talk page, and with that line, the box is already full.  In the past, it seemed there was strong consensus for keeping this template as compact as possible.  For an example of what a busy talk page can look like, try Talk:Iraq War.  You can see why some people want to reduce the footprint.  So if it comes down to one or the other, I'd say we're better off making it wrap on some screens, then adding a line for all screens.  I'm changing the draft back to that end.  •  Better phrasing may be possible, such that something concise gets the message across just as well.  I know in the past people have come up with ideas along that line that led to myself, at least, remarking, "Why didn't I think of that?"  • (BTW, thanks for fixing my think-o with the link to the draft.) — DragonHawk (talk|hist) 17:15, 17 August 2008 (UTC)

New section phrasing and formatting
In the draft, I added some CSS magic to make the "New section" text look like the actual tab. I think that might address both the goal making it clickable for people who are confused, as well as teaching people what to look for. I also made the phrasing a bit more concise (at the cost of making it a statement, rather than a command, but that might be a good thing). It's still longer than it was, and longer than the other three always-present lines. Further improving the phrasing might still be possible. It also still suffers from the problem in that the other skins simply don't have tabs at all. Not sure what to do about that. Sufficiently advanced CSS magic might be able to make it vary by skin, but that's beyond my skill. — DragonHawk (talk|hist) 18:02, 17 August 2008 (UTC)


 * Yet another new idea: I took out the part that mentions tabs at all. This relies on the formatting alone to convey the message.  While I'm concerned that removing "tab" might not be explicit enough for some new users, this is a step on the road to making it skin-independent.  I can't seem to figure out how to make it use the CSS defined for the tabs, though.  The actual "new section" HTML has , but I don't know what to do with that. — DragonHawk (talk|hist) 18:11, 17 August 2008 (UTC)


 * Okay, I think I've almost got it. Rather than specifying absolute styles, I'm now inheriting from the style sheets in use.  So it will look appropriate for the skin in use.  It's not inheriting the background color the tabs have, though.  I'm not sure why yet. — DragonHawk (talk|hist) 18:22, 17 August 2008 (UTC)


 * Hmmm, I threw every possible name for a class I could find at it, and it still lacks the blue background. It also doesn't pick up all the formatting in other skins.  For example, in the modern skin, it should be transformed to lower case, and have a slightly different font.  Hmmmm.  Any CSS experts here?  I'm really just guessing.  — DragonHawk (talk|hist) 18:33, 17 August 2008 (UTC)

Dismissable?
How about making it dismissable? LA (T) @ 06:46, 17 August 2008 (UTC)


 * Interesting idea. Anyone know how that is done?  I would guess it requires special support in the MediaWiki software, which I think this template is unlikely to get.  The user style CSS change (now documented) has the same effect, without that kind of software maintenance cost.  OTOH, if it can be done easily with existing facilities, it might be a win.  I do wonder if it might be bad to make it too easy to dismiss this message, though.  Sometimes, a bit of a reminder can be useful for even the most experienced of editors.  I'm not sure on that front.  — DragonHawk (talk|hist) 17:11, 17 August 2008 (UTC)

Talkheader + WikiProjectBannerShell ≈ Good?
I was thinking that adding the WikiProject banners into this one might be a good thing. I did some tweaking here to add it. A few other little things changed, such as all of the borders being collapsed and the background for the big box changes from white to an off-white color, but that is about it. Everything from those two templates has been kept, except that to add the project banners, instead of  it is   I would like to know what you all think. Oh, and even if this isn't accepted, could someone please go through and make sure all of the alpha characters in the color hex codes are made lower case and maybe squeeze out some of the unnecessary spaces in the style declarations? LA (T) @ 06:42, 18 September 2008 (UTC)


 * Can you put an example on the talk page? Or somewhere :) -- SatyrTN (talk / contribs) 20:48, 18 September 2008 (UTC)


 * I don't have a point of view on whether or not the Talkheader and the WikiProjectBannerShell should be merged. But I would like to point to some related ongoing technical discussions:
 * Template talk:Tmbox
 * Wikipedia talk:WikiProject Council
 * We are about to change these boxes to use the "tmbox" classes. (See tmbox.) All the "messagebox" classes are now deprecated except for the "messagebox standard-talk". But that one is probably going to be deprecated soon. The reasons we are going to change to the tmbox classes is among other things that they give better box flow. That is, in several browsers when other boxes are put next to "messagebox standard-talk" boxes the boxes overlap each other. And the tmbox classes will automatically make the banners 100% wide when inside the bannershells without the need for the "nested=yes" parameter, thus making it much easier to create WikiProject banners that work inside shells. But note, this doesn't necessarily mean the banners or shells will use the tmbox meta-template, just that they can use the tmbox CSS classes.
 * But there is no hurry in doing the changeover. We are still tinkering with some of the details on how to best use classes in the bannershells, and it is likely we will have to change some of the JavaScript for the [show / hide] button too, to finally get rid of the "nested=yes" parameter.
 * I just wanted to inform you guys about what is going on.
 * --David Göthberg (talk) 21:29, 19 September 2008 (UTC)


 * If Talkheader and WikiProjectBannerShell were combined, some option to turn off the talkheader message, keeping the archive links, would probably be necessary. Gimmetrow 21:38, 19 September 2008 (UTC)
 * "Off" would be the default setting, if indeed god exists. I'm not convinced this template needs to exist in the first place, much less automatically appear as part of another template. — CharlotteWebb 01:00, 20 October 2008 (UTC)


 * No. The point of the banner is to tame clutter on talk pages, and talkheader isn't needed on all talk pages.  Sandy Georgia  (Talk) 01:38, 21 September 2008 (UTC)


 * I do not like an arrangement that would give the WikiProject banners top billing. There are more important things, notably the article history. Waltham, The Duke of 23:13, 21 September 2008 (UTC)


 * I think leaving them separate is better. -- Avi (talk) 23:47, 21 September 2008 (UTC)

Archive option
Hi. I've just seen the archive option of the talkheader template in action and have to say I really don't like it. I knew from the edit history that the talk page had been edited to put the link to the archive in a different place but, even as an experienced editor, it took me a while to spot that link was.

I think the existance of archives needs to be far more prominent than is currently displayed in the talkheader. However, my suggestion isn't to make them more prominent in the template, butto remove the option from the template altogether. Instead, I think dedicated and more visible template such as archivebox should be used for this useful and important function. Thanks for listening. GDallimore (Talk) 12:50, 25 September 2008 (UTC)


 * I agree 500% with everything GDallimore wrote. It's a very poor feature. --<b style="color:#7E2217;">Melty</b> <b style="color:#C35817;">girl</b> 17:26, 2 October 2008 (UTC)


 * It might be worth pointing out that the archive list feature of talkheader can be disabled with the  parameter.  So the separate box can be used on a case-by-case basis.  Personally, I find that kind of solution ugly, and tending to invite non-harmonious editing, but it's an option. ·  As for broader scope: Personally, I don't see a clear consensus for having this feature or for removing it.  I'd suggest inviting more discussion.  Perhaps a post at the pump, or an WP:RFC.  — DragonHawk (talk|hist) 02:57, 20 October 2008 (UTC)

De-link "talk page"
I'd like to suggest de-linking "talk page" in the template. New and unregistered users frequently post off-topic questions and comments on the WP:TALK discussion page (recent examples documented here), and I would guess that many of them have followed that link and then not understood where they were. PSWG1920 (talk) 00:56, 20 October 2008 (UTC)


 * This has been suggested before. It is my feeling that delinking would be the wrong thing to do.  We're trying to be helpful and guide people with signposts.  Some people clearly cannot follow on-screen instructions, and are looking to post something, and will do so the first place they stumble into.  I don't think there's much we can do about that.  On the other hand, removing the links means that people who are *are* sufficiently clueful to follow instructions now don't have instructions.  Practical upshot being, we're punishing the clueful, and the clueless will probably still post off-topic comments.  Maybe I'm in the minority in this thinking; I dunno.  ·  I've also seen some evidence that people post random off-topic comments for reasons other than this template.  Particularly amusing is [[Media:Wiki discussion tab.png]] -- even a picture of the discussion tab attracts cluebies. — DragonHawk (talk|hist) 03:09, 20 October 2008 (UTC)

Archive Links
I would like to see a function added to this that allows users to create customized links to their talk page archives, instead of automatically adding the links only with a standard naming scheme. Personally, I would like to use link to an old revision as my archives. Why? Personal taste, I guess. Any thoughts? --HoboJones (talk) 03:55, 13 November 2008 (UTC)


 * No offense, but this seems like needless feature creep to me. :)  — DragonHawk (talk|hist) 13:21, 10 December 2008 (UTC)

Removing draft
The current "draft" doesn't look like it's going anywhere. Meanwhile, I've started a sandbox at template:talkheader/sandbox, where I'm going to be working on tweaks to this. Does anyone mind if I delete the draft template? Chris Cunningham (not at work) - talk 11:58, 10 December 2008 (UTC)


 * Six of one, half-dozen of the other. I would've just done your work at the "draft", it served the same purpose, but since you've already done your work in "sandbox", I see no harm in deleting the "draft" page.  :)


 * Cheers. I've redirected the draft page to the sandbox, which is the standard location for such things - the documentation automatically looks for a sandbox link and adds the line "This template has a sandbox (edit) for editors to experiment."