search

innoq / statuses

statuses
Apache License 2.0
13 stars 14 forks source link

Add semantic markup for the 'next' link (and the whole page) #118

Closed tloist closed 9 years ago

tloist commented 9 years ago

Currently the layout is like

 <body>
    <div class="navbar navbar-default navbar-static-top" role="navigation">
    <div class="container-fluid">
       <div class="row">
         <div class="col-xs-12 col-md-12">
           <div> <!-- Query Area -->
           <div> <!-- Main Content Area -->
           <a>Next</a>
         </div>
       </div>
     </div>
    <!-- Script includes -->
 </body>

My suggestion is that this could use some additional semantic markup, like

Im particular interested in the Next link at the bottom of the page. I would wrap it up in a <footer> and use an appropiate link type (most presumably next).

That would enable browser plugins like AutoPagerize and would ease technical access to the website.

Oh and by the way, the same thing would apply for a prev link, in case there would be one (currently there is none).

aheusingfeld commented 9 years ago

I'm already taking on it while also refining the layout. Unfortunately those proper elements don't go too well with our Bootstrap layout. 😒

would ease technical access to the website

@tloist I hope by "technical access" you're not talking about screen scraping but instead are thinking of the same approach as #116 and #72?!

mvitz commented 9 years ago

I hope the problems you are mentioning are mostly in refining the layout?!? Introducing header, footer and main should not be a problem for bootstrap as long as you keep the classes.

aheusingfeld commented 9 years ago

I hope the problems you are mentioning are mostly in refining the layout

Yes, though I had some issues with previous versions of bootstrap requiring the usage of <div> elements. |-( I'd like to adapt to the Twitter layout a bit but their markup is really awful. Will update #119 asaiad

aheusingfeld commented 9 years ago

@tloist This has been fixed with #119/ cc102dd. To support your intention of indexing the data, I'd request the introduction of microdata to Statuses.

Another (less awesome) option would be Facebook OpenGraph which duplicates the information on the page into specific <meta> tags. See #128 for details.

stilkov commented 9 years ago

Or maybe RDFa instead of microdata. I’m not sure we want to open that can of worms.