"Establishing a standard format"

Although... you're only using the data in one place... so I don't really see a point in templating it.

I thought we planned on making individual pages for each title type, and and also having it on the main page? Though you have a point.

Main page?

Titles page.

Traaaaansclusion?

Ahhhh, okay.

My goals are three-fold:

1. Split Titles page into many smaller, more specific sub-pages.
2. Update all of those pages to make them more consistent and visually appealing.
3. Transclude updates to those sections on Titles.

So far, there hasn't been a significant-enough change to update anything. It's a work in-progress, but it would be great if I get some help with it.

How may I assist?

Explain to me what needs to be done to do something similar to what you have done for Enchants.

I wasn't the one who did enchants, but basically, using this title for example:
|-
| the Master of [[Combat Mastery|Combat]]
| <span style="color:blue">Max HP +20<br />Max Stamina +20<br />Strength +10</span><br /><span style="color:red">Intelligence -10<br />Luck -20</span>
that is what is currently in the table format. So, what we'd do is we decide on a standard name for these parameters, like Name, HP, SP, MP, Str, etc; and paste it on a page along the name of Template:DataTitlethe Master of Combat or something. Then we make a Style template, which would include first of all a template for the header (or just include the header in the page) and then a list template like this, which organizes the paramets from the data template, and just on the titles page type something along the lines of "{{Datawhatever|Stylewhatever}}." My main concern would be how to make it so positive numbers appear on top and negative numbers appear on bottom (if we go with the current format and not redesign the template). The advantage of a data/style approach is that if we edit the template, we only have to edit that template and all the entries would automatically follow the new design, rather than manually editing each one every single time. But as Kevin said, each title will probably only ever be used on one page, minus maybe skill titles, so I don't know if it would be that useful.

I don't believe that Kevin was referring to that in that way.

“	Although... you're only using the data in one place... so I don't really see a point in templating it.	„

From this quote, I garnered that he misunderstood the plans for the Titles.

Also, enchants are used just as much on the wiki. There aren't many pages outside of the Enchant pages and Skill pages that have enchants listed, yet look at the templates it has.

You're forgetting modifier pages.

Those are pretty much enchant-only pages, Kevin.

I sense some sort of misunderstanding.

What kevin is trying to get at is

Rank 6 Skill Page Modifier Page

Master Title Skill Page

That there would be at least two pages for all enchants and three for some, but only one page for most titles and two for some.

There will be Status modifier pages for Titles.

And there will be plenty other Title-based pages.

When I said I would make Category:Titles the Category:Enchants of Titles, did you think I was joking?

Sortability is a must. Not to mention the lack of visual appeal for the current tables.

Ah, then sounds good. If you create a base table design I can try and make it a template.

Looking at the table format, the problem with the table for Titles is that it is too wide. I think a new table format should be less wide.

If you're going to make each stat it's own sortable column, I don't see how you can.

Err... that's not how Enchants were done and that's not how I would like Titles done.

Wasn't the whole point of this to make title stats more easily sortable?

Yes, but there won't be sortability for each stat...

I don't see what's wrong with the current way master titles are formatted in skill pages? It's not like you'll ever need to sort them or anything.

Ctrl+F solves EVERYTHING 8D...