Description
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.
Screenshots
Blocks
This plugin provides 21 blocks.
- Pricing / Investment Table
- Trusted-by Logo Strip
- Team Grid
- Deliverables Checklist
- Comparison Columns
- Case Study
- Callout Box
- Timeline / Phases
- Key Metrics
- Closing CTA
- Pull Quote / Testimonial
- Process Steps
- FAQ Accordion
- Testimonial Grid
- Chapter Summary
- Plate
- Epigraph
- Section Break
- Pull Quote
- References
- Aside
Installation
- In your WordPress admin, go to Plugins Add New Plugin and search for “Enrove Folios”, or upload the ZIP with Upload Plugin.
- Activate the plugin.
- Go to Enrove Add New, pick a theme, and tick the sample content box to start from a finished example.
- Optional: to see the themes in their own typefaces, press Download Fonts on Enrove Settings Fonts. To see the sample content with its photos, press Download Photos on Enrove Settings Imagery first.
FAQ
-
Does a folio use my site’s theme?
-
No. A folio is rendered by its folio theme alone, as a standalone page, so it looks the same on any site. Your site’s theme still controls the rest of your site.
-
Why are there no photos in the sample content?
-
The sample photos come from Pexels, whose licence does not allow them to be redistributed inside a plugin. Press Download Photos on Enrove Settings Imagery and the plugin fetches this site’s own copy. Folios you have already seeded pick the photos up once they have been downloaded, except for each page’s featured image, which is attached only when the sample content is created.
-
Can I make my own folio theme?
-
A folio theme is a small folder with a manifest, a cover template, a page template and a stylesheet. The full specification and a step-by-step playbook are on Enrove Themes, under the Spec and Playbook tabs. Installing a theme of your own is not possible yet; support for third-party themes is coming soon.
-
Why do my folios use system fonts?
-
The theme fonts have not been downloaded to your site yet. Press Download Fonts on Enrove Settings Fonts. Folios load their fonts from your own site rather than from Google, so readers are never sent to a third party.
-
Where do folios live on my site?
-
Under a base path,
/folio/by default. You can change it on Enrove Settings Routing. -
Where can I get help?
-
Post in the plugin’s support forum on WordPress.org, or email enrove@studioen.us. To report a security problem, please email rather than posting it publicly.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Enrove Folios” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Enrove Folios” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.5.1
- First release on WordPress.org.
- Folios load their fonts from your own site, never from Google. Download them once from Enrove Settings Fonts, or use system fonts.
- A setup dialog the first time an administrator opens an Enrove screen offers the theme fonts and sample photos, and a Reset tab on Settings starts over.
- Covers without a photo show a soft gradient in the theme’s colours.
- No “Powered by” credit appears on folios.
- Installing themes from a .zip is removed; support for third-party themes is coming soon.
- A folio page’s block inserter offers only the blocks its theme styles, and the site’s WordPress theme no longer leaks into folios or the folio page editor.
- A folio’s pages go live with it. While a folio is unpublished, its pages can’t be published; unpublishing a folio returns its live pages to draft, and publishing it again brings them back as they were.
- Publish and Unpublish in the folio editor ask first, and say how many pages change with the folio.
- A page unpublished in a published folio leaves the folio’s navigation for everyone, its editors included.
- Security: Contributors submit folios for review instead of publishing them, can open only folios they may edit, and can no longer add pages to other people’s folios.
- Security: a published page of a private, password-protected or unpublished folio is no longer readable through the REST API, feeds, searches or the sitemap.
- Folio covers show a logo only when you choose one; the Enrove wordmark is no longer added by default.
- Folios have a page title, and Contributors no longer see other people’s private folios in All Folios.
- Fixed: duplicating a folio or starting one from sample content no longer drops backslashes from block settings.
- Fixed: the folio editor fits a phone, and its remaining messages can be translated.
- Fixed: Enrove Magazine now honours a folio’s font choices.
- Fixed: the folio page editor’s content ran edge to edge on sites with a block theme.
0.5.0
- Change theme in the folio editor uses the same dialog as choosing a theme for a new folio.
- Switching a folio’s theme asks first when the new theme would hide blocks or proposal details, and nothing is applied until you press Switch theme.
- Removing a theme on Enrove Themes asks on a second screen of the theme’s dialog, with a count of the folios that use it.
- The folio editor’s header shows Preview, Save, Publish and Copy link on every tab. Save is greyed out when there is nothing to save.
- Copy link on a draft folio copies the preview link until the folio is published.
- Publishing a folio no longer clears its collection tags.
- With reduced motion on, the Add New dialog no longer blocks clicks after it closes.
0.4.0
- Sample photos are downloaded on request (Settings Imagery) instead of being bundled.
- Published folios are served with HTTP 200 instead of 404.
- Security: headings in the eBook, Magazine and Newsletter themes can no longer inject markup.
- Sample content works on PHP 7.1 and 7.2.
- CHANGELOG.md in the plugin folder has the full history.