--- title: "Project Language: Agency Terms Explained" lang: en type: glossary canonical: https://www.arocom.de/en/glossary alternate: https://www.arocom.de/woerterbuch last_updated: 2026-04-16 --- # Project Language: Agency Terms Explained The arocom Project Language glossary explains 48 key terms from agency and web project workflows: from deployment to sprint to GEO. Each entry is concise, precise, and includes an example sentence from real projects. Aimed at decision-makers who commission web projects, not code them. Informed clients make better projects. For both sides. Terms from Drupal projects, precisely explained, with insights from 160+ projects. Every web project has its own language. API, staging, content model, technical debt, terms that come up in briefings and aren't always explained. Here they are. Precise, no hedging. ## Project Management ### Ticket A digital task in the project management system. Contains description, priority, assignee and status. Everything that needs to be done is tracked as a ticket. *Example:* Please create a ticket so we can schedule the change. [More about ticket systems](https://www.arocom.de/en/knowledge/development/ticket-system) ### Approve To authorize, sign off, give permission. Used when work has been reviewed and confirmed as correct. *Example:* The design was approved by the client, we can start development. ### Assign To designate a task to a specific person. In the ticket system, someone is marked as responsible. *Example:* I'll assign the ticket to our frontend developer. ### Change Request A ticket requesting modification to an existing feature. Different from a Feature Request, which asks for something entirely new. *Example:* What changes does the Change Request cover exactly? ### Feature Request A request for a new feature that doesn't exist yet. Described in a ticket, then estimated and scheduled. *Example:* We've received a Feature Request for multilingual support. ### Sprint A fixed time period (usually 2 weeks) in which a defined set of tasks is completed. Each sprint ends with a demonstrable result. *Example:* In the next sprint, we'll implement the contact form redesign. [More about Scrum](https://www.arocom.de/en/knowledge/development/scrum) ### Definition of Done Pre-agreed criteria for when a task is considered complete. E.g.: code written, tested, verified on staging, signed off by the client. *Example:* Per our Definition of Done, a feature isn't done until it's also accessible. ### Review To check and evaluate whether a task has been completed correctly. Both internally (code review by colleagues) and externally (sign-off by the client). *Example:* Could you review the new copy on staging? ### High (Critical Path) Ticket priority: very high. No other task can proceed until this one is resolved, it blocks project progress. *Example:* The ticket was prioritized as High because it blocks the launch. ### Urgent / Business Critical The highest priority level. Mission-critical, must be addressed immediately, e.g. security vulnerabilities or outages. *Example:* The site is down, that's Business Critical. ### Rejected Status: declined. The result doesn't meet requirements and needs rework. *Example:* The ticket was rejected, the mobile layout still needs work. ### Error Report A ticket documenting a bug. Ideally includes: What happens? What should happen? Which device/browser? Screenshot? *Example:* Please create an Error Report with a screenshot, that helps us fix it faster. ### Service Request A request for a service by arocom, e.g. create a new user, renew SSL certificate, restore a backup. *Example:* We need a Service Request for CMS access for the new colleague. ### Support Request A ticket requesting help. Can be technical (something's broken) or content-related (how do I manage content?). *Example:* For the image upload question, please create a Support Request. ### Scope The agreed deliverables of a project or sprint. What's included, what's not? Clear scope management prevents projects from spiraling. *Example:* That wasn't in the original scope, we'll create a Change Request for it. ## Web Development ### Feature A function of the website, e.g. search, contact form, image slider or multilingual support. *Example:* The multilingual feature is one of the most complex on the site. ### Deploy To transfer and activate new software or changes on a server. Today mostly automated via CI/CD pipelines. *Example:* We'll deploy the changes tonight to the live server. [More about deployment](https://www.arocom.de/en/knowledge/development/deployment) ### Launch To make the website publicly accessible for the first time (or after a relaunch). The big moment everyone works toward. *Example:* The launch is planned for the 15th of this month. ### Relaunch Complete overhaul of an existing website, technically, content-wise, or both. Not to be confused with a redesign (visual only). *Example:* Even the best website benefits from a relaunch after many years. [More about relaunch](https://www.arocom.de/en/knowledge/development/relaunch) ### CMS Content Management System, software that lets you manage your website content without programming skills. arocom works with Drupal CMS. *Example:* Through the CMS, you can update text and images yourself at any time. [More about Drupal CMS](https://www.arocom.de/en/knowledge/drupal/what-is-drupal) ### Module A building block that adds new functionality to the CMS. Contrib modules come from the community (free), custom modules are built specifically for your project. *Example:* For the search feature, we use a proven contrib module. [Top Drupal modules](https://www.arocom.de/en/knowledge/drupal/top-module) ### Custom Code Code written specifically for your project. Required when no existing solution covers your requirements. *Example:* For the ERP system integration, we need custom code. ### Refactoring Rewriting code without changing its behavior, for better maintainability, performance, or compatibility with new versions. *Example:* The upgrade to Drupal 11 required some refactoring. ### CI/CD Continuous Integration / Continuous Deployment, automated processes that check, test, and deploy code changes. Reduces errors and accelerates releases. *Example:* Our CI/CD pipeline tests every change automatically before it goes live. [More about DevOps](https://www.arocom.de/en/knowledge/development/devops) ### API Application Programming Interface, an interface through which two systems communicate. E.g. an API connects your website with your CRM or ERP. *Example:* Through the API, we sync product data from your inventory system. ### Accessibility (BFSG) Designing websites so they're usable by everyone, including people with visual impairments, motor disabilities, or screen readers. Legally mandatory in Germany since June 2025. *Example:* Under the BFSG, the website must be accessible by the end of 2025. [More about accessibility](https://www.arocom.de/en/accessibility) ### Responsive Design The website automatically adapts to any screen size, desktop, tablet, smartphone. Today's standard, not an optional extra. *Example:* In responsive design, we test every page across three screen sizes. [More about responsive design](https://www.arocom.de/en/knowledge/drupal/responsive-webdesign) ## SEO & GEO ### 404 (Error) Page not found. The server can't locate the requested URL. Happens when a page was deleted or moved without setting up a redirect. *Example:* We set up 184 new redirects so no more 404 errors occur. ### Redirect Automatic forwarding from an old URL to a new one. Essential during relaunches so visitors and search engines can still find the content. *Example:* For all old blog URLs, we set up 301 redirects to the new knowledge articles. ### SEO Search Engine Optimization, all measures to help your website rank in Google. Covers technical, content, and link-building aspects. Increasingly complemented by GEO. *Example:* Technical SEO is the foundation, content and links build on top. [Our GEO optimization](https://www.arocom.de/en/services/geo-optimization) ### GEO Generative Engine Optimization, visibility not just in classic search results, but also in AI answers (ChatGPT, Google AI Overviews, Perplexity). The next evolution after SEO. *Example:* Thanks to GEO, arocom is found not just on Google but also cited by AI systems. [GEO explained](https://www.arocom.de/en/knowledge/seo-geo/geo-explained) ### AI Overviews AI-generated summaries that Google shows directly above search results. Answers questions without users visiting a website, making it even more important to be cited there. *Example:* Our knowledge articles are structured so they get cited in AI Overviews. [More about AI Overviews](https://www.arocom.de/en/knowledge/seo-geo/ai-overviews) ### Core Web Vitals Google's metrics for user experience: How fast does the page load (LCP)? How quickly does it respond to clicks (INP)? How stable is the layout (CLS)? Affects ranking. *Example:* Our Core Web Vitals are in the green, the site loads in under 2 seconds. [More about PageSpeed](https://www.arocom.de/en/knowledge/seo-geo/pagespeed) ### Schema Markup Invisible metadata in the code that helps search engines understand page content. Enables rich results (stars, FAQ, images) in search results. *Example:* The FAQ schema ensures our common questions appear directly on Google. ### E-E-A-T Experience, Expertise, Authoritativeness, Trustworthiness, Google's quality criteria for websites. The more real experience and competence visible, the better the ranking. *Example:* Our knowledge articles demonstrate E-E-A-T through real project examples. ### Canonical URL The official URL of a page. Prevents Google from treating the same content at multiple addresses as duplicates. *Example:* Every page has exactly one canonical URL, that avoids duplicate content. [More about canonical tags](https://www.arocom.de/en/knowledge/seo-geo/canonical-tag) ## AI & Automation ### Prompt An input or instruction to an AI system. The more precise the prompt, the better the result. Prompt engineering is the art of asking the right questions. *Example:* With the right prompt, AI drafts a meta description in seconds. [More about prompts](https://www.arocom.de/en/knowledge/ai/prompt) ### RAG Retrieval Augmented Generation, a technique where AI doesn't just answer from its training but also looks up your documents. Makes AI answers current and fact-based. *Example:* With RAG, the AI search on your website can answer questions using your own content. [More about RAG](https://www.arocom.de/en/knowledge/ai/rag) ### Hallucination When AI produces convincing-sounding but factually incorrect statements. That's why AI-generated content always needs human quality control. *Example:* ChatGPT hallucinated, the cited study doesn't even exist. ### AI Agent An AI system that can independently execute tasks, e.g. answer emails, analyze data, or create content. Integrated into existing processes via workflows. *Example:* Our AI agent screens incoming support requests and routes them to the right department. [AI integration at arocom](https://www.arocom.de/en/services/ai-integration) ### Token The billing unit of AI models. One token equals roughly one word or word fragment. AI costs are calculated per token consumed. *Example:* A request to an AI model uses several hundred tokens, that costs just a few cents. ## Server & Operations ### Staging The test environment of your website. Development and testing happen here without affecting the live site. Only accessible with credentials. *Example:* The changes are ready on staging, can you test them there? ### Live (Production) The production system, the publicly accessible website. Changes on live are immediately visible to all visitors. *Example:* We don't make configuration changes directly on live, that's what staging is for. ### Clear Cache Reset the website's temporary storage. Needed when changes were made but the old version still shows. Can be triggered by the client in the CMS. *Example:* If the changes aren't visible, please clear the cache once. ### Uptime The time your website is reachable, expressed as a percentage. 99.9% uptime means a maximum of 8.8 hours of downtime per year. arocom monitors uptime proactively. *Example:* Our servers have 99.95% uptime, we monitor around the clock. [More about monitoring](https://www.arocom.de/en/knowledge/development/monitoring-icinga) ### SSL / HTTPS Encrypted connection between browser and server (the lock icon in the address bar). Standard and a Google ranking factor. Without HTTPS, browsers show a warning. *Example:* The SSL certificate renews automatically, we take care of that. ### Backup Regular copies of your website and database. In emergencies (hack, accidental deletion), yesterday's state can be restored. *Example:* Thanks to daily backups, we restored the deleted content within an hour. ### DNS Domain Name System, translates domain names (www.arocom.de) into IP addresses. DNS changes take up to 48 hours to propagate worldwide. *Example:* We'll do the DNS switch over the weekend, propagation won't affect anyone. [More about DNS](https://www.arocom.de/en/knowledge/drupal/dns)