Skip to content

docs: webinar series initiative #1847

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

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

iambami
Copy link
Contributor

@iambami iambami commented Apr 6, 2025

Hello everyone 👋
Given our discussion, here is a draft of the webinar series initiative.

Go through it and drop your reviews.

cc/ @derberg @thulieblack @TRohit20 @AceTheCreator

Summary by CodeRabbit

  • Documentation
    • Introduced a new document outlining the AsyncAPI Webinar Series Initiative, including goals, benefits for attendees and speakers, event structure, preparation guidelines, and participation details.

Copy link
Contributor

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

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

Rest looks good to me.

@thulieblack
Copy link
Member

please follow the appropriate Conventional Commits

Copy link

coderabbitai bot commented Apr 8, 2025

Walkthrough

A new document has been added describing the AsyncAPI Webinar Series Initiative. The document outlines the purpose, goals, benefits, format, event checklist, potential speakers, and calls to action for the webinar series, providing comprehensive guidelines for organizing and participating in the initiative.

Changes

File(s) Change Summary
webinar_series_initiative.md Added a new document detailing the AsyncAPI Webinar Series Initiative, including purpose, goals, benefits, format, event checklist, speaker profiles, and participation guidelines.

Poem

A webinar series, fresh and bright,
For AsyncAPI, sharing insight.
With speakers and learners from far and near,
Questions and answers, everyone here!
Rabbits hop in, eager to see
How knowledge grows in community.
🌱🎤

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@iambami iambami changed the title docs:webinar-series-initiative docs: webinar series initiative Apr 8, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (5)
webinar_series_initiative.md (5)

7-10: Enhance Descriptor for Insights

On lines 9–10, the phrase “gain deeper insights” could be strengthened. Consider using “gain in-depth insights” to deliver a more impactful message.

-As AsyncAPI continues to evolve, we recognize the need for more interactive and accessible learning opportunities. While documentation, blog posts, and conferences are great, webinars offer a real-time, engaging format where participants can ask questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem.
+As AsyncAPI continues to evolve, we recognize the need for more interactive and accessible learning opportunities. While documentation, blog posts, and conferences are great, webinars offer a real-time, engaging format where participants can ask questions, share experiences, and gain in-depth insights into the AsyncAPI ecosystem.
🧰 Tools
🪛 LanguageTool

[style] ~9-~9: Consider an alternative adjective to strengthen your wording.
Context: ... questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem. ...

(DEEP_PROFOUND)


32-37: Refine Bullet Point Phrasing

The bullet points in the “Benefits of the Webinar Series” section all begin with “For …”. Rephrasing these can improve the flow and readability. For example:

- - For Attendees: Learning, skill-building, and networking opportunities.
- - For Speakers: Exposure, recognition, and a platform to share ideas.
- - For the Community: A growing knowledge base, increased collaboration, and a more vibrant ecosystem.
+ - Attendees enjoy learning, skill-building, and networking opportunities.
+ - Speakers benefit from enhanced exposure, recognition, and a platform to showcase their ideas.
+ - The community gains an expanding knowledge base, improved collaboration, and a more vibrant ecosystem.
🧰 Tools
🪛 LanguageTool

