A Title for this Guide [please capitalize]

1 Affiliation One

2 Affiliation Two

Abstract

1 First-level heading [headings are not capitalized]

[| Paragraph] This is a standard paragraph.

The standard font for this publication is “Source Sans Pro”. All fonts are embedded in the file. Hyperlinks like www.gesis.org are automatically formatted in the “Hyperlink” format.

Please use American English. Please use APA style for your references; do not use footnotes or endnotes. Please use Oxford commas in conjunctions. Please use en dashes – with spacing – for parentheses. For emphasizing text please use bold [“| Bold” font style format]. Please use typographical quotation marks, apostrophes, or high commas (“quote with a ‘quote’ within”) everywhere (except in code sections). Word generates them automatically when typing. Please note the difference between typographical and non-typographical quotation marks: "non-typographical quote with a 'non-typographical quote' within". The latter can happen when text is pasted into the manuscript.

1.1 Second-level heading

Word will automatically keep track of the numbering of headings and subheadings.

Please do not use more than two levels of headings.

Inline heading to structure text. To add a third-level structure to your manuscript, use the “| Heading Inline” style.

Sometimes we need paragraphs with extra space between paragraphs (e.g., to create logical text breaks or to separate boxes/figures/tables/quotes from text paragraphs). To create this extra space, insert a “| Divider” paragraph. The following divider has text for demonstration purposes, otherwise it must be without text:

2 Formatting Expert Insights

2.1 Questions and answers

2.2 Core quotes

3 Special features

3.1 Lists and numbered lists

This is a list, using the “| List” style:

• Apples

• Oranges

• Bananas

Numbered list, using the „| List Numbered“ style:

1. Apples

2. Oranges

3. Bananas

This is a list of checkboxes, using the “| List Checkboxes” style:

• Apples

• Oranges

• Bananas

3.2 Hyperlinks

Hyperlinks like www.gesis.org are automatically formatted in the “Hyperlink” format.

3.3 Citation

Please use APA style. This is a citation of multiple references using the Zotero citation manager. Example citations (Hofman et al., 2021; Lindgren, 1945; Merton, 1948; Soundarajan et al., 2016; White, 1992). It is also possible to just cite a year when the author name Watts (2003) is used in the text. A page can be cited (DiTomaso, 1982, p. 12 ) –make sure the standard language in Word is English so “page” is abbreviated with a “p” –, also without the name of the author Gershenson and Heylighen (2003, p. 12 ). It is possible to use a prefix (cf. Barabási, 2012), a suffix (Bourdieu, 1990, and references therein), or both (cf. Wasserman & Faust, 1994, and similar stuff). More citations are added below to test jumping.

3.4 Endnotes

To insert an endnote, (1) use the “Insert endnote” button in the “References” menu and (2) add “[…]” brackets around it. There are endnotes here [¹] and here [²].

The endnotes will be in the “Endnotes” section before the reference list.

4.1 Mathematics

The Pythagorean theorem \(a^{2} + b^{2} = c^{2}\) is a fundamental relation in Euclidean geometry between the three sides of a right triangle. Sometimes, one only mentions a single mathematical variable \(a\) in the text. And sometimes a mathematical equation takes its own row:

\[P(k) \sim k^{- \alpha}\]

The paragraph continues here.

4.2 Code

There are two ways to handle code. As a display block like

if true:
    print("Hello")

and as an inline block [| Code Inline] like pip install numpy. This can also be used to highlight package names like numpy.

Note that typographical quotation marks are not possible – and should not be possible – in code blocks.

Snippets of code must use one of the following styles:

• | Code

• | Code Inline

• | Code Python

• | Code R

The styles that include the name of a programming language will format the code with colors (like in an IDE). The colors aren’t visible in Word, only in HTML when generated from this manuscript. This is Python code:

result, candidates = [], [self]
while candidates:
    node = candidates.pop()
    distance = node._get_dist(obj)
    if distance <= max_dist and distance >= min_dist:
        result.extend(node._values)
    candidates.extend(node._get_child_candidates(distance, min_dist, max_dist))
