Kotlin website

This is the source for the http://kotlinlang.org.

• Installation
• How to run
• Project structure & overview
• Writing content
• Filing bugs

Installation

1. You will need Docker to run site lifecycle tasks. Installation for macOS and Windows.
2. If you want to develop frontend Yarn package manager is also needed (installation instructions). Don't forget to install frontend dependencies - yarn install.
3. All specific app parameters stored in env-file. Copy sample file .env.sample and rename it to .env. Change variables values if needed.

How to run

• All in one option (suitable for content authors/writers):
  • docker-compose up. It will build all stuff and create site on localhost:5000.
• Developer has 2-step option:
  • docker-compose up website will run only site at localhost:5000.
  • yarn start will run webpack-dev-server on localhost:9000. This address should be used for development. All pages from origin server will be proxied.

Project structure & overview

Data

All data is stored in the *.yml files in folder data:

• _nav.yml site navigation and PDF building.
• releases.yml info about releases.
• videos.yml data for the Videos page. The content property is used to create categories. It contains a list of videos or other categories. Maximum tree depth level is 3.
• events.xml event data.

Templates

Kotlinlang uses Jinja2 templates that can be found in templates folder. Note that all Markdown files are processed as Jinja templates before being converted to HTML. This allows you to use all Jinja power inside Markdown (for example, build urls with url_for function).

Page metadata

Every page can have an unlimited number of metadata fields. More information here. The most important of them are the page template (e.g. layout: reference) and its type (e.g. type: tutorial). category and title fields are added for future development.

Kotlin grammar reference

The Kotlin grammar reference (grammar.xml) is generated by the Kotlin grammar generator from the Kotlin grammar definition.

Writing content

Markup

kramdown with some additions (like GitHub fenced code blocks) is used as Markdown parser. See the complete syntax reference at the kramdown site.

Specifying page element attributes

With kramdown you can assign HTML attributes to page elements via {:%param%}. E.g.:

• *important text*{:.important} - produces <em class="important">important text</em>
• *important text*{:#id} - produces <em id="id">important text</em>

For block elements this instruction must be specified on the line following element definition:

This is a paragraph
{:.important}

This is a paragraph

More information about attributes can be found here.

Custom element styles

Inline elements

• {:.keyword} highlights a keyword.
• {:.error} highlights an error.
• {:.warning} highlights a warning.

Tables

• {:.wide} stretches a table to occupy the entire width of a page.
• {:.zebra} interleaves table rows.

E.g.:

| Expression | Translated to |
|------------|---------------|
| `a++` | `a.inc()` + see below |
| `a--` | `a.dec()` + see below |
{:.wide.zebra}

Quotation blocks

They're used in a slightly other manner that they were originally designed for: as universal block container elements.

• {:.note} highlights a note block.

E.g.:

> **`inc()/dec()` shouldn't mutate the receiver object**.
>
> By "changing the receiver" we mean `the receiver-variable`, not the receiver object.
{:.note}

Filing Bugs

We use YouTrack for bug reports and suggestions. Click here to report an issue.