MODX

MODX Revolution is an open-source content management system well suited for corporate websites, catalogs, online services, and projects with custom structures. MODX gives developers direct control over HTML markup, templates, page URLs, data structures, and server-side logic. This makes it possible to build a website around specific business requirements, SEO objectives, and future development plans.

Big Fish web studio uses MODX for projects that require custom design, high performance, complex section structures, and extensive development capabilities. We design the architecture before programming begins: page types, templates, fields, relationships between sections, URL rules, database structure, and integration points with external systems.

MODX runs on PHP and typically uses MySQL or MariaDB. Data is managed through xPDO, the MODX object model that allows developers to work with resources, users, settings, and custom database tables. This architecture makes it possible to create MODX websites with dozens of data types and thousands of pages while keeping the management system structured and maintainable.

In MODX, a page is represented by a resource. A resource contains system parameters, URL, title, content, template, and additional fields. The website structure is organized as a tree, so both a 20-page corporate website and a portal containing thousands of pages can be managed using the same clear logic.

Templates and chunks control the presentation layer. A template defines the overall page structure, while chunks are used for recurring elements such as cards, forms, menus, benefit sections, contacts, navigation, footers, and other components. Snippets handle PHP logic. Template Variables (TVs) make it possible to create custom data structures for different page types.

In practice, we can create separate sets of fields for services, projects, employees, offices, articles, equipment, documents, or products. Editors get a clear administration interface while developers retain full control over page generation.

For more complex structures, we use MIGX and custom database tables. For example, a catalog containing 10,000 records does not have to be stored as 10,000 standard MODX pages. Large datasets can use a dedicated data model, with the required records retrieved through xPDO. This reduces unnecessary database queries and simplifies future development.

One of MODX's strengths is the clear separation of content, presentation, and application logic. We do not place all website logic inside a single template. The interface is divided into reusable components, while program operations are moved into separate snippets.

A typical corporate project may use 5–15 main templates, several dozen chunks, and dedicated TV field sets for different sections. The number of components is determined by the project architecture rather than by the number of ready-made add-ons available.

This approach becomes particularly important for long-term maintenance. Two or three years later, a developer can open the project, identify the purpose of a component, and modify a specific part of the system without rebuilding other pages.

Where appropriate, we use Fenom, a template engine that provides convenient handling of conditions, loops, variables, and complex structures at the presentation layer. We use pdoTools for standard data queries, while complex business logic is implemented with custom PHP code and xPDO.

The MODX server side is written in PHP. This provides access to full-scale server-side development: data processing, file operations, custom classes, database interaction, external APIs, and background processes.

During development, we separate the MODX system code from project-specific code. Custom logic is placed in dedicated components, classes, and namespaces. This reduces problems during core updates and makes the code easier to maintain.

For data exchange with external systems, we use JSON and REST APIs and configure authorization, request validation, error logging, and access restrictions for service methods. MODX can be integrated with CRM platforms, 1C, accounting systems, delivery services, payment gateways, telephony, mapping services, email platforms, and corporate databases.

MODX uses xPDO to work with databases. Instead of constantly writing direct SQL queries, developers use an object model to read, create, and modify data. Standard resources include modResource, modUser, modTemplate, modChunk, and other system objects.

For custom modules, we create dedicated models. For example, a system can contain entities such as property, city, specification, document, specialist, or request, each with predefined field types and relationships between database tables.

On large projects, we monitor database indexes, the number of queries per page, the volume of selected data, and repeated requests to the same tables. Retrieving 20 records from a table should not require loading 20,000 records into memory and filtering them with PHP. Details like these directly affect page generation time and server load.

MODX has its own caching system. Resources, website elements, and the results of individual operations can all be cached. With the right architecture, most public pages can be delivered without repeatedly executing the entire chain of PHP code and database queries.

We monitor server-side HTML generation time separately from client-side page rendering speed. PHP, MySQL, caching, and query count are critical on the server side. HTML, CSS, JavaScript, images, fonts, and resource loading order affect browser performance.

On the server side, we use an up-to-date PHP version, OPcache, HTTP/2 or HTTP/3, Brotli or Gzip compression, correct cache headers, and NGINX or Apache. On the website itself, we minimize the number of connected libraries, consolidate repeated styles, remove unused code, convert images to WebP or AVIF, and define image dimensions directly in the markup.

During development, we monitor Core Web Vitals: LCP, INP, and CLS. We aim for an LCP of up to 2.5 seconds, INP of up to 200 ms, and CLS of up to 0.1. These metrics are considered during front-end development because correcting architectural performance problems after launch is considerably more expensive.

Need a Fast MODX Website?

We will design the architecture, configure caching, and optimize PHP, the database, images, and the client-side code. For an existing project, we can conduct a performance audit and identify the causes of high server load or slow page loading.

Discuss Your Project

MODX gives developers full control over a page's HTML code, making the platform well suited for search engine optimization. We define the H1–H6 structure, Title, Description, canonical tags, robots directives, Open Graph data, Schema.org markup, and URL generation rules.

