Sitemap
Every page, in one place.
A human-readable index of every page on the IBC Denver site, organized the way our brain works. The robot version lives at /sitemap.xml.
Tell us what you need
Same form on every page. Same human inbox. We answer every inquiry — promise.
Products
Services
Resources
All field notes (23)
- → The most common mistake on incoming quote requests
- → A day in the reconditioning bay
- → Notes from the buy-back truck
- → The quietest week of the year
- → Cracks, hazes and stains: an honest guide to used tote grading
- → How to inspect a used IBC in 90 seconds
- → The trouble with the color blue
- → Inside our 9-stage hot-wash process
- → How to tell if a tote has been through one cycle too many
- → The hidden carbon cost of a brand-new IBC tote
- → Why we reject one in eleven totes that show up at the yard
- → The 275 vs. 330 gallon question, finally settled
- → Food-grade vs. industrial: what actually matters
- → Building a beekeeper's sugar feeder from a reborn tote
- → Why we photograph every tote
- → Why we stopped answering the phone in 2013
- → How pallet style affects IBC tote lifespan
- → The glycerin distillery that changed our buy-back program
- → Storing water in an IBC tote through a Colorado winter
- → Reading an IBC tote's data plate without losing your mind
- → The quiet renaissance of the plastic tote
- → Why stainless isn't always the answer
- → The most overlooked spec on a stainless IBC
About this sitemap
This page is the human-readable index of every page on the IBC Denver website. There is also a machine-readable sitemap at /sitemap.xml that search engines use to discover and re-crawl pages, and a robots.txt file at the root of the site that tells crawlers which pages they are welcome to visit.
We update this index whenever we add or remove a page. The blog section grows roughly every couple of months as we publish new field notes. The product, service, and resource sections change rarely — those pages are evergreen and we revise them in place rather than adding new ones.
Why we have a human-readable sitemap
Most websites only publish a machine-readable sitemap and assume that visitors will navigate via the menu. We publish a human-readable one for three reasons. First, the menu is fundamentally a designed structure that hides things — a sitemap shows everything at once. Second, accessibility tools and screen readers can use a flat list of pages more easily than a nested menu. Third, when we publish a new page that is not yet linked from the main navigation (a hidden landing page, a guest post, an experimental section), the sitemap is where it lives until we decide whether to add it to the menu.
Pages that are not in the main menu
A handful of pages on this site are deliberately not included in the main navigation menu and are only accessible through this sitemap or through internal links from other pages. They include the IBC Glossary, the Safety Notes, the Careers page, the Press Kit, and the Thank You confirmation. These exist because they are useful but they are not the kind of page we want to clutter the main menu with. They are documented in the sitemap so that anyone looking for them can find them.
If something is missing
If you arrived at this page from somewhere else and you are looking for a specific page that is not listed here, please write to us at hello@ibcdenver.com and tell us what you were looking for. The most likely explanation is that we removed a page (or never wrote one) and we should add a redirect for the URL you arrived at.
Site architecture, briefly
The site is built with Next.js using the App Router, statically rendered, and deployed to Vercel. There is no database, no CMS, no client-side JavaScript framework other than React. Pages are stored as JavaScript files inside the app directory and are mostly hand-written prose. The blog posts are stored in a single JavaScript data file. The sitemap above is generated dynamically from the static page tree plus the blog post slugs.
If you are an engineer curious about how this site is structured, the entire source is conceptually simple. We chose Next.js because it gives us static rendering, image optimization, automatic sitemap generation, and a sensible file-based router without any of the complexity of larger frameworks. The site is approximately 60 page files and a single API route — the entire codebase fits in a couple of megabytes.