Battlestar Wiki:Think Tank/CSS Layout

From Battlestar Wiki, the free, open content Battlestar Galactica encyclopedia and episode guide

This is an archive successful proposal that was vetted through the Think Tank, a place where ideas of all kinds are proposed and worked upon by the community prior to implementation. Please do not modify this proposal.

This is the overview. Basically, a summary of what the idea is about. You can get into the details later on.

Contents 1 CSS Layout 1.1 Why? 1.2 What would need to happen? 1.3 Questions

CSS Layout

Why?

The design has been done for a while. Not a lot of people commented it on BW:MAIN so I am moving it here. You would have to browse the few pages ont he Hanger Bay to get an idea of what certain elements would look like. Suggestions can be made on the "Colors" used and "style" used. There are limitations, but you have to remember that one thing changes, sometimes more than one things has to change to make sure it's all the same.

Images have been done by User:Mercifull.

The two examples are these:

• BSG Colors & BSG Style - http://www.battlestarwiki.org/hangarbay/index.php/Main_Page
• Wikipedia Colors & BSG Style - http://www.battlestarwiki.org/hangarbay/index.php?title=Main_Page&useskin=monobook

Speed tests are posted on BW:MAIN.

What would need to happen?

BW:CSS would be created first with "fake designs" for CSS reference. This page would look funny until the CSS was active, but then would look like what it's supposed to when it's created.

Since most of the templates and places are hard coded, the only bad thing is we could add the classes first to the pages with the hard coded values. Then when the CSS goes online in the background we can remove the hard coded values, but then again if you are not on the CSS of either of these, you will start to see some weird changes. It's kinda of a... once you start you gotta finish so nothing is really left out. There really isn't much to worry about expect int he form the main page and the custom made templates we made, which all have parent templates anyway. {{message box}} is inside {{project}} so the only change needed to be made is {{message box}} changes all the {{project}} tags automatically. In any case, there be some major editing for a few hours. Lot of tagging.

Questions

1. What is the benefit of this proposal to the wiki? Keeps the Wiki in a uniform so things look the same throughout all the same pages.
2. What is involved in implementing this idea? Joe has to upload the "files" to the server. Once activated the templates and any staic items need to be changed, but that won't be done until the BW:CSS page is created.
3. Who is going to do it? everyone uses CSS, but this is for mostly backend design.
4. Why should we do it at all? Because there is no standerization on the "use" of colors and having a "shortcut" for styling, keeps everything in-sync
5. How will we use the idea? There will be a BW:CSS page explaining the different CSS classes that can be used with examples.. This can be done even without having this "Style" being the default. All I need is for it to be installed so I can set my "style" to this and then after it's done.. it can be shared.
6. Should the proposal pass, when will work start on this idea? Right away...
7. Where will this idea be implemented? The Whole Wiki

See also

• The "Hangar Bay" for a preview...

The above is an archive of a proposal that was vetted through the Think Tank. Please do not modify or edit this archived proposal.