[wp-docs] WordPress-Generated CSS Classes for Menus

[Chip Bennett]

I just did a quick read-through, and nothing jumped out at me as being
appropriate as a "jump" link to the section. Of course, that probably
implies that some of the descriptive text could use updating as well, if
none of it makes mention of the function applying contextual CSS classes to
the menu list items. :)

I found and wrapped wp_page_menu() in <tt> tags in one subheading. I didn't
see any others; did I miss any?

Thanks,

Chip

On Tue, Apr 17, 2012 at 1:10 PM, Lorelle on WordPress <
lorelleonwordpress at gmail.com> wrote:

> It looks fabulous.
>
> Make sure, when ready, that there are jump links to that section from
> within the article, especially in the examples and mentions of the menu
> classes.
>
> Also, we usually do the "code" headings in <tt> code. I could go either
> way with these but that's the consistent look and feel.
>
> Well done! Thank you!
>
> Lorelle
>
>
>
> On Mon, Apr 16, 2012 at 7:47 AM, Chip Bennett <chip at chipbennett.net>wrote:
>
>> Here's a stab at a first draft:
>>
>> http://codex.wordpress.org/Function_Reference/wp_nav_menu#Menu_Item_CSS_Classes
>>
>> Let me know what you think. If this one is okay, I'll use the same format
>> for wp_page_menu() and wp_list_pages().
>>
>> Thanks,
>>
>> Chip
>>
>>
>> On Fri, Apr 13, 2012 at 7:30 PM, Lorelle on WordPress <
>> lorelleonwordpress at gmail.com> wrote:
>>
>>> Brilliant. What say ye, Chip?
>>>
>>> Lorelle
>>>
>>>
>>>
>>> On Fri, Apr 13, 2012 at 2:03 PM, Evan Cordulack <ecordulack at gmail.com>wrote:
>>>
>>>> I think Chip's orginal idea of adding the generated CSS to the function
>>>> reference is a fantatic idea.
>>>>
>>>> I will update the Menu User Guide to be WordPress Lesson.
>>>>
>>>> Consolidating these other two articles into one that covers
>>>> intermediate/advanced users and then links through to the function
>>>> references can go on my to do list as well.  After a quick search through
>>>> the codex, I didn't see anything else to consolidate.
>>>>
>>>> -Evan
>>>>
>>>> On Apr 12, 2012, at 12:10 PM, Lorelle on WordPress wrote:
>>>>
>>>> http://codex.wordpress.org/WordPress_Menu_User_Guide needs desperate
>>>> updating and compliance with Codex styles, so I would use this for the
>>>> WordPress Lesson article. Just update it. It's a good introduction.
>>>>
>>>> Add to the list:
>>>> http://codex.wordpress.org/Dynamic_Menu_Highlighting
>>>> http://codex.wordpress.org/Creating_Horizontal_Menus
>>>>
>>>> All long past due needing updates or merging.
>>>>
>>>> If we had two solid articles, one for beginners and another for
>>>> intermediate to advanced users, and they link to all the appropriate
>>>> supporting functions and template tags, would that be enough? Can we get
>>>> rid of the two above or consolidate things, or do we need more?
>>>>
>>>> Lorelle
>>>>
>>>>
>>>>
>>>> On Thu, Apr 12, 2012 at 7:12 AM, Evan Cordulack <ecordulack at gmail.com>wrote:
>>>>
>>>>> I could also see this being a useful WordPress Lesson.  Perhaps this
>>>>> come after a more technical write up for the codex?  I am happy to help
>>>>> with it.
>>>>>
>>>>> -Evan
>>>>>
>>>>> On Apr 12, 2012, at 9:20 AM, esmi at quirm dot net wrote:
>>>>>
>>>>> > on 12/04/2012 13:58 Chip Bennett said the following:
>>>>> >
>>>>> > <snip>
>>>>> >>  I'm thinking that the function references would be ideal?
>>>>> >> I note that wp_list_pages() does include a couple of the classes,
>>>>> under the
>>>>> >> "Markup and Style of Page Items" section. Should I follow this
>>>>> model for
>>>>> >> all three function reference pages?
>>>>> >
>>>>> > +1 for the function reference page. Another example is <
>>>>> http://codex.wordpress.org/Function_Reference/body_class>
>>>>> >
>>>>> > Mel
>>>>> > --
>>>>> > http://quirm.net
>>>>> > http://blackwidows.co.uk
>>>>> > _______________________________________________
>>>>> > wp-docs mailing list
>>>>> > wp-docs at lists.automattic.com
>>>>> > http://lists.automattic.com/mailman/listinfo/wp-docs
>>>>>
>>>>> _______________________________________________
>>>>> wp-docs mailing list
>>>>> wp-docs at lists.automattic.com
>>>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>>>
>>>>
>>>> _______________________________________________
>>>> wp-docs mailing list
>>>> wp-docs at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> wp-docs mailing list
>>>> wp-docs at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>>
>>>>
>>>
>>> _______________________________________________
>>> wp-docs mailing list
>>> wp-docs at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>
>>>
>>
>> _______________________________________________
>> wp-docs mailing list
>> wp-docs at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>
>>
>
> _______________________________________________
> wp-docs mailing list
> wp-docs at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-docs/attachments/20120417/78ea6165/attachment-0001.htm>