Initial commit

Author: SpeedJack

.gitignore

@@ -0,0 +1,4 @@
+hashes.json
+_build/
+_releases/
+_data/

CONTRIBUTING.md

@@ -0,0 +1,42 @@
+# Contributing to PostTOC
+
+## First setup
+
+1. You need [XenForo 2.x](https://xenforo.com/). You can setup a Scotch Box
+   environment as described in the [Xenforo 2.x Development
+   Documentation](https://xenforo.com/xf2-docs/dev/scotchbox/)
+2. Fork TwitchPiper
+3. Move in the `src/addon/` folder of your development enviroment and `mkdir Inforge && cd Inforge`
+4. `git clone https://github.com/<your-username>/PostTOC && cd PostTOC`
+5. `git remote add upstream https://github.com/InforgeNet/PostTOC`
+
+## Pull request
+
+Each time you want to submit a pull request, do the following:
+
+1. Download latest upstream modifications: `git fetch upstream`
+2. Ceate a new branch: `git checkout -b whatever-you-want-feature upstream/master`
+3. Make you changes, add them and commit
+4. `git push -u origin whatever-you-want-feature`
+5. Visit `https://github.com/<your-username>/PostTOC` and create a new pull request
+
+### Commit message
+
+Follow these guidelines to write a proper commit message: [How to Write a Git
+Commit Message](https://chris.beams.io/posts/git-commit/).
+
+### Code style
+
+General guidelines:
+
+* Indent code with a **single tab**
+* Avoid brackets when they are not necessary
+* Try to keep lines under 80 columns, assuming a tab width equal to 8 spaces
+  (yes!)
+* Follow the [XenForo 2.x](https://xenforo.com/xf2-docs/dev/) code style
+  conventions
+* In general, I like the [Linux Kernel Coding
+  Style](https://www.kernel.org/doc/html/latest/process/coding-style.html) and
+  try to adapt it to PHP, JS and every other C-like language
+* Check out the code already in the repository and try to follow the same style
+* Use common sense

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020 Niccolò Scatena (Inforge)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -0,0 +1 @@
+# PostTOC

Setup.php

@@ -0,0 +1,15 @@
+<?php
+
+namespace Inforge\PostTOC;
+
+use XF\AddOn\AbstractSetup;
+use XF\AddOn\StepRunnerInstallTrait;
+use XF\AddOn\StepRunnerUninstallTrait;
+use XF\AddOn\StepRunnerUpgradeTrait;
+
+class Setup extends AbstractSetup
+{
+	use StepRunnerInstallTrait;
+	use StepRunnerUpgradeTrait;
+	use StepRunnerUninstallTrait;
+}

addon.json

@@ -0,0 +1,22 @@
+{
+	"legacy_addon_id": "",
+	"title": "[Inforge] PostTOC",
+	"description": "Add BBCode to support the creation of a table of contents in posts.",
+	"version_id": 1000070,
+	"version_string": "1.0.0",
+	"dev": "Inforge",
+	"dev_url": "https://www.inforge.net",
+	"faq_url": "https://github.com/InforgeNet/PostTOC/wiki/Frequently-Asked-Questions",
+	"support_url": "https://github.com/InforgeNet/PostTOC/issues",
+	"extra_urls": {
+		"Forum": "https://www.inforge.net/forum",
+		"GitHub": "https://github.com/InforgeNet/PostTOC"
+	},
+	"require": {
+		"XF": [
+			2020010,
+			"XenForo 2.2.0+"
+		]
+	},
+	"icon": "fas fa-list"
+}