Contributing to the Discretize website has never been easier before! All you need to get started is a Github account, a little bit of brain power, and the ability to read.
Get started:
Create a free Github account at github.com. The sign-up is free, does not require any personal information except for an e-mail address and should only take 2 minutes.
Sign into our CMS (=content management system) at discretize.eu/cms and accept the creation of a fork.
Navigate to any site you want to edit. It is recommended to disable "Sync scrolling" on the very right side of the screen for an optimal experience. Make your changes, and click "Publish" to save your changes. Please be aware that clicking "Publish" does not actually publish your changes but saves them. After a review your changes will appear first on staging.discretize.eu , and later on the main website.
The CMS requires access to your full account because it acts on your behalf (oauth). This is a static page, there are no server components and no outgoing requests are made that could possibly steal your oauth token. Your login never leaves your PC. More information. As an alternative you can copy-paste the guide files into the editor.
Important information:
Adding new sites from the CMS is not possible. Please ask on the discord server for help. An admin will create the page for you and it will appear in the cms.
In case there are elements, that are not rendering as intended on the staging site, please add an enter before and after the component. That should fix all rendering issues given the component is correctly set up.
Pictures are not rendering in the cms!
Documentation CMS:
Equipment
To create the gear display it is recommended to study an existing example first. Copy-paste it, and replace the gear sections as follows.
Go to the Gear Optimizer . Insert the build you want to get the equipment for (including the correct Agony Resistance), hit calculate and click the button at the bottom of the screen to copy the equipment.
Markdown Components
Inline components
Inline components can be used as standalone elements or within block components like paragraphs or tables.
Most of our Gw2 components are created with the help of the official game API. In general it should not be necessary to research IDs, as we resolve them automatically with the help of other identifiers like name or affix.
Our current mapping can be queried using the ID Helper tool. As we keep its size as small as possible, some special items might not be present - in those cases you can still specify a fixed ID. You can find a specific ID by searching for the desired Item/Skill/whatever in the wiki and then clicking on "API".
Items
Items can be created by specifying either a name or a type and affix combination.
If there are multiple results for the query, the one with the lowest id will be taken.
Special characters like ', spaces and capital letters are normalized for the mapping.
Skills and traits are resolved using a name and a profession (optional).
The profession theme color is automatically applied to the link, even if you don't specify one.
Again - special characters, case sensitivity and spaces don't matter. <Skill name="TotHe LiMiT!"/> will be resolved as .
Parameter
Type
Description
Example
Output
name
string
Skill/trait name
<Trait name="Pyromancers Training"/>
profession
string
Skill/trait profession
<Skill name="Stab" profession="Mesmer"/>
size
one of tiny, small, medium, large, big
Icon size
<Trait name="King of Fires" size="large"/>
disableText
boolean
Disables the text
<Skill name="Epidemic" disableText/>
id
number
Skill/trait id
<Skill id="13113"/>
Other Gw2 components
Some other game-related components can be created with a simple name identifier.
Check the reference column for the proper spelling.
Note that you can use the size and disableText parameters with those as well.
Shows a composition with tooltip and link to the meta page. Predefined compositions can be selected starting with an underscore. The size parameter is optional.
Available pregenerated: _Rainbow, _Rainbearbow, _RGB
- Change to if you dont need the additional CC - Play !
Skill usage
Block components
Block elements always take up the entire width of their parent element.
Paragraphs
Plain text is automatically wrapped in a paragraph element.
Use four spaces to force a new line.
Inserting a blank line between passages results in two distinct paragraphs.
Plain text is automatically wrapped in a paragraph element.
Use four spaces to force a new line.
Inserting a blank line between passages results in two distinct paragraphs.
- Item one
- Item two
- Nested item one
- Nested item two
- Item three with a new line using four spaces
- Item four
Note that using - instead of the \* character works as well.
Item one
Item two
Nested item one
Nested item two
Item three with a new line using four spaces
Item four
Ordered list
1. Item one
2. Item two
1. Nested ordered items need to be indexed with **three** spaces
2. Nested item two
3. Item three with a new line
using four spaces
4. Item four
Item one
Item two
Nested ordered items need to be indexed with three spaces
If you want to create a head-less table, simply leave the column header cells blank.
Column header 1
Column header 2
Cell 1
Cell 2 with a new line
Cell 3
Cell 4
Dividers
---
<Divider text="Divider text"/>
Divider text
Blockquote
> Lorem ipsum is placeholder text commonly used in the graphic, print, and publishing industries for previewing layouts and visual mockups.
Lorem ipsum is placeholder text commonly used in the graphic, print, and publishing industries for previewing layouts and visual mockups.
Grids
Our grid system is based on a 12-column grid layout. You can use <Grid> for the container and <GridItem> for the item components.
There are five grid breakpoints:
xs, extra-small: 0px or larger
sm, small: 600px or larger
md, medium: 960px or larger
lg, large: 1280px or larger
xl, extra-large: 1920px or larger
You can define multiple widths per column, causing the layout to change at the defined breakpoint.
If not specified otherwise, a <GridItem> will have the attributes xs="12" and sm="6" by default, causing the item to be 100% wide at mobile resolutions and 50% wide above.
<Grid>
<GridItem>
Left content
</GridItem>
<GridItem>
Right content
</GridItem>
<GridItem>
This item will be placed in a new row
</GridItem>
</Grid>
Image paths need to be absolute to the actual markdown file within our GitHub repository.
Sadly this does not work in the editor.
Image images/hero_sunqua2.jpg not found
Although the above syntax is the preferred variant, you can use the standard Markdown image syntax to preview images in editor context or to embed external images. Keep in mind that images are not minified this way!
<Video title="Example video title" youtube="xcJtL7QggTI" timestamp={12} />
Example video title
Build guide components
Writing build summaries has never been easier thanks to our automatic ID resolving.
Note that you suffix Id behind parameters if you want to use a fixed ID, like glovesRuneId="76491".