Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
30cfe68
Update if-nodejs-pr-testing.yml
Shriya-Chauhan Jul 23, 2025
abea2c0
Revert "Update if-nodejs-pr-testing.yml"
Shriya-Chauhan Jul 23, 2025
9782522
chore: update meetings.json and newsrooom_videos.json (#4487)
asyncapi-bot Oct 17, 2025
eeac2ea
ci: update of files from global .github repo (#4475)
asyncapi-bot Oct 17, 2025
68a6c3d
feat: updated case studies page
Shriya-Chauhan Oct 22, 2025
d917850
fix: blog desktop design
Shriya-Chauhan Oct 25, 2025
e2baf06
fix: fixing mobile view
Shriya-Chauhan Oct 25, 2025
0896ab1
fix: changing heading sizes
Shriya-Chauhan Oct 25, 2025
c0f4f3b
fix: update ambassadors page
Shriya-Chauhan Nov 3, 2025
979097a
feat:adding graphic on ambassadors page
Shriya-Chauhan Nov 4, 2025
18e6a76
fix: tsc page draft
Shriya-Chauhan Nov 4, 2025
63bac4c
fix: roadmaps page redesign
Shriya-Chauhan Nov 4, 2025
4d8820e
fix: adding events and updates page
Shriya-Chauhan Nov 6, 2025
c01c51c
fix: lint errors
Shriya-Chauhan Nov 6, 2025
6ec9574
fix:add dark mode to individual blog post
Shriya-Chauhan Nov 7, 2025
a88ec06
fix: lint issues and warnings
Shriya-Chauhan Nov 7, 2025
574c152
fix:enhanced tools dashboard page
Shriya-Chauhan Nov 9, 2025
d0beb7f
fix:enhanced blog page card animation
Shriya-Chauhan Nov 9, 2025
146cd6c
fix: community page
Shriya-Chauhan Nov 10, 2025
2f5d5b7
fix:lint errors-s
Shriya-Chauhan Nov 13, 2025
d323f1e
fix: added dark mode background colour to body
Shriya-Chauhan Nov 14, 2025
e0e5647
fix: dark mode smooth transition
Shriya-Chauhan Nov 14, 2025
be534d4
fix: fixed dashboard
Shriya-Chauhan Nov 16, 2025
13976ca
fix: lint errors
Shriya-Chauhan Nov 16, 2025
4b25bcc
fix: creating a single pagination component
Shriya-Chauhan Nov 16, 2025
c7f24b1
fix: dark mode mode for board members page
Shriya-Chauhan Nov 17, 2025
ff26241
fix: fixing community icons
Shriya-Chauhan Nov 17, 2025
ab59699
fix: dark mode to tools pages
Shriya-Chauhan Nov 17, 2025
caf15b4
fix: dark mode to roadmaps arrows
Shriya-Chauhan Nov 17, 2025
e9876f0
fix: dark mode subscribe section
Shriya-Chauhan Nov 17, 2025
1a87de9
fix: added date data to blog cards
Shriya-Chauhan Nov 17, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
101 changes: 75 additions & 26 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,46 +1,95 @@
# Contributor Covenant Code of Conduct

# Contributor Covenant 3.0 Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
We pledge to make our community welcoming, safe, and equitable for all.

## Our Standards
We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.

Examples of behavior that contributes to creating a positive environment include:
## Encouraged Behaviors

- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.

Examples of unacceptable behavior by participants include:
With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:

- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
2. Engaging **kindly and honestly** with others.
3. Respecting **different viewpoints** and experiences.
4. **Taking responsibility** for our actions and contributions.
5. Gracefully giving and accepting **constructive feedback**.
6. Committing to **repairing harm** when it occurs.
7. Behaving in other ways that promote and sustain the **well-being of our community**.

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
## Restricted Behaviors

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.

## Scope
1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
7. Behaving in other ways that **threaten the well-being** of our community.

### Other Restrictions

1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.


## Reporting an Issue

Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.

When an incident does occur, it is important to report it promptly. To report a possible violation, here are a few simple ways to do it:

- Join our [AsyncAPI Slack](https://asyncapi.com/slack-invite) and share your report in the `#coc` channel.
- Reach out directly to any member of the [Code of Conduct Committee](https://github.com/orgs/asyncapi/teams/code_of_conduct).
- Or, if you’d prefer, just send us an email at **[email protected]**.
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion | 🟠 Major

Format email address as a proper markdown link.

The email address should be formatted as a link to comply with markdown best practices and improve user experience.

Apply this diff:

-- Or, if you'd prefer, just send us an email at **[email protected]**.
+- Or, if you'd prefer, just send us an email at [[email protected]](mailto:[email protected]).
📝 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
- Or, if youd prefer, just send us an email at **[email protected]**.
- Or, if you'd prefer, just send us an email at [[email protected]](mailto:[email protected]).
🧰 Tools
🪛 LanguageTool

[style] ~53-~53: In some texts, you can shorten this phrase. Consider using “email us”.
Context: ...f_conduct). - Or, if you’d prefer, just send us an email at [email protected]. Community...

(SEND_PRP_AN_EMAIL)

🪛 markdownlint-cli2 (0.18.1)

53-53: Bare URL used

(MD034, no-bare-urls)

🤖 Prompt for AI Agents
In CODE_OF_CONDUCT.md around line 53, the email address is plain text; change it
to a proper Markdown mailto link by replacing the text with
[[email protected]](mailto:[email protected]) so it renders as a clickable
email link in Markdown.


This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
## Addressing and Repairing Harm

****

If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.

1) Warning
1) Event: A violation involving a single incident or series of incidents.
2) Consequence: A private, written warning from the Community Moderators.
3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
2) Temporarily Limited Activities
1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
3) Temporary Suspension
1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
4) Permanent Ban
1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
3) Repair: There is no possible repair in cases of this severity.

