-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Content]: You can probably remove "blocks"? #6100
Comments
sanscontext
added
content
When the bug is about content that needs to get fixed
triage
labels
Feb 21, 2024
This issue is stale because it has been open 60 days with no activity. |
Pretty sure this is still there. ;) |
This issue is stale because it has been open 60 days with no activity. |
It's still there though. @pwseg Do I need to make a PR? |
This issue is stale because it has been open 60 days with no activity. |
Is there anyone on the Docs team anymore? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What article on segment.com/docs is affected?
https://segment.com/docs/guides/intro-impl/#message-schemas-blocks-and-specs
What part(s) of the article would you like to see updated?
When I wrote this in (twenty-mumblety) @sperand-io and I had been talking about how to differentiate between the specs that actually had transforms, and the specs that were just recommendations. "Blocks" were the latter, but I don't think that term ever took off. (That said, if it did please close-won't-fix this, and I'll be pleased. :) )
Additional information
Source: I was the docs team from 2018 to 2020. :)
The text was updated successfully, but these errors were encountered: