Plugin for E-Mail Mailinglists

Resources Plugins
,
1

Hi,

I want to add some sort of E-Mail Manager to my Kirby instance. In theory, it’s nothing really complicated, but as I’m new to Kirby and dusty with PHP, I’m not quite sure how to get started.

To send the emails, I found this plugin which I think does all the heavy lifting: Courier | Kirby CMS Plugins

Screenshot 2025-04-09 at 15.22.14
Screenshot 2025-04-09 at 15.22.142920×744 118 KB

I then have a structure where I can store all of my contacts, and categorize them with tags.

Now comes the part where I’m a bit lost—currently, I’ve got an email template for my pages; so when I would write a mail, it’s essentially a page.
But I’d love to not have to have this weird double behaviour of needing to enter a slug (which isn’t used), or show the status as draft all the time, as I don’t want to “publish” the page, because it would then be visible on the website.

Also, I don’t really want the email to be editable after it’s sent—as that just doesn’t make sense.

Additionally, it would be awesome, if I could have this whole E-Mail thing in it’s own panel-view/tab.

Other than that, I love how I can just use the textarea field and stuff like the author field in the sidebar.

So now I’m wondering what the best approach is. Is this even possible without a huge effort? I saw that I can create entirely new panel views in Vue, but I don’t really feel like I need to have a fully custom interface. The textarea, the tag input, the author selection—all of that I would need to custom-build in Vue, right?

I hope i could make clear what I want to do, and maybe someone can guide me into the right direction :slight_smile:

Thanks!

2

A custom area is not a good idea, at least not for editing stuff, because you will have a hard time implementing fields in areas.

I’d use pages as originally planned, and if you don’t want them to be editable after sending, you can archive them, i.e. move out of the way and to a blueprint that makes everything readonly.

As for preventing general access to the pages from the frontend, you can either use routes that redirect to an error page, or make the pages accessible behind a login, i.e. only make them accessible to logged in users.

1 Like
3

And even when you use normal pages, you can use the panel.menu config option to add them to the Panel sidebar menu. So they function a little bit more like a custom area: panel.menu | Kirby CMS

4

Uh that’s neat! Is there a way to indicate that that page is active?

Edit: Nevermind, it’s litteraly in the docs :smiley: panel.menu | Kirby CMS

5

There probably is no way to set the panel.menu settings from inside a plugin, right?

6

No, it’s a config setting that needs to be in config.