> For the complete documentation index, see [llms.txt](https://style.pixelunion.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://style.pixelunion.net/formatting/urls.md). # URLs There are a couple things that merit mentioning when it comes to URLs. The first is how to style them in text. The second is how to actually structure them. Let's dig in! ### In-line URL styling It's pretty rare that you'll need to spell out a URL in text. Most of the time, writing the name of the company, product, publication, etc. will do just fine. If you must spell our a URL, try to make it as concise and non-ugly as possible. Leave off the "" bit. URLs are case-insensitive, but you should always write them in lowercase. If you're writing about our website—especially internally—it's okay to abbreviate to **pxu.net** ### Structuring URLS URLs should be short, memorable, and easy to type. Your control over your URL may be limited, but you should do what you can with the pieces you can control. Customize page URLs to cut out extraneous words and emphasize keywords, separated by hyphens. For example, the default URL for a blog post might be:`/blog/5-reasons-why-ultimate-special-offers-is-shopifys-best-all-in-one-sales-app` But something like this is much nicer:\ `/blog/ultimate-special-offers-shopifys-best-sales-app` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://style.pixelunion.net/formatting/urls.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.