Before the technical conversation

A clearer web vocabulary.

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 web basics

The address, the place where a site runs and the difference between presenting information and supporting a process.

Domain

The memorable address people use to reach your website, such as example.com.

Hosting

The server resources and operating environment that make a website or application available.

Website

A connected set of public pages that helps people understand your business and take a useful next step.

Web application

Software used in a browser to carry out a task or support a business process.

Planning and building

How an idea becomes a working interface, what happens behind it and where editing or integrations fit.

Prototype

An early representation used to discuss the structure, interaction or direction of a product.

Frontend and backend

The browser-facing interface and the server-side rules that work together to deliver a feature.

CMS

A content management system that lets authorized people edit defined website content.

Integration

A defined connection that lets separate systems exchange information or coordinate a task.

Being found and understood

How search systems discover and interpret public content, and why visibility needs realistic expectations.

SEO

Search engine optimization: making public content easier to discover, understand and use.

Indexing

The process by which a search system considers a page for inclusion in its searchable collection.

Structured data

Machine-readable descriptions that explain the meaning of information already present on a page.

AI search

Search and answer tools that use AI to select, summarize or combine information from sources.

Security and continuity

The everyday measures that help protect a service and make recovery possible when something goes wrong.

HTTPS

An encrypted connection between a browser and the website it is communicating with.

Updates

Controlled changes to software that address fixes, security issues or supported functionality.

Backups

Retained copies of required information that can be used in a tested recovery procedure.

Maintenance

Agreed ongoing work that keeps a website or application usable and supported.

Ownership and agreement

What you control, what needs to be handed over and how to keep the agreed project understandable.

Source code

The human-readable files that describe how software is built and behaves.

Domain ownership

The registration rights and account control needed to keep and manage your business address.

Project scope

The shared description of what will be delivered, what is excluded and how completion is assessed.

Put the terms into context.

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
TELL US WHAT YOU NEED

Tell us about
your project.

Describe what you do and what you need. A few sentences are enough to get started.

What do you need?

In this local preview, you can prepare and download a summary. This form does not send data to IT Officium.

ILLUSTRATIVE EXAMPLE

Website example

This is an example for a fictional company.
We build your website around your business.