yes, lets use header tags (ie h2, h3, etc) instead of bold for headings at least… you can bold text in line, but if a heading style thing then header tags…

and you want to pick the appropriate header tag and nest them correctly…  that is, first header tag would be h2…  and any other at the same level…  nested header tags would get the next level, in this case h3… and so forth…

before you go forward though, it is a good time for this discussion…

and you allude to this, but that page is not for the template tags in that plugin…  it should be a discussion about the purpose, how to use and coding template tags in user developed plugins…  the whole parent section is about developing plugins…

the template tags you are referring to are in a plugin…  we should decide where we want to talk about any plugins that we have… certainly we could talk about and detail our provided plugins, but what about user contributed? I think yes to both…  and frankly, allowed for this when creating the basic codex layout…  I had intended for us to list all available plugins at:

http://codex.simple-press.com/codex/plugins/plugins-repository/

that page would be a list, with each plugin hyperlinked to the specific plugin page (a child page) where details would be listed… so we could create a template tags plugin page there and put your stuff including the widget…

optionally, I was also thinking you could download any of the latest plugins from that page, hence the name plugins-repository… but I was not convinced that was the best idea…  we need to come up with how we are going to make plugins available…  not sure a download page in the codex is the best place and we dont want multiple (though could each link to the file)… 

one thing would be to just make this info about plugis (but why no link folks might ask)…

and of course, this discussion pertains to themes too…

thoughts?

Re: The Plugin template tags pages

I am thinking repository isn’t quite right.

Maybe Something like

Simple:Press Supplied Plugins

Included on that page would be.

• How to get the full plugin package. No link to individual plugins.
  
• How to install the Plugins
• How Plugins are automatically updated in WP
• How to Manage Plugins. Directed to the Manage Plugins page http://codex.simple-press.com/codex/administration/manage-plugins/
• List of all supplied Plugins with links to each one
• Where to find user-created plugins

  On each linked-to plugin page

• Name of Plugin
• Reiterate on how to manage or turn it on. Directed to the Manage Plugins page http://codex.simple-press.com/codex/administration/manage-plugins/ (Basically one sentence)
  
• Reiterate where to get the complete plugin package or note back to the Supplied Plugins page. (Basically one sentence)
• How to invoke plugin. For example if it is one that you might call via php
• Then the info on how to use similar the sample sp_get_auth page http://codex.simple-press.com/codex/simplepress-api/functions/sp_get_auth/

Brandon, not ignoring this…  just trying to get the Beta release out on Sunday…

we need to discuss this amongst us and come to consensus… personally, I would like to see all plugins/themes listed together…  not opposed to segmenting by SP team contributed and user contributed…

need more time next week, job permitting – gonna be hairy between now and Christmas, to read in depth again…  and need Andy’s feedback too…

Cant say thanks enough for all the help you have given thus far!!!!!