Introducing the EnderDash blog

EnderDash now has a blog because docs and marketing pages solve different jobs.

The docs should stay focused on setup, configuration, and reference material. The blog is where we can publish shorter product updates, operating notes, and practical guidance that would be awkward to bury inside the documentation tree.

What belongs here

• Product changes that affect how teams run Minecraft infrastructure.
• Notes from building features like Ocelot, console workflows, and plugin management.
• Practical advice for server operators who want fewer moving parts in their day-to-day work.

What stays in docs

Step-by-step setup still belongs in the docs. If you need installation details, API reference material, or feature walkthroughs, the documentation remains the source of truth.

What to expect next

We will use this space for product release notes, workflow guidance, and operational lessons from building a panel that is supposed to help admins act faster instead of opening three more tabs.

For posts that depend on changing technical details, we will prefer clear sourcing and visible update dates over pretending infrastructure advice is timeless. Comparisons should say what was checked, guides should name their assumptions, and product notes should point back to the docs when the reader needs exact setup steps.

If you want the broader product context, read more on the about page. If you want to see where the product is heading commercially, the pricing page is the right place.