chore(blog): add ashmit spotlight story #3726
Conversation
iambami
requested review from
thulieblack,
quetzalliwrites,
TRohit20,
derberg,
akshatnema,
anshgoyalevil,
Mayaleeeee and
asyncapi-bot-eve
as code owners
WalkthroughA new markdown file has been added that documents Ashmit Jagtap's journey from a Google Summer of Code (GSoC) mentee to a maintainer in the AsyncAPI community. The article is structured with metadata, sections on his experiences, challenges, and a Q&A format that offers insights on mentorship and community involvement. Changes
Sequence Diagram(s)(No sequence diagram generated as the changes do not modify control flow or introduce new interactive features.) Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3726 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 21 21
Lines 667 667
Branches 113 113
=========================================
Hits 667 667 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (7)
markdown/blog/community-spotlight-ashmit.md (7)
25-25: Style Suggestion: Enhance Verb ChoiceIn the sentence "I learned how to navigate large codebases, improve my problem-solving skills, and contribute in a structured manner," consider using a more compelling verb than "contribute" (e.g., "execute" or "implement") to add greater impact.
🧰 Tools
🪛 LanguageTool
[style] ~25-~25: Consider an alternative verb to strengthen your wording.
Context: ...earned how to navigate large codebases, improve my problem-solving skills, and contribu...(IMPROVE_STRENGTHEN)
52-53: Style Suggestion: Adverb StrengtheningReplace "completely new" with "entirely new" in the statement regarding learning TypeScript to more effectively convey the novelty of the experience.
🧰 Tools
🪛 LanguageTool
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...(COMPLETELY_ENTIRELY)
62-63: Style Suggestion: Hyphenation for Compound AdjectivesIn the phrase "crucial in open source and professional environments," consider hyphenating "open-source" when used as a compound adjective before a noun for improved clarity.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~63-~63: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...roject management, which are crucial in open source and professional environments.* ## Key...(EN_COMPOUND_ADJECTIVE_INTERNAL)
72-73: Style Suggestion: Vary Adverb UsageIn the sentence describing the transition from a GSoC mentee to a maintainer, consider replacing "completely different" with "entirely different" to provide a stronger, more precise description.
🧰 Tools
🪛 LanguageTool
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...(COMPLETELY_ENTIRELY)
123-125: Style & Typographical Refinement: Dialogue on HobbiesIn the response regarding hobbies, consider refining the phrasing:
- Use "enjoy cooking" instead of "like to cook" for a stronger expression.
- Insert a comma after "sometimes" and rephrase "if I have some free time" to "when I have spare time" for enhanced readability.
For example:
"Yeah, I do enjoy cooking sometimes, because when I have spare time, that's where I head to the kitchen."🧰 Tools
🪛 LanguageTool
[typographical] ~124-~124: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because if ...(YES_NO_COMMA)
[style] ~124-~124: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because if I have some free t...(LIKE_TO_ENJOY)
[style] ~124-~124: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...o cook sometimes because if I have some free time that's where I go towards the kitchen.*...(FREE_TIME)
126-126: Style Suggestion: Conciseness in LanguageReplace "a lot of people" with "many people" to streamline the query on community acknowledgments.
🧰 Tools
🪛 LanguageTool
[style] ~126-~126: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...(A_LOT_OF)
127-128: Style Suggestion: Reduce Wordiness and Improve PunctuationConsider replacing "And on top of that" with "Additionally," in the acknowledgment section. Also, if the sentence connects independent clauses, inserting a comma before "and" may further improve clarity.
🧰 Tools
🪛 LanguageTool
[style] ~128-~128: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz](https:/...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
[uncategorized] ~128-~128: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... that required his Assistance throughout and he was there for it. Honestly, that's q...(COMMA_COMPOUND_SENTENCE)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-ashmit.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-ashmit.md
[style] ~25-~25: Consider an alternative verb to strengthen your wording.
Context: ...earned how to navigate large codebases, improve my problem-solving skills, and contribu...
(IMPROVE_STRENGTHEN)
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...
(COMPLETELY_ENTIRELY)
[uncategorized] ~63-~63: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...roject management, which are crucial in open source and professional environments.* ## Key...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...
(COMPLETELY_ENTIRELY)
[typographical] ~104-~104: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...
(TO_BE_HONEST_COMMA)
[typographical] ~116-~116: It seems that a comma is missing.
Context: ...** Linux. Not hardcore Linux like fedora though.* Bami: Apple or Samsung. ***Ash...
(THOUGH_COMMA)
[typographical] ~124-~124: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because if ...
(YES_NO_COMMA)
[style] ~124-~124: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because if I have some free t...
(LIKE_TO_ENJOY)
[style] ~124-~124: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...o cook sometimes because if I have some free time that's where I go towards the kitchen.*...
(FREE_TIME)
[style] ~126-~126: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...
(A_LOT_OF)
[style] ~128-~128: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz](https:/...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
[uncategorized] ~128-~128: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... that required his Assistance throughout and he was there for it. Honestly, that's q...
(COMMA_COMPOUND_SENTENCE)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-ashmit.md
110-110: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
114-114: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (1)
- GitHub Check: Lighthouse CI
🔇 Additional comments (6)
markdown/blog/community-spotlight-ashmit.md (6)
1-17: Approval: YAML Front Matter is Well-StructuredThe metadata is comprehensive and clearly outlines the post’s title, publication date, type, tags, cover image, author details, and excerpt.
19-20: Approval: Engaging IntroductionThe introductory paragraph effectively sets the stage for Ashmit’s story.
102-104: Typographical Correction: Insert Comma in DialogueIn Ashmit’s response, "Yeah, both are toxic in their own ways to be honest," adding a comma before "to be honest" (i.e., "Yeah, both are toxic in their own ways, to be honest") would improve readability.
[typographical]🧰 Tools
🪛 LanguageTool
[typographical] ~104-~104: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...(TO_BE_HONEST_COMMA)
115-116: Typographical Correction: Comma and CapitalizationIn the sentence "Not hardcore Linux like fedora though," consider adding a comma and capitalizing "Fedora" (e.g., "Not hardcore Linux, like Fedora, though") to enhance clarity.
[typographical]🧰 Tools
🪛 LanguageTool
[typographical] ~116-~116: It seems that a comma is missing.
Context: ...** Linux. Not hardcore Linux like fedora though.* Bami: Apple or Samsung. ***Ash...(THOUGH_COMMA)
106-110: Markdown Formatting: Emphasis as Dialogue StylingThe use of bold text for lines like "Bami: Slack or discord." is a deliberate stylistic choice to denote dialogue in the Q&A format. The markdownlint MD036 warning regarding emphasis used as headings can be safely ignored here.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
110-110: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
112-116: Markdown Formatting: Dialogue ConsistencySimilarly, the emphasis in lines such as "Bami: Window or Linux" reinforces the conversational tone of the interview. This formatting is intentional, so no changes are required despite markdownlint suggestions.
🧰 Tools
🪛 LanguageTool
[typographical] ~116-~116: It seems that a comma is missing.
Context: ...** Linux. Not hardcore Linux like fedora though.* Bami: Apple or Samsung. ***Ash...(THOUGH_COMMA)
🪛 markdownlint-cli2 (0.17.2)
114-114: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
iambami
changed the title
asyncapi-bot
requested review from
devilkiller-ag,
sambhavgupta0705,
Aahil13 and
VaishnaviNandakumar
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (10)
markdown/blog/community-spotlight-ashmit.md (10)
19-25: Strengthen Descriptive Wording
In the paragraph where Ashmit recalls his learning experience, consider using a more impactful verb in the phrase “improve my problem-solving skills.” For example, you might try “enhance my problem-solving abilities” to add extra punch to the narrative.[style]
🧰 Tools
🪛 LanguageTool
[style] ~25-~25: Consider an alternative verb to strengthen your wording.
Context: ...earned how to navigate large codebases, improve my problem-solving skills, and contribu...(IMPROVE_STRENGTHEN)
51-53: Refine Adverb Usage
Within the Q&A section, the statement “I didn’t learn a completely new programming language…” could be improved by replacing “completely” with “entirely” to offer a more natural emphasis.[style]
🧰 Tools
🪛 LanguageTool
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...(COMPLETELY_ENTIRELY)
60-63: Hyphenate Compound Adjectives for Consistency
When using “open source” as an adjective (e.g., in “open source and professional environments”), consider hyphenating it as “open‑source” for clarity and consistency.🧰 Tools
🪛 LanguageTool
[uncategorized] ~63-~63: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...roject management, which are crucial in open source and professional environments alike.* ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
103-105: Enhance Punctuation for Improved Readability
In the sentence “Yeah, both are toxic in their own ways to be honest,” consider adding a comma after the phrase “to be honest” (e.g., “to be honest,”) to further enhance clarity and pacing.[typographical]
🧰 Tools
🪛 LanguageTool
[typographical] ~104-~104: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...(TO_BE_HONEST_COMMA)
110-112: Consistent Q&A Formatting
The Q&A sections currently use emphasis for differentiating questions and answers. For improved readability and structure, consider using a consistent markdown format—such as incorporating blockquotes or headings for questions—to clearly distinguish between interviewer prompts and Ashmit’s responses.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
110-110: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
115-117: Improve Punctuation in Affiliation Description
In the segment discussing Linux usage, the line “Linux. Not hardcore Linux like fedora though.” might benefit from a slight punctuation adjustment. For example, “Linux. Not hardcore Linux, like Fedora though.” improves clarity.[typographical]
🧰 Tools
🪛 LanguageTool
[typographical] ~116-~116: It seems that a comma is missing.
Context: ...** Linux. Not hardcore Linux like fedora though.* Bami: Apple or Samsung. ***Ash...(THOUGH_COMMA)
123-125: Enhance Informal Language and Punctuation
In the response about hobbies, the sentence “For hobbies, I might say cooking is one of them. Yeah I do like to cook sometimes because if I have some free time that's where I go towards the kitchen.” can be refined for a more engaging tone. Consider rephrasing to something like:“For hobbies, I enjoy cooking. When I have some spare time, I often head to the kitchen.”
This revision avoids repetition and improves clarity.
[style]
[typographical]🧰 Tools
🪛 LanguageTool
[typographical] ~124-~124: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because if ...(YES_NO_COMMA)
[style] ~124-~124: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because if I have some free t...(LIKE_TO_ENJOY)
[style] ~124-~124: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...o cook sometimes because if I have some free time that's where I go towards the kitchen.*...(FREE_TIME)
126-126: Refine Word Choice in Thank You Section
In the question “Is there anyone or a lot of people you would like to thank…”, consider replacing “a lot of people” with “many people” to achieve a more concise and polished expression.[style]
🧰 Tools
🪛 LanguageTool
[style] ~126-~126: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...(A_LOT_OF)
128-128: Streamline Transitional Phrase
Instead of “and on top of that,” a more succinct transitional phrase such as “additionally” or “furthermore” might improve the flow of the sentence in the thank-you note.[style]
🧰 Tools
🪛 LanguageTool
[style] ~128-~128: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz](https:/...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
[uncategorized] ~128-~128: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... that required his Assistance throughout and he was there for it. Honestly, that's q...(COMMA_COMPOUND_SENTENCE)
110-114: Markdown Formatting Note on Emphasis
Static analysis flagged the use of emphasis instead of headings in certain areas (e.g., “Bami: …”). While the current format effectively distinguishes the dialogue, you may consider using proper markdown headings or another consistent style if it better aligns with the overall documentation style guidelines.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
110-110: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
114-114: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-ashmit.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-ashmit.md
[style] ~25-~25: Consider an alternative verb to strengthen your wording.
Context: ...earned how to navigate large codebases, improve my problem-solving skills, and contribu...
(IMPROVE_STRENGTHEN)
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...
(COMPLETELY_ENTIRELY)
[uncategorized] ~63-~63: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...roject management, which are crucial in open source and professional environments alike.* ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...
(COMPLETELY_ENTIRELY)
[grammar] ~73-~73: The pronoun ‘you’ must be used with a non-third-person form of a verb.
Context: ...ributions, whereas as a maintainer, you oversees multiple contributions and ensure the s...
(NON3PRS_VERB)
[typographical] ~104-~104: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...
(TO_BE_HONEST_COMMA)
[typographical] ~116-~116: It seems that a comma is missing.
Context: ...** Linux. Not hardcore Linux like fedora though.* Bami: Apple or Samsung. ***Ash...
(THOUGH_COMMA)
[typographical] ~124-~124: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because if ...
(YES_NO_COMMA)
[style] ~124-~124: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because if I have some free t...
(LIKE_TO_ENJOY)
[style] ~124-~124: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...o cook sometimes because if I have some free time that's where I go towards the kitchen.*...
(FREE_TIME)
[style] ~126-~126: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...
(A_LOT_OF)
[style] ~128-~128: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz](https:/...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
[uncategorized] ~128-~128: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... that required his Assistance throughout and he was there for it. Honestly, that's q...
(COMMA_COMPOUND_SENTENCE)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-ashmit.md
110-110: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
114-114: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (2)
- GitHub Check: Lighthouse CI
- GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (2)
markdown/blog/community-spotlight-ashmit.md (2)
1-16: Metadata Front Matter Looks Great
The YAML front matter is well-structured and includes all the essential fields (title, date, type, tags, cover, authors, and excerpt) to support SEO and content organization.
1-137: Overall Content Quality and Engagement
The blog post is engaging and thoroughly documents Ashmit’s journey from mentee to maintainer. The Q&A format provides a conversational and accessible tone that will resonate well with the community. Addressing the minor style and grammatical suggestions above will further polish the content.🧰 Tools
🪛 LanguageTool
[style] ~25-~25: Consider an alternative verb to strengthen your wording.
Context: ...earned how to navigate large codebases, improve my problem-solving skills, and contribu...(IMPROVE_STRENGTHEN)
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...(COMPLETELY_ENTIRELY)
[uncategorized] ~63-~63: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...roject management, which are crucial in open source and professional environments alike.* ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...(COMPLETELY_ENTIRELY)
[grammar] ~73-~73: The pronoun ‘you’ must be used with a non-third-person form of a verb.
Context: ...ributions, whereas as a maintainer, you oversees multiple contributions and ensure the s...(NON3PRS_VERB)
[typographical] ~104-~104: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...(TO_BE_HONEST_COMMA)
[typographical] ~116-~116: It seems that a comma is missing.
Context: ...** Linux. Not hardcore Linux like fedora though.* Bami: Apple or Samsung. ***Ash...(THOUGH_COMMA)
[typographical] ~124-~124: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because if ...(YES_NO_COMMA)
[style] ~124-~124: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because if I have some free t...(LIKE_TO_ENJOY)
[style] ~124-~124: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...o cook sometimes because if I have some free time that's where I go towards the kitchen.*...(FREE_TIME)
[style] ~126-~126: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...(A_LOT_OF)
[style] ~128-~128: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz](https:/...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
[uncategorized] ~128-~128: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... that required his Assistance throughout and he was there for it. Honestly, that's q...(COMMA_COMPOUND_SENTENCE)
🪛 markdownlint-cli2 (0.17.2)
110-110: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
114-114: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
|
Hey @TRohit20 All the changes have been implemented. Kindly go through it. Thank you. |
iambami
changed the title
There was a problem hiding this comment.
I love the interview. There are a few things to change:
- Follow the correct conventional commit for your title
- Use Full names when mentioning mentors and use the correct names as well
- Be consistent in using the word Open Source. Some parts have hyphens. Some don't, so pick the spelling you want and use it consistently throughout the article.
Apart from this, it should be good to go.
iambami
changed the title
iambami
changed the title
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
markdown/blog/community-spotlight-ashmit.md (1)
73-73:⚠️ Potential issueSubject–Verb Agreement Correction
In line 73, the sentence “...whereas as a maintainer, you oversees multiple contributions and ensure the stability of the project.” contains a verb agreement error. Please change “oversees” to “oversee” so that it correctly pairs with “you.”🧰 Tools
🪛 LanguageTool
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...(COMPLETELY_ENTIRELY)
[grammar] ~73-~73: The pronoun ‘you’ must be used with a non-third-person form of a verb.
Context: ...ributions, whereas as a maintainer, you oversees multiple contributions and ensure the s...(NON3PRS_VERB)
🧹 Nitpick comments (11)
markdown/blog/community-spotlight-ashmit.md (11)
1-16: YAML Front Matter Review
The metadata is well-structured with clear fields (title, date, type, tags, cover, authors, excerpt). As a minor stylistic note, you might consider rephrasing the excerpt for improved flow (for example, “Says, Ashmit” could be refined for clarity).
19-19: Introduction Paragraph Stylistic Suggestion
In the opening paragraph, consider hyphenating “Open source contributions” to “Open‐source contributions” so that the compound adjective clearly modifies “contributions” per style guidelines.
21-27: The GSoC Experience Section
This section is engaging and effectively conveys Ashmit’s early GSoC journey. As a minor suggestion, in line 25, consider a stronger verb than “improve” (e.g. “enhance”) to further bolster the impact of the learning described.🧰 Tools
🪛 LanguageTool
[style] ~25-~25: Consider an alternative verb to strengthen your wording.
Context: ...earned how to navigate large codebases, improve my problem-solving skills, and contribu...(IMPROVE_STRENGTHEN)
39-43: Project Description Clarity
The section detailing the revamp of the AsyncAPI Conference website is clear. For enhanced clarity, you might expand briefly on how standardizing the codebase improved maintainability.
55-63: Community Experience and Mentorship
The discussion on mentorship and community support is comprehensive. As a stylistic improvement, in line 63 consider hyphenating “open source” to “open‐source” for consistency when used as an adjective.🧰 Tools
🪛 LanguageTool
[uncategorized] ~63-~63: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...roject management, which are crucial in open source and professional environments alike.* ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
92-103: Fun Q&A Activity Section
The interactive Q&A is engaging. As a minor note, review the trailing asterisks in the speaker labels for consistency, though they do not impede understanding.
110-112: Consistent Branding for Code Editors
In the segment about code editors (lines 110–112), please update “Vs code” to “VS Code” and consider clarifying “X code” to “Xcode” to ensure consistent and standard naming.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
110-110: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
114-115: Operating System Naming & Punctuation
The question “Window or Linux” on line 114 likely intends “Windows” rather than “Window.” Additionally, in Ashmit’s response on line 115, consider capitalizing “Fedora” and adding a comma for clarity (e.g. “Linux. Not hardcore Linux, like Fedora though.”).🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
114-114: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
122-124: Hobby Description Enhancement
In the hobby section (lines 122–124), consider rephrasing “I do like to cook” to “I enjoy cooking” to enhance the tone. Also, adding a comma after introductory phrases can improve readability (e.g. “if I have some free time, that’s where I go…”).🧰 Tools
🪛 LanguageTool
[typographical] ~124-~124: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because if ...(YES_NO_COMMA)
[style] ~124-~124: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because if I have some free t...(LIKE_TO_ENJOY)
[style] ~124-~124: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...o cook sometimes because if I have some free time that's where I go towards the kitchen.*...(FREE_TIME)
126-128: Streamlining the Thank-you Note
In Ashmit’s shout-out section, the phrase “and on top of that” is a bit wordy. Consider replacing it with a more concise term such as “additionally” to tighten the language.🧰 Tools
🪛 LanguageTool
[style] ~126-~126: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...(A_LOT_OF)
[style] ~128-~128: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz](https:/...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
132-132: Concluding Narrative Consistency
The concluding passage on line 132 nicely encapsulates Ashmit’s journey. For consistency, when “open source” is used as an adjective (as in “open-source”), consider applying the hyphen even here.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-ashmit.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-ashmit.md
[uncategorized] ~18-~18: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... in Computer Science from India." --- Open Source contributions have long been a gateway ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~25-~25: Consider an alternative verb to strengthen your wording.
Context: ...earned how to navigate large codebases, improve my problem-solving skills, and contribu...
(IMPROVE_STRENGTHEN)
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...
(COMPLETELY_ENTIRELY)
[uncategorized] ~63-~63: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...roject management, which are crucial in open source and professional environments alike.* ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...
(COMPLETELY_ENTIRELY)
[grammar] ~73-~73: The pronoun ‘you’ must be used with a non-third-person form of a verb.
Context: ...ributions, whereas as a maintainer, you oversees multiple contributions and ensure the s...
(NON3PRS_VERB)
[typographical] ~104-~104: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...
(TO_BE_HONEST_COMMA)
[typographical] ~116-~116: It seems that a comma is missing.
Context: ...** Linux. Not hardcore Linux like fedora though.* Bami: Apple or Samsung. ***Ash...
(THOUGH_COMMA)
[typographical] ~124-~124: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because if ...
(YES_NO_COMMA)
[style] ~124-~124: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because if I have some free t...
(LIKE_TO_ENJOY)
[style] ~124-~124: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...o cook sometimes because if I have some free time that's where I go towards the kitchen.*...
(FREE_TIME)
[style] ~126-~126: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...
(A_LOT_OF)
[style] ~128-~128: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz](https:/...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-ashmit.md
110-110: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
114-114: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (5)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Test NodeJS PR - macos-13
- GitHub Check: Lighthouse CI
🔇 Additional comments (8)
markdown/blog/community-spotlight-ashmit.md (8)
29-37: Getting Started Section
The “Getting Started with Google Summer of Code and AsyncAPI” section is clear and inviting. Ashmit’s narrative is well-presented with no notable issues.
45-49: Challenges and Learning Experiences
This segment candidly presents the challenges faced and the lessons learned. The narrative is informative and needs no change.
79-87: Looking Ahead Section
This section clearly outlines Ashmit’s future plans and reflects well on his commitment. The content is clear and needs no revisions.
104-104: Punctuation Enhancement in Response
In line 104, consider adding a comma after “just this week” to improve readability (e.g. “I deleted both of them just this week, yeah, both are toxic in their own ways…”).
[typographical]🧰 Tools
🪛 LanguageTool
[typographical] ~104-~104: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...(TO_BE_HONEST_COMMA)
106-108: Simple Q&A Clarity
The “Google Docs or Microsoft Word” question and response are clear and succinct.
118-120: OS Preference Clarity
The “Apple or Samsung” Q&A is clear. Ashmit’s response “Samsung” is concise and requires no changes.
130-130: Encouraging Advice Section
The guidance provided on line 130 is clear and appropriately inspirational. No changes are necessary here.
134-134: Final Call-to-Action
The closing invitation welcoming new contributors is engaging and well-written.
iambami
changed the title
|
@akshatnema @thulieblack @TRohit20 Final review, please. 🙏 |
iambami
changed the title
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (11)
markdown/blog/community-spotlight-ashmit.md (11)
39-43: Project Description & Wording ImprovementIn Ashmit’s answer about his project (lines 39–43), consider revising the adverb in the phrase “didn’t learn a completely new programming language.” Using a more precise alternative (for example, “entirely” or “brand new”) could add clarity and strength to the statement.
🧰 Tools
🪛 LanguageTool
[style] ~43-~43: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...(COMPLETELY_ENTIRELY)
51-53: Article Correction: Article UsageIn the response on lines 51–53, please change “a entirely new programming language” to “an entirely new programming language” to correct the article usage.
🧰 Tools
🪛 LanguageTool
[misspelling] ~53-~53: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...nd-to-end testing. While I didn’t learn a entirely new programming language durin...(EN_A_VS_AN)
71-73: Punctuation & Style in Experience ReflectionIn Ashmit’s reflection on his earlier open‑source experience, consider removing (or re‑evaluating) the comma before “when they still gave out T-shirts” to improve flow. Additionally, you might consider revising “a completely different experience” for even greater impact.
🧰 Tools
🪛 LanguageTool
[typographical] ~73-~73: Usually, there’s no comma before “when”.
Context: ...ously participated in Hacktoberfest 2021, when they still gave out T-shirts! However, ...(IF_NO_COMMA)
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...(COMPLETELY_ENTIRELY)
89-89: Markdown Emphasis CorrectionThe phrase This or That is currently formatted in italics. For consistency with the overall style (and based on previous guidance), consider using bold formatting instead (for example, "This or That").
91-94: Brand Name CasingIn the Q&A activity, “Github” appears on line 93. Consider capitalizing it as “GitHub” to align with the correct brand styling.
95-98: Consistent Platform NamingOn line 95, “Slack or discord” is mentioned. For consistency, ensure both platform names are capitalized (e.g., “Slack or Discord”).
99-101: Punctuation Improvement in ResponseIn Ashmit’s response about LinkedIn or Twitter (lines 99–101), adding a comma before “to be honest” (i.e. “Yeah, both are toxic in their own ways, to be honest.”) would improve readability.
🧰 Tools
🪛 LanguageTool
[typographical] ~101-~101: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...(TO_BE_HONEST_COMMA)
107-110: Correct Capitalization for IDE NamesIn the exchange on lines 107–110, please update “Vs code” to “VS Code” and consider standardizing “X code” to “Xcode” to maintain product naming consistency.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
107-107: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
111-113: Improve Linux DescriptionFor the Linux preference (lines 111–113), add a comma and capitalize “fedora” to “Fedora.” For example, revise to: “Linux. Not hardcore Linux, like Fedora, though.”
🧰 Tools
🪛 LanguageTool
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like fedora though.* Bami: Apple or Samsung. ***Ashm...(THOUGH_COMMA)
🪛 markdownlint-cli2 (0.17.2)
111-111: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
119-122: Hobbies Description EnhancementIn Ashmit’s reply about his hobbies (lines 119–122), consider rephrasing “like to cook” as “enjoy cooking” and replacing “free time” with “spare time.” Also, adding a comma after introductory phrases could improve readability.
🧰 Tools
🪛 LanguageTool
[typographical] ~121-~121: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because whe...(YES_NO_COMMA)
[style] ~121-~121: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because when I have some free...(LIKE_TO_ENJOY)
[style] ~121-~121: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...cook sometimes because when I have some free time that's where I go, towards the kitchen....(FREE_TIME)
123-125: Refine Gratitude ExpressionIn the gratitude section (lines 123–125), rephrase “the ones who I would like to shout out to like is” to something like “the mentors I would like to shout out—namely” to improve grammatical clarity and conciseness. Also, consider replacing “on top of that” with a simpler transitional phrase.
🧰 Tools
🪛 LanguageTool
[style] ~123-~123: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...e kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...(A_LOT_OF)
[uncategorized] ~125-~125: The verb “is” doesn’t seem to fit in this context, “are” is probably more formally correct.
Context: ...s who I would like to shout out to like is [Aishat Muibudeen](https://www.linkedin...(AI_HYDRA_LEO_CPT_IS_ARE)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-ashmit.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-ashmit.md
[style] ~43-~43: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...
(COMPLETELY_ENTIRELY)
[misspelling] ~53-~53: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...nd-to-end testing. While I didn’t learn a entirely new programming language durin...
(EN_A_VS_AN)
[typographical] ~73-~73: Usually, there’s no comma before “when”.
Context: ...ously participated in Hacktoberfest 2021, when they still gave out T-shirts! However, ...
(IF_NO_COMMA)
[style] ~73-~73: Consider using a different adverb to strengthen your wording.
Context: ... GSoC mentee and later a maintainer was a completely different experience. As a mentee, you ...
(COMPLETELY_ENTIRELY)
[typographical] ~101-~101: Consider adding a comma here.
Context: .... Yeah, both are toxic in their own ways to be honest.* **Bami: Google Docs or Mic...
(TO_BE_HONEST_COMMA)
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like fedora though.* Bami: Apple or Samsung. ***Ashm...
(THOUGH_COMMA)
[typographical] ~121-~121: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do like to cook sometimes because whe...
(YES_NO_COMMA)
[style] ~121-~121: You could make your writing stronger and more vivid by rephrasing “like to cook” as “enjoy cooking”.
Context: ...t say cooking is one of them. Yeah I do like to cook sometimes because when I have some free...
(LIKE_TO_ENJOY)
[style] ~121-~121: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...cook sometimes because when I have some free time that's where I go, towards the kitchen....
(FREE_TIME)
[style] ~123-~123: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...e kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...
(A_LOT_OF)
[uncategorized] ~125-~125: The verb “is” doesn’t seem to fit in this context, “are” is probably more formally correct.
Context: ...s who I would like to shout out to like is [Aishat Muibudeen](https://www.linkedin...
(AI_HYDRA_LEO_CPT_IS_ARE)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-ashmit.md
107-107: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
111-111: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (3)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
🔇 Additional comments (14)
markdown/blog/community-spotlight-ashmit.md (14)
1-16: Metadata Header VerifiedThe YAML header is well‑structured and includes all the necessary metadata such as title, date, type, tags, cover image, author details, and an excerpt. Please double‑check that the excerpt’s tone matches your intended messaging.
19-27: Introduction Content OverviewThe introductory paragraph effectively sets the stage for Ashmit’s spotlight story. The narrative clearly outlines the blog’s purpose and establishes context.
29-32: Section Heading & Q&A IntroductionThe section heading "Getting Started with Google Summer of Code and AsyncAPI" and the opening question are engaging and clear.
33-34: Ashmit’s Initial ResponseAshmit’s first answer provides a strong background on his aspiration and preparation for GSoC. The tone is conversational and clear.
35-37: Detailing Early DiscoveriesThe explanation on how Ashmit discovered AsyncAPI is descriptive and informative. No changes necessary.
55-63: Community Experience SectionThe Q&A segment discussing Ashmit’s experience with the AsyncAPI community and mentorship is clear and effectively communicates support and collaboration.
65-69: Key Takeaways SectionThe key lessons and takeaways from the GSoC experience are well summarized and motivating.
75-77: Advice for Future ContributorsThe advice provided to future GSoC mentees and newcomers to AsyncAPI is clear and encouraging.
79-83: Future Plans SectionAshmit’s outlook and plans for the future are well articulated, providing a natural transition from his GSoC experience.
85-87: Discussion on Proposed ImprovementsThe conversation regarding potential new features or improvements for AsyncAPI is concise and on‑point.
103-106: Tool Preference ClarityThe response regarding Google Docs vs. Microsoft Word is clear and succinct.
115-118: Device Preference VerificationThe preference for “Apple or Samsung” is clearly stated, and the response “Samsung” is concise.
127-127: Encouragement Quote IntegrityThe quoted advice for prospective contributors (line 127) is motivational and well‑presented.
129-131: Conclusion & Call-to-ActionThe final paragraph effectively invites new contributors and wraps up the spotlight story in an engaging manner.
|
@akshatnema Do you have an idea why this PR is not passing the checks? |
|
@iambami check the nitpicks as well |
|
@thulieblack @akshatnema kindly check it out. |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (7)
markdown/blog/community-spotlight-ashmit.md (7)
27-28: Smooth Transition with Minor Opportunity for Clarity
The transitional sentence ("We then asked Ashmit about his GSoC experience with the AsyncAPI Initiative.") works well. Consider a slight rewording (for example, “Following his initial journey, we sat down with Ashmit to discuss his GSoC experience with the AsyncAPI Initiative”) to make the transition even smoother.
39-44: Project Description Dialogue – Minor Grammar Suggestion
The section detailing the conference website project is well written. As a minor nitpick, consider rephrasing the question on line 41 for improved clarity. For example:-**Bami: Can you tell us about your project, the problem it solved, and why was it important?** +**Bami: Can you tell us about your project, the problem it solved, and why it was important?**This change makes the question slightly more fluent.
51-53: Refine Adverb Usage in Technology Explanation
The description of the technologies used is clear. As a style refinement, consider replacing “completely new programming language” with “entirely new programming language” (or a more emphatic alternative) to enhance the strength of the wording.🧰 Tools
🪛 LanguageTool
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...(COMPLETELY_ENTIRELY)
89-90: Balanced Markdown Emphasis in Playful Game Intro
The playful introductory line for the “This or That” game employs triple asterisks appropriately. While triple emphasis (bold and italic) is acceptable, consider if using double asterisks (for bold) might better match the styling of other dialogue portions. Consistency is key, so adjust if needed per the project’s style guidelines.
91-112: Dialogue for “This or That” Activity – Minor Punctuation and Formatting Suggestions
The fun Q&A segment is engaging. A couple of points to consider:
- In the response describing Linux (line 110), the text “Linux. Not hardcore Linux, like Fedora though.” could benefit from a comma for clarity. For example:
-Linux. Not hardcore Linux, like Fedora though. +Linux. Not hardcore Linux, like Fedora, though.- The dialogue lines using bold for the questions (e.g., “Bami: …”) are styled using markdown emphasis. While this is acceptable for dialogue, note that markdownlint flagged such usage (MD036). If the project style prefers blockquotes or actual headings for dialogues, consider a brief discussion with the team; otherwise, this format is fine as is.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
107-107: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
111-111: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
113-114: Enhance Readability in Hobby Response
In Ashmit’s response regarding his hobbies (line 114), a couple of commas would improve readability. For instance, adding a comma after “Yeah”—resulting in:-Yeah I do enjoy cooking sometimes because when I have some spare time that's where I go, towards the kitchen. +Yeah, I do enjoy cooking sometimes because when I have some spare time, that's where I go, towards the kitchen.This minor change will help the sentence flow better.
🧰 Tools
🪛 LanguageTool
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like Fedora though.* Bami: Apple or Samsung. ***Ashm...(THOUGH_COMMA)
115-117: Streamline Mentor Shout-out Response
In Ashmit’s answer thanking mentors (line 116), consider refining the phrasing:
- Instead of “a lot of people,” a more concise phrase (e.g., “many”) might improve clarity.
- Replace “And on top of that” with a shorter alternative like “Additionally” to avoid wordiness.
For example, a revised version might read:-And on top of that, I would like to thank [Lukasz Gornicki](https://www.linkedin.com/in/lukasz-gornicki-a621914/) for being quite helpful. Some issues in my project required his assistance, and he was there for them. +Additionally, I would like to thank [Lukasz Gornicki](https://www.linkedin.com/in/lukasz-gornicki-a621914/) for his helpful assistance when issues arose in my project.These are optional refinements aimed at enhancing clarity and conciseness.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-ashmit.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-ashmit.md
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...
(COMPLETELY_ENTIRELY)
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like Fedora though.* Bami: Apple or Samsung. ***Ashm...
(THOUGH_COMMA)
[typographical] ~121-~121: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do enjoy cooking sometimes because wh...
(YES_NO_COMMA)
[style] ~123-~123: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...e kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...
(A_LOT_OF)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-ashmit.md
107-107: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
111-111: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
🔇 Additional comments (11)
markdown/blog/community-spotlight-ashmit.md (11)
1-16: Metadata Front Matter is Well Structured
The YAML front matter correctly defines the title, date, type, tags, cover image, authors, and excerpt. Everything is properly formatted and consistent with the project guidelines.
19-20: Engaging Introduction Paragraph
The opening paragraph effectively sets an inviting tone for the spotlight story. No changes are needed here.
21-25: Clear Section on GSoC Experience
The section "The GSoC Experience: A Transformative Phase" and its content clearly outline Ashmit’s early journey in GSoC. The narrative is engaging and provides good context.
31-38: Dialogue on Getting Started is Clear and Readable
The Q&A segment regarding how Ashmit got started with Google Summer of Code is clearly formatted. The dialogue markers (using bold for the questions and triple asterisks for Ashmit’s answers) are consistent.
55-60: Mentorship and Community Section is Strong
The narrative on community experience and mentorship is detailed and uses the full, correct names for the mentors. This section aligns well with previous feedback and is clear.
61-63: Clear Explanation of Unexpected Challenges
The response regarding unexpected challenges is candid and informative. The content is clear and does not require changes.
65-73: Key Takeaways and Reflection are Impactful
Ashmit’s reflections on the GSoC experience and his evolving view on open source are effectively communicated. The dialogue flows naturally, offering genuine insights.
75-77: Concise and Inspiring Advice for Future Contributors
The advice section is succinct and encouraging. It delivers a clear message to upcoming GSoC mentees and newcomers without unnecessary wordiness.
79-83: Future Aspirations are Well Articulated
The segment outlining Ashmit’s future plans and aspirations communicates his next steps clearly. The tone is positive and forward-looking.
85-88: Clear Vision for Future Improvements
The discussion about potential future improvements to AsyncAPI is clear and focused. It invites engagement without overwhelming the reader.
117-119: Effective Conclusion and Call-to-Action
The closing paragraphs succinctly summarize Ashmit’s journey and encourage future contributors to engage. The tone and messaging are inspirational and align well with the community spirit.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (15)
markdown/blog/community-spotlight-ashmit.md (15)
19-20: Introduction Paragraph ClarityThe opening paragraph effectively introduces the theme and importance of open-source contributions. A minor stylistic review might help polish the tone if needed in subsequent edits.
23-25: GSoC Experience DetailsThe narrative detailing Ashmit’s initial journey is engaging. Consider a slight rewording for clarity (for example, refining adjectives or adverbs) to maintain an even tone throughout the document.
31-33: Q&A Formatting and Emphasis ConsistencyThe format for the question and answer—using markdown emphasis for the speakers (e.g., Bami: and *Ashmit: )—is clear. However, consider reviewing the balance of asterisks in Ashmit’s responses to ensure consistency across all Q&A items.
51-53: Technologies and Skills DiscussionAshmit’s explanation of the technologies used (Next.js, Cypress, and TypeScript) is succinct. A minor stylistic tweak—such as selecting a stronger adverb if desired—could enhance clarity.
🧰 Tools
🪛 LanguageTool
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...(COMPLETELY_ENTIRELY)
55-59: Community and Mentorship AppreciationThe section highlighting the AsyncAPI community and mentorship is well written. Please double-check that mentor names are fully correct and match the project’s naming guidelines.
65-69: Key Takeaways and AdviceThe “Key Takeaways” section presents valuable lessons from the GSoC experience. Consider using a blockquote for the advice in future edits to visually highlight these insights.
85-87: AsyncAPI Improvement DiscussionThe brief discussion on future improvements for the conference website is to the point. Expanding on specifics in future revisions might further engage the technical audience.
91-94: Fun Activity Q&A FormattingThe rapid-fire Q&A segment (starting with "Bami: Okay, so I have a fun activity…") is engaging. However, note that in Ashmit’s answers (e.g., line 93), the closing emphasis markers are unbalanced (e.g., ending with a single asterisk). Please adjust these so that the opening and closing emphasis markers match (for example, use three asterisks on both sides).
95-97: Slack vs Discord Format ConsistencySimilar to the previous Q&A block, ensure that Ashmit’s answer in this segment uses balanced markdown emphasis to avoid rendering issues.
99-101: Social Media Preferences FormattingThe Q&A regarding LinkedIn versus Twitter is clear in content. However, verify that the markdown emphasis in Ashmit’s answer is balanced, as seen in previous blocks.
107-109: Code Editor Preference FormattingThe line "Bami VS Code or Xcode" appears as emphasized text rather than a clearly formatted question. Consider reformatting this line (for example, by using a proper heading or blockquote) to distinguish it from other emphasized text used for dialogue.
[markdownlint]🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
107-107: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
111-113: Operating System PreferenceThe exchange on “Window or Linux” is engaging. In Ashmit’s response ("Linux. Not hardcore Linux, like Fedora though."), a comma after “Linux” would improve clarity as suggested by static analysis.
🧰 Tools
🪛 LanguageTool
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like Fedora though.* Bami: Apple or Samsung. ***Ashm...(THOUGH_COMMA)
🪛 markdownlint-cli2 (0.17.2)
111-111: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
115-117: Device Preference DetailingThe question regarding Apple versus Samsung is clear. As with previous answers, ensure that the markdown emphasis for Ashmit’s response is balanced.
119-121: Hobbies and Interests DetailAshmit’s response on his hobbies is personable. A missing comma after “spare time” is noted by static analysis; consider revising to:
"Yeah, I do enjoy cooking sometimes because when I have some spare time, that's where I go, towards the kitchen."🧰 Tools
🪛 LanguageTool
[typographical] ~121-~121: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do enjoy cooking sometimes because wh...(YES_NO_COMMA)
[uncategorized] ~121-~121: A comma might be missing here.
Context: ...ometimes because when I have some spare time that's where I go, towards the kitchen....(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
123-125: Community Shout-Outs ClarityThe thank-you note is warm and inclusive. To tighten the prose, consider rephrasing phrases like "on top of that" to something more concise (e.g., "I would also like to thank…").
🧰 Tools
🪛 LanguageTool
[style] ~123-~123: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...e kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...(A_LOT_OF)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-ashmit.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-ashmit.md
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...
(COMPLETELY_ENTIRELY)
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like Fedora though.* Bami: Apple or Samsung. ***Ashm...
(THOUGH_COMMA)
[typographical] ~121-~121: It seems that a comma is missing.
Context: ...es, I might say cooking is one of them. Yeah I do enjoy cooking sometimes because wh...
(YES_NO_COMMA)
[uncategorized] ~121-~121: A comma might be missing here.
Context: ...ometimes because when I have some spare time that's where I go, towards the kitchen....
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[style] ~123-~123: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...e kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...
(A_LOT_OF)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-ashmit.md
107-107: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
111-111: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (5)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Test NodeJS PR - macos-13
- GitHub Check: Test NodeJS PR - windows-latest
🔇 Additional comments (15)
markdown/blog/community-spotlight-ashmit.md (15)
1-16: Front Matter ValidationThe YAML front matter is well structured with all required metadata (title, date, type, tags, cover, authors, and excerpt). Ensure that the excerpt’s tone aligns with the article’s narrative.
21-22: Heading FormattingThe “## The GSoC Experience: A Transformative Phase” heading is clearly rendered as a markdown section title.
27-28: Conversation TransitionThe sentence transitioning into the Q&A format ("We then asked Ashmit about his GSoC experience…") provides a smooth segue.
29-30: Section Heading ConsistencyThe heading “## Getting Started with Google Summer of Code and AsyncAPI” is appropriately formatted and sets the stage for the following Q&A segment.
35-37: AsyncAPI Discovery DiscussionThe question regarding how Ashmit learned about AsyncAPI and his motivations is clearly delineated, and the answer enriches the narrative with specific details.
39-43: Project Description SectionThe “The Project: Revamping the AsyncAPI Conference Website” section effectively outlines the problem and the implemented solution, including standardized updates and automated testing.
45-49: Challenges and ResolutionThe challenges section clearly recounts the difficulties faced, and the fix (“troubleshot” instead of “troubleshoot”) ensures past-tense consistency.
61-63: Remote Collaboration ChallengesThe discussion regarding the challenges of remote collaboration is clear and informative, outlining a common modern challenge in open-source work.
71-73: Perception Shift DiscussionThe exchange on the evolution from a mentee to a maintainer is coherent. The comparative language is simple and effective.
75-77: Future Advice for MenteesThe advice offered to future GSoC mentees is succinct and impactful. The formatting is consistent with other Q&A items.
79-83: Outlook on Future ContributionsThe section on future plans clearly outlines Ashmit’s intentions regarding his career and ongoing contributions. The narrative is both engaging and motivational.
89-89: Emphasis on Fun ActivityThe sentence "To add a bit of fun to our spotlight interview, we played a This or That game with Ashmit." appears correctly formatted with balanced emphasis markers.
103-105: Document Software ChoiceThe section discussing the preference for Google Docs over Microsoft Word is clearly stated and correctly formatted.
127-127: Final Advice QuotationThe concluding quote that advises new contributors is effectively emphasized with italic formatting. Please double-check that the quotation marks and asterisks are balanced for correct rendering.
129-131: Conclusion and Call-to-ActionThe final paragraphs succinctly summarize Ashmit’s journey and encourage community participation. The tone is motivational and the call-to-action is clear.
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.
Actionable comments posted: 1
🔭 Outside diff range comments (7)
config/tools-automated.json (7)
13-25:⚠️ Potential issueDuplicate Filter Keys in APIs Entry
In the first "AsyncAPI Server API" entry (lines 6–12), the
"filters"object contains duplicate keys:"filters": { "technology": [ "Node.js", "TypeScript" ], "categories": [ "api" ], "hasCommercial": false, "isAsyncAPIOwner": true, "hasCommercial": false, "isAsyncAPIOwner": false }The duplicate keys (lines 21–24) will cause the latter values to override the former. Please remove the duplicates and ensure that the correct boolean values are set (for example, if the official API should be owned by AsyncAPI, then use
"isAsyncAPIOwner": trueonly).- "hasCommercial": false, - "isAsyncAPIOwner": true, - "hasCommercial": false, - "isAsyncAPIOwner": false + "hasCommercial": false, + "isAsyncAPIOwner": true
55-88: 🛠️ Refactor suggestionOverwritten Filters in Code-first Tools Entry
Within the "Code-first tools" section's first entry for "Zod Sockets", two separate
"filters"objects are defined consecutively (lines 59–74 and lines 75–87). Because JSON objects cannot have duplicate keys, the second"filters"key will overwrite the first one entirely. If you intended to list multiple sets of filter criteria, consider splitting this into two separate tool entries or merging the criteria into one"filters"object.
91-114: 🛠️ Refactor suggestionDuplicate "Code-first tools" Key
A second "Code-first tools" key is defined starting at line 91. Duplicate keys in JSON are invalid and can lead to unpredictable behavior. Please merge these sections into a single "Code-first tools" key and consolidate their tool list entries.
115-140:⚠️ Potential issueMalformed JSON Structure in AsyncAPI.Net Entry
The entry for "AsyncAPI.Net" (starting at line 115) shows structural issues – for example, the
"filters"object is not closed properly before another"links"key appears, and duplicate keys are present. This results in invalid JSON. Please review and correct the JSON structure, ensuring that each tool entry has a single, well-formed set of keys.
178-203: 🛠️ Refactor suggestionDuplicate Zod Sockets Entries
Two entries for "Zod Sockets" are present. The first (lines 178–196) is complete, while the second (lines 199–203) appears incomplete (e.g. it has an empty
"links"object). To avoid confusion and redundancy, consider removing the incomplete duplicate or merging its content with the complete entry.
224-265: 🛠️ Refactor suggestionInconsistent Structure in the Latter Part of Code-first Tools Section
Following the asyncapi-python entry, the subsequent part of this section includes another nested block with duplicated
"links"and"filters"keys (lines 224–265) that appears to repeat configuration details for the Socket.IO tool. The duplicated keys and nested structure are causing inconsistencies. Please review this segment and restructure it to ensure valid JSON and coherent grouping of tool information.
266-1709: 🛠️ Refactor suggestion
⚠️ Potential issueOverall Tools Automated Configuration Review
This file contains extensive updates across multiple sections (APIs, Code-first tools, Code Generators, DSL, Frameworks, etc.). In several segments, duplicate keys, repeated entries, and malformed JSON structures are evident. It is critical to consolidate duplicate entries and validate the JSON structure (using a JSON linter) before merging. Please review each section carefully to ensure that:
• Every tool entry is defined only once.
• The nested objects (such as"links"and"filters") are well formed and free from duplicate keys.
• The overall JSON complies with the required schema.These issues are structural and must be resolved to avoid runtime configuration errors.
🧹 Nitpick comments (7)
package.json (6)
6-6: ESM Module Declaration Added
The addition of"type": "module"clearly signals that the package is using ECMAScript modules. Please verify that all project modules and dependencies are compatible with ESM, especially if any legacy CommonJS modules are still in use.
7-15: Updated Script Commands for TypeScript Execution
The modifications to the scripts (e.g.,"build:pages","build:posts", and the new"write:blog"command) now leveragetsxfor executing TypeScript files. Ensure that these new commands are thoroughly tested and that any documentation or usage instructions are updated accordingly.
22-29: New Asset Generation Scripts Introduced
The new commands for generating meetings, dashboard, videos, and tools (usingtsx) help standardize asset generation. Please double-check that these scripts work as intended in all environments and consider adding tests or documentation for maintenance.
119-120: New Dependencies: tsx and winston
Adding"tsx": "^4.19.2"supports the new TypeScript script execution commands, and"winston": "^3.17.0"provides robust logging. Verify that their inclusion does not introduce any compatibility issues and that related documentation reflects these updates.
124-148: Enhanced TypeScript and Build Tooling in devDependencies
The addition of dev-dependencies such as@babel/preset-typescript,@types/fs-extra,@types/inquirer,@types/jest, andbabel-plugin-transform-import-metawill improve the build process and development experience. Make sure that any custom build scripts or testing configurations are updated to accommodate these changes.
169-170: Updated Storybook and TypeScript Versions
The updates tostorybookandtypescriptindicate a move toward more current tool versions. It would be beneficial to perform comprehensive end-to-end tests following these upgrades to ensure that there are no unexpected issues.config/all-tags.json (1)
1-1: Updated Scala language color scheme!The color scheme for Scala has been changed from reddish tones to green tones. However, I noticed there's a duplicate entry for Scala in the technologies section that still uses the old colors.
Consider also updating the duplicate Scala entry in the technologies section to maintain color consistency:
-{"name":"Scala","color":"bg-[#D7C7F2]","borderColor":"border-[#A387D2]"}, +{"name":"Scala","color":"bg-[#57f281]","borderColor":"border-[#37f069]"},
🛑 Comments failed to post (1)
config/tools-automated.json (1)
27-47: 🛠️ Refactor suggestion
Duplicate API Entry Detected
There are two entries for "AsyncAPI Server API" in the APIs section. The second entry (lines 27–47) is almost identical to the first one but already uses the corrected key values. To avoid redundancy and potential confusion, please consolidate these entries into a single entry.
| @@ -0,0 +1,131 @@ | |||
| --- | |||
| title: "From Mentee to Maintainer: The Ashmit GSoC Story!" | |||
| date: 2025-03-10T06:00:00+01:00 | |||
There was a problem hiding this comment.
Before approving, change the date to the 17th
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (7)
markdown/blog/community-spotlight-ashmit.md (7)
53-53: Stylistic Adverb Suggestion.
Consider replacing "completely new programming language" with "entirely new programming language" to improve the flow of the sentence.🧰 Tools
🪛 LanguageTool
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...(COMPLETELY_ENTIRELY)
89-89: Creative Use of Emphasis.
The styling for the "This or That" game (i.e. using triple emphasis as in***This or That***) is engaging. Please verify that it renders as intended across various Markdown viewers.
93-117: Markdown Emphasis Consistency in Ashmit's Responses.
Several responses by Ashmit (lines 93, 97, 101, 105, 109, 113, and 117) include an extra trailing asterisk (e.g.,***Ashmit:** GitHub*), which leads to unbalanced Markdown formatting. Removing the extra trailing asterisk will improve consistency.For example:
-***Ashmit:** GitHub* +***Ashmit:** GitHub🧰 Tools
🪛 LanguageTool
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like Fedora though.* Bami: Apple or Samsung. ***Ashm...(THOUGH_COMMA)
🪛 markdownlint-cli2 (0.17.2)
107-107: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
111-111: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
107-111: Dialogue Formatting and Typo Correction.
- On line 107, add a colon after "Bami" to maintain consistent dialogue formatting (e.g., Bami: VS Code or Xcode?).
- On line 111, correct "Window" to "Windows" for the operating system name.
For example:
-**Bami VS Code or Xcode** +**Bami: VS Code or Xcode?**-**Bami: Window or Linux** +**Bami: Windows or Linux**🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
107-107: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
111-111: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
113-113: Punctuation Adjustment in Linux Dialogue.
On line 113, consider adding a comma after "Linux" to improve readability.For example:
-***Ashmit:** Linux. Not hardcore Linux, like Fedora though. +***Ashmit:** Linux, not hardcore Linux, like Fedora though.🧰 Tools
🪛 LanguageTool
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like Fedora though.* Bami: Apple or Samsung. ***Ashm...(THOUGH_COMMA)
123-125: Refine Dialogue Wording.
- In the question on line 123, consider rephrasing "a lot of people" to "many people" for conciseness.
- On line 125, replace "And on top of that" with "Additionally," to streamline the sentence.
🧰 Tools
🪛 LanguageTool
[style] ~123-~123: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...e kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...(A_LOT_OF)
[misspelling] ~125-~125: Did you mean “should”?
Context: ...Ashmit: The mentors I would like to shout out are [Aishat Muibudeen](https://www....(SHOUT_SHOULD)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
125-125: Tone Adjustment Suggestion.
Consider rephrasing "shout out" to "thank" in line 125 for a slightly more formal tone, if that aligns with the overall style of the article.🧰 Tools
🪛 LanguageTool
[misspelling] ~125-~125: Did you mean “should”?
Context: ...Ashmit: The mentors I would like to shout out are [Aishat Muibudeen](https://www....(SHOUT_SHOULD)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-ashmit.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-ashmit.md
[style] ~53-~53: Consider using a different adverb to strengthen your wording.
Context: ...nd-to-end testing. While I didn’t learn a completely new programming language during GSoC, I...
(COMPLETELY_ENTIRELY)
[typographical] ~113-~113: It seems that a comma is missing.
Context: ...* Linux. Not hardcore Linux, like Fedora though.* Bami: Apple or Samsung. ***Ashm...
(THOUGH_COMMA)
[style] ~123-~123: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...e kitchen.* **Bami: Is there anyone or a lot of people you would like to thank or give ...
(A_LOT_OF)
[misspelling] ~125-~125: Did you mean “should”?
Context: ...Ashmit: The mentors I would like to shout out are [Aishat Muibudeen](https://www....
(SHOUT_SHOULD)
[style] ~125-~125: ‘on top of that’ might be wordy. Consider a shorter alternative.
Context: ...s://www.linkedin.com/in/acebuild/). And on top of that, I would like to thank [Lukasz Gornicki...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-ashmit.md
107-107: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
111-111: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (3)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
🔇 Additional comments (1)
markdown/blog/community-spotlight-ashmit.md (1)
1-16: Metadata Front Matter Looks Good.
The YAML metadata is correctly formatted and captures all the necessary information (title, date, tags, cover image, authors, and excerpt). If desired, you might review the excerpt's phrasing for clarity, but it works well as is.
Description
Hello everyone,
Our first community spotlight blog is up. Kindly give your review.
cc @thulieblack @quetzalliwrites @TRohit20
Summary by CodeRabbit