Ctxt.info

Documentation / Technical / Specs

Knowledge and reference domain.

Where developers, integrators, and advanced users go to understand how Ctxt works.

content

✔ Developer documentation

• API docs

• Architecture diagrams

• Class references

• Configuration guides

• Integration examples

✔ Specs + internals

• FTdata, ValueParser, Applier system

• Template syntax

• Data flows

• Versioned specs

• RFC-style documents

✔ Guides and reference materials

• How-to guides

• Troubleshooting

• FAQ (technical)

• Example projects

• Performance notes

✔ Release notes

• Changelog

• Migration guides

• Deprecation notices

Goal:

This domain is factual, versioned, technical — something you’d use when building or debugging with CTX.

⸻

Why This Split Works Well

✔ Clean separation of audiences

• Non-technical users → getctx.com

• Developers / integrators → ctxt.info

✔ SEO clarity

Marketing content stays on .com

Technical docs stay on .info

✔ Future-proof structure

As the product grows, you avoid clutter:

the .info domain remains a clear namespace for all documentation.

✔ Easy deep-linking

Docs can grow arbitrarily without polluting the main site.

⸻

Optional Best Practices

Redirects

• getctx.com/docs → redirect to ctxt.info

• ctxt.info → always canonical (no redirect to .com)

Versioning

ctxt.info/v1/

ctxt.info/v2/

Subdomains you might eventually add

• api.getctx.com (API host)

• status.getctx.com (status page)

• app.getctx.com (app UI)