HTML Convention

[cooper.semantics]

Basically I am looking for the best solution for a naming convention schema that eliminates page specific names while keeping my html modular...

Ideally the designs I work with consist of:

Header

Main Navigation

Content Main
    Section - Main
    Section - Features
    Section - Entries

Content Related
    ....

Footer

The pages for example could include:
about.html
news.html
work.html
hobbies.html

[AlexDawson]

How about using the following...

<div id="section-main">
   <div id="about">...</div>
   <div id="news">...</div>
   <div id="work">...</div>
   <div id="hobbies">...</div>
</div>

[oddz]

I've been finding the patterns here nice and practical.

[logic_earth]

Yum XML <3

<?xml version="1.0"?>
<bucket xmlns="http://xmlns.org/logic/super/markup">
    <section type="about">
        <header>About whatever...</header>
        <intro>
            <para>Some long winded intro...</para>
            <para>Some long winded intro...</para>
        </intro>
        <para>Continue on with the paragraphs.</para>
    </section>
</bucket>

[felgall]

And then just use XSL to parse it into something web browsers can display.

[oddz]

<?xml version="1.0"?>
<bucket xmlns="http://xmlns.org/logic/super/markup">
<section type="about">
<header>About whatever...</header>
<intro>
<para>Some long winded intro...</para>
<para>Some long winded intro...</para>
</intro>
<para>Continue on with the paragraphs.</para>
</section>
</bucket>

The advantages of that approach don't seem to out weight the disadvantages. Although in theory it does seem like a good solution. The practicality seems very low. Bucket… really,lol

[logic_earth]

...Bucket… really,lol

Felt to lazy to come up with a better root element. So *shrugs*

[oddz]

naming… seems so easy in theory,lol

[Karpie]

I would not use either of those naming schemes.

[zcorpan]

Not sure I understand the problem, but: have you considered multiple classes on one element? <div class="hobbies section-main obj">

[RetroNetro]

I might not be understanding what you want to do, but won't this work:

.section-main {...}
.work{...}
.hobbies{...}
.features{...}

[cooper.semantics]

Not sure I understand the problem, but: have you considered multiple classes on one element? <div class="hobbies section-main obj">

I can't use any page specific naming conventions because each block can be dropped into any page...
Here is a solution I came up with that will make my html modular and not page specific while reusing the same naming conventions. Again this could turn into a nightmare:

about.html
<div id="document">
	<div class="section-main-obj1">...</div>
	<div class="section-features-obj1">...</div>
	<div class="section-entries-obj1">...</div>
</div>
 
work.html
<div id="document">
	<div class="section-main-obj2">...</div>
	<div class="section-features-obj2">...</div>
	<div class="section-entries-obj2">...</div>
</div>
 
news.html
<div id="document">
	<div class="section-main-obj3">...</div>
	<div class="section-features-obj3">...</div>
	<div class="section-entries-obj3">...</div>
</div>

I could even interchange these if I want as well...

[Arlen]

Basically I am looking for the best solution for a naming convention schema that eliminates page specific names while keeping my html modular...

Ideally the designs I work with consist of:

Header

Main Navigation

Content Main
    Section - Main
    Section - Features
    Section - Entries

Content Related
    ....

Footer

Sounds like you have your names. Assuming these blocks appear once and once only on a page, convert the names you used to ids on div tags and you're done.

Don't make things harder than they need to be. Overthinking will almost always bite you back.

[cooper.semantics]

Sounds like you have your names. Assuming these blocks appear once and once only on a page, convert the names you used to ids on div tags and you're done.

Don't make things harder than they need to be. Overthinking will almost always bite you back.

These blocks can appear how ever many times on a page or another page. That's why I am using the class design pattern...