OTel-in-focus: link core components to website section #2444
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Btw, unfortunately, Prettier doesn't handle definitions lists yet, which is why I added the ignore directives. For details, see: |
chalin
force-pushed
the
chalin-im-otel-in-focus-2023-03-03
branch
from
c9eff10
to
f564ded
Compare
|
lgtm |
|
Thanks for the reviews. FYI, I'll follow up with some styling fixes (so that the page doesn't contain an embedded |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What you think about linking core components to their website landing pages -- @austinlparker @svrnm @cartermp? This makes it easier for readers to find out more about the component.
Screenshot
Here's a screenshot of what it could look like:
Before
In contrast, this is what is was before this PR:
Note that I moved the PHP news into the Releases and Updates section.