bd4c7ce578
This PR cleans up the docs in a way to make them simpler to ingest by our [docs repo](https://gitea.com/gitea/gitea-docusaurus). 1. It includes all of the sed invocations our ingestion did, removing the need to do it at build time. 2. It replaces the shortcode variable replacement method with `@variable@` style, simply for easier sed invocations when required. 3. It removes unused files and moves the docs up a level as cleanup. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>
41 lines
1.3 KiB
Markdown
41 lines
1.3 KiB
Markdown
---
|
|
date: "2019-12-28"
|
|
title: "Adding Legal Pages"
|
|
slug: adding-legal-pages
|
|
sidebar_position: 110
|
|
toc: false
|
|
draft: false
|
|
aliases:
|
|
- /en-us/adding-legal-pages
|
|
menu:
|
|
sidebar:
|
|
parent: "administration"
|
|
name: "Adding Legal Pages"
|
|
identifier: "adding-legal-pages"
|
|
sidebar_position: 110
|
|
---
|
|
|
|
Some jurisdictions (such as EU), requires certain legal pages (e.g. Privacy Policy) to be added to website. Follow these steps to add them to your Gitea instance.
|
|
|
|
## Getting Pages
|
|
|
|
Gitea source code ships with sample pages, available in `contrib/legal` directory. Copy them to `custom/public/`. For example, to add Privacy Policy:
|
|
|
|
```
|
|
wget -O /path/to/custom/public/privacy.html https://raw.githubusercontent.com/go-gitea/gitea/main/contrib/legal/privacy.html.sample
|
|
```
|
|
|
|
Now you need to edit the page to meet your requirements. In particular you must change the email addresses, web addresses and references to "Your Gitea Instance" to match your situation.
|
|
|
|
You absolutely must not place a general ToS or privacy statement that implies that the Gitea project is responsible for your server.
|
|
|
|
## Make it Visible
|
|
|
|
Create or append to `/path/to/custom/templates/custom/extra_links_footer.tmpl`:
|
|
|
|
```go
|
|
<a class="item" href="{{AppSubUrl}}/assets/privacy.html">Privacy Policy</a>
|
|
```
|
|
|
|
Restart Gitea to see the changes.
|