improve attribution to derived CC licensed work, close forgejo/website#132

docs/admin/installation-binary.md

@@ -2,6 +2,8 @@
 title: 'Installation from binary'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://github.com/DanielGibson/DanielGibson.github.io/blob/58362695f743a545d2530508ce42d5fe1eea84a9/content/post/setup-vps-with-wireguard-and-forgejo.md'
+origin_author: 'Daniel Gibson'
+origin_title: 'How to set up a Linux server to host git with LFS behind a VPN'
 ---
 
 ## Install Forgejo and Git, create git user

docs/user/email-settings.md

@@ -2,6 +2,8 @@
 title: 'Email Settings'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48badb27f8e4371263db3354f70836dfd/content/getting-started/email-settings.md'
+origin_author: 'Codeberg Docs Contributors'
+origin_title: 'Email Settings'
 ---
 
 By default, Forgejo will send notifications to your registered email addresses.

docs/user/first-repository.md

@@ -1,7 +1,9 @@
 ---
-title: Your First Repository
+title: 'Your First Repository'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48badb27f8e4371263db3354f70836dfd/content/getting-started/first-repository.md'
+origin_author: 'Codeberg Docs Contributors'
+origin_title: 'Your First Repository'
 ---
 
 Almost everything on Forgejo happens in a repository. Think of a repository as a home for your project, where all of its source code can be organized using Git, as well as where you can track issues and read and write wikis.

docs/user/issue-tracking-basics.md

@@ -2,6 +2,8 @@
 title: 'The Basics of Issue Tracking'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48badb27f8e4371263db3354f70836dfd/content/getting-started/issue-tracking-basics.md'
+origin_author: 'Codeberg Docs Contributors'
+origin_title: 'The Basics of Issue Tracking'
 ---
 
 Issues are an important mean of communication on Forgejo.

docs/user/pull-requests-and-git-flow.md

@@ -1,7 +1,9 @@
 ---
-title: Pull requests and Git flow
+title: 'Pull requests and Git flow'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48badb27f8e4371263db3354f70836dfd/content/collaborating/pull-requests-and-git-flow.md'
+origin_author: 'Codeberg Docs Contributors'
+origin_title: 'Pull requests and Git flow'
 ---
 
 ## Benefits of a pull request based workflow

docs/user/releases.md

@@ -2,6 +2,8 @@
 title: 'Tags and Releases'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/3bd7c665c7b0121a6b14cb5ef567c54b42b5698d/content/git/using-tags.md'
+origin_author: 'Codeberg Docs Contributors'
+origin_title: 'Tags and Releases'
 ---
 
 ## What are tags?

docs/user/repo-permissions.md

@@ -2,6 +2,8 @@
 title: 'Repository Permissions'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48badb27f8e4371263db3354f70836dfd/content/collaborating/repo-permissions.md'
+origin_author: 'Codeberg Docs Contributors'
+origin_title: 'Repository Permissions'
 ---
 
 When you invite collaborators to join your repository or when you create teams for your organization, you have to decide what each collaborator/team is allowed to do.

docs/user/wiki.md

@@ -2,6 +2,8 @@
 title: 'Integrated Wiki'
 license: 'CC-BY-SA-4.0'
 origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48badb27f8e4371263db3354f70836dfd/content/getting-started/wiki.md'
+origin_author: 'Codeberg Docs Contributors'
+origin_title: 'Integrated Wiki'
 ---
 
 A [wiki](https://en.wikipedia.org/wiki/Wiki) is a collaborative space on the web. It is a common practice to use wikis to collect knowledge and share information.