AniDB talk:Page layout

Content

• 'g_section *_all' have been added to all pages. was this wanted? rename? g_content @ dev

No, it's only wanted for pages with no internal sections (which is quite a few). Stuff like the calendar quite correctly has a g_section div per logical section (top and bottom nav and each anime listed).

• should g_section be the only allowed element (first level childs) inside #layout-content (except h1)?

Pretty much. There can be multiples though, and it's not a hard rule (forms etc could usefully live outside and around sections).

• • general vertical margins. g_actionlist/etc. is subs of g_section?

Vertical margins are a function of layout and should not be presented in the markup at all.

• should g_navlist and g_numonpage be in one (parent) div?

Not just because.

• should g_jumplist be inside the table div?

What is a 'table div'? They should be in the same section where appropriate.

Text visibility

• v_high (red bold)
• v_med (bold)
• v_low (italics)
• v_pos (green)
• v_neg (red)

These tread on the toes of both <font> level decoration and <em> level meaning. Classes are about what something is, not how it should be presented. Marking pos/neg is a different issue from 'text', and the current solution is not ideal.

Text content

• c_title
• c_text
• c_number
• c_time
• c_state (creq, message, animegroup, etc.)
• c_stats (x/x/x/x, mylist/file stats, etc.)
• c_rating (x.xx (x), mixed)
• c_action (links, report/del/rate)
• c_icons (mylist state)
• c_list (links, resources)

The c_ prefix names were for collation purposes only - marked in table headers. There seems no reason for filling the namespace just because.

Text alignment

Default alignment. (vs. text content or in addition)

• a_center
• a_left
• a_right
• ...

or (pos)

• p_c (center)
• p_w (west)
• p_ne (northeast)
• ...

Alignment and text positioning are functions of layout, not markup. Using anything like this is just as stupid as doing <span class="bold">hi mum</span> etc.

Table types

Probably don't want this /to be renamed to t_* ?

• inner (file table inside ep table, ...)
• dummy (table in title td in ep table, ...)
• container (not inner, for layout only, f.ex. vote section @ anime page)

Don't want is right. All these kinds of tables just want eradicating.

Elements

name	type	description	note	example
g_navlist	li	subpages		latest files/anime/...
g_numonpage	li	number of rows wanted	sub of g_navlist
g_jumplist	table	ext/prev page, filter char		for all sortable lists
g_actionlist	- separated	list of different possible actions (links)		should be in most pages
g_definitionlist	table	vertical field name -> value list		div.anime_info div.data
g_infobox	non-existing	image, defintion list, description		all info pages (anime/group/ep/..)
g_newsbox/g_msgitem	non-existing	header(title-by-date-action) and body		news item, agcmt
g_navprev/g_navnext	?
g_menu	ul	page/sub menu		mylist, my messages, etc.
g_filterlist	ul	filtering		latest files

These need cleaning up.

File states

• g_fs_ok
• g_fs_invalid
• g_fs_deprecated
• g_fs_generic
• g_fs_lame

These don't need to be in the global namespace.

Messages

• g_infobox
• g_notebox
• g_warnbox
• g_errorbox
• g_successbox

Could use g_box m_info / g_msg v_high / ...? unless g_*box is possible

Error handling needs redoing, no point fiddling till then.

Other

• td/tr/li.pause
  • pause in lists, f.ex. between normal eps and special eps

This is a function of layout, not markup. No empty rows should exist for layout purposes.

• td.fill, width/height 100%

This is a function of layout, not markup.

• .g_even, .g_odd

With IE7, I think _even is now redundant.

• .g_description
• .g_info
• .g_howto

These three probably want better and clearer definition.

• .field, .value (in definition lists)

These seem redundant.

• .nowrap

This is a function of layout, not markup.

• tr.mod (mod message)

This isn't a global meaning.

• div.g_image

Is this actually needed?

• div.g_end (used to mark the end of content, used for clear: right, maybe not needed)
• .state (creq state)

This isn't a global meaning.

• li.here (inside g_navlist, currently selected)

This isn't a global meaning.