Revision as of 02:38, 15 May 2009

What kinds of things would be useful to add to the language template? Official website? Largest IRC support channel? --Short Circuit 02:48, 14 February 2009 (UTC)

Official website would be cool. You should use named arguments when you add these things. --Mwn3d 03:06, 14 February 2009 (UTC)

How about "syntax highlighting tag" so that we can standardize unimplemented languages and let people know what to use for supported ones? --Mwn3d 22:35, 14 February 2009 (UTC)

Language template beta

I created Template:Language_beta, so folks can experiment with the language template and make it better. Make changes and additions there, and we'll move over whatever works well over to the main template. Think of the beta template as a staging ground for ideas and features, to see what works well.

Don't be obsessed with keeping information in the language template confined to the boxes on the right; If it warrants space in the main body of the page, put it there. The idea is to come up with way of uniformly presenting all types of information that should be available for any given language.

Don't be terrified of including templates within templates, either. If there's a segment or section you want to add to the language template, create a template for that particular section, and do any additional nesting you might need in that template. If it makes the information easier to organize and edit, that's not a problem. But don't go overboard; If the maintenance of the segment is a pain because of deeply nested templates, it will eventually have to be removed or replaced when a change needs to be made.--Short Circuit 02:38, 15 May 2009 (UTC)

Language template wishlist

Official site
Appropriate HOPL link (There's already a HOPL link, but most RC template links don't take you where you would have wanted to go.)
Ancillary/support sites, forums and appropriate newsgroups
Helpful literature (I'm hoping to help fund RC's server and service expenses based referral/affiliate links, so be aware that this might get changed to that purpose.)
Language tag (If someone has a good idea how to do this, I'm all ears. It's non-trivial to map backwards from a language name to the appropriate GeSHi language file, as some languages have duplicate files, and most languages on Rosetta Code aren't supported at all.)

@@ Line 2: / Line 2: @@
 :Official website would be cool. You should use named arguments when you add these things. --[[User:Mwn3d|Mwn3d]] 03:06, 14 February 2009 (UTC)
 :How about "syntax highlighting tag" so that we can standardize unimplemented languages and let people know what to use for supported ones? --[[User:Mwn3d|Mwn3d]] 22:35, 14 February 2009 (UTC)
+=Language template beta=
+I created [[Template:Language_beta]], so folks can experiment with the language template and make it better.  Make changes and additions there, and we'll move over whatever works well over to the main template.  Think of the beta template as a staging ground for ideas and features, to see what works well.
+Don't be obsessed with keeping information in the language template confined to the boxes on the right; If it warrants space in the main body of the page, put it there.  The idea is to come up with way of uniformly presenting all types of information that should be available for any given language.
+Don't be terrified of including templates within templates, either.  If there's a segment or section you want to add to the language template, create a template for that particular section, and do any additional nesting you might need in that template.  If it makes the information easier to organize and edit, that's not a problem.  But don't go overboard; If the maintenance of the segment is a pain because of deeply nested templates, it will eventually have to be removed or replaced when a change needs to be made.--[[User:Short Circuit|Short Circuit]] 02:38, 15 May 2009 (UTC)
+=Language template wishlist=
+* Official site
+* Appropriate HOPL link (There's already a HOPL link, but most RC template links don't take you where you would have wanted to go.)
+* Ancillary/support sites, forums and appropriate newsgroups
+* Helpful literature (I'm hoping to help fund RC's server and service expenses based referral/affiliate links, so be aware that this might get changed to that purpose.)
+* Language tag (If someone has a good idea how to do this, I'm all ears.  It's non-trivial to map backwards from a language name to the appropriate GeSHi language file, as some languages have duplicate files, and most languages on Rosetta Code aren't supported at all.)