Please STOP USING CUSTOM COLORS.
You should NEVER set custom color in the code of the page.
How will we do the day we update the design of the website ?
If you need I can add some classes to the css to allow you more customization but having color hardcoded in html code is a very bad idea.
By the way, please also use the wiki syntax for table and not create html table directly ;-)
If someone has difficulties to edit the wiki, feel free to pm me with questions and I will answer you precisely.
For one, the class is extremely easy to set. "Wikitable" is all that needs to be put and it automatically skins to the page.
For two, there's no difference between
|-
|
and <tr.><td.><./td><./tr>
To the browser it's exactly the same thing. If you'd really like to be bothered when I'm done, you can rewrite the whole thing in wiki syntax if you'd like. I haven't seen where it's particularly made it easier on anyone anyhow, it's there in case you have no idea what you're doing. As I said, there's no offense intended, but if you can't be bothered to do it yourself please don't tell me how to do it. Especially so considering I've already invested several hours in the first project for weapon tables (which was then scrapped) and now I've made it through half the catalog or more. I feel this is a much more eloquent solution, but I can't help but feel like if you can't look at a simple table and figure out what you need to replace then you shouldn't be messing with it anyways.
I appreciate the direction, but again understand I've already started work and completed much of it. At what point of a project do you figure templating out? Yes, that'd basically mean I'd have to start over to say the same thing again which is just being used similar BBCode to be translated to what I'm doing anyways. Let's not forget, I could've nearly done a whole category of weapons in the time I've taken to respond to this.
P.S., it doesn't matter what colorizing someone may do. Simply attaching class="Wikitable" forces it regardless of what's inside of it. For the record, though, that does look pretty atrocious after you look at it for a while. It'd be nice if you'd tweak the main CSS files towhere there wasn't quite such a significant difference between a link and text. Seems kind of odd having Oswald right there with Helvetica to begin with, I don't see the need for such a large increase.
P.P.S., Again, I'm not trying to be a dick. I've put a lot of hard work into what I'm doing and willingly so. If you want people to follow your guiding, take initiative and make some template files. It's ridiculous to either have to scheme behind you (AKA figure out how you accomplished what you have) or copy/paste everything over which, to me, is as tedious or more as editing a table. Either that, y'know, or pay me. Then I'll redo it every day if I need to. Sorry if I'm trying too hard to make my point, but the Wiki's in a state of constant updating and I think your time would be much better spent elsewhere especially if the only gripe you have is syntax. Also, it would be different if there were any kind of management. The Wiki requires folks that'll step up, go in the game, pull out the data, and put it up. I don't mind doing that, but I've done made a revision to this once and I've posted about doing it for several days.
Not just that, but:
No problem.
For the weapons I think a big table could help but I my opinion individual pages should still exist as there is the ingredients for crafting, ect.. on it. Do you agree ?
Been talking weapon table for over two weeks now. That would've been the place and point to specify.
Thanks for understanding.
Author
Topic: Page management (Read 16282 times)