DEV GLOSSARY

API

devs

A set of rules that allows software programs to communicate with each other

non-devs

Like a waiter taking your order from the frontend to the backend and bringing the result back

clients

Used when clients request things like 'Can the contact form send to my CRM?'

why it's important

Connects frontend to backend systems like WordPress or databases

backend

devs

The server-side part of a web application that processes data, runs logic, and communicates with databases

non-devs

The behind-the-scenes engine that makes the site work

clients

Clients don't see it directly, but they use tools (like WordPress) powered by it

why it's important

Powers features like content management, authentication, and integrations

CMS

devs

Software that allows users to manage digital content without needing to code

non-devs

A website editor that lets you change text, images, and more

clients

Often where clients do most of their post-launch work

why it's important

Makes it easier for clients or content teams to manage content

component

devs

A reusable piece of frontend UI code (e.g., a button or a card)

non-devs

Like a Lego block that can be reused throughout the site

clients

If clients want the same hero section as the homepage, it's reused as a component

why it's important

Encourages consistency and speeds up development

frontend

devs

The part of the website or application that users interact with directly, typically built with HTML, CSS, and JavaScript

non-devs

It's the “face” of the website—what people see and click on

clients

This is what the client usually reviews, gives feedback on, and signs off

why it's important

Determines the user experience and design implementation

fullstack

devs

Development that covers both frontend and backend components

non-devs

Like having someone who can design the storefront and build the warehouse

clients

It helps clients get a more cohesive, end-to-end product

why it's important

Fullstack developers can work across the entire system, improving efficiency

headless CMS

devs

A content management system that stores and manages content separately from the frontend

non-devs

A client-friendly editor/dashboard for updating website content

clients

Clients often use it daily to update pages, blog posts, etc

why it's important

Enables non-developers to manage content without needing to touch code

Next.js

devs

A React-based frontend framework for building server-rendered or statically generated websites

non-devs

A powerful toolkit developers use to build fast, modern websites

clients

Impacts how fast the site loads and how well it ranks on Google

why it's important

Offers speed, SEO benefits, and flexibility for custom frontend experiences

route / routing

devs

The mapping between URLs and content/components shown on a page

non-devs

The GPS system that determines what shows up when someone goes to a page

clients

Related to how the site is structured (e.g., homepage, /about, /contact)

why it's important

Enables developers to organize site structure and navigation

slug

devs

The part of a URL that identifies a page (e.g., /about-us)

non-devs

The name at the end of a link

clients

Clients often write or request custom slugs for clarity or SEO

why it's important

Slugs impact URLs and SEO