MODX personal cabinet with Office: registration, profile, authorization

Clients ask for a personal cabinet, budget is limited, deadlines are tight. A custom-built solution is an unjustified risk: a week just for authorization. We've seen projects where after two weeks of development there were still bugs with validation and error handling. Office is a ready-made package for MODX that, according to repository data, covers 90% of typical tasks. Everything works via AJAX — no page reloads. We've configured Office for dozens of projects and know which pitfalls are most common. Here's how to avoid mistakes and get a working cabinet in 3–4 days. Get a consultation for your project — we'll estimate timelines and complexity.

We recently set up a cabinet for an online store with 5000 products. Custom fields "TIN" and "Contract number" were required. Implemented via extended in one day. Registration confirmation emails started delivering within 5 seconds.

What problems does Office for MODX solve?

Standard MODX authorization means chunks and snippets that you have to polish for every task. Office offers a unified interface: registration with email confirmation, authorization via AJAX forms with redirect, profile with editing name, email, phone and custom extended fields, change and reset password. All actions happen without reload — Office renders only the needed blocks and loads the rest asynchronously. This saves user time and reduces server load. According to our measurements, such a cabinet works 30% faster than custom-built solutions, and server traffic decreases by 20%.

How to set up authorization and registration without errors?

Start with installation. Through Package Manager find Office — install together with dependencies pdoTools and Email. Then — page structure:

Personal cabinet (template: lk-base)
├── Profile (/profile/)
├── Settings (/settings/)
├── Order history (/orders/)  [optional]
└── Logout (/logout/)

Authorization:
├── Login (/login/)
├── Registration (/register/)
└── Password recovery (/forgot-password/)

Login form

[[!OfficeAuth?
    &loginTpl=`officeLoginForm`
    &successTpl=`officeLoginSuccess`
    &redirectTo=`42`
    &loginContext=`web`
]]

<form class="login-form" data-office="auth">
    <div class="form-group">
        <label for="username">Email</label>
        <input type="email" id="username" name="username" required>
        [[+fi.error.username:notempty=`<span class="error">[[+fi.error.username]]</span>`]]
    </div>
    <div class="form-group">
        <label for="password">Password</label>
        <input type="password" id="password" name="password" required>
    </div>
    <button type="submit">Log in</button>
    <a href="/forgot-password/">Forgot password?</a>
</form>

Registration form

[[!OfficeRegister?
    &submitVar=`office-register`
    &successTpl=`officeRegisterSuccess`
    &activateTpl=`officeActivateEmail`
    &activateSubject=`Confirm registration`
    &groups=`Member`
    &redirectTo=`42`
    &validate=`username:email:required,password:required:minLength=^8^,password_confirm:password_confirm=^password^`
    &placeholderPrefix=`of.`
]]

Profile editing form

[[!OfficeProfile?
    &submitVar=`office-profile`
    &successTpl=`officeProfileSuccess`
    &placeholderPrefix=`of.`
]]

<form data-office="profile">
    <input type="text" name="fullname" value="[[!+of.fullname]]" placeholder="Full name">
    <input type="email" name="email" value="[[!+of.email]]" placeholder="Email" required>
    <input type="text" name="phone" value="[[!+of.phone]]" placeholder="Phone">
    <input type="text" name="extended[company]" value="[[!+of.extended.company]]" placeholder="Company">
    <button type="submit">Save</button>
</form>

Password change and recovery forms

[[!OfficeChangePassword? &validate=`password_old:required,password:required:minLength=^8^,password_confirm:password_confirm=^password^`]]
[[!OfficeForgotPassword? &emailSubject=`Password recovery` &emailTpl=`officeForgotPasswordEmail` &redirectTo=`reset-password`]]

To check authorization, use the OfficeCheck snippet with redirectTo parameter pointing to the login page. It can be placed in the required templates.

What if custom fields are needed?

MODX stores extended user data in JSON in the extended field. Data is accessible via the of.extended placeholder. To write, use the API: $profile->set('extended', json_encode([...])). This allows adding arbitrary fields — from contract number to notification settings — without hacking the core. For example, in one project we added a "Contract number" field in 2 hours.

When is additional customization needed?

Office covers 90% of tasks. If you need integration with an external CRM, non-standard notifications, or complex roles, we extend the functionality without breaking the core. Timelines and costs are discussed individually. Average customization time: 1 to 3 days depending on complexity.

Why is Office better than a custom solution?

Building authorization with native MODX snippets is a week-long task. Office provides a proven architecture, error handling, and AJAX out of the box. No need to write validation, email sending, or controllers — everything is already there. You just need to design the forms and connect custom fields. The result: a stable solution in 3–4 days instead of a week of development, with 20% less server load.

What's included in the setup?

Basic functionality — 3–4 days. Complex customizations (CRM integration, custom notifications) — discussed separately.

Guarantee and support

10+ years of experience with MODX, over 50 personal cabinet setups. We guarantee correct operation of all authentication mechanisms. If something breaks after an update — we fix it under support. Order a personal cabinet setup — we'll evaluate your project and offer the optimal solution.

Contact us for a consultation — we'll help you determine the functionality and timelines.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.