npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

plone4svelte

v0.0.2

Published

Plone4Svelte allows you to render contents managed by the (Plone CMS)[https://plone.org] in a (SvelteKit)[https://kit.svelte.dev/] site.

Readme

Plone4Svelte

Plone4Svelte allows you to render contents managed by the (Plone CMS)[https://plone.org] in a (SvelteKit)[https://kit.svelte.dev/] site.

Content management is hard but is very useful when non-technical people are meant to maintain a website. As a frontend developer, you might not love the idea of working with WordPress.

Plone is great because:

  • It is fast and easy to use. A modern editing experience your content editor will love.
  • That’s the most secure CMS on the market. Security built-in with a track record of over 20 years.
  • It is 100% open source and free, forever.

Thanks to the Plone REST API, Plone4Svelte allows you to use Plone as a headless CMS. You won't need to worry about the backend, you can focus on the frontend.

Setup

Run the Plone server:

docker run --name plone6-backend -e SITE=Plone -e CORS_ALLOW_ORIGIN='*' -d -p 8080:8080 plone/plone-backend:6.0

Create a SvelteKit project:

npm create svelte@latest my-app
# choose the "skeleton" template
cd my-app
npm install

Add the Plone4Svelte package:

npm install plone4svelte

Replace the ./my-app/src/routes generated folder with the ./src/routes folder from this repository.

Copy ./static/global.css from this repository to ./my-app/static/global.css.

Create a .env file in the root of the project with the following content:

VITE_PLONE_BACKEND_URL=http://localhost:8080/Plone

Run the SvelteKit project:

npm run dev -- --port 3001 --open

You can now see the default home page.

Editing contents in Plone

To create or edit contents, run the Plone user interface:

docker run --name plone6-frontend --link plone6-backend:backend -e RAZZLE_API_PATH=http://localhost:8080/Plone -e RAZZLE_INTERNAL_API_PATH=http://backend:8080/Plone -d -p 3000:3000 plone/plone-frontend:latest

Go to http://localhost:3000 and log in with the default credentials (the default user is admin and the password is admin).

You can now create new pages or edit the default home page and see the changes in the SvelteKit side on http://localhost:3001.

Customizing the theme

Styles

You can customize the theme by editing the ./my-app/static/global.css file.

The same Svelte component (./src/routes/[...path]/+page.svelte) is used to render all the contents, buthe main <div> element has specific classes that will allow you to style the content differently based on the content type and the section/sub-section the content belongs to:

  • type-<the content type>, for example type-Document for a Document content type.
  • section-<the section id> for each section/sub-section the page belongs to, for example a page with a path like http://localhost:3001/news/2024/flowers will have the following classes: section-news section-2024 section-flowers.

Overriding the components

You can override any default component using the overrideComponent function. For example, to override the breadcrumbs component, create a new Svelte component in the ./src/overrides folder and use the overrideComponent function in the ./src/+layout.svelte file:

import { overrideComponent } from 'svelet4plone';
import CustomBreadcrumbs from '../overrides/CustomBreadcrumbs.svelte';

overrideComponent('breadcrumbs', CustomBreadcrumbs);