@@ -0,0 +1,47 @@
+# Code of Conduct
+
+This project follows the
+[Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+It is the same code of conduct as the
+[language repository](https://github.com/lambda-discipline/lambda-discipline/blob/master/CODE_OF_CONDUCT.md).
+In short:
+
+## Our pledge
+
+We want participation in Lambda Discipline to be a harassment-free experience
+for everyone, regardless of age, body size, visible or invisible disability,
+ethnicity, sex characteristics, gender identity and expression, level of
+experience, education, socio-economic status, nationality, personal
+appearance, race, caste, color, religion, or sexual identity and orientation.
+
+## Expected behavior
+
+* Be kind and patient, and assume good intent.
+* Respect different viewpoints and experience levels.
+* Give and accept constructive feedback gracefully.
+* Take responsibility for mistakes and learn from them.
+* Focus on what is best for the community and the project.
+
+## Unacceptable behavior
+
+* Sexualized language or imagery, and unwelcome sexual attention.
+* Trolling, insulting or derogatory comments, and personal or political attacks.
+* Public or private harassment.
+* Publishing others' private information without their explicit permission.
+* Other conduct that would reasonably be considered inappropriate in a
+  professional setting.
+
+## Scope
+
+This applies in all project spaces (issues, pull requests, discussions and
+other channels) and when someone officially represents the project elsewhere.
+
+## Reporting and enforcement
+
+Report unacceptable behavior privately to the maintainers through GitHub
+([private report](https://github.com/lambda-discipline/lambda-discipline.github.io/security/advisories/new)
+or a direct message to a maintainer). All reports are reviewed promptly and
+handled confidentially. Maintainers may remove, edit or reject contributions,
+and warn, temporarily ban or permanently ban participants, following the
+Contributor Covenant's
+[enforcement guidelines](https://www.contributor-covenant.org/version/2/1/code_of_conduct/#enforcement-guidelines).
@@ -0,0 +1,104 @@
+# Contributing to the Lambda Discipline website
+
+Thanks for helping! Fixes to wording, new pages, better examples and design
+improvements are all welcome. By taking part you agree to follow the
+[Code of Conduct](CODE_OF_CONDUCT.md).
+
+This repository is the website only. Bugs in the language or the `lbd`
+interpreter belong in the
+[language repository](https://github.com/lambda-discipline/lambda-discipline/issues).
+Some of the site comes from there, too:
+
+* the [builtin reference](https://lambda-discipline.github.io/builtins/) is
+  generated from `lbd docs --json`, so builtin descriptions are fixed in the
+  `builtins!` table in the language's `src/builtins.rs`;
+* the [examples](https://lambda-discipline.github.io/examples/) are `.lbd`
+  files from the language repository, so a new example goes there first and
+  is then listed in `site.toml` here.
+
+## Reporting issues
+
+Open an issue with the matching template: a broken page or link, a mistake in
+the docs, or an idea for the site. Include the page URL. For security
+problems, see [SECURITY.md](SECURITY.md) instead.
+
+## Development setup
+
+You need Python 3.11 or newer, Git, and Rust 1.85 or newer to build `lbd`.
+
+```bash
+python -m venv .venv
+```
+
+```bash
+.venv/bin/pip install -r requirements-dev.txt
+```
+
+On Windows the scripts are in `.venv\Scripts\` instead of `.venv/bin/`.
+
+Build the site and preview it:
+
+```bash
+python build.py
+```
+
+```bash
+python -m http.server -d _site
+```
+
+`build.py` clones the language repository into `.cache/`, builds `lbd` and
+writes `_site/`. If you already have a checkout of the language, use it as is
+with `--repo ../lambda-discipline`, and skip the Cargo build with
+`--lbd path/to/lbd`. See [README.md](README.md) for every option and for how
+the repository is laid out.
+
+Optional but recommended: install the [pre-commit](https://pre-commit.com)
+hooks, which format and check your changes before each commit.
+
+```bash
+pre-commit install
+```
+
+## Writing pages
+
+* Pages are Markdown in `content/`, with `title` and `description` front
+  matter. Mark Lambda Discipline code blocks with `lbd` so they are
+  highlighted.
+* Keep the tone plain and precise. Every code sample should run, and its
+  comments should show what it really prints: check them with `lbd run`.
+* Link to other pages with root-relative paths such as `/reference/#types`.
+  The link checker verifies them, including the `#fragment`.
+
+## Before you open a pull request
+
+Everything CI checks can be run locally:
+
+```bash
+black --check .
+```
+
+```bash
+ruff check .
+```
+
+```bash
+mypy
+```
+
+```bash
+python build.py
+```
+
+```bash
+lychee --offline --root-dir "$PWD/_site" _site
+```
+
+Drop `--offline` to check external links too. Look at the pages you changed
+in a browser, in both light and dark mode and at phone width.
+
+## Commit messages
+
+Use `prefix: summary`, with the summary in lowercase and the imperative mood,
+for example `docs: explain let-polymorphism`. Common prefixes are `feat`,
+`fix`, `docs`, `style`, `refactor`, `ci`, `deps` and `chore`. Explain why in
+the body when it isn't obvious.
@@ -0,0 +1,34 @@
+# Security policy
+
+## Supported versions
+
+Only the live site, built from the `master` branch, is supported.
+
+## Reporting a vulnerability
+
+Please do not open a public issue. Report it privately through GitHub:
+**Security → Report a vulnerability** on this repository
+([direct link](https://github.com/lambda-discipline/lambda-discipline.github.io/security/advisories/new)).
+
+Include the affected page or file and the steps that reproduce the problem.
+You should get an acknowledgement within a week. We will agree on a
+disclosure date with you once a fix is ready, and credit you in the advisory
+unless you prefer otherwise.
+
+## Scope
+
+The site is static: plain HTML and CSS, one small inline script to filter the
+builtins, no cookies, no analytics and no third-party resources. Things that
+are in scope:
+
+* Content injection or cross-site scripting through anything the build
+  renders, such as an example program, its output, or a builtin's
+  documentation.
+* The build and deploy workflows: anything that could let a pull request,
+  a change in the language repository, or a dependency publish content to the
+  site or reach the workflow's credentials.
+* Vulnerabilities in the Python dependencies (`requirements.txt`) or GitHub
+  Actions this repository uses. Dependabot keeps them up to date.
+
+Vulnerabilities in the language or the `lbd` interpreter belong to the
+[language repository's security policy](https://github.com/lambda-discipline/lambda-discipline/blob/master/SECURITY.md).