Okay/Sketchbook

Multiple days in a row now I have woken up in a cold sweat having dreamt new Okay markup. I'm writing it here so I can gather feedback and iterate before specifying. I think this is what normal spec writers do already.

Room Directory

Initial Concept

<main class="ok-rooms">
    <h1>Rooms</h1>
    <p>Here are all the rooms on this server.</p>
    <ul>
        <li><a rel="ok-room" href="/rooms/room-1">Room 1</a></li>
        <li><a rel="ok-room" href="/rooms/room-2">Room 2</a></li>
    </ul>
    
    <section>
        <h2>Cooler Rooms</h2>
            <ul>
                <li><a rel="ok-room" href="/rooms/room-3">Room 3</a></li>
                <li><a rel="ok-room" href="/rooms/room-4">Room 4</a></li>
            </ul>
    </section>
</main>

Thoughts:

• To what extent do we want to enforce structure? Right now the only things I would say are significant to the client are the links and sections. Everything else is window dressing for browsers.
• Do we really need the outer ok-rooms element?
• Should ok-room be a rel or a class
• Is the section syntax silly
• Do we want to require them to be in a list element.
• I had a thought that it would be fun for clients to just load the room directory page inside a little window or something and then when you click one of the rooms it opens it in the client's own interface. You could probably do this as a browser extension actually.