Why 1 and 2?[edit source]
What is the purpose of the {{{2}}}? Is it just so that a different name can show than the actual name? Is this only for how to? If so, I think that we can deal with How to vs Howto, especially considering that howto is not a word. Great work so far. Thank you --Lonny 16:25, 18 October 2006 (PDT)
- It's not just for "How to". First param is upper case for the Category name. The 2nd is lower case to build the preload text template name. (If we are okay with funky preload text template names, we could maybe live with just the upper case, but still an issue with "how to".) I bet there's a much cleaner way to do this (see section below), but I figured this was workable for the time being and had the advantage (?) of not requiring separate templates for maintenance. On the other hand, I currently have separate preload text templates, but it now occurs to me that those could be much simplied by embedding a common preload text template within the area-specific preload templates. --CurtB 16:37, 18 October 2006 (PDT)
Newparampageresource challenge[edit source]
My clever (?) scheme to use parameters for the Newpageresource template worked great for the other areas, but came to grief with Howto since the category name has a space in it, but the template for the preload text does not have a space. It's not too bad, but it could be improved with a (yuck) third parameter. Alternatively, we could maybe use a simple numeric parameter and some complex conditional stuff within the template --CurtB 16:37, 18 October 2006 (PDT)
- Can we use an underscore, or am I not understanding the problem? --Lonny 16:45, 18 October 2006 (PDT)
- Maybe. The parameters get used in 3 places, really. In the category (upper case), in the verbiage (I used both cases, which probably wasn't needed or clever), and in constructing the preload text template name. An underscore would work for how_to, which would handle the preload text template name, and would probably be tolerable in the verbiage, or could just use the upper case param. I guess we could even get down to a single parameter, if we are willing to tolerate something like "NewHow_topage" as a template name. --CurtB 16:52, 18 October 2006 (PDT)
- I like the one parameter solution the best. I think the readers can deal with capitals (which may also help to point out that the word choice is not casual, i.e. this is the ______ area), and even one underscore. Keep up the awesome push to make Appropedia not just easy to submit to, but alluring as well. --Lonny 16:58, 18 October 2006 (PDT)
- Okey dokey. "I'm goin' in!"
- I like the one parameter solution the best. I think the readers can deal with capitals (which may also help to point out that the word choice is not casual, i.e. this is the ______ area), and even one underscore. Keep up the awesome push to make Appropedia not just easy to submit to, but alluring as well. --Lonny 16:58, 18 October 2006 (PDT)
- Maybe. The parameters get used in 3 places, really. In the category (upper case), in the verbiage (I used both cases, which probably wasn't needed or clever), and in constructing the preload text template name. An underscore would work for how_to, which would handle the preload text template name, and would probably be tolerable in the verbiage, or could just use the upper case param. I guess we could even get down to a single parameter, if we are willing to tolerate something like "NewHow_topage" as a template name. --CurtB 16:52, 18 October 2006 (PDT)
- Ack! It doesn't work with one param... And although I'm pretty sure I tested it with 2 parameters, I can't remember for sure. Problem is, the new page is not preloaded correctly with the area-specific template. If I hard-code the template, it works fine. Gotta run, unfortunately. Not too serious: if someone uses it now, they will get the Project preload for every page, and the only difference is the categorization, so we can live with it for the moment. Durn it! --CurtB 17:44, 18 October 2006 (PDT)