Sweez playground

Design A: current design
Design objectives:
 * This is what we currently have (see Maps)
 * Sorted by biome and alphabet
 * Shows scenic and iconic image for each map

Design flaws:
 * Sorting maps by biome does not really serve any useful purpose
 * It lacks additional useful map information (map size, map image)
 * The design/look is simple (not bad, but not particularly attractive either)

Eastern Europe
Maps based out of regions in the Russian Federation, Republic of Ukraine, the Republic of Georgia, and the Republic of Estonia. Regions include dense taiga forests, brown plains, small villages, urban areas and industrial areas.

Southern Asia
Maps based out of regions in the Islamic Republic of Afghanistan and the Islamic Republic of Pakistan. Regions include massive farms, large rural communities, tall hills, and rivers.

Middle East
Maps based out of regions in the Republic of Iraq. Regions usually consist of urban areas, villages, and large deserts.

Training
Players can test out weapons and vehicles and practice shooting in this camp in Southern Asia.

Design B: compact table view
Design objectives:
 * Table view with sortable columns
 * Compact but informative
 * Include mini-map image - we can experiment with the perfect image sizes (make it smaller or bigger)
 * Further idea: a column for a list of all layers (see table below)
 * Further idea: preview could be a slideshow of screenshots (see right below) - no idea how that shows up on a mobile device and how it will affect loading time of the page

 File:Al Basrah Expansion 1.jpg File:Squad Al Basrah 2.jpg File:Squad Al Basrah 3.jpg File:Squad Al Basrah 5.jpg File:Al Basrah Expansion 5.jpg File:Squad Al Basrah 4.jpg File:Squad Al Basrah 6.jpg

Design flaws:
 * What do you not like about this design? Please let me know.

Design C: preview of all layers
Design objectives:
 * Preview ALL layers for all maps (inspiration/competition taken from http://squadmaps.com/)

Design flaws:
 * Not pretty and maybe not as practical as design B.
 * Do we really need to show ALL layers on the map overview page? What is its usefulness? (Yes, http://squadmaps.com/ looks pretty with it)
 * Icon delete.png The map overview page will get far too long (vertically) and the "overview" is lost. With more and more maps in the mid- and long-term future, this does not scale at all.

Design D: Tabs with different views
At the top of a wiki page, you can list different tabs, each providing different page content. This way, we could have multiple views of the map overview.

For example:
 * A simple overview like today, maybe even more compact
 * A detailed table of all layers, sortable columns, with useful information, similar to OWI's Map Layers for B17.
 * We can preview all map layers in a list or table for each map, similar to https://squadmaps.com/
 * We can automatically generate a rotation config file for server admins with all layers
 * And many more

Design A: AAS v1
Simple headline: just the game mode and layer version.

Design B: AAS v1 - Russian Ground Forces vs. Irregular Militia
Include factions in the headline because it is one of the most useful information and it will show up in the table of content of the wiki page (hence, useful for readers).

Design A: Vertical layout (current design)
Design objectives:
 * Our current design on some map pages (example: Belaya)

Design flaws:
 * Icon delete.png of horizontal space just wasted
 * Icon delete.pngr has to scroll all the time (even to just look at all information for one layer)
 * Icon delete.png



Flags
 * Militia Main
 * Radio Station
 * Nikola
 * Train Tunnel
 * Tire factory
 * Russia Main

Design B-1: 2 by 2 layout
Design objectives:
 * Use as little page space as possible (aka use it as efficiently as possible)
 * Create a layout that gives a good overview and lets reader quickly find what they are looking
 * Create a layout as esthetical pleasing as possible

Design flaws:
 * Not sure how this looks on mobile view
 * Still a lot of wasted space (horizontally)

Design B-2: 2 by 2 layout (swap)
Design objectives:
 * Trying to put the tables above the map image to see if this feels any better

Design flaws:
 * Is it better than B-1? - Depending on the tables, it flows even worse (in this example, with uneven tables, it looks terrible)

Design C-1: Horizontal layout
Design objectives:
 * Use as little vertical page space as possible

Design flaws:
 * Probably far worse on mobile view (unless it breaks lines nicely - we have to try it out)
 * Doesn't feel/flow nicely.

Design C-2: Horizontal layout (remix 1)
Design objectives:
 * Rearranage the information differently (because design C-1 doesn't feel/flow nicely)

Design flaws:
 * Is it any better than the other C designs?

Design C-3: Horizontal layout (remix 2)
Design objectives:
 * Small adjustment with the flag list

Design flaws:
 * Is it any better than the other C designs?

Design D: Sortable table view
Design objectives:
 * List all layers of a map in a sortable table
 * Very compact and good overview

Design flaws:
 * Icon delete.png is not enough space, even on a modern screen, to show all information without ugly line breaks
 * Icon delete.png looks terrible; lots of empty space, very bad overview and structure
 * Icon delete.png complex table, hardly possible to create and maintain by hand
 * Conclusion: This design is a total failure

Design F-1: Use of infobox style
Design objectives:
 * Use design style from current infoboxes
 * Create shorten version of esssential layer information (without vehicle assets)

Design flaws:
 * Somehow, the factions and tickets look confusing - the information is not clear, too cramped



Design F-2: Put factions into headline and data below image
Design objectives:
 * Try different spacing

Design flaws:
 * A bit better but still not perfect
 * Flags still missing. Damn it, where should I put them?



Design F-3: All into one headline but multiple lines
Design objectives:
 * Make it more compact

Design flaws:



Design F-4: Two headlines
Design objectives:
 * Make it look better

Design flaws:
 * But it doesn't look better



Design F-4: Headlines above and below
Design objectives:
 * Make it look better

Design flaws:

