# Site Content --- From: [Austin Office](/locations/austin/) # Austin Office Austin handles demos, customer success, and projects that benefit from a second regional contact. OpnPress Austin — Product demos and customer support. Address: 301 Congress Ave, Austin, TX 78701 Hours: Mon-Thu 9am-5pm Website: [Goto Page](../) Email: [austin@opnpress.com](mailto:austin@opnpress.com) Phone: [+1 (512) 555-0142](tel:+15125550142) ## Local services - discovery calls and demos - customer support and handoff - project planning sessions - location page maintenance ## Service area Central Texas, nearby metro areas, and clients who want a second office contact for sales and support. --- From: [Chicago Office](/locations/chicago/) # Chicago Office Chicago is the main office and the place where the team handles project kickoff, site launches, and support. OpnPress Chicago — Sales, support, and onboarding. Address: 200 N Clark St, Chicago, IL 60601 Hours: Mon-Fri 9am-5pm Email: [chicago@opnpress.com](mailto:chicago@opnpress.com) Phone: [+1 (312) 555-0100](tel:+13125550100) - new site launches - content migration planning - location page setup - editorial workflow support Chicago, the surrounding suburbs, and remote clients who want a central Midwest contact. --- From: [Locations](/locations/) # Locations Location pages work the same way as every other page in the site tree: markdown first, relative links, and source mirrors for machine-readable traversal. OpnPress Chicago — Sales, support, and local onboarding. Website: [Goto Page](./chicago/) Website: [Goto Page](./austin/) ## What these pages are for - Show the same business in more than one city. - Give each office a unique page with local details. - Keep the structure predictable enough for LLMs to follow. --- From: [About](/about/) # About OpnPress treats content like a source tree and the rendered site like a publishable view of that tree. The point is not just to move fast. The point is to make the structure obvious enough that a human can edit it and an LLM can understand it without guessing. ## What this changes - Markdown becomes the source of truth. - Relative links show how pages connect. - Source mirrors expose the same content in a machine-friendly form. - Page metadata gives an LLM the context it needs to traverse the site correctly. ## Why that matters When an LLM has better source data, it can produce better answers for the user. That matters whether the user is asking for a local business recommendation, a service comparison, or a page update. ## What authors get Instead of fighting a visual builder, authors write the actual page structure directly. That makes the site easier to maintain, easier to expand, and easier to hand off to tools that generate or update pages from context. ## How it fits the product The home page explains why AI discovery is changing how people find site and company data. This page explains the publishing model that makes that possible. --- From: [Hello OpnPress](/blog/hello-opnpress/) # Hello OpnPress OpnPress keeps the markdown source close to the rendered site so humans and LLMs are working from the same content model. ## What that means - markdown is the source of truth - links stay relative so the structure is obvious - source mirrors expose the content in a machine-friendly format - page metadata tells tools how to traverse the site ## Why it helps When content is already structured for traversal, the LLM does less guessing and can focus on generating useful pages, edits, and follow-up content. Related pages A few places to continue exploring the sample site. --- From: [Insights](/blog/) # Insights This section acts like a small editorial hub. It shows that blog-style content is just another set of pages in the tree, with the same source mirror and linking model as the rest of the site. Latest insights Articles under the blog folder. ## Why this section exists The sample site needs at least one place where longer-form content feels natural. These pages are meant to read like articles a real team would publish about content structure, local pages, and AI-friendly publishing. --- From: [Local Pages at Scale](/blog/local-pages-at-scale/) # Local Pages at Scale If a business has multiple offices or service areas, the page structure needs to stay predictable. ## What works well - one page per city or branch - shared contact patterns - a consistent info hierarchy - links back to services and contact ## Why it matters It becomes much easier to update locations, generate new branches, and keep the site understandable for both editors and LLMs. --- From: [Structured Content for LLMs](/blog/structured-content/) # Structured Content for LLMs The best output from an AI tool usually starts with a site that is already predictable. ## Useful patterns - stable headings - relative links - repeatable page sections - source mirrors for each page ## What to avoid - pages that are only layout experiments - content buried inside unusual wrappers - links that do not explain how pages connect --- From: [Contact](/contact/) # Contact Use this page as the central contact surface for the site. It shows the company-wide contact details, reusable contact links, and the single-action shortcuts that can be reused in page content or headers and footers. Email: [hello@opnpress.com](mailto:hello@opnpress.com) Website: [https://opnpress.com](https://opnpress.com) --- From: [Hello World](/hello/world/) # Hello World This page proves that nested markdown files map cleanly to nested routes. The build should turn this file into a static page under /hello/world/ . --- From: [Hello from OpnPress](/) # Build in markdown. Publish like a site. OpnPress is built for teams that want their website content to live in markdown, not in a visual editor. That makes the source easy for people to edit and easy for LLMs to read, traverse, and extend. The rendered site is just the public surface. The markdown tree is the system of record. ## How it works - Write pages in content/ - Use shortcodes for structure, not page templates - Generate static output into dist/ - Publish from the build output, with Cloudflare Pages as the default target ## What the LLM sees The site exposes source mirrors and machine-readable indexes so an LLM can follow the structure without reverse-engineering the rendered HTML. - llms.txt - source.md - page.json See the home page source mirror here: source.md ## Why this matters Search and answer engines increasingly resolve the question before a site visit happens, and more people are skipping classic search for AI tools when they want a direct answer. - Future reported that 55% of U.S. consumers use AI instead of search engines for certain tasks. Source - BrightLocal found that 45% of consumers now ask AI for local business recommendations, up from 6% the year before. Source - Pew Research Center found that when Google showed an AI summary, users clicked a traditional result in 8% of visits versus 15% when no summary appeared, and only 1% clicked a cited source inside the summary. Source That is why OpnPress ships markdown mirrors, relative links, and simple page indexes. Better source data gives LLMs better context, which gives users better answers. The content still needs to make sense when the first read happens in search, in an AI answer, or through a source mirror instead of a browser visit. ## The next directory Google Search and Maps replaced the Yellow Pages because they made it faster to find a business and decide what to do next. AI summaries and direct LLM prompts are doing the same thing now for website and company data. Users ask an LLM for recommendations, comparisons, summaries, and next steps instead of opening ten pages and stitching the answer together themselves. For OpnPress, that means the site is not only built to be published. It is built to be read by an LLM first, so the model can surface the right page, the right office, or the right service with less guessing and better results for the person asking. Explore the sample site The sample pages are linked the same way a real site would be linked. --- From: [Integrations](/integrations/) # Integrations This page is a reference for the reusable blocks that make a markdown site feel complete. They are here to support real pages, not replace them. ## Site-wide blocks Get in touch Use the contact form provider configured in `site.config.yaml`. Share this page These links are generated from the current page URL. Twitter: opnpress X: opnpress Github: https://github.com/OpnPress Facebook: https://facebook.com/OpnPress Website: https://opnpress.com ## Page-local blocks OpnPress Chicago — Page-local contact card for a specific office. Website: [Goto Page](../locations/chicago/) Book a call Embed your scheduling provider with a single declarative block. Find us Use a maps embed to show a location or service area. ## Single-action blocks Watch the demo Embed a video provider directly in content. ## Why these exist These blocks let the sample site show the same content model a real site would use: reusable company data, page-local contact cards, simple action links, and embeds only where they add value. --- From: [AI Workflow Design](/services/ai-workflows/) # AI Workflow Design We design the content surface so AI tools can work with the site instead of fighting it. ## What this includes - LLM-friendly markdown patterns - llms.txt and source mirror strategy - shortcode guidance for structured blocks - page naming and traversal conventions If the site is structured for machine reading from the start, the LLM does less guessing and more useful work. --- From: [Services](/services/) # Services OpnPress can power a services section for an agency, studio, or local business that wants each offering to live as its own markdown page. The pages below are written like real service pages, not feature demos. Core offerings Each card links to a real page in the services folder. ## How the service section works - Each service is a separate page. - Each page can target a different audience or use case. - The index page stays short and acts like a directory, not a wall of text. --- From: [Local Content Systems](/services/local-content-systems/) # Local Content Systems This service is for teams that need many pages with the same overall structure, such as offices, service areas, or franchise locations. - location page templates - contact card patterns - map and contact link reuse - relative linking conventions - local SEO-friendly structure When the same structure repeats across cities or branches, the content should stay predictable so editors and LLMs both understand it quickly. --- From: [Markdown Site Setup](/services/markdown-sites/) # Markdown Site Setup We help teams start with a content tree that is easy to edit, easy to review, and easy for LLMs to parse. - site structure planning - homepage and landing page setup - content folder conventions - source mirror support for each page - practical navigation and footer structure A markdown-first site is easier to version, easier to automate, and easier to extend later when the content model grows. --- From: [raw landing](/hello/raw-landing/) Custom HTML Raw HTML page This file is colocated with the route it serves, without a separate custom folder. This content is authored directly as HTML for special landing pages.