Skip to content

Commit 391a4b8

Browse files
authored
Add plugins faq (#184)
* add plugins faq * fix spelling
1 parent 266b3b8 commit 391a4b8

1 file changed

Lines changed: 53 additions & 0 deletions

File tree

src/pages/faq.mdx

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,4 +132,57 @@ Here are some of the most asked questions that were asked in our Q&A stage on 4/
132132
We can't say that. That's up to the Maintainer of Pterodactyl. Pelican and Pterodactyl are separate projects.
133133
</details>
134134
</TabItem>
135+
<TabItem label="Plugins" value="plugins">
136+
<details>
137+
<summary>When will the plugin system be available?</summary>
138+
139+
The plugin system was released with beta30!
140+
</details>
141+
<details>
142+
<summary>Will pterodactyl addons work with the new system?</summary>
143+
144+
No. Pterodactyl "addons" are just code modifications. Our codebase now greatly differs from pterodactyls.
145+
Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
146+
</details>
147+
<details>
148+
<summary>Will blueprint plugins work with the new system?</summary>
149+
150+
No. And the creator of blueprint won't port blueprint to also support pelican:
151+
> [I] do not have the capacity to work on multiple Pterodactyl forks [and I] do not believe making an extension framework for a platform promising it's own addon system is worth our time.
152+
</details>
153+
<details>
154+
<summary>Do I need the commercial license to use or develop plugins?</summary>
155+
156+
No. Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
157+
</details>
158+
<details>
159+
<summary>Do I need to license my plugins under the same license as pelican?</summary>
160+
161+
No. You can do whatever you want with your plugins, it's your code.
162+
</details>
163+
<details>
164+
<summary>What can plugins do?</summary>
165+
166+
Pretty much anything you want! They can add new pages, change existing ones (to some extent), add new languages, change the theme (color/ font/ css) and more.
167+
168+
The first iteration _will_ have some limitations but we will continuously improve the capabilities of plugins.
169+
</details>
170+
<details>
171+
<summary>How are plugins installed?</summary>
172+
173+
You can find information on that [here](./docs/panel/advanced/plugins#install-a-plugin).
174+
</details>
175+
<details>
176+
<summary>How do you create plugins?</summary>
177+
178+
You can find detailed information on that [here](./docs/panel/advanced/plugins#create-a-plugin).
179+
</details>
180+
<details>
181+
<summary>Are the plugins from the sneak peaks available?</summary>
182+
183+
Yes! Everything that was shown as little sneak peaks (+ more!) is available as plugin, for free and open source.
184+
185+
You can find the official plugin repo [here](https://github.com/pelican-dev/plugins).
186+
</details>
187+
</TabItem>
135188
</Tabs>

0 commit comments

Comments
 (0)