templates in codex?

[EdB]

Just decided a quickie I could get done is completing the print.css files but then remembered that meant 40 or so other templates which reminded me we don't have a home for templates not in the actual package. So I was gonna ask what are we gonna do with them when I remembered the codex blog.

So is that a good place for extra templates? b2evo's use of evo and a tempskin to show how a blog looks is a good idea but maybe we can do it with a blog post? Make a templates blog, and put up a screenshot and a little descriptive bit about it? Link the screenshot to the .zip file and there you go.

Being a stub file kind of guy I'd do it with templates.php then categories for 'big picture' stuff like 2-col or 3-col and fixed width or stretchy width, then tags for whatever else seemed worth providing sortability on.

[Tblue]

Make a templates blog, and put up a screenshot and a little descriptive bit about it? Link the screenshot to the .zip file and there you go.

Sounds good to me. But I would use an additional subdomain like "templates.quamplures.net".

[EdB]

If I knew how I would

Same for the plugins.php stub file? All I know is the bits I do, which pretty much means stub files. Always. Actually ever since forever. Never did understand the folks who didn't get stub files because to me it was obvious stuff. Doing the thing.domain.tld part is mysterious and arcane.

Got a clue you can share?

[EdB]

Been thinking about this one. And the plugins.php blog in codex.quamplures.net

I guess the question is are we going to have codex as the master home for everything, or a handful of little homes? For example I saw a category for plugins and figured "nope" and gave them their own blog, and obviously would do the same for templates. So http://codex.quamplures.net/index.php/codex/ is the main page (which is a weird looking URL but whatever), and http://codex.quamplures.net/plugins.php is for plugin stuff. Just a bunch of blank posts there now - placeholders for what I reckon will just be the README file all over again.

Alternatively I guess we could have plugins.codex.quamplures.net but I have no idea how to make that happen. Or templates.blahblahblah - you get the idea.

Anyway playing more in plugins makes me need to make more pages for plugin help URLs to point to, which made me think of this post and the whole codex thing in general again.