Domain
The memorable address people use to reach your website, such as example.com.
Twenty useful terms for planning a website or application, asking better questions and understanding a proposal.
Start with the subject that matters to you. Each explanation connects a technical term with a practical decision, an example and questions worth asking before work begins.
The address, the place where a site runs and the difference between presenting information and supporting a process.
The memorable address people use to reach your website, such as example.com.
The server resources and operating environment that make a website or application available.
A connected set of public pages that helps people understand your business and take a useful next step.
Software used in a browser to carry out a task or support a business process.
A layout that adapts its content and controls to different screen sizes.
How an idea becomes a working interface, what happens behind it and where editing or integrations fit.
An early representation used to discuss the structure, interaction or direction of a product.
The browser-facing interface and the server-side rules that work together to deliver a feature.
A content management system that lets authorized people edit defined website content.
A defined connection that lets separate systems exchange information or coordinate a task.
How search systems discover and interpret public content, and why visibility needs realistic expectations.
Search engine optimization: making public content easier to discover, understand and use.
The process by which a search system considers a page for inclusion in its searchable collection.
Machine-readable descriptions that explain the meaning of information already present on a page.
Search and answer tools that use AI to select, summarize or combine information from sources.
The everyday measures that help protect a service and make recovery possible when something goes wrong.
An encrypted connection between a browser and the website it is communicating with.
Controlled changes to software that address fixes, security issues or supported functionality.
Retained copies of required information that can be used in a tested recovery procedure.
Agreed ongoing work that keeps a website or application usable and supported.
What you control, what needs to be handed over and how to keep the agreed project understandable.
The human-readable files that describe how software is built and behaves.
The registration rights and account control needed to keep and manage your business address.
The shared description of what will be delivered, what is excluded and how completion is assessed.
A useful project conversation starts with what your business needs to achieve. The technology and the scope can then follow that purpose.
See how we work