Skip to content
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

feat: new community section from community branch #917

Merged
merged 35 commits into from
Mar 30, 2023
Merged

Conversation

akshatnema
Copy link
Member

Description
This PR adds a new page to the website which describes all the community-related information and announcements in it. This PR is made draft to track the changes done in the community branch. Whoever wants to contribute to this issue/PR has to make a branch from community branch to his forked repo.

Related issue(s)
Resolves #903

@netlify
Copy link

netlify bot commented Aug 25, 2022

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 4c43126
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/64253cd23e19a70008b46046
😎 Deploy Preview https://deploy-preview-917--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@akshatnema
Copy link
Member Author

@AceTheCreator, the PR for community section is initiated again and you can now track the changes made in the branch, with respect to the master branch.

Regarding resolving the conflicts, I would tag @magicmatatjahu @derberg for this. Which method we should use, directly make a merge commit to the communtiy branch or we should initialize a PR for this to track what changes are made during the merge command in the branch?

@derberg
Copy link
Member

derberg commented Aug 29, 2022

any is good, really, it is merged into feature branch anyway, so if something is broken with solving conflicts, it can also be fixed as a followup.

I say, if easier for you is to do it directly to community branch, then do it. @magicmatatjahu ?

@AceTheCreator
Copy link
Member

@derberg what happened to the previous PR that got merged into the community branch?

@derberg
Copy link
Member

derberg commented Aug 29, 2022

what happened to the previous PR that got merged into the community branch?

@AceTheCreator it got merged as you noticed 😄 #902

akshatnema and others added 21 commits August 31, 2022 22:41
Signed-off-by: akshatnema <20bcs022@iiitdmj.ac.in>
Signed-off-by: akshatnema <20bcs022@iiitdmj.ac.in>
Signed-off-by: akshatnema <20bcs022@iiitdmj.ac.in>
Signed-off-by: akshatnema <20bcs022@iiitdmj.ac.in>
Co-authored-by: Khuda Dad Nomani <32505158+KhudaDad414@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Anisat Akinbani <52763841+Annysah@users.noreply.github.com>
Co-authored-by: Anurag Goswami <64116092+Anurag607@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: Alejandra Quetzalli <alejandra.olvera.novack@gmail.com>
Co-authored-by: Amisha Kumari <amishakumari544@gmail.com>
Co-authored-by: asyncapi-bot <bot+chan@asyncapi.io>
Co-authored-by: Christophe Dujarric <christophe@bump.sh>
Co-authored-by: Martin F <gabel@users.noreply.github.com>
Co-authored-by: Nelson <iamnelsonmichael@gmail.com>
Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com>
Signed-off-by: akshatnema <20bcs022@iiitdmj.ac.in>
Co-authored-by: Khuda Dad Nomani <32505158+KhudaDad414@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Anisat Akinbani <52763841+Annysah@users.noreply.github.com>
Co-authored-by: Anurag Goswami <64116092+Anurag607@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: Alejandra Quetzalli <alejandra.olvera.novack@gmail.com>
Co-authored-by: Amisha Kumari <amishakumari544@gmail.com>
Co-authored-by: asyncapi-bot <bot+chan@asyncapi.io>
Co-authored-by: Christophe Dujarric <christophe@bump.sh>
Co-authored-by: Martin F <gabel@users.noreply.github.com>
Co-authored-by: Nelson <iamnelsonmichael@gmail.com>
Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com>
Signed-off-by: akshatnema <20bcs022@iiitdmj.ac.in>
@akshatnema akshatnema marked this pull request as ready for review February 8, 2023 18:21
@derberg
Copy link
Member

derberg commented Mar 1, 2023

the thing is that when you go to /community, to a kinda Community Landing Page, you see it promotes:

  • discussions
  • ambassadors
  • meetings
  • slack
  • goals and upcoming work

but when you look at:
Screenshot 2023-03-01 at 13 42 24

there are some additional community items that are not promoted on landing page


so in short I think the idea behind /community view should be to highlight all the items that people can find there.

makes sense? not a must-have for me in this PR but if we have an agreement we should definitely have a dedicated followup issue on that

@AceTheCreator
Copy link
Member

the thing is that when you go to /community, to a kinda Community Landing Page, you see it promotes:

  • discussions
  • ambassadors
  • meetings
  • slack
  • goals and upcoming work

but when you look at: Screenshot 2023-03-01 at 13 42 24

there are some additional community items that are not promoted on landing page

so in short I think the idea behind /community view should be to highlight all the items that people can find there.

makes sense? not a must-have for me in this PR but if we have an agreement we should definitely have a dedicated followup issue on that

I understand now. But i thought keeping the landing page simple and straightforward was a really good approach.

