Planning a Separate Mobile Version Without Cloning the Whole Site

Some clients ask not for a responsive theme, but for a completely separate mobile version. That sounds straightforward until you realize how quickly two parallel sites turn into a maintenance burden.

The practical question is not just “can Evolution CMS detect mobile devices?” It is whether the mobile experience can be split at the template level without duplicating content and business logic.

The safer architecture

• keep one content tree,
• switch templates or chunks by device detection,
• avoid creating a second copy of every page unless the content really differs,
• centralize the detection logic instead of scattering it through many templates.

If the mobile site only changes layout and some UI blocks, template switching is far safer than creating a second content structure. Cloned resources almost always drift apart and become difficult to support.

A dedicated mobile version only makes sense when mobile content genuinely differs. Otherwise, a shared content model with device-aware templates is the cleaner long-term solution.