FANDOM


m
m (Tiberium's been cancelled a looooong time ago.)
Line 86: Line 86:
 
|Gen
 
|Gen
 
|Generals and expansions
 
|Generals and expansions
|-
 
|Tib
 
|Tiberium, concept art and the like for the unreleased game
 
 
|}
 
|}
   

Revision as of 11:08, May 26, 2009

Forums: Index > General Discussion > Image reorganization


Greetings,

Quality and organization are the foundations of any wiki and, to put it bluntly, the CnC Wiki is sorely lacking in both departments. My impression that the wiki's contributors have been hampered not by lack of enthusiasm, for which there is abundant supply, but rather by a lack of direction. Without such direction contributions have been inconsistent in both the aforementioned quality and organization.

The state of image management unfortunately reflects this lamentable state. Currently auditing the image repository is not possible without significant labour. Lack of comprehensive categorization and inadequate descriptive file naming makes it impossible to check for duplicates, among other things.

I propose the following policy and plan to rectify this. It will require preserverance to implement fully but it will give those who have an interest in seeing the wiki's foundations strengthened for future growth something to work with.

Step 1: Categorization

Every image must be categorized. The image category structure will be something like as follow (incomplete example):

  • Images
    • Allied images
      • Allied unit images
        • Allied Rifleman images
        • Allied Medium Tank images
        • etc.
      • Allied structure images
        • Allied Construction Yard images
        • etc.
      • Allied organization images
        • etc.
      • Allied character images
        • etc.
    • Chinese images
      • etc.
    • Empire of the Rising Sun images
      • etc.
    • GDI images
      • etc.
    • GLA images
      • etc.
    • Nod images
      • etc.
    • Soviet images
      • etc.
    • USA images
      • etc.
    • User images

I'm not sure if you want to group the factions by game or what have you, but this is basic idea. Not the capitalization. Categorization of existing images can begin immediately as it is the easiest thing to do.

Step 2: File Naming

Some files have incredibly undescriptive names, like being just a string of numbers which doesn't tell us what the image subject is. The basic filename should look like:

<object name>_

Invalid language.

You need to specify a language like this: <source lang="html4strict">...</source>

Supported languages for syntax highlighting:

4cs, 6502acme, 6502kickass, 6502tasm, 68000devpac, abap, actionscript, actionscript3, ada, algol68, apache, applescript, apt_sources, arm, asm, asp, asymptote, autoconf, autohotkey, autoit, avisynth, awk, bascomavr, bash, basic4gl, bf, bibtex, blitzbasic, bnf, boo, c, c_loadrunner, c_mac, caddcl, cadlisp, cfdg, cfm, chaiscript, cil, clojure, cmake, cobol, coffeescript, cpp, cpp-qt, csharp, css, cuesheet, d, dcl, dcpu16, dcs, delphi, diff, div, dos, dot, e, ecmascript, eiffel, email, epc, erlang, euphoria, f1, falcon, fo, fortran, freebasic, freeswitch, fsharp, gambas, gdb, genero, genie, gettext, glsl, gml, gnuplot, go, groovy, gwbasic, haskell, haxe, hicest, hq9plus, html4strict, html5, icon, idl, ini, inno, intercal, io, j, java, java5, javascript, jquery, kixtart, klonec, klonecpp, latex, lb, ldif, lisp, llvm, locobasic, logtalk, lolcode, lotusformulas, lotusscript, lscript, lsl2, lua, m68k, magiksf, make, mapbasic, matlab, mirc, mmix, modula2, modula3, mpasm, mxml, mysql, nagios, netrexx, newlisp, nsis, oberon2, objc, objeck, ocaml, ocaml-brief, octave, oobas, oorexx, oracle11, oracle8, oxygene, oz, parasail, parigp, pascal, pcre, per, perl, perl6, pf, php, php-brief, pic16, pike, pixelbender, pli, plsql, postgresql, povray, powerbuilder, powershell, proftpd, progress, prolog, properties, providex, purebasic, pycon, pys60, python, q, qbasic, rails, rebol, reg, rexx, robots, rpmspec, rsplus, ruby, sas, scala, scheme, scilab, sdlbasic, smalltalk, smarty, spark, sparql, sql, stonescript, systemverilog, tcl, teraterm, text, thinbasic, tsql, typoscript, unicon, upc, urbi, uscript, vala, vb, vbnet, vedit, verilog, vhdl, vim, visualfoxpro, visualprolog, whitespace, whois, winbatch, xbasic, xml, xorg_conf, xpp, yaml, z80, zxbasic


_<type><numericid>.<fileextension></code>

For example: <code>MediumTank_RA1_Head1.jpg</code>

This ensures each image has a unique name, makes auditing ludicrously simple, and allows us to group different iterations of the same unit in the same category.  For example, for the Nod Stealth Tank we could have:

<code>StealthTank_CC1_Game1.jpg</code> and <code>StealthTank_CC2_Game1.jpg</code> and <code>StealthTank_CC3_Game1.jpg</code> and <code>StealthTank_Ren1_Game1.jpg</code> all in the same category for easy reference.

The ''source'' ID would be something like the following:

{| border="1"
|-
!ID
!Games
|-
|CC1
|First game and expansions
|-
|CC2
|Tiberian Sun and expansions
|-
|CC3
|Tiberium Wars and expansions
|-
|RA1
|Red Alert and expansions
|-
|RA2
|Red Alert 2 and expansions
|-
|RA3
|Red Alert 3 and expansions
|-
|Ren
|Renegade
|-
|Gen
|Generals and expansions
|}

The ''type'' string would be something like the following:

{| border="1"
|-
!ID
!Purpose
|-
|Head
|Sidebar portrait
|-
|Game
|Images of the ingame unit sprite or model
|-
|Cncpt
|Concept art
|-
|Art
|Other art
|}

'''Step 3: Sourcing'''

As you go through the images categorizing, and renaming the worst offenders, try to figure out where it came from and add that to the image description. This would be a good time to look out for unofficial art ("fanart") which should be purged along with duplicates.

'''Step 4: Profit?'''
This should get things rolling. Suggestions and comments are of course welcome. - [[User:Meco|Meco]] ([[User talk:Meco|talk]]) 03:54, 21 May 2009 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.