return result

This is R code:

set.seed(42) ## for sake of reproducibility
n <- 6
dat <- data.frame(id=1:n, 
                  date=seq.Date(as.Date("2020-12-26"), as.Date("2020-12-31"), "day"),
                  group=rep(LETTERS[1:2], n/2),
                  age=sample(18:30, n, replace=TRUE),
                  type=factor(paste("type", 1:n)),
                  x=rnorm(n))

We can also create code output. For this, use the “| Code Output” style:

This is code input

This is code output as a block
With two rows

In addition, there is a “| Code Output Inline” format for inline code output, for example, to write that a command creates a MemoryOverflow! error.

4.3 Tables

Small and simple tables. Table 1 is a small (that fits in a single A4 portrait page) and simple (only column labels) table. To build it, (1) create a table in Word, (2) make sure the “Table Style Options”/“Tabellenformatoptionen” have only “Header Row”/“Kopfzeile” enabled, (3) apply the “| Table” or “| Table Small Font” or “| Table Narrow” style, (4) apply the “Guides Table Standard” style in the table layout menu, (5) manually adjust column width if you wish, and (6) change the font style in the first row to “Source Sans Pro”.

References to tables are capitalized and in semibold. For example, this is a reference to Table 1.

Contingency tables. Table 2 is a contingency table. To build it, (1) create a table in Word, (2) make sure the “Table Style Options”/“Tabellenformatoptionen” have only “Header Row”/“Kopfzeile” and “First column”/“Erste Spalte” enabled, (3) apply the “| Table” or “| Table Small Font” or “| Table Narrow” style, (4) apply the “Guides Table Contingency” style in the table layout menu, (5) manually adjust column width if you wish, (6) make the top-left cell background is white, and (7) make the font in the first column dark blue (top row in the font color from the palette).

Big, sortable, and searchable tables. Table 3 is so big that it could be placed on a landscape page, and it has a very long table caption. The example uses the “| Table Narrow” style. To make such tables sortable and searchable in HTML, apply the “Guides Table Sortable” style in the table layout menu.

Simple tables and contingency tables are not sortable and searchable in HTML by default.

4.4 Figures, graphics, images

Insert figures. The preferred formats for inserted figures are SVG, PNG, and JPEG. All figures must have a caption. Captions must have the style “Figure Caption”. Figure 1 is an example of an SVG figure and Figure 2 is an example for a PNG figure.

For setting the width of a figure in HTML, there are three styles. Figures styled with “| Figure 100” will be as wide as the HTML page, figures styled with “| Figure 50” will be half as wide as the HTML page, and figures styled with “| Figure 33” will be a third as wide as the HTML page. The following is a “| Figure 100”:

The following is a “| Figure 50”:

And we repeat the same figure as a “| Figure 33”:

Here in Word, adjust figure size by hand. As a rule of thumb, fonts in figures should be as large as in the text.

Word art. You can craft figures using Word art. The editors will help with styling.

4.5 Boxes

To highlight summaries, lessons learned, or something along those lines, use boxes. To create a box, (1) choose one of the colored boxes below and copy it where you want it, (2) the paragraph containing the box must be a standard “| Paragraph”, and (3) make sure the text inside the box (not the box itself) is formatted using one of the “| Box Blue/ Pink/ Bubble/ Turquoise” styles. The box is as wide as the page and automatically adjusts its height.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.

5 File metadata

In order for the pipeline to work as intended, metadata must be set for the DOCX file. Navigate to File > Info > Properties > Advanced properties (you must click on the pull-down menu of properties to get to the advanced properties). In the window that opens, click on the right folder where you can set parameter values. Set the guide title as the value of the title parameter, and set the DOI (without the “http://doi.org/” part) as the value of the doi parameter. If the guide is an Expert Insights interview, change the value of the DocumentType parameter to “interview” (without quotation marks).

Acknowledgements [optional]

Notes [optional]

Version note [optional]

Declaration of AI [optional]

About the author / About the authors