One of the earliest routing decisions was whether MediTracer should have a single company-wide blog right away.
For the first migration pass, the answer is no.
That is not because a company-wide publication is a bad idea. It is because a shared editorial layer works best when the company voice is mature enough to hold multiple kinds of stories without flattening them.
Separate product voice
Tubular Daily Care has its own audience, product language, and roadmap context.
Keeping the blog under /products/tubular/blog preserves that voice while the company site is still taking shape.
That matters for readers. A family looking for Tubular updates should land in content that sounds clearly connected to the product they are evaluating, not content that feels generalized to every future MediTracer initiative.
It also matters for the team. Product-level writing can stay close to the practical questions people actually have about route changes, feature framing, launch timing, and what stays product-specific.
Easier migration path
This avoids forcing every legacy article into a new editorial model before the parent company messaging is ready.
The codebase can still support a future aggregate publication layer later if that becomes useful.
In other words, the separate product blog is not a permanent philosophical statement. It is a sequencing decision.
The migration can move forward now, the company shell can strengthen around it, and editorial consolidation can happen later if it serves readers better.
Why this is the calmer choice
A slower editorial merge reduces the risk of mixing company voice, product voice, and migration notes too early.
That gives MediTracer room to grow a clearer company narrative while Tubular continues speaking in the more focused, product-specific language its current audience expects.
For now, that separation creates less confusion, less rewriting, and a more trustworthy experience for the people following the product closely.