Enrove Folios

Enrove Folios turns WordPress into a place to write and publish longer, multi-page pieces: an ebook, a newsletter issue, a magazine, a portfolio, a client proposal. A folio is a cover plus an ordered set of pages. You write every page in the block editor you already know, and the folio’s theme decides whether it reads as a book, a newsletter or a pitch.

Folios render through their own self-contained themes, not your site’s WordPress theme, so a folio looks the same whatever your site looks like, and changing your site’s theme never breaks one.

What you get

• Five built-in folio themes: Folio Starter, Enrove eBook, Enrove Newsletter, Enrove Magazine and Enrove Proposal. Each has its own cover, page layout, typography and, where it helps, its own content blocks.
• A dedicated folio editor: add, reorder and edit pages, set the cover, logo and typefaces, and preview the result before publishing.
• Sample content for every theme, so a new folio starts as a finished example you can write over.
• Password-protected folios, with a reading gate styled to match the theme.
• Collection tags to organise folios, plus quick edit and duplication from the All Folios list.
• Configurable URLs: folios live under a base path you choose, for example /folio/your-title/.
• Theme documentation built in: the full folio theme specification and a step-by-step playbook are on Enrove → Themes. Support for third-party themes is coming soon.

Privacy

Enrove Folios collects nothing: no analytics, no usage tracking, no telemetry, and nothing is ever sent to StudioEN. Settings → Privacy lists every request the plugin makes. There are two, and both are described under External services below.

External services

This plugin uses two third-party services. Neither receives anything about your site’s content or your visitors beyond what is described here.

Google Fonts

Folio themes set their type in open-licence fonts from Google Fonts. Folios never load them from Google: they are served from your own site, so your readers’ browsers do not contact Google. An administrator fetches them by pressing Download Fonts on Enrove → Settings → Fonts, or by choosing to download them in the Finish setting up Enrove Folios dialog that opens the first time an administrator visits an Enrove screen. That sends one request per font family to fonts.googleapis.com and one per font file to fonts.gstatic.com (about 110 files, 4 MB) from your server. Google receives your server’s IP address and the names of the fonts requested. The dialog only offers the download: nothing is fetched until one of those buttons is pressed, and until then folios use system fonts. The fonts are then served from your own uploads folder.

• Terms of service: https://developers.google.com/fonts/terms
• Privacy policy: https://policies.google.com/privacy

Pexels (sample photos)

Theme covers and the photos in sample content come from Pexels. Their licence does not allow them to be packaged with the plugin, so the plugin does not include them. An administrator can fetch them by pressing Download Photos on Enrove → Settings → Imagery, or in the same setup dialog. That sends one request per photo (46 in total, about 4 MB) from your server to images.pexels.com. Pexels receives your server’s IP address and the addresses of the photos requested. Nothing else is sent, no account or API key is involved, and nothing is fetched until one of those buttons is pressed. The photos are then served from your own uploads folder.

The developers choose these photos with the Pexels API (api.pexels.com), their own API key and a curation script. None of these is part of the released plugin, so the released plugin never contacts the Pexels API.

• Pexels licence: https://www.pexels.com/license/
• Terms of service: https://www.pexels.com/terms-of-service/
• Privacy policy: https://www.pexels.com/privacy-policy/

Credits and licences

Enrove Folios is licensed under the GPLv2 or later. It includes or uses:

• eicons icon font (5.21.0) by Elementor, distributed under the GPLv3 as part of the Elementor plugin. Some glyphs are based on Font Awesome 4.7.0, licensed under the SIL Open Font License 1.1. https://github.com/elementor/elementor-icons
• Tailwind CSS, compiled into assets/build, licensed under the MIT licence. https://tailwindcss.com
• Google Fonts typefaces, fetched on request (not bundled) and served from your own site, each under the SIL Open Font License or Apache License 2.0.
• Pexels photos, fetched on request (not bundled), under the Pexels licence. Each photo is credited to its photographer on Enrove → Settings → Imagery.

Source code and build

The compiled admin stylesheet in assets/build/ is generated from assets/css/tailwind.css with Vite and Tailwind CSS. The source, package.json and vite.config.js are included in the plugin. To rebuild it, run npm install and then npm run build.