| Astro | The tool that turns Homio’s files into a website. You don’t need to learn it to edit content |
| Tailwind CSS | The styling system. Classes like bg-sage or mt-8 in components set colors and spacing |
| Static site | A website made of ready-made files, with no database or server code to run, so it is simple to host |
| Node.js | The program that runs Astro on your computer |
| npm | Comes with Node.js. Installs the theme’s tools (npm ci or npm install) and runs its commands (npm run dev) |
| Terminal | A window where you type commands. In VS Code: Terminal → New Terminal |
| Dev server | The local copy of your site at http://localhost:4321/ that updates when you save. Started with npm run dev |
| Build | Turning the files into the finished website in the dist/ folder, with npm run build |
| Deploy | Putting the built site on the internet, on a host such as Netlify, Vercel, or Cloudflare Pages |
| Route | A file in src/pages/ that becomes a page and decides which sections it shows |
| Section | One full-width block of a page (hero, plans, FAQ). A component plus a content file |
| Component | A .astro file that draws part of the page. You rarely need to edit these |
| Content file | A .md or .mdx file in src/content/ that holds text and options |
| Markdown | A simple way to format text: **bold**, ## heading, - list item |
| MDX | Markdown that can also use components (shortcodes) such as <Callout> or <JobTicket> |
| Shortcode | A ready-made component you can place inside an .mdx file. /components/ on your local site shows them all |
| Frontmatter | The settings block between two --- lines at the top of a content file, written in YAML |
| YAML | The key: value format used in frontmatter. Indentation matters |
| TOML | The key = value format of config.toml, grouped under [tables] |
| JSON | The "key": "value" format of the menu, language, font, social, and translation files |
| Collection | A folder of similar entries: services, areas, reviews, projects, job openings, blog posts |
| Entry | One file in a collection, which usually becomes one page |
| Slug | The part of the URL that names a page: deep-cleaning in /services/deep-cleaning/. Comes from the file name, or customSlug |
| Named block | A section’s settings written inside a page’s frontmatter, to change that section on that page only |
| Layout | One of the looks a section can have, chosen with options.layout. /elements/ previews them |
| Draft | A page with draft: true. It shows on the dev server but is not built |
| i18n | Short for “internationalization”: the multi-language setup |
| Schema | The list of fields a content file may have. npm run astro-check and the build report mistakes in files that have one. Section files and the contact page file have none, so check those pages in the browser |
| Lucide | The free icon set Homio uses. Any name from lucide.dev/icons works, for example "House" or "Wrench" |
| Dark mode | The dark color scheme. Visitors switch with the light/dark button; [settings.colorScheme] default sets what they see first |
| Open Graph image | The preview picture shown when a link is shared on social media or in chat apps. Homio generates one per page |
| Structured data | Hidden JSON-LD in each page that tells search engines about your business, services, areas, and prices |
| Sitemap | A list of every page, for search engines (/sitemap-index.xml) |
llms.txt | A proposed format: a Markdown map of your site, with your business facts first, that AI assistants can read |
| Git | A tool that saves versions of your project, so you can undo any change |
| Commit | One saved version in git |
| Diff | A view of exactly what changed in a file: removed lines and added lines |
