Skip to content

Commit 4c3780a

Browse files
committed
feat: lots of refinement
1 parent 0020f87 commit 4c3780a

File tree

13 files changed

+74
-41
lines changed

13 files changed

+74
-41
lines changed
Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
2-
title: Admin configuration
3-
description: Add configuration options to your extension's admin page
2+
title: Configuration options in the admin panel
3+
description: Add a few configuration options to your extension's admin page
44
author:
55
category: dev
66
thumbnail: adminconfiguration.jpeg
7-
order:
8-
unlisted: true
7+
unlisted: false
98
---
109

1110
...
Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
2-
title: Admin controller
3-
description: Add a custom PHP controller to an extension's admin page
2+
title: Custom admin page controllers
3+
description: Render your admin page using a custom controller
44
author:
55
category: dev
66
thumbnail: controller.jpeg
7-
order:
8-
unlisted: true
7+
unlisted: false
98
---
109

1110
...

apps/frontend/content/guides/dev/adminpage.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
2-
title: Admin page
3-
description: Create your extension's admin page
2+
title: Your first admin page
3+
description: Learn how to build a simple admin page for your extension
44
author: Emma
55
category: dev
66
thumbnail: adminpage.jpeg
7-
order:
8-
unlisted: false
7+
order: -1
98
---
109

1110
## Introduction
Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
2-
title: Dashboard wrappers
3-
description: Extend the Pterodactyl client and admin dashboard within the Laravel blade wrapper
2+
title: Extending the user dashboard wrapper
3+
description: Extend the Pterodactyl user dashboard using the Laravel blade wrapper
44
author:
55
category: dev
66
thumbnail: dashboard.jpeg
7-
order:
8-
unlisted: true
7+
unlisted: false
98
---
109

1110
...

apps/frontend/content/guides/dev/docker.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Develop with Blueprint Docker
33
description: Set up Blueprint Docker for local development
44
author: Loki and Emma
55
category: dev
6-
thumbnail: blueprintdocker.jpg
6+
thumbnail: blueprintdockerdev.jpg
77
---
88

99
::card

apps/frontend/content/guides/dev/packaging.md

Lines changed: 19 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,16 @@
11
---
2-
title: Packaging extensions
3-
description: Export extensions into ".blueprint" files for distribution
2+
title: Exporting your extension
3+
description: Export extensions into "myextension.blueprint" files for distribution
44
author: Emma
55
category: dev
66
thumbnail: files.jpeg
7-
order:
87
---
98

10-
## Export your extension with the CLI
9+
## Introduction
10+
11+
Blueprint extensions are distributed with `{identifier}.blueprint` files. Users can upload these files to their Pterodactyl directory and install your extension through the Blueprint CLI.
12+
13+
## Export the extension
1114

1215
To turn your development files into a distributable `{identifier}.blueprint` file, we'll need to use Blueprint's CLI utility to package it.
1316

@@ -28,12 +31,20 @@ Blueprint can generate a temporary download link for your extension for easier e
2831
blueprint -export expose
2932
```
3033

31-
### Test your exported extension
34+
## Test the extension
3235

3336
Testing is important! You should always check if an extension still works as expected, especially when using export scripts. Install your extension, test it on your panel and finally, if all is right, distribute it.
3437

35-
## Manually export your extension
38+
```bash
39+
# Make sure to remove your extension beforehand, if it is
40+
# installed.
41+
blueprint -remove myextension
42+
43+
# Install the myextension.blueprint file once again, which
44+
# should now exist in your Pterodactyl panel.
45+
blueprint -install myextension
46+
```
3647

37-
Don't do this! Even though extensions are practically ZIP files, exporting manually can break your extension, in current and future releases of Blueprint.
48+
## That's it!
3849

39-
Our CLI does more than just archiving extensions, it excludes certain directories, runs export scripts and enforces the folder structure Blueprint expects.
50+
You can now distribute your `{identifier}.blueprint` file. There are a few marketplaces that have specific categories/tags for Blueprint extensions. If your extension is open-source, add the [blueprint-extension](https://github.com/topics/blueprint-extension) tag to your repository!

apps/frontend/content/guides/dev/quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Make your very own Blueprint extension
44
author: Emma
55
category: dev
66
thumbnail: code.jpeg
7-
order: -1
7+
order: -2
88
---
99

1010
::card
112 KB
Loading

apps/frontend/src/components/elements/form/Textbox.vue

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,6 @@
2121
:wrap="props.wrap"
2222
:class="props.class"
2323
@input="resize"
24-
@click="resize"
2524
class="h-auto w-full resize-none overflow-hidden rounded-2xl border border-neutral-700 bg-gray-800/40 p-4 outline-0 transition-colors focus:bg-gray-800/60"
2625
/>
2726
</template>

apps/frontend/src/pages/app/extensions/[id].vue

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -257,7 +257,7 @@
257257
<ElementsFormBinarytoggle
258258
v-model="form.unlisted"
259259
label="Visibility"
260-
description="Public extensions are discoverable through the platform, unlisted extension only using their direct link. If your extension is pending review, this setting will immediately apply after approval."
260+
description="Public extensions are discoverable through the platform, unlisted only available to users with access. If your extension is pending review, this setting will immediately apply after approval."
261261
:options="[
262262
{
263263
value: false,
@@ -266,7 +266,7 @@
266266
},
267267
{
268268
value: true,
269-
icon: 'pixelarticons:link',
269+
icon: 'pixelarticons:hidden',
270270
label: 'Unlisted',
271271
},
272272
]"
@@ -276,7 +276,7 @@
276276
</div>
277277
</div>
278278

279-
<div class="rounded-3xl border border-neutral-700">
279+
<div class="overflow-hidden rounded-3xl border border-neutral-700">
280280
<div
281281
class="flex items-center justify-between gap-2 border-b border-neutral-700 p-4"
282282
>
@@ -288,20 +288,24 @@
288288
<SvgIconMarkdown :size="32" class="text-neutral-500" />
289289
</div>
290290
</div>
291-
<div class="p-4">
292-
<div
293-
class="flex grid-cols-2 flex-col overflow-hidden rounded-2xl border border-neutral-700 xl:grid"
294-
>
295-
<div class="grid grid-cols-1 bg-neutral-800/40">
291+
<div
292+
class="bg-stripes flex grid-cols-2 flex-col divide-y divide-neutral-700 overflow-hidden rounded-2xl xl:grid xl:divide-x xl:divide-y-0"
293+
>
294+
<div>
295+
<div
296+
class="border-neutral-700 bg-neutral-950 p-4 xl:-mb-[2px] xl:border-b"
297+
>
296298
<ElementsFormTextbox
297299
v-model="form.description"
298300
:rows="12"
299-
class="rounded-none border-0 bg-transparent font-mono"
301+
class="font-mono"
300302
:placeholder="`(ノ*・_・)ノ \\\n**markdown** is supported`"
301303
/>
302304
</div>
305+
</div>
306+
<div>
303307
<div
304-
class="border-t border-neutral-700 p-4 xl:border-s xl:border-t-0"
308+
class="border-neutral-700 bg-neutral-950 p-4 xl:-mb-[2px] xl:border-b"
305309
>
306310
<template v-if="!form.description || form.description == ''">
307311
<p>(ノ*・_・)ノ</p>

0 commit comments

Comments
 (0)