Building so people using keyboards, screen readers, magnification or high contrast can complete the same tasks as everyone else. It is a legal requirement in several markets, and the same work improves usability for everyone, including anyone on a phone in bright sunlight.
The routing system introduced in Next.js 13, where folders define URLs and components run on the server by default. It replaced the older Pages Router and is the reason a Next.js project can serve marketing pages, an application and an API from one codebase.
Three measurements Google uses to score real-world page experience: how quickly the main content appears, how quickly the page responds to a tap or click, and how much the layout jumps while loading. They influence search ranking and correlate strongly with conversion.
لماذا يهم: A slow score is a revenue problem before it is a ranking problem.
A documented set of reusable components, colours, spacing and type rules shared across a product. Its value shows on the fifth screen rather than the first: new pages get assembled from existing parts instead of designed and rebuilt each time.
A content management system that stores and edits content but does not render the website. The front end fetches content over an API, so your team edits in a familiar admin while the site itself stays a fast custom build.
لماذا يهم: It is the middle path between WordPress and a fully custom site.
The step where JavaScript attaches interactive behaviour to HTML the server already sent. Until it finishes, the page looks ready but buttons do nothing. Heavy hydration is a common cause of pages that appear fast in screenshots and feel slow to use.
A compromise between static and dynamic pages. A page is served from a pre-built cache, and the server quietly rebuilds it in the background after a set interval. Visitors get static speed while content stays current without a full site rebuild.
Structuring an application so language, currency, date format and text direction are configuration rather than content. Done at the start it costs little; added afterwards it usually means touching every screen, which is why bilingual requirements belong in the first scope conversation.
React components that execute on the server and send rendered output rather than code to the browser. Database queries can happen directly inside them, and the libraries they use never reach the visitor, which keeps the downloaded bundle small.
One layout that reflows to suit any screen size rather than separate desktop and mobile sites. Modern practice tests against mid-range Android phones rather than the newest iPhone, because that is what most visitors in most markets actually hold.
Building an interface so Arabic, Hebrew or Persian reads correctly, with layout direction set at the document level. Directional icons flip, object icons do not, and numerals stay left-to-right inside sentences. Retrofitting it later costs several times what it costs to plan.
لماذا يهم: A mirrored English layout is not an Arabic interface, and Gulf customers notice immediately.
The page is assembled into finished HTML on the server before it reaches the browser. The visitor sees content on first paint rather than a blank frame that fills in afterwards, and any crawler that does not run JavaScript still receives the full text.
لماذا يهم: Search engines and AI crawlers read server-rendered pages reliably; client-only pages often reach them empty.
Pages are built once at deploy time and served as plain files. Nothing is computed per visit, so pages load close to instantly and hosting costs almost nothing. The trade is that content changes require a rebuild, which can be automated on publish.
A defined way for one system to ask another for data or actions, without either knowing how the other is built. Your website, mobile app and accounting tool can all talk to the same API, which is why it is designed before the screens are.
Authentication proves who someone is; authorisation decides what they may do. They are separate problems and are frequently confused. Most access-control incidents are authorisation failures in systems whose login worked perfectly.
The structure of your data: which tables exist, what fields they hold and how they relate. It is the most expensive decision to reverse in any system, which is why it is designed and reviewed in plain language before any screen is built.
An API style where the client states exactly which fields it wants in a single request. It reduces round trips for complex screens, at the cost of more setup and more care around performance. Worth it for data-dense applications, overkill for simple ones.
A property where performing the same operation twice has the same effect as performing it once. It is what stops a retried payment webhook from charging or shipping twice, and it is the difference between an integration that works and one that works until it is busy.
A signed token a server issues after login, which the browser sends with later requests to prove identity. Because it is signed rather than encrypted, it should never carry secrets, and it needs a short lifetime plus a way to revoke sessions.
A versioned script that changes the database structure. Migrations run in order on every environment, so the staging database and the production database are provably the same shape. Without them, schema drift is discovered during an outage.
One deployment serving many separate customer organisations, each seeing only its own data. It is far cheaper to operate than one installation per client, and the isolation must be enforced at the query level in every single request.
A layer that lets application code work with database records as typed objects instead of hand-written queries. Prisma also generates migrations, so schema changes are versioned files that run identically on every environment rather than manual steps someone remembers to repeat.
A cap on how many requests one client may make in a period. It protects login forms from password guessing, contact forms from spam floods, and paid third-party APIs from a runaway loop that produces a large invoice overnight.
The most common API style, where each address represents a resource and standard verbs read, create, update or delete it. Its predictability is the point: any developer who joins later can guess how it works before reading the documentation.
Permissions attached to roles rather than to individuals, so an admin, a staff member and a customer each see a different system. Correctly built, the rules are enforced in the database query, not by hiding buttons in the interface.
لماذا يهم: Hiding a button is not security; the data must be unreachable, not merely invisible.
A message one system sends to another the moment something happens, rather than the second system asking repeatedly. Payment confirmations arrive this way. Because they are fire-and-forget, they must be built to survive duplicates and retries.
لماذا يهم: Badly built payment webhooks fail silently, which means orders that were paid for but never fulfilled.
Connecting two systems so information moves between them automatically. Most of the difficulty is never the connection itself; it is deciding which system is the source of truth when the two disagree about the same customer.
An automation platform that connects applications through visual workflows and can run on your own server. Because self-hosting removes per-task pricing and keeps data inside your infrastructure, it usually overtakes hosted tools somewhere around a couple of thousand tasks a month.
Running software on infrastructure you control instead of paying a vendor to run it. It removes usage-based fees and keeps data in your jurisdiction, and it transfers responsibility for backups, updates and monitoring to you or to whoever holds the maintenance retainer.
Software performing a repeated business process without a person moving data between tools. Value comes from frequency rather than complexity: a dull step running forty times a day returns far more than an elaborate one running twice a month.
A private logged-in area where your customers see their own projects, files, invoices and messages. Most are commissioned to stop the same four questions arriving by email, which is a smaller and faster build than replacing your project management tool.
The service that takes card details and moves money, such as Stripe, PayPal or PayTabs. Choice is regional rather than technical: acceptance rates, settlement currency and fees differ enough between markets to change how many customers complete checkout.
The security standard governing how card data is handled. The practical implication is that a well-built store never touches raw card numbers; the gateway collects them directly, which keeps almost all of the compliance burden away from your system.
Automation that tests and deploys code whenever it changes. Its practical value is that deployment stops being an event somebody performs carefully on a Friday and becomes a routine that happens the same way every time.
A short paid review of an existing codebase producing a written list of risks, what is salvageable, and a fix plan with estimates. It is the standard first step when taking over work from a previous developer, because quoting a rescue unseen is guesswork.
A defined chunk of work with its own deliverable and payment. Milestones convert a large commitment into several small ones, which limits how much either side can lose if the working relationship turns out to be wrong.
The smallest version that proves the core assumption, usually the one workflow people will pay for. It is not a cheap version of the full product. Everything not required to test that assumption is deliberately deferred.
The accumulation of small additions that were each reasonable alone. It is the most common reason projects run late, and it is managed by pricing changes openly rather than by refusing them, so the trade-off stays visible to whoever is paying.
A written statement of what will be built, what will not, and in what order. It exists so that a later request is a priced change rather than an argument, and it protects both sides equally.
لماذا يهم: A fixed price is only meaningful next to a fixed scope.
Who legally owns and can access the code after payment. It should be written into the agreement, with the repository under your own organisation from day one. Without that clause, leaving a supplier means rebuilding rather than transferring.
لماذا يهم: Ask for this before the project starts; it costs nothing then and is a negotiation later.
A full copy of the live system, with its own database, used to review work before customers see it. It is where you click through a feature and say no. Reviewing on the live site instead is how customers find bugs first.
Shortcuts taken to ship sooner, which make later changes slower. Some is a deliberate and sensible trade. The dangerous kind is undocumented, so nobody knows it exists until a small feature request turns out to take three weeks.
A numeric representation of a piece of text that places similar meanings close together. Embeddings are what let a search find the right paragraph when the user phrased the question in words that do not appear in the document.
Making a site legible and quotable to AI assistants rather than only to search engines. In practice: server-rendered content, structured data, direct answers under question headings, machine-readable files such as llms.txt, and consistent identity across third-party sources.
لماذا يهم: Buyers increasingly ask an assistant for a shortlist before they ever open a search engine.
When a language model states something false with complete confidence. It is the reason a customer-facing assistant must be grounded in retrieved documents and instructed to decline rather than guess, and why anything with legal or financial consequences keeps a human approval step.
A plain text file at the root of a site summarising what it contains and linking to its key pages, written for AI crawlers the way robots.txt is written for search crawlers. A companion llms-full.txt carries the whole site as Markdown.
A technique where an AI model answers from documents retrieved from your own content rather than from memory. It is what makes a chatbot about your business accurate, and it must be built to say it does not know when nothing relevant was found.
Machine-readable labels embedded in a page describing what it contains: a person, a service, a question and answer, a product. Search engines and AI systems use it to understand a page without inferring meaning from the layout.