I can create a separate issue and make someone contribute to it :)

What do you think @alequetzalli?

@quetzalliwrites
Copy link
Member

I understand now. But i thought keeping the landing page simple and straightforward was a really good approach.
I can create a separate issue and make someone contribute to it :)

What do you think @alequetzalli?

Uh oh... do I have to answer this one? 😄 Can't I just agree with everyone? 😂😂😂😂 LOL kidding...

Ok, so tbh here's my take:

  1. I agree with @derberg on his concern over the Community item's behavior in the nav bar; I too would expect to be allowed to click on it and have it take me directly to the landing page.
  2. I happen to feel that the current Community landing page feels too marketing-like. IOW... full of pretty colors and graphics, but not necessarily have the information I need as a community member. I also think that Lukasz makes a good point about that page currently missing the most context of what community members will look for there... my vote is to fix that page because it currently does not serve the community as well as it could. ♥️

Copy link
Member Author

@akshatnema akshatnema left a comment

Choose a reason for hiding this comment

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

Hey @AceTheCreator, here's my review...

I see that lot of images are being added via this PR and they are in various formats like PNG, JPEG or JPG. Kindly make these images compressed (if possible) and in the format of either SVG or WEBP. You can use https://squoosh.app/ to convert the images.

Also, I see 2 images of Fran being added, both are same, just different in terms of format of the images. Kindly have only 1 image of each person.

image

Comment on lines 1 to 23
import React from 'react';
import Head from '../Head';
import Container from './Container';
import NavBar from '../navigation/NavBar';
import StickyNavbar from '../navigation/StickyNavbar';


export default function CommunityLayout({
title,
description,
children,
wide = true,
}) {
return (
<>
<Head title={title} description={description} />
<StickyNavbar>
<NavBar className="max-w-screen-xl block px-4 sm:px-6 lg:px-8 mx-auto" />
</StickyNavbar>
<Container wide={wide}>{children}</Container>
</>
);
}
Copy link
Member Author

Choose a reason for hiding this comment

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

Suggested change
import React from 'react';
import Head from '../Head';
import Container from './Container';
import NavBar from '../navigation/NavBar';
import StickyNavbar from '../navigation/StickyNavbar';
export default function CommunityLayout({
title,
description,
children,
wide = true,
}) {
return (
<>
<Head title={title} description={description} />
<StickyNavbar>
<NavBar className="max-w-screen-xl block px-4 sm:px-6 lg:px-8 mx-auto" />
</StickyNavbar>
<Container wide={wide}>{children}</Container>
</>
);
}

This file has been created but not used anywhere in the repo and it already has the same changes as in GenericLayout. Kindly remove this file as it is not needed.

Comment on lines 10 to 84
const data = [
{
title: 'Written content',
details:
'Write guides, step-by-step tutorials, community documentation, AsyncAPI blog posts, and beyond.',
icon: '/img/illustrations/blog.svg',
},
{
title: 'Video content',
details:
'Produce educational videos on YouTube and other platforms for AsyncAPI.',
icon: '/img/illustrations/video-creation.svg',
},
{
title: 'Live streams',
details: 'Moderate or host live streams that demo the AsyncAPI ecosystem.',
icon: '/img/illustrations/live.svg',
},
{
title: 'Give talks',
details:
'Speak at meetups and conferences; we’ll help with slides, abstract submissions, and travel budget.',
icon: '/img/illustrations/speaking.svg',
},
{
title: 'Interactive Learning',
details:
'Gamify educational content and create interactive learning paths for teaching AsycnAPI and event-driven architectures.',
icon: '/img/illustrations/learning-app.svg',
},
{
title: 'Build real-life usecases example',
details:
'Develop real-life usecase project example using the AsyncaAPI specification',
icon: '/img/illustrations/codes.svg',
},
{
title: 'AsyncAPI Contributions',
details:
'Collaborate with the AsyncAPI community via diverse contributions and improvements.',
icon: '/img/illustrations/advisor.svg',
},
{
title: 'Gather Use-Cases',
details:
'Collect data from existing AsyncAPI users and create use-case studies.',
icon: '/img/illustrations/meeting.jpg',
},
];


const tokens = [
{
emoji: '🗺️',
title: 'Travel',
details: 'Ambassadors are provided free entry to AsyncAPI conferences.',
},
{
emoji: '🌟',
title: 'Recognition',
details: 'Ambassadors receive community-wide recognition.',
},
{
emoji: '🎁',
title: 'Special Swags',
details:
'Community members recognize you by gifting you exclusive AsyncAPI Ambassador swag.',
},
{
emoji: '🧰',
title: 'Workshop Swags',
details:
'Ambassadors are gifted swag from AsyncAPI conferences and workshops.',
},
];
Copy link
Member Author

