Skip to content

Add plugins faq #184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Boy132 merged 2 commits into from
Dec 30, 2025
Merged

Add plugins faq #184

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6ac04ec
add plugins faq
Boy132 Dec 28, 2025
3afd0b6
fix spelling
Boy132 Dec 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 53 additions & 0 deletions src/pages/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,4 +132,57 @@ Here are some of the most asked questions that were asked in our Q&A stage on 4/
We can't say that. That's up to the Maintainer of Pterodactyl. Pelican and Pterodactyl are separate projects.
</details>
</TabItem>
<TabItem label="Plugins" value="plugins">
<details>
<summary>When will the plugin system be available?</summary>

The plugin system was released with beta30!
</details>
<details>
<summary>Will pterodactyl addons work with the new system?</summary>

No. Pterodactyl "addons" are just code modifications. Our codebase now greatly differs from pterodactyls.
Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
</details>
Comment on lines +135 to +146
Copy link

@coderabbitai coderabbitai bot Dec 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Good structure, but fix possessive form.

The new Plugins tab integrates well with the existing FAQ structure. However, line 144 has a grammar issue.

🔎 Proposed fix for possessive form 
-            No. Pterodactyl "addons" are just code modifications. Our codebase now greatly differs from pterodactyls.
+            No. Pterodactyl "addons" are just code modifications. Our codebase now greatly differs from Pterodactyl's.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<TabItem label="Plugins" value="plugins">
<details>
<summary>When will the plugin system be available?</summary>
The plugin system was released with beta30!
</details>
<details>
<summary>Will pterodactyl addons work with the new system?</summary>
No. Pterodactyl "addons" are just code modifications. Our codebase now greatly differs from pterodactyls.
Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
</details>
<TabItem label="Plugins" value="plugins">
<details>
<summary>When will the plugin system be available?</summary>
The plugin system was released with beta30!
</details>
<details>
<summary>Will pterodactyl addons work with the new system?</summary>
No. Pterodactyl "addons" are just code modifications. Our codebase now greatly differs from Pterodactyl's.
Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
</details>
🤖 Prompt for AI Agents 
In src/pages/faq.mdx around lines 135 to 146, fix the possessive/capitalization
issues: change "pterodactyls" to the possessive and proper-cased "Pterodactyl's"
on the line about addons, and likewise change "Pelicans plugin system" to
"Pelican's plugin system" so both project names are capitalized and use the
correct apostrophe for possession.

<details>
<summary>Will blueprint plugins work with the new system?</summary>

No. And the creator of blueprint won't port blueprint to also support pelican:
> [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.
</details>
<details>
<summary>Do I need the commercial license to use or develop plugins?</summary>

No. Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
</details>
Comment on lines +153 to +157
Copy link

@coderabbitai coderabbitai bot Dec 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix possessive form: "Pelicans" → "Pelican's".

Line 156 is missing the possessive apostrophe.

🔎 Proposed fix 
-            No. Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
+            No. Pelican's plugin system will be a "real" plugin system where plugins don't touch any core files.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<details>
<summary>Do I need the commercial license to use or develop plugins?</summary>
No. Pelicans plugin system will be a "real" plugin system where plugins don't touch any core files.
</details>
<details>
<summary>Do I need the commercial license to use or develop plugins?</summary>
No. Pelican's plugin system will be a "real" plugin system where plugins don't touch any core files.
</details>
🤖 Prompt for AI Agents 
In src/pages/faq.mdx around lines 153 to 157, the phrase "Pelicans plugin
system" uses the incorrect non‑possessive form; change it to the possessive
"Pelican's plugin system" (add the apostrophe) so the sentence reads that
Pelican owns the plugin system; update that single line and scan nearby
occurrences for the same possessive mistake to keep wording consistent.

<details>
<summary>Do I need to license my plugins under the same license as pelican?</summary>

No. You can do whatever you want with your plugins, it's your code.
</details>
<details>
<summary>What can plugins do?</summary>

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.

The first iteration _will_ have some limitations but we will continuously improve the capabilities of plugins.
</details>
<details>
<summary>How are plugins installed?</summary>

You can find information on that [here](./docs/panel/advanced/plugins#install-a-plugin).
</details>
<details>
<summary>How do you create plugins?</summary>

You can find detailed information on that [here](./docs/panel/advanced/plugins#create-a-plugin).
</details>
<details>
<summary>Are the plugins from the sneak peaks available?</summary>

Yes! Everything that was shown as little sneak peaks (+ more!) is available as plugin, for free and open source.

You can find the official plugin repo [here](https://github.com/pelican-dev/plugins).
</details>
</TabItem>
</Tabs>