Template:comic discussion

Explain xkcd: It's 'cause you're dumb.
(Difference between revisions)
Jump to: navigation, search
(hmmm)
(don't show in main page)
Line 2: Line 2:
 
<div style="border:1px solid grey; background:#eee; padding:1em;">
 
<div style="border:1px solid grey; background:#eee; padding:1em;">
 
{{#ifexist:{{TALKPAGENAME}}
 
{{#ifexist:{{TALKPAGENAME}}
   |<onlyinclude>{{:{{TALKPAGENAME}}}}</onlyinclude>
+
   |{{#ifeq:{{PAGENAME}}|Main Page||{{:{{TALKPAGENAME}}}}}}
 
   |''No comments yet.''
 
   |''No comments yet.''
 
}}</div>__NOTOC__
 
}}</div>__NOTOC__

Revision as of 17:19, 6 August 2012

Comment.png add a comment!Discussion

The template eats whitespace, compare Talk:1101: Sketchiness and 1101: Sketchiness. --Kronf (talk) 20:58, 30 August 2012 (UTC)

Nope. In most cases it performs fine. Here's just a few examples:
I don't know what is wrong with that talk page, but it appears to be happening only for that comic.
lcarsos (talk) 22:19, 30 August 2012 (UTC)

New topic for testing purposes

Just testing what the TOC looks like... Mark Hurd (talk) 11:01, 14 April 2013 (UTC)

FYI I've mentioned my change to "add a topic!" here for a wider audience. Mark Hurd (talk) 11:33, 14 April 2013 (UTC)

Switched to level-1 header

I was just on 1110 and I noticed that all the talk page sections were showing up as the same level as content sections... leaving a "Discussion" section with nothing actually in it. While level-1 is normally reserved for article titles, it doesn't really bother people usually, and I think it's preferable to the alternative... it's also somewhat fitting, since we are transcluding another page after all. (Another option would be configuring the "new section" button to create a level-3 header on talk pages... if that's possible.) PinkAmpersand (talk) 14:33, 30 April 2013 (UTC)

Thanks. This actually had been done before. Please see this discussion and add your thoughts :) Waldir (talk) 16:48, 1 May 2013 (UTC)

"add a comment!" button

I noticed that the link appended onto the "add a comment!" button is {{fullurl:{{TALKPAGENAME}}|action=edit}}. Wouldn't it make more sense to have it as {{fullurl:{{TALKPAGENAME}}|action=edit&section=new}}, as to create a new section by clicking that button? Schiffy (Speak to me|What I've done) 15:48, 12 July 2013 (UTC)

If someone just wants to add a comment without making a new section, the current add a comment button serves them well. Plus, headers and transclusion do not mix well, and we tend to avoid them in discussion pages unless we're not transcluding; see Time and its respective talk page. Davidy²²[talk] 16:39, 12 July 2013 (UTC)
I agree with Davidy22. Most replies should not start a new section because users are just replying to an existing one. If some likes to open a new section it's still easy.--Dgbrt (talk) 17:26, 12 July 2013 (UTC)
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox

It seems you are using noscript, which is stopping our project wonderful ads from working. Explain xkcd uses ads to pay for bandwidth, and we manually approve all our advertisers, and our ads are restricted to unobtrusive images and slow animated GIFs. If you found this site helpful, please consider whitelisting us.

Want to advertise with us, or donate to us with Paypal or Bitcoin?
http://www.explainxkcd.com/wiki/index.php?diff=4940
www.explainxkcd.com
crawl=CC-MAIN-2014-23
31951
application/http; msgtype=response
sha1:E44DIVIPKH3ZNNGPEU4I7RMRIIWOHECQ
<urn:uuid:4dc781d6-b0e3-45ca-a430-858c63a4fbba>
2014-07-23T20:12:48Z
104.28.22.60
sha1:2P5754PXH2QIPDOGHEZA47V7HAW4V75W
<urn:uuid:c51258e6-a197-4a9a-9596-bafe6cb5c762>
http://www.explainxkcd.com/wiki/index.php?diff=4940
length
response
<urn:uuid:606332d2-0c26-489a-95bd-9c99ca384015>
robots: classic
hostname: ip-10-33-131-23.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2014-23
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for July 2014
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf