Skip to content

Commit 113c604

Browse files
committed
Merge branch 'master' of github.com:kajal-jotwani/conference-website into feat/conference-gallery
2 parents c8f639d + e7fa1bf commit 113c604

80 files changed

Lines changed: 3315 additions & 1902 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.github/workflows/scripts/mailchimp/package-lock.json

Lines changed: 6 additions & 6 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

CODEOWNERS

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@
55
# For more details, read the following article on GitHub: https://help.github.com/articles/about-codeowners/.
66

77
# The default owners are automatically added as reviewers when you open a pull request unless different owners are specified in the file.
8-
* @AceTheCreator @thulieblack @Mayaleeeee @ashmit-coder
8+
* @AceTheCreator @thulieblack @Mayaleeeee @TenzDelek
99

10-
README.md @AceTheCreator @thulieblack @Mayaleeeee @ashmit-coder
11-
12-
#codeTriagers: vishvamsinh28
10+
README.md @AceTheCreator @thulieblack @Mayaleeeee @TenzDelek

CODE_OF_CONDUCT.md

Lines changed: 20 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
21
# Contributor Covenant 3.0 Code of Conduct
32

43
## Our Pledge
@@ -21,7 +20,6 @@ With these considerations in mind, we agree to behave mindfully toward each othe
2120
6. Committing to **repairing harm** when it occurs.
2221
7. Behaving in other ways that promote and sustain the **well-being of our community**.
2322

24-
2523
## Restricted Behaviors
2624

2725
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
@@ -41,55 +39,51 @@ We agree to restrict the following behaviors in our community. Instances, threat
4139
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
4240
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
4341

44-
4542
## Reporting an Issue
4643

4744
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.
4845

49-
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:
46+
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:
5047

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

5552
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.
5653

57-
5854
## Addressing and Repairing Harm
5955

60-
****
56+
---
6157

6258
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.
6359

64-
1) Warning
65-
1) Event: A violation involving a single incident or series of incidents.
66-
2) Consequence: A private, written warning from the Community Moderators.
67-
3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
68-
2) Temporarily Limited Activities
69-
1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
70-
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.
71-
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.
72-
3) Temporary Suspension
73-
1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
74-
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.
75-
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.
76-
4) Permanent Ban
77-
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.
78-
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.
79-
3) Repair: There is no possible repair in cases of this severity.
60+
1. Warning
61+
1. Event: A violation involving a single incident or series of incidents.
62+
2. Consequence: A private, written warning from the Community Moderators.
63+
3. Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
64+
2. Temporarily Limited Activities
65+
1. Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
66+
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.
67+
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.
68+
3. Temporary Suspension
69+
1. Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
70+
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.
71+
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.
72+
4. Permanent Ban
73+
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.
74+
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.
75+
3. Repair: There is no possible repair in cases of this severity.
8076

8177
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.
8278

83-
8479
## Scope
8580

8681
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.
8782

88-
8983
## Attribution
9084

9185
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/).
9286

9387
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/)
9488

95-
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).
89+
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).

CONTRIBUTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The following is a summary of the ideal contribution flow. Please, note that Pul
4040
```
4141

4242
## Code of Conduct
43-
AsyncAPI has adopted a Code of Conduct that we expect project participants to adhere to. Please [read the full text](./CODE_OF_CONDUCT.md) so that you can understand what sort of behaviour is expected.
43+
AsyncAPI has adopted a [Code of Conduct](./CODE_OF_CONDUCT.md) that we expect project participants to adhere to. Please read it carefully to understand what sort of behaviour is expected.
4444

4545
## Our Development Process
4646
We use Github to host code, to track issues and feature requests, as well as accept pull requests.
@@ -79,4 +79,4 @@ Happy contributing :heart:
7979
When you submit changes, your submissions are understood to be under the same [Apache 2.0 License](https://github.com/asyncapi/asyncapi/blob/master/LICENSE) that covers the project. Feel free to [contact the maintainers](https://www.asyncapi.com/slack-invite) if that's a concern.
8080

8181
## References
82-
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md).
82+
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md).

components/About/about.tsx

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ import Heading from '../Typography/heading';
44
import Paragraph from '../Typography/paragraph';
55
import Button from '../Buttons/button';
66
import Image from 'next/image';
7+
import Download from '../illustration/download';
78

89
function About(): JSX.Element {
910
return (
@@ -51,27 +52,25 @@ function About(): JSX.Element {
5152
target="_blank"
5253
rel="noreferrer"
5354
>
54-
<Button type="button" className="w-[200px]">
55-
Become a sponsor now
56-
</Button>
55+
<Button
56+
type="button"
57+
className="w-[200px]"
58+
text="Become a sponsor now"
59+
/>
5760
</a>
5861
<a
5962
className="flex justify-center "
6063
href="/pdf/conf-2025.pdf"
6164
download={`conf ${new Date().getFullYear()}.pdf`}
6265
>
63-
<Button type="button" overlay={true} className="w-[240px] border">
64-
<div className="flex gap-2 justify-center items-center">
65-
<Image
66-
src="/img/Download_icon.png"
67-
height={20}
68-
width={20}
69-
alt="Download-icon"
70-
objectFit="contain"
71-
/>
72-
<div>Sponsorship prospectus</div>
73-
</div>
74-
</Button>
66+
<Button
67+
type="button"
68+
outline={true}
69+
className="w-[240px] border"
70+
text="Sponsorship prospectus"
71+
icon={<Download />}
72+
iconPosition="left"
73+
/>
7574
</a>
7675
</div>
7776
</div>

components/Accordion/Accordion.tsx

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
import React, { useState } from 'react';
2+
import Button from '../Buttons/button';
3+
import Plus from '../illustration/plus';
4+
import { FaqTypes } from '../../types/types';
5+
6+
interface AccordionProps {
7+
faq: FaqTypes[];
8+
}
9+
10+
function Accordion({ faq }: AccordionProps) {
11+
const [show, setShow] = useState<number | null>(null);
12+
return (
13+
<>
14+
{faq?.length > 0 &&
15+
faq.map((q, i) => {
16+
return (
17+
<div
18+
key={q.q}
19+
onClick={() => {
20+
if (show === i) {
21+
setShow(null);
22+
} else {
23+
setShow(i);
24+
}
25+
}}
26+
>
27+
<div className="pb-4 cursor-pointer mt-4 border border-[#333] p-4 rounded-xl">
28+
<div
29+
className={`flex justify-between ${show === i ? 'text-white' : 'text-gray-400'} hover:text-white`}
30+
>
31+
<h2 className={`text-xl w-[90%]`}>{q.q}</h2>
32+
<Button
33+
type="button"
34+
outline={true}
35+
className="pointer h-[30px] border-[#ffff] mr-[20px] rounded-3xl p-1"
36+
icon={
37+
<Plus
38+
className={`w-[20px] transition-transform duration-700 ${show === i ? 'rotate-45' : 'rotate-90'}`}
39+
/>
40+
}
41+
iconPosition="left"
42+
/>
43+
</div>
44+
{
45+
<p
46+
className={`text-md text-white overflow-hidden transition-all duration-500 ease-in-out transform ${show === i ? 'mt-2 max-h-[1000px] opacity-100 translate-y-0' : 'max-h-0 opacity-0 -translate-y-2'}`}
47+
>
48+
{q.a}
49+
</p>
50+
}
51+
</div>
52+
</div>
53+
);
54+
})}
55+
</>
56+
);
57+
}
58+
59+
export default Accordion;

0 commit comments

Comments
 (0)