Folio - Personal Organizer & Concierge Service Module

[maximus]

I'm excited to share Folio, a new personal organizer and concierge service module built natively on ProcessWire pages.

If you need a single-user workspace or personal dashboard to manage projects, tasks, calendar events, contacts, places, bookmarks, and long-term goals without relying on external SaaS tools, Folio brings everything right into your ProcessWire admin.

---

✨ Key Features

• Unified Dashboard: Icon-chip statistics, quick-add buttons (+ Project, Event, Contact, Place, Link, Goal, Milestone), and summary cards (In progress, Projects, Coming up, Goals, Roadmap, Recently done).
• Projects, Sprints & Tasks: Strict hierarchy built on ProcessWire's native page tree (Project → Sprint → Task), with automatic "Backlog" sprint creation on project addition. Includes a Kanban board view with status and priority color-coding.
• Calendar & Recurring Events: Month grid calendar view, point-in-time events, and recurring event rules (e.g. annual birthdays, monthly retrospectives).
• Contacts: Card grid with photo, company, role, phone, email, birthday tracking, and tags.
• Places: Locations with visit status (Want to visit, Visited), links, and coordinates.
• Links: Bookmarks and reference links.
• Goals & Roadmap: Long-term goals and vertical milestone timeline.
• Timeline: Historical feed of completed items across projects, tasks, goals, places, and syprents.

---

🚀 Getting Started & Demo Data

1. Copy the Folio folder to /site/modules/Folio/.
2. In the ProcessWire admin, go to Modules → Refresh.
3. Install Folio — the companion ProcessFolio module installs automatically, creating all necessary fields (folio_*), templates (folio-*), and the hidden /folio/ page tree.

Instant Demo Data: To instantly populate your new admin with realistic demo projects, tasks, contacts, calendar events, and places, run the included CLI seed script:

php site/modules/Folio/src/Cli/seed.php

(Use --clear to reset demo data anytime).

🔗 Links & Support

• GitHub Repository: github.com/mxmsmnv/Folio

Feedback, feature requests, and pull requests are very welcome! Let me know what you think.

[adrian]

Hey @maximus - thanks as always. Can you please explain how this would integrate with Verk, or does it supersede it?

[maximus]

Thanks Adrian! Folio is a separate solution from Verk; it neither integrates with nor supersedes it.

Folio is intended as a personal organizer for everyday projects, tasks, events, contacts, places, goals, and other day-to-day information. Verk remains focused on ProcessWire site operations: page-linked tasks, editorial planning, content audits, sprints, and the knowledge base.

For broader business use, I’m developing a separate project called Kontor. It is an open-source, modular ERP, CRM, and business operations ecosystem built natively for ProcessWire. The repository is currently private, but I’m aiming to make it public and publish the first release around mid-to-late August.

Kontor is designed as a shared core with independently installable components, so a business can install only what it needs. The wider ecosystem includes:

• contacts, companies, addresses, tags, duplicate detection, and import/export;
• CRM with leads, pipelines, deals, Kanban-style workflows, and sales handover;
• products and services, categories, price lists, quotations, orders, invoices, credit notes, payments, and allocations;
• warehouses, stock movements, reservations, purchasing, goods receipts, expenses, approvals, projects, time tracking, and project invoicing;
• recurring tasks and reminders, comments, mentions, followers, personal dashboards, reports, and scheduled exports;
• private files, document templates, multilingual PDF generation, global search, queues, caching, workflows, automation, and custom entity types;
• REST and GraphQL APIs, OpenAPI documentation, webhooks, a component marketplace, shared mailboxes, and a customer portal;
• optional AI assistance, double-entry accounting foundations, and country-specific localization packages.

All components share the same ProcessWire-native admin interface, users, roles, permissions, audit log, events, health checks, backup and recovery tools, while keeping their own versions, migrations, tests, and release cycles. Business records are stored in dedicated tables rather than being forced into ProcessWire pages and templates.

It’s still in active development and needs more real-world testing before I would call it production-ready. I’d be very interested in your thoughts — especially which components or integrations would be most useful to the ProcessWire community, and whether there are any important business workflows you think are missing.

[adrian]

Thanks - Kontor actually sounds fantastic - I've been offering my team to build a replacement for Hubspot (I really hate all these SaaS tools that people want to use), but they won't see the light :)

I am still a bit confused about Folio vs Verk, because I feel like Verk can already be used for everyday projects and tasks, etc and I worry about users needing to use one tool for personal and another for one for page-linked tasks etc, but that might just be me.

[maximus]

You’re right that there is some functional overlap. I think the distinction is less about whether each module can create a project or task, and more about the context and scale for which it was designed.

Verk was developed primarily as an editorial and site-operations layer for content-heavy media websites — think of something like People.com, a magazine or news publication, or a large multi-section portal with many content types, editors, publication dates, and large amounts of structured content. In that environment, tasks are usually connected to specific ProcessWire pages and editorial work: preparing or reviewing content, planning publication, finding missing data, coordinating sprints, and maintaining content quality.

Folio is aimed more at an individual user: a solo creator, blogger, freelancer, or anyone who simply wants a small personal workspace inside ProcessWire. Projects and tasks are only part of it; it also keeps everyday events, contacts, places, bookmarks, goals, and milestones close at hand. It is for someone who does not need the entire editorial orchestra and just wants a simple base for organizing daily life and personal work.

Kontor is a different level again. It is intended for managing a company and for organizations that want to own their data rather than depend on SaaS products such as HubSpot. Its scope includes CRM, sales, quotations, orders, invoicing, payments, inventory, purchasing, projects, reporting, automation, APIs, and other business operations. One of the planned directions is integration with Mercato, so Kontor could also serve as the operational back office for a ProcessWire-based online store.

I don’t think a single universal module can solve every problem equally well. Sometimes a separate solution is needed for a particular purpose and scale. So the intended distinction is:

• Folio for personal and solo organization;
• Verk for editorial and content-heavy website operations;
• Kontor for running a business.

There will inevitably be some overlap, but I don’t necessarily expect the same user to install and use all three. Your question does show that I need to make these boundaries much clearer in their descriptions — thanks for pointing that out.

[Krlos]

48 minutes ago, maximus said:

Kontor is designed as a shared core with independently installable components, so a business can install only what it needs. The wider ecosystem includes:

• contacts, companies, addresses, tags, duplicate detection, and import/export;
• CRM with leads, pipelines, deals, Kanban-style workflows, and sales handover;
• products and services, categories, price lists, quotations, orders, invoices, credit notes, payments, and allocations;
• warehouses, stock movements, reservations, purchasing, goods receipts, expenses, approvals, projects, time tracking, and project invoicing;
• recurring tasks and reminders, comments, mentions, followers, personal dashboards, reports, and scheduled exports;
• private files, document templates, multilingual PDF generation, global search, queues, caching, workflows, automation, and custom entity types;
• REST and GraphQL APIs, OpenAPI documentation, webhooks, a component marketplace, shared mailboxes, and a customer portal;
• optional AI assistance, double-entry accounting foundations, and country-specific localization packages.

WOW 🤯