Separate SEO fields and automated rules can be created for every page. For example, in a catalog containing several thousand pages, Title and Description tags can be generated from templates using category names, cities, service types, and other parameters. Priority pages can have individually written metadata.

MODX supports clean URLs and hierarchical URL structures. Instead of addresses containing technical parameters, the website can use structures such as /services/development/, /portfolio/project-name/, or /catalog/category/product/. This is convenient for users, search engine crawlers, and SEO specialists.

When developing a turnkey website, we define rules for URLs with and without trailing slashes, HTTP and HTTPS, www and non-www versions, letter case, and URL parameters. Duplicate pages receive 301 redirects and canonical tags. This prevents multiple versions of the same page from being indexed.

The sitemap.xml file is generated automatically and updated when new content is published. For large projects, the sitemap can be divided into several files covering pages, articles, products, categories, projects, and other content types.

We configure robots.txt according to the actual project structure. Technical sections, service URLs, and internal operation results are excluded from crawling. The MODX administration area is also excluded from search engine indexing.

For individual page types, we provide meta robots controls. An editor or SEO specialist can exclude a specific page from indexing without modifying the program code.

After launch, we connect Yandex Webmaster and Google Search Console and check indexing, server responses, redirects, canonical URLs, and sitemap files.

For corporate projects, we use Schema.org structured data. Depending on the page content, this can include Organization, WebSite, BreadcrumbList, Article, Product, Service, FAQPage, and other appropriate types.

Structured data is generated from MODX content. Names, images, publication dates, authors, prices, and specifications are retrieved from the corresponding page fields. Editors do not need to manually edit JSON-LD whenever content changes.

This is particularly useful for websites containing hundreds of similar pages. The rule is configured once, after which structured data is generated automatically across the entire section.

We Develop MODX Websites with SEO Built In

We incorporate search engine optimization into the website architecture: page URLs, metadata, headings, structured data, sitemaps, indexing rules, redirects, and management of large website sections.

Order a MODX Website

When migrating an existing website to MODX, we create a mapping table between old and new URLs. Every significant URL receives a permanent 301 redirect to the corresponding new page. For projects with hundreds or thousands of URLs, redirect rules are imported in bulk and checked automatically.

On existing projects, we use Redirector or a custom redirect mechanism. We separately monitor redirect chains, loops, 404 pages, and incorrect internal links.

During a website redesign, retaining existing URLs is often more effective than making large-scale structural changes. We therefore define the URL architecture after analyzing current indexing and organic search traffic.

Security starts with server configuration. We restrict access to system directories and configuration files, use HTTPS, configure file and directory permissions, disable PHP error output for visitors, and control access to the administration area.

The administration panel can be moved from the default /manager/ URL. Administrative accounts use strong passwords and differentiated access permissions. MODX allows us to create user groups and assign permissions for individual sections, resources, and actions. A content manager does not need system administrator privileges.

We protect forms against automated submissions, validate incoming values on the server, and restrict permitted upload file types. Database operations use standard xPDO methods and prepared queries. User data is escaped according to its output context.

At the server level, we additionally configure request limits, suspicious activity logging, and backups. Projects with increased security requirements can use a Web Application Firewall and network-level protection.

We often use FormIt for contact forms. It allows us to configure required fields, data validation, message delivery, custom handlers, and additional actions following a successful form submission.

For complex projects, we develop custom handlers. A request can simultaneously be stored in the database, transferred to a CRM, sent to a manager, recorded as an analytics goal, and return an individual result to the user.

All validation is performed on the server side. JavaScript validation improves the user experience, while the server checks the submitted data again before processing it.

MODX can serve as the public-facing part of a corporate information system. A website can send enquiries to Bitrix24, amoCRM, or another CRM, receive product information from 1C, and synchronize stock levels, prices, statuses, and documents.

Data exchange can use APIs, JSON, XML, CommerceML, or intermediate tables depending on the capabilities of the external system. For large datasets, we use batch processing. Updating 50,000 product records should not block the public website.

All critical operations are logged. Logs allow us to determine request time, returned responses, error codes, and identifiers of transferred entities. This significantly speeds up troubleshooting of integrations.

MODX is suitable for catalogs of services, equipment, real estate, specialists, projects, and products. The structure is designed around the actual business data.

For smaller catalogs, resources and TV fields are sufficient. For larger datasets, we use MIGX, MIGXdb, or custom xPDO models. Filters work with actual database fields, and frequently queried fields are indexed.

When developing a catalog, we define filter indexing rules in advance. Search engines should not receive tens of thousands of low-value parameter combinations. Important landing pages are created separately, while other combinations are excluded from indexing or assigned a canonical URL.

The MODX administration panel can be adapted to the employees of a specific company. We hide unnecessary fields, create custom tabs, change the order of elements, add instructions, and restrict access according to user roles.

A service page editor can be given 10–15 fields that are actually required instead of dozens of system parameters. Projects, articles, and products can each have their own data sets. This reduces errors during day-to-day website management.

