News
Release-shaped notes and program launches. Essays live on the blog.
What belongs here
News covers programme launches, major product surface changes, and high-level incident notes when they matter publicly. Essays live on the blog. Curriculum lives in Academy.
Press inquiries: include deadline and outlet. Security advisories for critical issues go to affected customers first; high-level notes may appear here after.
News purpose
News exists as part of the CEDX resource library next to Academy, product pages, and customer scenarios. Content stays operator-grade and tied to live software wherever a product claim is made.
Use this surface when its job matches your moment: learning, release notes, live sessions, listings, or essays. Do not expect one page to replace the whole estate evaluation path.
Editorial and product truth rules still apply: no parallel mockup universe, no thin listicles, no bait-and-switch demos. If a session or essay points at a product, open the live app and test the claim.
Partners and customers share public surfaces; partner-only depth remains in the portal after approval. That split keeps evaluation open without giving away co-sell assets.
How to use it
Start from the hero metrics and section map, then deep-link into product catalog or Academy as needed. Bring operators when decisions depend on queue design rather than feature checkboxes alone.
Capture decisions in your pilot doc or joint plan so sessions and essays produce artifacts. Without artifacts, content becomes entertainment.
Escalate to contact for estate map, partner intro, or private sessions when public material is not enough. Include industry, products, timeline, and constraints so routing is correct.
Related hubs always include Customers, Partners program, Developers, and Support where relevant. The estate is one system; the library is one map.
Standards
Live product when product is claimed; honest illustrative language for scenarios; written FAQs for procurement paste. Security and identity questions get real answers or a path to the security pack.
No paid directory ranking; no calendar filler essays; no webinars that cannot open the app. Violations are process bugs we fix rather than exceptions we normalize.
Accessibility and clarity beat cleverness; operators should finish a section with an action. If a section has no action, it is incomplete.
Refresh cadence follows product change, not an arbitrary publishing calendar. Material changes may appear in News when they affect programmes.
Next step
Pick one product to open live, one Academy module or scenario to read, and one conversation to book if needed. Three actions beat thirty open tabs.
Share links with the people who own the queue so evaluation is not stuck in a single inbox. Estate programs fail when only one champion understands the map.
Partners: complete enablement and clean portal hygiene before promising Premier outcomes internally. Customers: write the retire list before config week one.
When ready, use contact with context both sides can act on within two business days for most intro and map requests. Serious inputs get serious routing.
Recent
Practical detail for operators, partners, and builders evaluating the estate.
Paths, tiers, apply, directory.
Live software embeds estate-wide.
Unique concepts per product page.
Full-depth corporate hubs.
Streams
Programme and release-shaped notes.
Sparse essays worth Friday.
Curriculum and checklists.
Enablement after approval.
Live software truth.
Customer advisories when critical.
FAQ
Straight answers before you book time or open a ticket.
press@cedxsystems.com - include deadline and outlet.
Critical issues to affected customers; high-level notes may appear here.
No. Essays live under /blog/. News is release-shaped.
Open a live product, book an estate map, or join the partner program.