This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.


## Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).

Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
Comment on lines -1 to +95
Copy link
Member

Choose a reason for hiding this comment

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

What is the reason behind making changes to the Code of Conduct?

2 changes: 1 addition & 1 deletion components/AlgoliaSearch.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -315,7 +315,7 @@ export function SearchButton({ children, indexName = INDEX_NAME, ...props }: ISe
} else {
setChildren(children);
}
}, []);
}, [actionKey, children]);

return (
<button
Expand Down
8 changes: 6 additions & 2 deletions components/Calendar.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -34,11 +34,15 @@ export default function Calendar({ className = '', size }: ICalendarProps) {
return (
<div
className={twMerge(
'overflow-hidden rounded-md border border-gray-200 bg-white p-4 h-full flex flex-col gap-2',
'overflow-hidden rounded-md border border-gray-200 bg-white dark:bg-dark-background dark:border-border p-4 h-full flex flex-col gap-2',
className
)}
>
<Heading level={HeadingLevel.h2} typeStyle={HeadingTypeStyle.mdSemibold}>
<Heading
level={HeadingLevel.h2}
typeStyle={HeadingTypeStyle.mdSemibold}
className='dark:text-dark-heading text-gray-900'
>
{t('calendar.title')}
</Heading>
<ul>
Expand Down
34 changes: 22 additions & 12 deletions components/CaseStudyCard.tsx
Original file line number Diff line number Diff line change
@@ -1,16 +1,18 @@
import Link from 'next/link';
import React from 'react';

import type { ICaseStudies } from '@/types/post';
import { ParagraphTypeStyle } from '@/types/typography/Paragraph';

import Button from './buttons/Button';
import Paragraph from './typography/Paragraph';

interface ICaseStudyCardProps {
studies?: ICaseStudies;
}

/**
* @description A component that displays a list of case studies in a card format
* @description Enhanced case study card component with modern design
Comment on lines -13 to +15
Copy link
Member

Choose a reason for hiding this comment

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

Please improve the description. It currently reads like AI-generated text.

The description shouldn’t use terms like “Enhanced component” because this code will be viewed as it is, not compared with older versions — so words like “enhanced” become redundant.

For documentation or comments in code, the description should explain something that is not already obvious from simply reading the code. Otherwise, keep it short and straightforward. You can refer to clean coding guidelines for better clarity on this.

* @param {ICaseStudies} props.studies - The list of case studies to display
*/
export default function CaseStudyCard({ studies = [] }: ICaseStudyCardProps) {
Expand All @@ -19,21 +21,29 @@ export default function CaseStudyCard({ studies = [] }: ICaseStudyCardProps) {
}

return (
<div className='flex flex-wrap justify-center gap-3 pt-10 lg:gap-8 lg:text-center'>
<div className='grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6 lg:gap-8'>
{studies.map((study, index) => (
<a key={index} className='lg:w-[30%]' href={`casestudies/${study.id}`}>
<div
className='h-full min-h-[300px] max-w-sm overflow-hidden rounded-md border border-gray-200 bg-white p-4'
data-testid='CaseStudyCard-main'
>
<span className='mr-2'>
<img className='m-auto h-16' src={study.company.logo} alt={study.company.name} />
</span>
<Paragraph typeStyle={ParagraphTypeStyle.md} className='my-4'>
<Link key={index} href={`/casestudies/${study.id}`} className='group block h-full'>
<div className='h-full bg-white dark:bg-dark-background border border-gray-200 dark:border-gray-700 rounded-2xl p-6 transition-all duration-300 hover:shadow-xl hover:-translate-y-1'>
{/* Company Logo */}
<div className='flex items-center justify-center h-20 mb-6'>
<img src={study.company.logo} alt={study.company.name} className='max-h-16 max-w-full object-contain' />
</div>

{/* Description */}
<Paragraph typeStyle={ParagraphTypeStyle.md} className='text-gray-600 dark:text-gray-400 mb-6 line-clamp-4'>
{study.company.description}
</Paragraph>

{/* CTA Button */}
Copy link
Member

Choose a reason for hiding this comment

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

As I mentioned in the above review comment, avoid adding comments that state obvious things. Your code should be self-explanatory, which can be achieved by following clean coding practices.

<div className='mt-auto'>
<Button
text='Read case study →'
className='w-full bg-primary-500 hover:bg-primary-600 text-white group-hover:bg-primary-600 transition-colors'
/>
</div>
</div>
</a>
</Link>
))}
</div>
);
Expand Down
4 changes: 2 additions & 2 deletions components/CaseTOC.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -163,8 +163,8 @@ export default function CaseTOC({ className, cssBreakingPoint = 'xl', toc }: Cas
open && 'mb-4'
} flex-1 text-primary-500 font-medium uppercase tracking-wide text-sm font-sans antialiased ${
cssBreakingPoint === 'xl'
? 'xl:mb-4 xl:text-xs xl:text-gray-900 xl:font-bold'
: 'lg:mb-4 lg:text-xs lg:text-gray-900 lg:font-bold'
? 'xl:mb-4 xl:text-xs xl:text-gray-900 dark:text-gray-300 xl:font-bold'
: 'lg:mb-4 lg:text-xs lg:text-gray-900 dark:text-gray-300 lg:font-bold'
}`
)}
>
Expand Down
Loading
Loading