Corporate Website Information Architecture: Menu, URL and Page Hierarchy
Corporate website information architecture: content inventory, user tasks, card sorting and tree testing, menu depth, permanent URLs and service–content linking.
React and Next.js web applications, headless CMS and API-first architecture, custom business process software, admin panels, PWAs and corporate design systems.
Some projects don’t fit a ready-made CMS mold. Then the requirements decide the technology: the rendering strategy (SSG, SSR, ISR), testable code, a documented API and a maintenance plan are settled from the start. No tool is imposed.
The choice is justified by content, business logic, SEO and cost.
The data model, permissions, testing and versioning are designed before any code is written.
Source code and documentation are handed over to you.
Scope, technical detail, deliverables and frequently asked questions are on each service’s own page.
Fast-loading web applications built for your business processes that scale under load.
Architectures that distribute content to web, mobile and other channels via APIs.
Turning business processes tracked with Excel or email into an application.
Screens that turn scattered operational data into panels you can decide from.
Browser-based applications for field teams working from their phones.
The same components and the same user experience across several portals and sites.
| Your situation | Recommended starting service |
|---|---|
| We want to turn a process run in Excel into an application | Custom Web Application and Business Process Software |
| We need a fast, SEO-friendly web application | React and Next.js Web Applications |
| We’ll use content across several channels | Headless CMS and API-First Web Architecture |
| Management reports are scattered | Management Dashboards and Corporate Reporting |
| The field team will use it on mobile | PWA and Mobile Web Applications |
ERP, CRM, API and XML connections, Microsoft Graph, website migration, maintenance and business process consulting.
Nginx, Apache and Microsoft IIS web servers, Docker and container deployment, CI/CD, Linux VPS and Virtualmin management, load balancing, high availability and web monitoring.
Corporate website information architecture: content inventory, user tasks, card sorting and tree testing, menu depth, permanent URLs and service–content linking.
Honeypots, signed time tokens, Turnstile and reCAPTCHA, Nginx rate limiting, content filters and reliable delivery of notification emails for preventing form spam.
Secure file upload: type validation with an allowlist and magic bytes, storage outside the web root, signed URLs, quarantine with ClamAV and safe serving headers.
Core Web Vitals monitoring: reading CrUX sources, the 75th percentile logic, setting up your own RUM with web-vitals, page group reports and regression alerts.
The default environment risk in Power Platform, separating development, test and production, solutions, connection references, environment variables, DLP and managing ownerless flows.
Compatibility scanning for a PHP upgrade, running PHP-FPM versions separately, gradual migration and a tested rollback plan.
React is a library for interface components; Next.js is an application framework on top of React that adds routing, server-side rendering, caching and build infrastructure.
When the same content will be used in more than one channel, when the front end will be developed separately, or when the performance target is very high. For a single-channel content site, a classic CMS is more economical.
Your own servers, Linux servers managed by Eretek, or the cloud. The decision is made based on security, cost and team competence.
First we listen to the current setup and the problem: which system, which bottleneck, which schedule. Then we send the scope, technology recommendation and deliverables in writing.