Documenting Extension Points. Fixes #20.

[tjvantoll]

It'll probably take me another day or two to make my way through these. I'll ping people when this is ready for review.

[jzaefferer]

This one is looking good. May need to update once anchors are gone from menu, but that would go into the 1-11 branch anyway.

[tjvantoll]

I made the recommended changes to _renderItem. The <a> requirement is in its own paragraph now so it's easily axed when that requirement is removed.

[tjvantoll]

Ok, I discovered this after I moved onto the next method. Although you can use any element for menu items, it's silly to use anything other than <li> elements because the menu itself is created as a <ul> in the middle of an epic (aka not feasibly overridable) _create() method.

I'm thinking we should just stick with the ul parameter and <ul> element in the docs for _renderItem since you will actually be getting a <ul>. Thoughts?

[scottgonzalez]

Yeah, sounds good. I forgot that we didn't design autocomplete to be super flexible in terms of markup since the <ul>/<li> combo allows for a decent amount of customization within the items.

[tjvantoll]

@scottgonzalez @jzaefferer @kborchers ping. These should be good to go if you want to take a look. Here are screenshots so you don't have to sift through XML.

[scottgonzalez]

Looks good to me.

[kborchers]

👍

[jzaefferer]

👍