Web Design & Development department

It designs, builds, integrates and operates your website — on WordPress, Shopify, Wix, Wix Studio or Webflow — as a managed department, inside the CMS and domain you already own. Scope is agreed during design and can run from a single rebuild through to ongoing maintenance and improvement.

Yes. WordPress development covers custom and child themes, custom post types, plugin configuration and custom plugin development, and WooCommerce where ecommerce is part of the brief.

Yes. Shopify development covers store architecture, theme customisation, Liquid sections, checkout configuration and app integrations, sized to whether the store is a simple catalogue or a high-volume operation.

Yes, at both levels. Standard Wix covers business sites with built-in CMS, bookings and ecommerce; Wix Studio adds Velo development, dynamic content and layout control for sites that have outgrown the standard configuration.

Yes. Webflow development covers CMS collections, responsive layouts, interactions and custom code, and suits marketing sites that need frequent, editorially-led page changes.

On requirements, not preference: content structure, ecommerce needs, integrations, who will manage the site day to day, and the maintenance plan. A content-heavy B2B site, a high-volume store and a campaign-led marketing site rarely land on the same platform.

Existing technology gets evaluated first. Where a theme or plugin already meets the requirement, it gets configured or customised; a full rebuild only happens where the existing setup genuinely can’t support what the site needs to do.

Yes, where no existing plugin covers the requirement. Custom plugin development is scoped like any other feature: what it needs to do, how it’s maintained, and what happens when WordPress core updates.

Yes. Existing sites get audited first — content, structure, integrations and what’s actually broken — before a redesign scope is agreed, so the rebuild fixes the real problem rather than just refreshing the visual design.

Yes, including WordPress to Shopify, Shopify to another platform, or Wix and Webflow in either direction. Content, URL structure and redirects are mapped deliberately so existing SEO value carries across rather than resetting.

Yes, on WooCommerce or Shopify depending on fit. Store architecture, product and category structure, checkout and payment configuration are built around your actual catalogue, not a generic template.

Yes, under named access at the permission level you set. Integrations connect the CRM, payment gateway, email platform and marketing tools you already run, rather than requiring you to switch systems.

Yes, where an existing integration doesn’t cover the requirement. Custom API development is built and documented specifically for the systems it connects, with error handling and authentication scoped up front.

Yes, from a rule-based FAQ bot through to an AI assistant trained on your content, policies and product data, with a defined handoff to a person for anything outside its scope.

No. The assistant is built to handle repeatable questions and route anything else to your team with context attached — it’s designed to reduce the queue a person deals with, not replace the person.

Yes. Registration, login, role-based access and account dashboards are built to the access rules your business needs, whether that’s a customer portal, a membership site or an internal tool.

Yes. Calculators, estimators, configurators and quizzes are built as custom functionality, scoped around the specific inputs and logic the tool needs to run.

Yes. Landing pages are built and connected to forms, CRM routing and analytics as one system, so results from one campaign inform how the next landing page is built rather than starting from a blank page each time.

Yes. Maintenance covers core, theme and plugin updates, monitoring, backups and small content changes on a standing schedule, reviewed on the operating cadence described on this page.

Yes. Performance work covers image optimisation, caching, script review and Core Web Vitals, measured before and after so the improvement is verifiable rather than assumed.

Technical implementation, yes — schema, URL structure, redirects, sitemaps and page speed. Search strategy, keyword research and content planning sit with Nexoryl’s SEO & AEO department; the two work from the same plan rather than working separately.

Yes. An accessibility review covers semantic markup, keyboard navigation, colour contrast and screen-reader compatibility, with fixes prioritised by impact rather than addressed as a single pass.

You do, always. The domain, hosting account and any customer or business data stay in your name regardless of who manages the site day to day; access is granted to Nexoryl and can be revoked at any time.

Yes, and it’s the usual approach. Most engagements start with a single platform build or a defined service, such as a redesign or an integration project, with process documented before scope widens.

Yes. The department can take on a defined layer — development on one platform, or a specific integration — while your internal team or existing agency retains the rest, with the boundary agreed in writing.

With a review of the current site, goals and technical constraints, followed by a design stage that agrees platform, scope and measures. From there the build runs through the sequence described on this page, and moves into ongoing operation once it’s live.