Technologies · Next.js
Next.js for sites that must be fast and found.
For marketing sites, product fronts and portals where search ranking and first-paint speed both matter. Pages render on the server, so crawlers and visitors get real HTML.
01
When we choose it, and when we don’t
The honest version
No stack is right for every job. This is the test ATPL applies before recommending it.
We choose Next.js when
- The site needs to rank. Every page is server-rendered HTML with proper metadata, structured data and a sitemap, not an empty shell filled by JavaScript.
- Content and application live together: a marketing site with a logged-in area, or a product with public pages.
- The team already works in React and wants one framework for routing, images, fonts and deployment.
We don’t when
- A content site a non-technical team must edit daily with no developer on hand. WordPress with a managed host is simpler to operate.
- A pure internal dashboard with no search requirement, where a plain React single-page app is lighter.
02
How we approach this
Approach
This website is built on Next.js 16: every page you are reading is server-rendered, with the page transition layered on top of real HTML. Client Next.js work is named as clients confirm it.
01
Scoped to one job first, so the first release is small and real.
02
Source code in a repository you control from day one.
03
The same engineers support what they built after launch.
04
Questions people ask
FAQ
The questions asked before buying, answered plainly. If yours is not here, ask it on the contact page.
Yes. Next.js renders each page to HTML on the server, so search engines and AI crawlers read the full content, titles and structured data without running JavaScript. ATPL’s own site runs on it for that reason.
React is a library for building interfaces in the browser. Next.js is a framework around React that adds server rendering, file-based routing, image and font optimisation and a production build. You use React inside Next.js.
A company website on Next.js from ATPL typically costs more than a WordPress site of the same size, because each template is hand-built, and less to run, because there are no plugins to patch. Ask for a quote with your page list and we will price both options.
Yes. Content can live in files in the repository, in a headless CMS, or in ATPL’s own Openextcms, and Next.js renders it at build or request time. Which fits depends on how often your team publishes.
Continue to
TechnologiesReactInterfaces that stay fast as they growOpen ServicesWebsitesCompany sites that earn enquiriesOpen ServicesWeb applicationsTools your team keeps open all dayOpen