[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ition, and a platform to share ideas. - For the Community: A growing knowledge base...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


40-40: Heading Formatting – Remove Trailing Punctuation

The heading “### For Hosts:” on line 40 ends with a colon, which is flagged by markdown lint. Removing it will ensure consistency with style guidelines.

-### For Hosts:
+### For Hosts
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

40-40: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


42-42: Typo Correction

In the bullet under “For Hosts”, “familarized” is misspelled. It should be “familiarized”.

- - Get familarized with the hosting platform (Restream)
+ - Get familiarized with the hosting platform (Restream)

48-48: Heading Formatting – Remove Trailing Punctuation

Similarly, the heading “### For Guests:” on line 48 ends with a colon. Removing the colon will align the heading with markdown style guidelines.

-### For Guests:
+### For Guests
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

48-48: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1a1c24 and 09043d2.

📒 Files selected for processing (1)
  • webinar_series_initiative.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
webinar_series_initiative.md

[style] ~9-~9: Consider an alternative adjective to strengthen your wording.
Context: ... questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem. ...

(DEEP_PROFOUND)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ition, and a platform to share ideas. - For the Community: A growing knowledge base...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 markdownlint-cli2 (0.17.2)
webinar_series_initiative.md

40-40: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


48-48: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

🔇 Additional comments (11)
webinar_series_initiative.md (11)

1-2: Great Title and Overview

The title clearly sets the tone and purpose of the document. The use of a descriptive headline benefits readers immediately.


3-6: Clear Introduction Section

The introduction succinctly communicates the initiative’s purpose and audience. The message is clear and engaging.


11-15: Well-Defined Goals

The “Our goals include:” section is concise and clearly outlines the objectives of the webinar series.


16-23: Why You Should Attend is Effective

This section clearly communicates the benefits for attendees. The bullet points are direct and informative.


24-31: Compelling Call to Speak

The “Why You Should Speak” section effectively encourages potential speakers by highlighting tangible benefits.


55-61: Solid Content Structure Outline

The “Suggested Content Structure” section clearly lays out the webinar flow. The steps are well-organized and easy to follow.


62-78: Comprehensive Event Checklist

Both the “Pre-Event” and “Post-Event” checklists are thorough and cover necessary logistics for a successful webinar.


79-87: Effective Potential Speakers Section

The section on potential speakers communicates diversity in expertise and inclusivity effectively.


88-93: Strong Recap Section

The recap of the first session is engaging, and the inclusion of a replay link adds great value for those who missed the live event.


94-100: Engaging Conclusion

The “What’s Next?” section does a great job of inviting ongoing participation and clearly calls the community to action.


1-100: Commit Message Best Practices Reminder

While the document is well-structured and comprehensive, please ensure that future commit messages adhere to the Conventional Commits guidelines as recommended in previous discussions.

🧰 Tools
🪛 LanguageTool

[style] ~9-~9: Consider an alternative adjective to strengthen your wording.
Context: ... questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem. ...

(DEEP_PROFOUND)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ition, and a platform to share ideas. - For the Community: A growing knowledge base...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 markdownlint-cli2 (0.17.2)

40-40: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


48-48: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

Copy link
Member

@thulieblack thulieblack left a comment

Choose a reason for hiding this comment

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

Minor additions, but make sure that everyone who usually hosts the series reviews and approves the requirements. Also, it'll be nice to know which community/marketing goal the initiative aligns with and how frequently the series will be for consistency's sake.


The AsyncAPI Webinar Series is just getting started! Stay tuned for upcoming sessions, and if you have suggestions for topics or speakers, we’d love to hear from you.

Want to attend the next session? Follow our updates and turn on notifications! 📢 Interested in speaking? Reach out to us—we’d love to have you!
Copy link
Member

Choose a reason for hiding this comment

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

Where should they follow for updates? To whom are they reaching out, and how do they propose a topic?


### Post-Event

- Share a recap blog post and recording.
Copy link
Member

Choose a reason for hiding this comment

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

Who will write the blog post? Recording I may understand

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Me! If it won’t be too much of a blog post. I plan to write a summary blog after each webinar. Do you advise otherwise? @thulieblack

### Post-Event

- Share a recap blog post and recording.
- Gather feedback from attendees and speakers.
Copy link
Member

Choose a reason for hiding this comment

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

How will the feedback be gathered?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The same way the previous one was gathered. From the attendees' comments on Youtube and on socials when it’s landed.

- Interactive Q&A: Participants get the chance to ask questions and engage with the speaker.
- Closing Remarks: Final takeaways, announcements, and what’s coming next.

## Event Checklist (Pre and Post)
Copy link
Member

Choose a reason for hiding this comment

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

Make this section an actual checklist.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Alright @thulieblack

- Keep the session on time and moderate the Q&A effectively.
- Coordinate with the speaker in advance to understand their presentation flow.

### For Guests:
Copy link
Member

Choose a reason for hiding this comment

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

Any recommended aspect ratio to be used? Guidelines on how to present the demo would be good. And mention how the demos should be visible

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Aspect ratio?

Copy link
Member

Choose a reason for hiding this comment

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

yes aspect ratio for when they're presenting demos

@iambami
Copy link
Contributor Author

iambami commented Apr 8, 2025

Minor additions, but make sure that everyone who usually hosts the series reviews and approves the requirements. Also, it'll be nice to know which community/marketing goal the initiative aligns with and how frequently the series will be for consistency's sake.

Alright.

@thulieblack
Copy link
Member

@iambami any update here?

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🔭 Outside diff range comments (1)
webinar_series_initiative.md (1)

90-93: 🛠️ Refactor suggestion

Enhance call-to-action: add LinkedIn link and fix typos

  • Provide the actual AsyncAPI LinkedIn URL.
  • Correct "subcribe" → "subscribe".
  • Wrap URLs in angle brackets to prevent Markdown parsing issues.
-The AsyncAPI Webinar Series is just getting started! Stay tuned for upcoming sessions, and if you have suggestions for topics or speakers, [we’d love to hear from you](https://join.slack.com/t/asyncapi/shared_invite/zt-32hejdicx-NrD~boRq71gpCBJAM8mFoA).
+The AsyncAPI Webinar Series is just getting started! Stay tuned for upcoming sessions, and if you have suggestions for topics or speakers, [we’d love to hear from you](<https://join.slack.com/t/asyncapi/shared_invite/zt-32hejdicx-NrD~boRq71gpCBJAM8mFoA>).

-Want to attend the next session? Follow our updates on LinkedIn, [subcribe to our YouTube page and turn on notifications!](https://www.youtube.com/@AsyncAPI) Interested in speaking? Reach out to us, we’d love to have you!
+Want to attend the next session? Follow our updates on LinkedIn at <https://www.linkedin.com/company/asyncapi/>, subscribe to our YouTube page and turn on notifications: <https://www.youtube.com/@AsyncAPI>. Interested in speaking? Reach out to us, we’d love to have you!
♻️ Duplicate comments (1)
webinar_series_initiative.md (1)

5-6: Introduction follows previously suggested copy
The introduction mirrors the wording recommended by @TRohit20 and effectively sets the tone for the initiative. Well done.

🧹 Nitpick comments (2)
webinar_series_initiative.md (2)

9-10: Consider strengthening the adjective in the key sentence
The phrase "gain deeper insights" is clear, but you might consider a stronger adjective for impact (e.g., "gain profound insights").

-While documentation, blog posts, and conferences are great, webinars offer a real-time, engaging format where participants can ask questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem.
+While documentation, blog posts, and conferences are great, webinars offer a real-time, engaging format where participants can ask questions, share experiences, and gain profound insights into the AsyncAPI ecosystem.
🧰 Tools
🪛 LanguageTool

[style] ~9-~9: Consider a different adjective to strengthen your wording.
Context: ... questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem. ...

(DEEP_PROFOUND)


48-54: Improve guest guidelines with aspect ratio recommendation

  • Remove trailing colon in the guest heading.
  • Suggest including a recommended aspect ratio for demos to address display consistency.
-### For Guests:
+### For Guests

- Prepare slides or a live demo that fits the topic.
+- Prepare slides or a live demo that fits the topic.
+- Ensure slides and demos are in a 16:9 aspect ratio for optimal viewing.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

48-48: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 09043d2 and bd56fb0.

📒 Files selected for processing (1)
  • webinar_series_initiative.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
webinar_series_initiative.md

[style] ~9-~9: Consider a different adjective to strengthen your wording.
Context: ... questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem. ...

(DEEP_PROFOUND)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ition, and a platform to share ideas. - For the Community: A growing knowledge base...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 markdownlint-cli2 (0.17.2)
webinar_series_initiative.md

40-40: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


48-48: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

@thulieblack
Copy link
Member

@AceTheCreator @TRohit20 your review

@iambami
Copy link
Contributor Author

iambami commented May 19, 2025

Hey @AceTheCreator, @thulieblack, and @TRohit20, please give your final review.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (1)
webinar_series_initiative.md (1)

1-1: Title consistency verified.
The document title now matches the file name and PR objective, including “Series” for clarity.

🧹 Nitpick comments (3)
webinar_series_initiative.md (3)

9-9: Consider stronger adjective to replace “deeper.”
To enhance impact, you might substitute “gain deeper insights” with a more vivid phrase, such as “gain comprehensive insights” or “gain in-depth insights.”

🧰 Tools
🪛 LanguageTool

[style] ~9-~9: Consider a different adjective to strengthen your wording.
Context: ... questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem. ...

(DEEP_PROFOUND)


75-76: Specify feedback collection method.
To close the feedback loop, clarify how feedback will be gathered (e.g., via a survey link, Slack poll, YouTube comments). For example:

- [ ] Gather feedback from attendees and speakers via a post-event survey (e.g., Google Forms or Typeform) and Slack channel poll.

90-93: Fix typo and add LinkedIn link.

  • Correct “subcribe” → “subscribe.”
  • Provide the LinkedIn updates link for consistency.
    Example diff:
-Want to attend the next session? Follow our updates on LinkedIn, [subcribe to our YouTube page and turn on notifications!](https://www.youtube.com/@AsyncAPI)
+Want to attend the next session? Follow our updates on [LinkedIn](https://www.linkedin.com/company/asyncapi/) and [subscribe to our YouTube channel](https://www.youtube.com/@AsyncAPI) to turn on notifications!
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between bd56fb0 and becdc88.

📒 Files selected for processing (1)
  • webinar_series_initiative.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
webinar_series_initiative.md

[style] ~9-~9: Consider a different adjective to strengthen your wording.
Context: ... questions, share experiences, and gain deeper insights into the AsyncAPI ecosystem. ...

(DEEP_PROFOUND)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ition, and a platform to share ideas. - For the Community: A growing knowledge base...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🔇 Additional comments (1)
webinar_series_initiative.md (1)

5-6: Intro paragraph well-aligned with community vision.
The opening succinctly captures the AsyncAPI community’s collaborative spirit and clearly introduces the webinar series.

Comment on lines +40 to +47
### For Hosts

- Get familiarized with the hosting platform (Restream)
- Prepare an engaging introduction and closing.
- Research and prepare relevant questions tailored to the speaker's topic.
- Keep the session on time and moderate the Q&A effectively.
- Coordinate with the speaker in advance to understand their presentation flow.

Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add aspect ratio and demo presentation guidelines.
Hosts would benefit from explicit technical guidance (e.g., recommended video aspect ratio like 16:9, minimum resolution, lighting/screen-capture tips) to ensure demos display clearly for all participants. Consider adding a bullet under “For Hosts”:

 ### For Hosts
 - Get familiarized with the hosting platform (Restream)
+- Ensure video is in 16:9 aspect ratio (1080p recommended) and demos are clearly visible (proper lighting and screen capture tools).
 - Prepare an engaging introduction and closing.
 ...
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### For Hosts
- Get familiarized with the hosting platform (Restream)
- Prepare an engaging introduction and closing.
- Research and prepare relevant questions tailored to the speaker's topic.
- Keep the session on time and moderate the Q&A effectively.
- Coordinate with the speaker in advance to understand their presentation flow.
### For Hosts
- Get familiarized with the hosting platform (Restream)
- Ensure video is in 16:9 aspect ratio (1080p recommended) and demos are clearly visible (proper lighting and screen capture tools).
- Prepare an engaging introduction and closing.
- Research and prepare relevant questions tailored to the speaker's topic.
- Keep the session on time and moderate the Q&A effectively.
- Coordinate with the speaker in advance to understand their presentation flow.
🤖 Prompt for AI Agents
In webinar_series_initiative.md around lines 40 to 47, add a bullet point under
the "For Hosts" section that provides technical guidance for demo presentations.
Include recommended video aspect ratio (such as 16:9), minimum resolution, and
tips on lighting and screen capture to ensure demos are clear and professional
for all participants.

Copy link
Contributor

@CBID2 CBID2 left a comment

Choose a reason for hiding this comment

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

Looks pretty good so far. Coderabbit suggested a tip I think is worth putting in there.


### For Hosts

- Get familiarized with the hosting platform (Restream)
Copy link
Contributor

Choose a reason for hiding this comment

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

[suggestion]: I think CodeRabbit made a good point with the ratio suggestion @derberg. It’ll ensure that hosts create effect videos. What do you think?

Suggested change
- Get familiarized with the hosting platform (Restream)
- Get familiarized with the hosting platform (Restream)
- Ensure video is in 16:9 aspect ratio (1080p recommended) and demos are clearly visible (proper lighting and screen capture tools).

@thulieblack
Copy link
Member

@iambami please update the pr with the pending reviews

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants