Web & Portal Development
Kornspire builds websites, customer portals and web platforms with Core Web Vitals, accessibility, structured data and search visibility engineered in from the start.
The problem
A site that looks finished and behaves unfinished
A great many websites pass a visual review and fail everything that follows: they load slowly on the mobile connections most visitors actually use, they cannot be operated by keyboard, their content is invisible to crawlers, and every content change needs a developer. Those are engineering problems, and they are not visible in a design mockup.
Signals you have this problem
- Mobile performance scores collapse even though the site looks fine on a desk
- Pages shift and jump while loading, and forms are hard to use one-handed
- Content updates require a developer and a deployment
- Pages are indexed inconsistently, or not at all, and nobody can say why
Our approach
Rendering strategy is a product decision
We choose per route whether content should be static, revalidated on a schedule, streamed from the server or rendered on the client — because that single decision drives load time, crawlability and hosting cost more than any other. Around it we build a design system, an accessible component layer, a metadata and structured-data architecture, and an editing workflow your team can actually use.
Design systems and component libraries
Tokenised colour, type, spacing and motion; documented, accessible components; light and dark themes designed separately rather than inverted.
Rendering and performance engineering
Per-route rendering strategy, image and font optimisation, bundle budgets, caching and Core Web Vitals work measured against field data.
Customer and partner portals
Authentication, role-based access, account and billing views, document exchange, notifications and audit trails.
Content architecture and CMS integration
Content modelling, headless CMS integration, editorial preview and publishing workflow so content changes do not need engineering time.
Accessibility engineering
Semantic structure, keyboard operability, visible focus, colour contrast, reduced-motion support and screen-reader testing against WCAG 2.2 AA.
Search and answer visibility foundations
Metadata architecture, canonical strategy, structured data, internal linking, sitemaps and crawl controls built in rather than retrofitted.
Outcomes
What changes for you
- Pages that stay fast on mid-range phones and unreliable networks
- A site operable by keyboard and screen reader, not only by mouse
- Content your team can publish without a deployment
- Technical foundations that make search and answer-engine visibility achievable
Deliverables
What you receive
- Design system with documented tokens and components
- Accessible, responsive page templates
- Metadata, canonical and structured-data implementation
- Sitemap, robots and crawl configuration
- Performance budget and measurement setup
- Editor guide for content publishing
Evidence
What you can check before you call
Each item below links to something you can verify yourself — our own product, this website, or the engineering playbook we publish.
- Our product
Upkilo, a multi-tenant SaaS in production
Our own platform for appointment-based businesses, live with paying customers: tenant isolation, per-tenant configuration and multi-location support.
Try it on upkilo.com(opens in a new tab) - This website
A statically rendered site
Every page prerendered at build time, with self-hosted, size-adjusted fonts and no client-side data fetching for content.
Measure it in PageSpeed Insights(opens in a new tab) - This website
Security headers in production
A strict Content Security Policy, HSTS with preload, and framing, MIME-sniffing and permissions policies on every response.
Check the headers(opens in a new tab) - This website
Analytics only after consent
Tag Manager loads with every analytics and advertising signal denied until a visitor accepts (Consent Mode v2).
Read how it works - Engineering playbook
ADR-002: Next.js for content-driven web
The rendering decision behind content-heavy sites like this one, with the alternatives considered.
Read ADR-002(opens in a new tab) - Engineering playbook
Security practices
Our baseline on every engagement: secrets, authentication, authorisation, input validation, transport, dependencies, an OWASP Top 10 review and data minimisation.
Read the practices(opens in a new tab) - Engineering playbook
Testing philosophy
What we test, at which level, and what we deliberately do not — the standard a handover is held to.
Read the philosophy(opens in a new tab) - Engineering playbook
Code review standards
What every change is reviewed for before it merges, and what blocks it.
Read the standards(opens in a new tab)
How it runs
The engagement, step by step
- 01
Architect
Information architecture, URL design, content model and rendering strategy per route, agreed before design work starts.
- 02
Design the system
Tokens, components and key templates in both themes, checked for contrast, focus order and behaviour at five breakpoints.
- 03
Engineer
Build against performance and accessibility budgets, with structured data and metadata generated from one source of truth.
- 04
Measure and tune
Lab and field performance measurement, accessibility audit, crawl and index verification, then targeted fixes before launch.
- Next.js
- React
- TypeScript
- Tailwind CSS
- Headless CMS
- Edge and CDN caching
- Schema.org JSON-LD
Typical engagements
What this looks like in practice
Illustrative shapes of work rather than client stories. We publish client work only with the client's consent and with real figures, so these describe the problem and the approach instead.
Corporate site with a real content operation
Marketing pages, insights and careers content published by non-developers, on a platform with performance budgets that hold over time.
Authenticated customer portal
Self-service account access, documents, requests and status — reducing inbound support volume for routine questions.
Multi-region public platform
Locale-aware routing, hreflang, region-specific content and a crawl strategy that keeps regional pages distinct rather than duplicated.
Answers
Web & Portal Development: questions
What is web and portal development?
Web and portal development is the design and engineering of browser-based products — public websites, authenticated customer or partner portals, and internal web platforms — including their performance, accessibility, security and search-visibility characteristics.
Which framework does Kornspire build websites with?
Next.js with React and TypeScript is our default for product-grade sites, because it lets each route choose its own rendering strategy and gives strong control over performance and metadata. The default is not dogma: a brochure site with little interactivity may be better served by a simpler static generator, and we say so when that is the case.
Will my team be able to edit content after launch?
Yes. Content that changes regularly is modelled and moved into a headless CMS with editorial preview, so publishing is a content task rather than a deployment. We document the model and train the people who will use it.
Is accessibility included or an extra?
Included. Semantic structure, keyboard operability, focus visibility, contrast and reduced-motion support are part of the build and part of the definition of done. WCAG 2.2 AA is the working standard; where a specific interaction cannot meet it, we document the limitation rather than quietly ship it.
Can you improve an existing site instead of rebuilding it?
Often, yes — and it is usually the cheaper answer. We audit performance, accessibility, crawlability and code health first, then propose the smallest set of changes that moves the metrics that matter to you. A rebuild is recommended only when the existing foundation makes those changes more expensive than replacing it.
Deep dives
5 detailed articles on this topic
Longer technical pieces, each covering one specific decision inside this service. Written to be argued with, not skimmed.
Keep reading
Related services
Considering web & portal development?
Tell us the outcome you need and the constraints you are working inside. You will get a straight answer about whether this is the right service, a smaller one, or none of ours.
Prefer email? hello@kornspire.com