Difference between revisions of "Swag and Sorcery Wiki"
m (Automated Import) |
|||
Line 1: | Line 1: | ||
+ | <!-- TO EDIT MAIN PAGE CONTENT, see "Templates used on this page" below and edit: |
||
− | <!-- This is a responsive front page design that adapts to the available width |
||
+ | * {{SITENAME}}/Top section |
||
− | of the browser by showing content in 1, 2, or 3 columns. |
||
+ | * {{SITENAME}}/Flex section |
||
+ | * {{SITENAME}}/Bottom section |
||
− | This is |
+ | This is a basic responsive front page design that adapts to the available width of the browser by |
+ | rearranging the sections themselves as well as content within each section. When narrow, the three sections |
||
− | When the window is narrow, as on low-res displays, the content is displayed in a |
||
− | single column |
+ | line up vertically in a single column. When wide enough, the middle (flex) section is pulled out to become a |
⚫ | |||
+ | Much of the layout and appearance is determined through styles defined in these pages: |
||
− | When the window is medium, as on medium-res displays, there are two columns. |
||
+ | * MediaWiki:Hydradark.css (for the desktop view) |
||
− | Section 1 and 2 are on top with 1 on the left and 2 on the right. |
||
+ | * MediaWiki:Mobile.css (for the mobile view) |
||
− | Sections 3 and 4 are on the bottom with 4 at the left and 3 at the right. |
||
− | |||
− | When the window is wide, as on high-res displays, there are three columns. |
||
− | Sections 1 and 4 take up the left column, with section 1 on top. |
||
− | Section 2 takes up the middle column. |
||
⚫ | |||
− | |||
− | Or, visually... |
||
− | Narrow Medium Wide |
||
− | |1| |1| |2| |1| | | | | |
||
− | |2| |4| |3| | | |2| |3| |
||
− | |3| |4| | | | | |
||
− | |4| |
||
--> |
--> |
||
− | <div id="mf-home" class=" |
+ | <div id="mf-home" class="fpcontent"> |
− | <div |
+ | <div id="fptopsection"><!-- BEGIN TOP SECTION --> |
⚫ | |||
− | |||
⚫ | |||
⚫ | |||
⚫ | |||
− | |||
⚫ | |||
⚫ | |||
⚫ | |||
− | |||
− | <div |
+ | <div id="fpbottomsection"><!-- BEGIN BOTTOM SECTION --> |
⚫ | |||
⚫ | |||
⚫ | |||
− | |||
⚫ | |||
− | |||
⚫ | |||
− | |||
− | <div class="fpsection3"><!-- BEGIN SECTION 3 --> |
||
− | |||
⚫ | |||
− | |||
⚫ | |||
− | </div><!--END LAYOUT WRAPPER FOR SECTIONS 2 and 3 --> |
||
− | |||
− | <div class="fpsection4"><!-- BEGIN SECTION 4 --> |
||
− | |||
− | {{:{{SITENAME}}/Section 4}} |
||
− | |||
− | </div><!--END SECTION 4--> |
||
</div> |
</div> |
||
⚫ | |||
− | <div class="nomobile" style="text-align: right;"><small>Main page sections: [[/ |
+ | <div class="nomobile" style="text-align: right; margin-right: 10px;"><small>Main page sections: [[{{SITENAME}}/Top section|Top]] · [[{{SITENAME}}/Flex section|Flex]] · [[{{SITENAME}}/Bottom section|Bottom]]. Changes for the main page can be proposed [[Talk:{{SITENAME}}|here]]. </small></div> |
− | |||
− | |||
⚫ | |||
− | |||
[[Category:{{SITENAME}}| ]] |
[[Category:{{SITENAME}}| ]] |
Revision as of 12:08, 13 September 2018
Welcome to Swag and Sorcery Wiki
the Official Swag and Sorcery guide for Quests, Monsters, Resources and more written and maintained by the players.
Please feel free to contribute by creating new articles or expanding existing ones.
About Swag and Sorcery
Build your own fantasy village, create and equip your characters and send them to collect swag in Swag and Sorcery - a new streamlined RPG from the creators of Punch Club and Graveyard Keeper, published by tinyBuild. [Read more...]
Guides
- Create a How to play guide for Swag and Sorcery
- Create a System requirements Page
- Create a Release date Page
Videos
Images
Twitter
Wiki
To write a new article, just enter the article title in the box below or in the search box at the top of the page.
- Adding content
- If you are unsure of what to do or how to create a page, search for a few articles on the same topic and see what they look like. You can always view the source code in a wiki and learn from what others have done.
- An edit doesn't have to be massive; if you feel you don't want to create whole articles, then just fixing spelling errors and broken links is enough.