TUFLOW Wiki Format Guide: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
Chris Huxley (talk | contribs) |
Chris Huxley (talk | contribs) No edit summary |
||
| Line 30: | Line 30: | ||
:''Note: Running a multiple domain model without a valid multiple domain licence (i.e. in Tutorial Mode) can only be achieved using TUFLOW Build 2016-03-AD or newer.''<br> |
:''Note: Running a multiple domain model without a valid multiple domain licence (i.e. in Tutorial Mode) can only be achieved using TUFLOW Build 2016-03-AD or newer.''<br> |
||
:''Tip 1: Bla bla bla.'' <br> |
:''Tip 1: Bla bla bla.'' <br> |
||
== Language == |
|||
Use succinct language. |
|||
Revision as of 10:26, 14 November 2016
Bullet Point Lists
View this section in "preview" mode to see the appropriate Wiki syntax.
- Item A
- Item B
- etc
Numbered lists are indented
- Item A
- Item B
- etc
Manual indent syntax
- ":" example...
TUFLOW File References
- TUFLOW is always uppercase (i.e. TUFLOW, not tuflow)
- TUFLOW GIS input and simulation file names should be bold: model\gis\2d_code_M01_001.mif and M01_5m_002.tcf
- Define acronyms before using them in each page: TUFLOW Geometry Control File (TGC), TUFLOW Boundary Control File (TBC).
- Note: This also applies to section headings.
- Control file acronyms are upper case: TCF, TGC, TBC
- Use colour formats for syntax text:
- ! Comment bla bla
- Command == <something>
User Advice (Comments)
Advice is written in italics.
- Note: Running a multiple domain model without a valid multiple domain licence (i.e. in Tutorial Mode) can only be achieved using TUFLOW Build 2016-03-AD or newer.
- Tip 1: Bla bla bla.
Language
Use succinct language.