Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove placeholder markup from <body> #926

Closed
wants to merge 1 commit into from
Closed

Remove placeholder markup from <body> #926

wants to merge 1 commit into from

Conversation

dhaigh
Copy link
Contributor

@dhaigh dhaigh commented Jan 20, 2012

I feel as though what's there is fairly arbitrary. For most of my stuff I'd always be adding IDs onto <header> and <footer> because I preferred it to having bulldozer selectors on all header and footer els, thus #925. However. On #203 @necolas and others think it might be a good idea to empty <body> completely and let people start from scratch. I think so too. Feels more boilerplatey.

@dhaigh
Copy link
Contributor Author

dhaigh commented Feb 2, 2012

I made (a start on) a <body> tips article. Not sure if it's of any use to anyone, it's the kind of thing that'd be useful to me though.

I think at any rate, an official 'body tips' article would be cool even if the placeholder markup in index.html stuff stays there. I think it'd be a good idea to have a link to an article in a comment before removing everything (as per index.html#L25).

http://declanhaigh.com/body-tips/

@necolas
Copy link
Member

necolas commented Feb 2, 2012

I think H5BP trying to provide tips on how to write HTML (which is basically what "body tips" ends up being) is probably beyond the scope of the project, opens a can of worms, and leads to repetition of content that is already out there. If we want to do anything, my preference would be to link to a handful of good, general source for learning about HTML in the Wiki on "Better web development".

@dhaigh
Copy link
Contributor Author

dhaigh commented Feb 3, 2012

I like the sound of that. My idea wasn't geared towards telling people how to write html. I hadn't thought about that though, so I updated my 'body tips' to make sure it was only informative. I agree that's a bad thing for reasons listed as well as it could come across as one-sided/poorly justified/personal preference etc. I think my goal was two-fold. 1) Talk about a few of the cool things you can do that are otherwise considered taboo 2) Give good examples of section element usage. I put the 'common snippets' in there as well because I thought it'd be a useful reference since they are already in the body of index.html and maybe deserve some attention. But yeah. It was really a matter of pointing out "hey look, you can totally do this and it works and it's cool", not "you should do this this and this". :)

Update: I've separated the contents of my page and it's largely turned into my own dubious musings. Make what you like of it if anything at all.

@yanneves
Copy link

Hm, kind of on the fence about this one. But emptying the <body> tags could be reasonable.

Unfortunately, you'd lose out on best HTML5 practices like <header> instead of <div id="header"> and <footer>, as well as the role=main attribute. Perhaps this should be treated similarly to the <head> tags content, with a basic foundational structure and a link to suggestions for extending / improving this structure?

@nullcitizen
Copy link

I will say I nearly always remove the markup from <body> in every project, as it never is exactly what I want. Though, to be quite honest, the markup isn't terribly offensive either.

@devinrhode2
Copy link
Contributor

There should be links on why this markup is good. I almost always remove it also.

@alilleybrinker
Copy link

I think keeping the markup as a general guideline or suggestion is harmless. It provides a nice starting point for those newer to HTML5, and for those more experienced it can be easily removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants