Front-end style guide: Difference between revisions

Content added Content deleted
imported>Aldeka
imported>Aldeka
Line 52: Line 52:
<module>
<module>
<module-head>
<module-head>
Optional.
Optional. The name of the module goes here, inside a h3. Inside of the h3 tag, you can make the title a link, if you want.
The name of the module goes here, inside a h3.
Inside of the h3 tag, you can make the title a link, if you want.
</module-head>
</module-head>
<module-body>
<module-body>
Line 58: Line 60:
</module-body>
</module-body>
<module-foot>
<module-foot>
Optional.
Optional. Want one of those clever links below your module content on the bottom right? Put it in here. If you want a link to also appear on the left, give it the "module-foot-left" class.
Want one of those clever links below your module content on the bottom right? Put it in here.
If you want a link to also appear on the left, give it the "module-foot-left" class.
</module-foot>
</module-foot>
</module>
</module>
Line 66: Line 70:
<submodule>
<submodule>
<submodule-head>
<submodule-head>
Optional.
Optional. This is where the title for the submodule goes, if you want to differentiate it somehow. Styling for this varies from context to context... see /missions/ for an example. Recommended to put the title inside an <h3>.
This is where the title for the submodule goes, if you want to differentiate it somehow.
Styling for this isn't standardized yet... see /missions/ for an example.
Recommended to put the title inside an <h3>.
</submodule-head>
</submodule-head>
<submodule-body>
<submodule-body>
Also optional.
Also optional; if you don't want to bother with a head/body distinction, you can just put content straight inside the submodule.
If you don't want to bother with a head/body distinction, you can just put content straight inside the submodule.
</submodule-body>
</submodule-body>
</submodule>
</submodule>