Skip to content

Conversation

pwseg
Copy link
Contributor

@pwseg pwseg commented Jul 30, 2025

Proposed changes

  • Rewrote Message schemas, Blocks and Specs section to use clearer/up-to-date terminology that aligns with current product behavior.
  • Specifically, it removes references to “Blocks,” which are no longer a relevant or supported concept.
  • Also emphasized what parts of the Segment Spec result in downstream transformations (mapped events), versus what are just recommendations.

Merge timing

  • ASAP once approved

Related issues (optional)

@pwseg pwseg added the content-update updates to content that are not new features, includes grammar fixes, added notes label Jul 30, 2025
@pwseg pwseg linked an issue Jul 30, 2025 that may be closed by this pull request
@pwseg pwseg requested a review from forstisabella July 30, 2025 02:09
@pwseg pwseg marked this pull request as ready for review July 30, 2025 02:09
@pwseg pwseg requested a review from a team as a code owner July 30, 2025 02:09
forstisabella
forstisabella previously approved these changes Jul 30, 2025
Copy link
Contributor

@sanscontext sanscontext left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🫡

@pwseg pwseg merged commit cc43b92 into develop Jul 31, 2025
4 checks passed
@pwseg pwseg deleted the 6100-content-you-can-probably-remove-blocks branch July 31, 2025 13:38
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-update updates to content that are not new features, includes grammar fixes, added notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Content]: You can probably remove "blocks"?
3 participants