Glossary

Technology

Terms from this group, explained plainly. All entries are in the full glossary.

  • API

    The way two systems exchange data, for example a website fetching stock levels from a warehouse program.

    In practice: Zdzichu: the device asks my server, and the server asks an AI model

  • Block editor (Gutenberg)

    The WordPress editor in which you build a page from blocks: paragraphs, photos, buttons, layouts.

    It lets you change content and layout without a developer, with a live preview. In modern block themes, the header, footer and templates are edited the same way. A well-prepared theme limits the choices to what fits the design, so it can't be broken by accident.

  • CI/CD

    Automation of building and deploying: an approved change in the code reaches the server on its own.

    It reduces the most common source of failures when publishing, which is copying files by hand.

    In practice: Dyżur: every change builds itself in GitHub Actions

  • Docker

    A tool that packages an application together with its environment so it runs the same way everywhere.

    This makes deployment to a new server repeatable and removes the need to configure the machine by hand.

    In practice: Dyżur: the panel runs in a container on my server

  • Framework

    A ready-made skeleton to build an application on, so you don’t have to write everything from scratch.

    Astro and Next.js are popular for websites, Flutter for mobile apps. The choice of framework affects how fast the site is and who will be able to develop it later.

  • Frontend and backend

    The frontend is the part you see in the browser; the backend is the server, logic and database working in the background.

    A simple business card site may have no backend at all. A shop, a customer panel or a login already needs one.

    In practice: Zdzichu: the device on the desk is the frontend, my server is the backend

  • Git

    A system that records every change to the code and lets you go back to it.

    With Git you know who changed a given line, when and why, and a failed change can be undone in seconds. The code is also kept in a remote repository (for example GitHub), so a computer failure does not mean losing the project.

  • Headless CMS

    A content editing system that doesn’t render the website: it hands only the data to another application.

    You keep the content in the panel, and a separate application (the frontend) fetches it through an API and takes care of the look. It gives technical freedom, but it means two systems to maintain instead of one. For a typical business website, plain WordPress is simpler and cheaper to run.

  • HTML, CSS, JavaScript

    The three core languages of websites: HTML is the content and structure, CSS is the look, JavaScript is the behaviour and interaction.

  • JSON

    A simple data format that programs use to exchange information.

    It looks like a list of fields with values and is readable by humans. Most APIs return data in JSON. In SEO it is also used for structured data (JSON-LD), which describes the page to search engines.

  • Progressive web app (PWA)

    A website you can add to your phone’s home screen and use like an app, without an app store.

    It works on any phone and computer from a single codebase and can partly work offline. It has less access to phone features than an app installed from a store.

    In practice: Guide: app or website

  • REST API

    The most popular way for applications to exchange data over the internet using ordinary web addresses.

    An application sends a request to an address (for example, get the list of posts) and receives a response, usually in JSON. WordPress has its own REST API. Every endpoint of such an API has to be secured just like the website: check who is asking and what they are allowed to do.

  • Staging environment

    A copy of the website where changes are tried out before they go to the live site.

    A plugin update or a new feature runs on the copy first. If something breaks, customers don't see it. It is standard for websites that earn money, because testing on the live site risks downtime at the worst possible moment.

  • VPS (virtual private server)

    A separate slice of a physical server, with its own system and resources just for you.

    It gives full control over the configuration, but also full responsibility: system updates, security and backups are on you or on the developer. Shared hosting is simpler; a VPS is more flexible and usually faster as traffic grows.

Ready to start?

Let’s start with a conversation

Describe what you want to build. The reply contains the scope, the price and the timeline. The inquiry costs nothing and commits you to nothing.