# Page Not Found

The URL `files/yGCoc5vdbzim9NLVXmzv` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Comparing looms](https://learning.loftyfiber.com/floor-and-table-looms-purchasing-information-and-support/comparing-looms.md)
- [Deflected Doubleweave - Managing Selvages](https://learning.loftyfiber.com/weaving-how-to/deflected-doubleweave-managing-selvages.md)
- [Rigid Heddle Basics - Information and Video Tutorials](https://learning.loftyfiber.com/rigid-heddle-e-learning/rigid-heddle-basics-information-and-video-tutorials.md)
- [Knitting Videos](https://learning.loftyfiber.com/knitting-and-crochet-videos/knitting-videos.md)
- [Adding Floating Selvages](https://learning.loftyfiber.com/weaving-how-to/adding-floating-selvages.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://learning.loftyfiber.com/floor-and-table-looms-purchasing-information-and-support/comparing-looms.md?ask=<question>
```

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.

### Option 2 — Browse the documentation index

Full index: https://learning.loftyfiber.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://learning.loftyfiber.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/floor-and-table-looms-purchasing-information-and-support/comparing-looms.md`).

You may also use `Accept: text/markdown` header for content negotiation.