> ## Documentation Index
> Fetch the complete documentation index at: https://calcs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Where things move when Blueprint closes

> Support, release notes, calculator requests, articles, and webinars all have a home outside Blueprint. Here is where to find each one.

Everything Blueprint was used for has a home. Here is the short version.

| What you need                               | Where to go                                                                 |
| ------------------------------------------- | --------------------------------------------------------------------------- |
| Help with a calculator or a how-to question | [calcs.com/docs](https://calcs.com/docs)                                    |
| What changed in the product                 | [calcs.com/docs/release\_notes](https://calcs.com/docs/release_notes)       |
| Request a specific calculator               | [calcs.com/request](https://calcs.com/request)                              |
| Articles and industry writing               | [calcs.com/blog](https://calcs.com/blog)                                    |
| Webinars and on demand training             | [calcs.com/webinars](https://calcs.com/webinars)                            |
| A bug in a calculator                       | [Reporting a bug](/docs/blueprint/reporting-a-bug)                               |
| Anything not covered above                  | [support@calcs.com](mailto:support@calcs.com), or the chat inside Calcs.com |

## When to use which

**Docs.** Start here for anything about how a calculator works, which standards it applies, or how to read its output. Search covers every calculator and every region.

**Release notes.** Blueprint carried product announcements. Release notes now do that, with the detail of what changed and which calculators it affected.

**Calculator requests.** Requests posted on Blueprint depended on someone seeing the thread. Requests submitted at calcs.com/request are logged and reviewed by the product team. See [Requesting a calculator or new feature](/docs/blueprint/requesting-a-calculator) for what to include.

**Bug reports.** Email [support@calcs.com](mailto:support@calcs.com) or open the chat inside Calcs.com. [Reporting a bug](/docs/blueprint/reporting-a-bug) covers what to send so our engineers can reproduce it.

**Blog.** Longer writing on standards, methods, and how engineers are working. This is where the discussion-style posts from Blueprint go.

**Webinars.** Live and recorded sessions, including standards walkthroughs and worked examples.

**Support.** For anything else, email [support@calcs.com](mailto:support@calcs.com) or open the chat inside Calcs.com. A person reads every one.

## Still not sure where something goes?

Email [support@calcs.com](mailto:support@calcs.com) and we will point you to the right place.