hAtom maybe?
http://microformats.org/wiki/hAtom
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*
On 20/02/2009, at 7:05 AM, Essential eBiz Solutions wrote:
I'm making a news plugin but I'm un-sure what the best/most
accesible way is to mark it up?
Try http://microformats.org/wiki/hatom#Examples_in_the_wild
Cheers,
Nathan de Vries
***
Don't avoid using a headline level just because
it's "already being used within the page".
Good call, Paul.
Respectfully,
Mike Cherim
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webs
At 2/19/2009 03:43 PM, Essential eBiz Solutions wrote:
It's basically a page on my site just to put news snippets such as new
client etc.
I've gone with
News Title (h1, h2 and h3 are already being used within the page
for heading and sub heading)
News Date
News Content
At the risk of reading
Hi Essential,
News Title (h1, h2 and h3 are already being used within the page
for heading and sub heading)
News Date
News Content
That works. You might be able to get rid of that what-will-be-repetitive
"news_content" class if you wrap the thing in a div (id="news"), then the
CSS would be l
al Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Mike at Green-Beast.com
Sent: 19 February 2009 23:12
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Marking up news
Hi Essential,
> Hi, it is going to be a list of news events and will hopefully whe
Hi Essential,
Hi, it is going to be a list of news events and
will hopefully when I figure it out print the info
to RSS that's why I was thinking of the DL so it's
just a list of some events rather that full news?
I'm sorry, I guess I don't realy understand what you're after. I mean I
underst
Kay in t Veen - Gmail wrote:
> i would not suggest to use for "our news" cause what benefit would
> a have on the keywords our news.
Think about page structure first, and what search engines think about it
second.
> further a news module is a sub part of your site and never use h1 for that
> an
[mailto:li...@webstandardsgroup.org] On
Behalf Of Mike at Green-Beast.com
Sent: 19 February 2009 21:47
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Marking up news
> i would not suggest to use for "our news" cause what benefit
I agree. That was just for demonstration purposes... I
i would not suggest to use for "our news" cause what benefit
I agree. That was just for demonstration purposes... I would certainly
suggest using whatever heading would be appropriate and semantic. I didn't
have that info so I created a new document and dropped the news in just so I
could sh
I'd suggest this as well, normally. However, it seems like how this is
going to be used is to provide a list of news articles, and since it's a
list it makes sense to use a list element for it's markup. At least
that's what I inferred from the initial examples.
Mike at Green-Beast.com wrote:
i would not suggest to use for "our news" cause what benefit
would a have on the keywords our news.
further a news module is a sub part of your site and never use h1 for
that
and surely dont use 2 h1's in 1 page.
use h3 of h4
On Feb 19, 2009, at 10:04 PM, Mike at Green-Beast.com wrote:
Hi Essential,
I'm making a news plugin but I'm un-sure what
the best/most accesible way is to mark it up?
I'd suggest neither. I'd recommend something more conventional such as:
Our News
The following are our latest news articles:
News Heading
News Date
News content
Not as fancy, but I b
I would say something like:
News Heading
News Dateline
News Content
could be most appropriate. The first example wouldn't really be
appropriate because it is trying to create visual groups without any
group being in the markup, unless you did multiple s, which st
14 matches
Mail list logo
