Development page content should be moved to Community

[brewsterdrinkwater]

The content in the development section should really be apart of the community section, so new and existing users can learn about sigs, wgs, Akash Insiders and other community based programming.

The Development section should focus on technical contributions including ways for technical users to contribute to areas like:

• Support repo
• Awesome Akash
• technical bounties
• technical documentation
• Cloudmos open source tools
• technical product and engineering roadmap
• discussions for further technical conversations

[aktdenis]

I'm having a look at this issue.

Quick question:
Which items from Development page should be in the Community page? I know community is involved, but it seems all items are development related.

I did some quick research and for example, Ethereum, Solana, Polkadot etc. all have separated sections for "Community" (dedicated for events, community news, content,... ) and "Development" (for all engineering things - even if the community is involved). It kinda looks like an established ux pattern in web3 world.

I'll explore how to bring some of the items you've stated above to Development page and we might have to redesign some of the existing items there.

[aktdenis]

Considering the points mentioned above, we could add them to the "Development" page.
Here's my suggested structure with these items included.

Before viewing design drafts please consider the proposal to restructure the menu here.

"Development" dropdown menu:

Secondary horizontal nav on the "Development" page

Design draft with items mentioned by @brewsterdrinkwater (*copy updates are not part of this draft)

Couple of explanation points for the draft above:

• Community calendar is a sticky floater - which stays in the bottom right corner. When clicked, it opens a pop-up with a view of a calendar. With this approach we actively invite visitors to join meetings while they browse through "Development" pages. The look and feel of the calendar should resonate with this example from tailwind.
• Important to note the section for "Product Strategy" is not included in any sections above. First we have to re-think the existing page and define what information is relevant, needs to be removed or changed. But we do have a CTA or a button for Product roadmap (on github) communicated in the main and secondary nav.

the whole page has a different experience, so we have to think what happens to other sub-pages. Below an example of community groups:

This issue is not finalized, further discussion and feedback is welcomed and appreciated.

[ShinySyntax]

Hello, @aktdenis
Is this issue resolved?
I can do it.

[aktdenis]

hello @kindlyman343423 , not yet.
we still need to discuss further development and direction.

if you're interested in joining working group for akash website please join our next meeting on Thu, Aug 22nd.

here is the calendar of all meetings;
https://akash.network/development/welcome/

[aktdenis]

@brewsterdrinkwater any thoughts on the drafts above?

[ShinySyntax]

Got it. @aktdenis
Thanks for your contact.

[aktdenis]

adding a mockup for "community calendar" sticky button.

[brewsterdrinkwater]

I love this.

I just want to add the calendar button to as many pages as possible. It will also be great to add bounties page.