From EncyclopAtys
FairyFighter (talk | contribs) m (→Design) |
FairyFighter (talk | contribs) m (→Mainpage layout) |
||
Line 24: | Line 24: | ||
===Mainpage layout=== | ===Mainpage layout=== | ||
*Main page | *Main page | ||
− | ** | + | **Nations page |
***Trykers | ***Trykers | ||
***Zorai | ***Zorai | ||
***Matis | ***Matis | ||
***Fyros | ***Fyros | ||
− | ** | + | **Geography |
+ | ***Lakes | ||
+ | ***Desert | ||
+ | ***Woods | ||
+ | ***Jungle | ||
+ | ***Prime roots | ||
+ | **Factions | ||
+ | |||
===CSS=== | ===CSS=== | ||
*CSS: | *CSS: |
Revision as of 09:30, 30 January 2021
Dear Wiki enthusiasts, Recently I joined your ranks. I have spoken with few of you to introduce myself and at the same time I had look at few pages. It was absolutely obvious that there is plenty issues that should be addressed. There for I would like to invite you all to create a document that we could use as handover to [RT]. Content of document should be as short as possible yet clearly stating our goals. To accommodate that I would suggest to define major parts, maybe even supported by examples. Before we will be able to create such document we should first internally agree on our vision of the wiki. There for I would suggest creating a wiki page were we will gradually consolidate our efforts. If you see better option please do not hesitate to suggest it.
Target: Creating wiki that is safe to be updated and easy to customize to our needs.
Wiki Concepts
- Use templates, for everything.
- Consistency
- Separate style from content
- I18n
Wiki configuration
- Needed extensions
Wiki backoffice
- Each template should contain its documentation.
- Define reusable templates.
- Flexible layout, faction dependent.
- Wiki contributors
Design
Mainpage layout
- Main page
- Nations page
- Trykers
- Zorai
- Matis
- Fyros
- Geography
- Lakes
- Desert
- Woods
- Jungle
- Prime roots
- Factions
- Nations page
CSS
- CSS:
- Decision: what do we put in CSS what do we control in wiki?
- Follow [RT] design
CSS centric
- Fluid layot: PC/Smartphone/Tablet
Procedural steps
- Design
- Implementation
- Tests/Verification
- Acceptance
- GoLife