{"route":"/en-US-v0.13.1/tutorial/advanced-styling/","title":"Advanced Styling","description":"Typst's tutorial.","part":null,"outline":[{"id":"guidelines","name":"Guidelines","children":[]},{"id":"set-rules","name":"Set Rules","children":[]},{"id":"title-and-abstract","name":"Title And Abstract","children":[]},{"id":"columns-and-headings","name":"Columns And Headings","children":[]},{"id":"review","name":"Review","children":[]}],"body":{"kind":"html","content":"

Advanced Styling

\n

In the previous two chapters of this tutorial, you have learned how to write a\ndocument in Typst and how to change its formatting. The report you wrote\nthroughout the last two chapters got a straight A and your supervisor wants to\nbase a conference paper on it! The report will of course have to comply with the\nconference's style guide. Let's see how we can achieve that.

\n

Before we start, let's create a team, invite your supervisor and add them to the\nteam. You can do this by going back to the app dashboard with the back icon in\nthe top left corner of the editor. Then, choose the plus icon in the left\ntoolbar and create a team. Finally, click on the new team and go to its settings\nby clicking 'manage team' next to the team name. Now you can invite your\nsupervisor by email.

\n

\"The

\n

Next, move your project into the team: Open it, going to its settings by\nchoosing the gear icon in the left toolbar and selecting your new team from the\nowners dropdown. Don't forget to save your changes!

\n

Now, your supervisor can also edit the project and you can both see the changes\nin real time. You can join our Discord server\nto find other users and try teams with them!

\n

The conference guidelines

\n

The layout guidelines are available on the conference website. Let's take a look\nat them:

\n\n

We already know how to do many of these things, but for some of them, we'll need\nto learn some new tricks.

\n

Writing the right set rules

\n

Let's start by writing some set rules for the document.

\n
#set page(\n  paper: "us-letter",\n  header: align(right)[\n    A fluid dynamic model for\n    glacier flow\n  ],\n  numbering: "1",\n)\n#set par(justify: true)\n#set text(\n  font: "Libertinus Serif",\n  size: 11pt,\n)\n\n#lorem(600)\n
\"Preview\"
\n

You are already familiar with most of what is going on here. We set the text\nsize to 11pt and the font to Libertinus Serif. We also enable paragraph\njustification and set the page size to US letter.

\n

The header argument is new: With it, we can provide content to fill the top\nmargin of every page. In the header, we specify our paper's title as requested\nby the conference style guide. We use the align function to align the text to\nthe right.

\n

Last but not least is the numbering argument. Here, we can provide a\nnumbering pattern that defines how to number the pages. By\nsetting into to "1", Typst only displays the bare page number. Setting it to\n"(1/1)" would have displayed the current page and total number of pages\nsurrounded by parentheses. And we could even have provided a completely custom\nfunction here to format things to our liking.

\n

Creating a title and abstract

\n

Now, let's add a title and an abstract. We'll start with the title. We center\nalign it and increase its font weight by enclosing it in *stars*.

\n
#align(center, text(17pt)[\n  *A fluid dynamic model\n  for glacier flow*\n])\n
\"Preview\"
\n

This looks right. We used the text function to override the previous text\nset rule locally, increasing the size to 17pt for the function's argument. Let's\nalso add the author list: Since we are writing this paper together with our\nsupervisor, we'll add our own and their name.

\n
#grid(\n  columns: (1fr, 1fr),\n  align(center)[\n    Therese Tungsten \\\n    Artos Institute \\\n    #link("mailto:tung@artos.edu")\n  ],\n  align(center)[\n    Dr. John Doe \\\n    Artos Institute \\\n    #link("mailto:doe@artos.edu")\n  ]\n)\n
\"Preview\"
\n

The two author blocks are laid out next to each other. We use the grid\nfunction to create this layout. With a grid, we can control exactly how large\neach column is and which content goes into which cell. The columns argument\ntakes an array of relative lengths or fractions. In\nthis case, we passed it two equal fractional sizes, telling it to split the\navailable space into two equal columns. We then passed two content arguments to\nthe grid function. The first with our own details, and the second with our\nsupervisors'. We again use the align function to center the content within the\ncolumn. The grid takes an arbitrary number of content arguments specifying the\ncells. Rows are added automatically, but they can also be manually sized with\nthe rows argument.

\n

Now, let's add the abstract. Remember that the conference wants the abstract to\nbe set ragged and centered.

\n
...\n\n#align(center)[\n  #set par(justify: false)\n  *Abstract* \\\n  #lorem(80)\n]\n
\"Preview\"
\n

Well done! One notable thing is that we used a set rule within the content\nargument of align to turn off justification for the abstract. This does not\naffect the remainder of the document even though it was specified after the\nfirst set rule because content blocks scope styling. Anything set within a\ncontent block will only affect the content within that block.

\n

Another tweak could be to save the paper title in a variable, so that we do not\nhave to type it twice, for header and title. We can do that with the let\nkeyword:

\n
#let title = [\n  A fluid dynamic model\n  for glacier flow\n]\n\n...\n\n#set page(\n  header: align(\n    right + horizon,\n    title\n  ),\n  ...\n)\n\n#align(center, text(17pt)[\n  *#title*\n])\n\n...\n\n
\"Preview\"
\n

After we bound the content to the title variable, we can use it in functions\nand also within markup (prefixed by #, like functions). This way, if we decide\non another title, we can easily change it in one place.

\n

Adding columns and headings

\n

The paper above unfortunately looks like a wall of lead. To fix that, let's add\nsome headings and switch our paper to a two-column layout. Fortunately, that's\neasy to do: We just need to amend our page set rule with the columns\nargument.

\n

By adding columns: 2 to the argument list, we have wrapped the whole\ndocument in two columns. However, that would also affect the title and authors\noverview. To keep them spanning the whole page, we can wrap them in a function\ncall to place. Place expects an alignment and the content it\nshould place as positional arguments. Using the named scope argument, we can\ndecide if the items should be placed relative to the current column or its\nparent (the page). There is one more thing to configure: If no other arguments\nare provided, place takes its content out of the flow of the document and\npositions it over the other content without affecting the layout of other\ncontent in its container:

\n
#place(\n  top + center,\n  rect(fill: black),\n)\n#lorem(30)\n
\"Preview\"
\n

If we hadn't used place here, the square would be in its own line, but here\nit overlaps the few lines of text following it. Likewise, that text acts like as\nif there was no square. To change this behavior, we can pass the argument\nfloat: true to ensure that the space taken up by the placed item at the top\nor bottom of the page is not occupied by any other content.

\n
#set page(\n  paper: "us-letter",\n  header: align(\n    right + horizon,\n    title\n  ),\n  numbering: "1",\n  columns: 2,\n)\n\n#place(\n  top + center,\n  float: true,\n  scope: "parent",\n  clearance: 2em,\n)[\n  ...\n\n  #par(justify: false)[\n    *Abstract* \\\n    #lorem(80)\n  ]\n]\n\n= Introduction\n#lorem(300)\n\n= Related Work\n#lorem(200)\n
\"Preview\"
\n

In this example, we also used the clearance argument of the place function\nto provide the space between it and the body instead of using the v\nfunction. We can also remove the explicit align(center, ..) calls around the\nvarious parts since they inherit the center alignment from the placement.

\n

Now there is only one thing left to do: Style our headings. We need to make them\ncentered and use small capitals. Because the heading function does not offer\na way to set any of that, we need to write our own heading show rule.

\n
#show heading: it => [\n  #set align(center)\n  #set text(13pt, weight: "regular")\n  #block(smallcaps(it.body))\n]\n\n...\n
\"Preview\"
\n

This looks great! We used a show rule that applies to all headings. We give it a\nfunction that gets passed the heading as a parameter. That parameter can be used\nas content but it also has some fields like title, numbers, and level from\nwhich we can compose a custom look. Here, we are center-aligning, setting the\nfont weight to "regular" because headings are bold by default, and use the\nsmallcaps function to render the heading's title in small capitals.

\n

The only remaining problem is that all headings look the same now. The\n"Motivation" and "Problem Statement" subsections ought to be italic run in\nheaders, but right now, they look indistinguishable from the section headings. We\ncan fix that by using a where selector on our set rule: This is a\nmethod we can call on headings (and other\nelements) that allows us to filter them by their level. We can use it to\ndifferentiate between section and subsection headings:

\n
#show heading.where(\n  level: 1\n): it => block(width: 100%)[\n  #set align(center)\n  #set text(13pt, weight: "regular")\n  #smallcaps(it.body)\n]\n\n#show heading.where(\n  level: 2\n): it => text(\n  size: 11pt,\n  weight: "regular",\n  style: "italic",\n  it.body + [.],\n)\n
\"Preview\"
\n

This looks great! We wrote two show rules that each selectively apply to the\nfirst and second level headings. We used a where selector to filter the\nheadings by their level. We then rendered the subsection headings as run-ins. We\nalso automatically add a period to the end of the subsection headings.

\n

Let's review the conference's style guide:

\n\n

We are now in compliance with all of these styles and can submit the paper to\nthe conference! The finished paper looks like this:

\n

\n

Review

\n

You have now learned how to create headers and footers, how to use functions and\nscopes to locally override styles, how to create more complex layouts with the\ngrid function and how to write show rules for individual functions, and the\nwhole document. You also learned how to use the\nwhere selector to filter the headings by their level.

\n

The paper was a great success! You've met a lot of like-minded researchers at\nthe conference and are planning a project which you hope to publish at the same\nvenue next year. You'll need to write a new paper using the same style guide\nthough, so maybe now you want to create a time-saving template for you and your\nteam?

\n

In the next section, we will learn how to create templates that can be reused in\nmultiple documents. This is a more advanced topic, so feel free to come back\nto it later if you don't feel up to it right now.

"}}