For larger companies, we configure several roles: administrator, editor, SEO specialist, and catalog manager. Each role receives access only to the functions it needs.

MODX does not restrict front-end development to ready-made themes. HTML is created for the approved design and then integrated with the content management system. This is important for projects with unconventional layouts, complex animation, interactive graphics, and numerous custom components.

We can develop a website using clean semantic HTML, CSS Grid, Flexbox, SVG, Canvas, WebGL, and JavaScript, while MODX handles content management and the server side.

This makes MODX a strong platform for a web studio developing corporate projects with custom visual solutions: the CMS operates behind the website without dictating how its pages should look.

MODX does not require a particular JavaScript framework. The public-facing website can use vanilla JavaScript, with additional libraries connected only where they are required.

We avoid loading hundreds of kilobytes of program code for a few simple interface elements. Menus, tabs, expandable sections, forms, and most animations can be implemented as small independent modules.

For complex interactive sections, MODX can operate as a data source while the interface communicates with the server through an API. This architecture works well for configurators, calculators, customer accounts, and other dynamic sections.

MODX technical support includes website monitoring, core and add-on updates, bug fixing, backups, database optimization, log monitoring, functionality improvements, and integration development.

Before an update, we create backups of the files and database and check add-on compatibility. Major updates are first performed on a staging copy of the project. After updating, we test the administration area, forms, search, integrations, email delivery, authorization, and key user scenarios.

For websites that have been operating for many years, we also conduct a technical audit. We check outdated PHP code, third-party add-ons, database queries, cache size, error logs, access permissions, and server configuration.

Already Have a MODX Website?

We will conduct a technical audit, update MODX and its add-ons, fix errors, improve loading speed, and check security and SEO. We can also provide ongoing technical support and continue developing the project.

Get a Support Cost Estimate

MODX is particularly well suited for corporate projects with custom structures, numerous page types, catalogs, integrations, and proprietary functionality.

A company can order a website on MODX and receive a system that can be developed progressively: adding new sections, creating new data types, connecting CRM and 1C, launching new landing pages, and expanding the catalog.

For a small website containing 5–10 pages, some MODX capabilities may remain unused. The platform's main advantages become more valuable on corporate projects that require controlled architecture and continued development.

When developing a turnkey website, we begin with planning and architecture. We define the structure, user scenarios, page types, functional modules, SEO requirements, and integrations. We then create prototypes and designs, develop the responsive front end, program the required functionality, and integrate it with MODX.

The next stage includes preparing the main website sections, configuring SEO parameters, redirects, sitemap.xml, robots.txt, analytics, and conversion goals. Before launch, we test the website across key screen resolutions and check forms, links, server response codes, 404 pages, performance, and the administration area.

This process allows us to develop a website with a predefined architecture instead of resolving structural technical limitations after publication.

The choice of content management system depends on the project. WordPress has an extensive ecosystem of ready-made solutions and works well for many standard corporate websites. 1C-Bitrix is widely used by Russian companies that require ready-made integrations with 1C products and corporate infrastructure. MODX gives developers a high degree of control over project structure, HTML, and custom application logic.

We select the CMS after defining the project requirements. WordPress may be the best choice for one project, MODX or 1C-Bitrix for another, while some projects are better suited to custom Laravel development.

A web studio's task is to select the technology according to the future website architecture, data volume, integrations, performance requirements, and development plan for the next several years.

The cost depends on the amount of planning required, the number of unique page types, design, catalog functionality, integrations, and application logic. The number of pages alone rarely determines development complexity: a website with 500 similar pages may be easier to build than a 30-page project containing calculators, integrations, and several data models.

Our estimates separately account for analysis and planning, UX/UI design, responsive front-end development, MODX programming, integrations, data migration, testing, and launch.

This gives the client a clear understanding of how the budget is structured and which part of the cost relates directly to custom development.

Big Fish has been developing websites since 2011. We work with PHP, SQL, JavaScript, MODX, WordPress, 1C-Bitrix, Laravel, and modern front-end technologies.

For MODX projects, we design resource structures, TV fields, chunks, snippets, and custom xPDO models, optimize SQL queries, configure caching and SEO, set up servers, and develop integrations. After launch, we can provide technical support and continue developing the project.

Companies can contact us to create a new MODX website or audit an existing project, improve performance, fix errors, migrate the website to a new server, add functionality, or continue developing an established website.

MODX remains a strong choice for companies that need a custom corporate website with controlled architecture. The platform combines custom design, PHP development, proprietary data structures, integrations, SEO, and convenient content management.

A properly designed project can evolve for years: new services and business areas can be added, catalogs expanded, landing pages created, external systems connected, and interfaces updated without rebuilding the entire content management system.

Big Fish web studio can create a turnkey MODX website, conduct a technical audit of an existing project, or take over its ongoing support and development.

We Develop Turnkey MODX Websites

Big Fish web studio designs and develops corporate websites on MODX: from structure, prototypes, and design to programming, integrations, SEO preparation, and launch. We will evaluate your requirements and propose a technical solution for your project.

Discuss Your Project