Choose a reason for hiding this comment

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

Can we include this array of data inside another json file as we are getting huge chunks of lines inside this file and later on, it will be difficult for us to extend the page further?

/>
</div>
</div>
);
Copy link
Member Author

@akshatnema akshatnema Mar 4, 2023

Choose a reason for hiding this comment

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

I see that you are making a separate variable to render this block. Will you think of making this as a separate component?

Also, I see that most of the files inside pages/communtiy has huge lines of code. Can we think of making separate components for them as we are also looking for making UI tests on website?

* replaced image format

* removed unused component

* moved ambassadors content to a new file

* created components for community section

* changes implemented

* .

* added shadow to cards and bd color

* added suggested changes

* .
@AceTheCreator
Copy link
Member

Any other suggestions? cc @derberg @akshatnema @alequetzalli

@derberg
Copy link
Member

derberg commented Mar 16, 2023

@AceTheCreator can you fix merge conflicts first 🙏🏼

@AceTheCreator
Copy link
Member

@AceTheCreator can you fix merge conflicts first 🙏🏼

@akshatnema your help is needed :)

Signed-off-by: akshatnema <20bcs022@iiitdmj.ac.in>
Copy link
Member Author

@akshatnema akshatnema left a comment

Choose a reason for hiding this comment

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

It's not possible for me to review this PR as a whole from the codebase point of view as there are around 2k lines of changes. So, we will make sure we won't be dealing with any such PR in the future and will review each individual PR despite having the thoughts that we can improve it later.

Here's my another round of review:

image

The videos in the list are not sorted according to the ascending order of dates, like the meeting of 20th March should be displayed first and then further meetings should be displayed according to the dates.

{ icon: IconDashboard, title: 'Dashboard',href: '/community/dashboard', description: `Just need a good first issue to start your contribution journey? or want to see what topics are hot in discussion?`},
{ icon: IconMeetings, title: 'Meetings', href: '/community/meetings', description: 'See what meetings are organized under AsyncAPI umbrella and join one of them.' },
{ icon: IconMeetings, title: 'Meetings', href: '/community/events', description: 'See what meetings are organized under AsyncAPI umbrella and join one of them.' },
Copy link
Member Author

Choose a reason for hiding this comment

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

Should the titile for this option be changed to something else for this page now, as we are not only restricted to Meetings but rather we are more focused on the events too like AsyncAPI Conference?
WDYT @derberg @alequetzalli

Copy link
Member

Choose a reason for hiding this comment

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

It's best if we rename the title to "Events"

@AceTheCreator
Copy link
Member

AceTheCreator commented Mar 20, 2023

The videos in the list are not sorted according to the ascending order of dates, like the meeting of 20th March should be displayed first and then further meetings should be displayed according to the dates.

@akshatnema you're right akshat

@AceTheCreator
Copy link
Member

It's not possible for me to review this PR as a whole from the codebase point of view as there are around 2k lines of changes. So, we will make sure we won't be dealing with any such PR in the future and will review each individual PR despite having the thoughts that we can improve it later.

@akshatnema I disagree with this approach, as it only prolongs this PR. So I'll advise you to create the review once, and whatever thing you find out later on can be opened as a GFI. Your approach will only keep making me open more PR fixing small changes

@akshatnema
Copy link
Member Author

akshatnema commented Mar 26, 2023

@akshatnema I disagree with this approach, as it only prolongs this PR. So I'll advise you to create the review once, and whatever thing you find out later on can be opened as a GFI. Your approach will only keep making me open more PR fixing small changes

Sorry, but actually you misunderstood my concern slightly. I'm not asking to make new PRs to make small changes in this PR. But what I said that when you had initialized individual PRs for the pages of the community section previously, I must have made a complete review for that PR instead of waiting for them to merge in the community branch. Anyways, my reviews are done. Approved ✔️. Waiting for the approval from @derberg @alequetzalli

Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

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

@alequetzalli we need your final approval

@AceTheCreator
Copy link
Member

@alequetzalli, any other suggestion from your end? Before we go ahead merge this PR

@akshatnema
Copy link
Member Author

@AceTheCreator Will you like to merge the PR? Since, you are the major contributor of this PR and I want you to take this pleasure. Just do the / rtm command in this PR 😄

@AceTheCreator
Copy link
Member

/rtm

@asyncapi-bot asyncapi-bot merged commit 57d4312 into master Mar 30, 2023
@derberg derberg deleted the community branch April 13, 2023 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Epic roadmap to the new AsyncAPI community section
5 participants