feat: adding GSoD and GSoC pages

[quetzalliwrites]

Contribution Description

The purpose of this PR is to create 2 NEW pages on our website for /GSoD (Google Season of Docs) and /GSoC(Google Summer of Code). In addition to adding those 2 pages to our website, I'm also proposing adding nav links to these pages under the Community nav group.

I truly love the idea of having them under Community because they are (potentially) a huge group event to do with the whole community. It just seemed to fit under that section best. But I know (as you can see too) that the sub-nav <li>s look like a long list now, so I will understand if you folks are wondering about that. Perhaps the styling should change to make the dropdown be a wider rectangle horizontally vs the current vertical grid?

Page sources

• The /GSoC(Google Summer of Code) page gets its details from here.
• The /GSoD (Google Season of Docs) page gets its details from here.

[netlify[bot]]

❌ Deploy Preview for asyncapi-website failed.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	96108ee881a335af4983bb839795e234a90b7e36
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/62a99f5684a9d600083fb14a

[quetzalliwrites]

Questions

Hey @derberg and @magicmatatjahu, I have a few development questions since this is the first time I add new pages to the website outside of the Docs markdown arena. 😄

Problem 1

Regardless of what I tried, HTML <table> and <ul> elements don't display as expected.

• The 🟩 box shows <ul> elements
• The 🟦 box shows a <table> element

In fact, there is only 1 section that displays the · (list item bullet point) as expected in the <ul> element:

When I compare the code samples, the only diff seemed to be that one of the <ul> elements had it's own <div>. So I tried to shuffle the other <ul> elements and give them their own <div>s to see if that fixed it. It didn't, 😂 so I put them back as they were:

Problem 2

When I open my 8080 localhost link to preview these pages, the website's main navigation seems to disappear!

What did I do? Where did it go? 🙊😂😂

[magicmatatjahu]

@alequetzalli As I see, this is copy/paste of the discussion's content about GSOC and GSOD. If we wanna these sites we should render them as mdx not as html. I can help but I need "approval" from @fmvilas and @derberg that these pages are needed :)

[derberg]

I'm definitely up for this change. Many orgs do it for transparency reasons on their involvement in different mentorship programs. It will also make it super easy for us to share our participation and share resources in future, because some rules do not change.

My suggestion though is to not have it as asyncapi.com/community/gsoc but asyncapi.com/community/mentorship/gsoc so we basically get:

• a "docs" like landing page under asyncapi.com/community/mentorship with navigation on the left, with links to Google Summer of Code and others and some short summary about these, like even hall of fame of those that completed. Like also have CodeForce participation update, then we will have Outreachy in few months, etc. But most important, we will get also a place to describe AsyncAPI Mentorship
• contend developed with markdown/mdx

[quetzalliwrites]

I'm definitely up for this change. Many orgs do it for transparency reasons on their involvement in different mentorship programs. It will also make it super easy for us to share our participation and share resources in future, because some rules do not change.

My suggestion though is to not have it as asyncapi.com/community/gsoc but asyncapi.com/community/mentorship/gsoc so we basically get:

@derberg Sure, I can move these pages into a sub-folder called community so that we end up with:

• asyncapi.com/community/mentorship/gsoc
• asyncapi.com/community/mentorship/gsod

• a "docs" like landing page under asyncapi.com/community/mentorship with navigation on the left, with links to Google Summer of Code and others and some short summary about these, like even hall of fame of those that completed. Like also have CodeForce participation update, then we will have Outreachy in few months, etc. But most important, we will get also a place to describe AsyncAPI Mentorship
• contend developed with markdown/mdx

Errrr. what now? @derberg sorry, got confused here a bit... can you show me a drawing of what you mean by "with navigation on the left, with links to Google Summer of Code and others and some short summary about these, like even hall of fame of those that completed".

(Also for the purposes of this PR, the scope is only adding these 2 pages.)

BTW, @magicmatatjahu can you confirm you know how to fix the CSS/styling issues I documented here? Lukasz was the one who told me I should tag you in this issue.

[magicmatatjahu]

@alequetzalli

can you confirm you know how to fix the CSS/styling issues I documented here? Lukasz was the one who told me I should tag you in this issue.

When we will move to the mdx probably all issues will be resolved :) If you want I can push some changes to your branch. Let me know :)

[derberg]

@alequetzalli sorry for not explaining well. I mean look at Getting Started navigation.

So by going to asyncapi.com/community/mentorship we would see in navigation like ☝🏼 elements like Google Summer of Code or Open Force or Google Season of Docs or Hacktoberfest or Outreachy or most important AsyncAPI Mentorship. So asyncapi.com/community/mentorship would be a single place where we have all different programs described and how we deal with them.

But yes, scope of this PR is GSoC and GSoD as a starter

[quetzalliwrites]

When we will move to the mdx probably all issues will be resolved :) If you want I can push some changes to your branch. Let me know :)

Yes, @magicmatatjahu you can totally push changes to my branch. You have alllll the permissions! ✨✨✨✨✨✨✨ 🙏🏽

[quetzalliwrites]

So by going to asyncapi.com/community/mentorship we would see in navigation like ☝🏼 elements like Google Summer of Code or Open Force or Google Season of Docs or Hacktoberfest or Outreachy or most important AsyncAPI Mentorship. So asyncapi.com/community/mentorship would be a single place where we have all different programs described and how we deal with them.

Huh🤔.. ok I think I get it now 😄 @derberg

[derberg]

removed gsoc and gsod labels as we add them to ideas issues for mentees

[github-actions[bot]]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	52
🟠 Accessibility	74
🟠 Best practices	83
🟢 SEO	90
🔴 PWA	30

Lighthouse ran on https://deploy-preview-642--asyncapi-website.netlify.app/

[magicmatatjahu]

@alequetzalli @derberg I added content as markdown. After merging PR with new navigation for docs I will improve navigation also for new pages in this PR, but for now we have to wait. Adding new pages for the /community/mentorship subpage is similar to adding new docs. You can check it out here: https://deploy-preview-642--asyncapi-website.netlify.app/community/mentorship

[derberg]

@magicmatatjahu just headings and titles are duplicated, but yeah, not code issue but fact that it is duplicated in metadata.

Looks nice ❤️

[magicmatatjahu]

@derberg Yeah, I duplicated the data just to show that new pages are being rendered :)

[derberg]

@magicmatatjahu where are we with this one?

[magicmatatjahu]

@derberg

https://github.com/asyncapi/website/pull/642#issuecomment-1105080050

After merging this PR https://github.com/asyncapi/website/pull/601 I will update navigation and you can review it :)

[magicmatatjahu]

We need to wait for https://github.com/asyncapi/website/pull/830

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[derberg]

Closing because work is done in https://github.com/asyncapi/community/pull/571

Of course we can reopen if needed