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

Reorganize VC resources #880

Closed
2 tasks done
danieltott opened this issue May 10, 2023 · 5 comments · Fixed by #895
Closed
2 tasks done

Reorganize VC resources #880

danieltott opened this issue May 10, 2023 · 5 comments · Fixed by #895
Assignees
Labels
Type: Content Content additions or updates

Comments

@danieltott
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Type of Change

Edit/Clarification on existing content

URL of existing page

https://virtualcoffee.io/resources/virtual-coffee

Context for content change

We have a lot going on at VC --which is great-- and it’s kind of hard to discover what’s going on, especially for new members.

Proposed solution

  • Guide To Virtual Coffee should be top-level with children
  • Many sections in that can be pulled out into their own pages that would live under “Guide to VC”
  • Move Channel guide under “guide to VC”
    Order should be:
    • Join VC
    • Guide to VC
    • Get Involved
  • Move how to ask questions to dev resources

On that last point, there’s a section that is specific to VC that I think we can pull out and maybe add to the channel guide or something like that, the rest of the content is great for general resources

Resources that can help

No response

Collaborators

No response

Code of Conduct

  • I've read the Code of Conduct and understand my responsibilities as a member of the Virtual Coffee community
@danieltott danieltott added the Type: Content Content additions or updates label May 10, 2023
@adiati98
Copy link
Contributor

@danieltott I have a couple questions (for now 😝) to clarify things:

  1. Bullet point 1:

    Guide To Virtual Coffee should be top-level with children

    Which children are we talking about?

  2. When I already understand the point above:

    Many sections in that can be pulled out into their own pages that would live under “Guide to VC”

    Do you mean that we should make new independent pages for the sections and put them under "Guide to VC"?

Thanks in advance! 😀

@danieltott
Copy link
Member Author

The children will be the new pages that you create from content inside the guide, as well as the Channel Guide

Hopefully that makes sense!

@adiati98
Copy link
Contributor

The children will be the new pages that you create from content inside the guide, as well as the Channel Guide

Hopefully that makes sense!

Ummmm... I still don't get it 🙈
Sorry 😅

@danieltott
Copy link
Member Author

So the new structure could be something like this:

  • Join Virtual Coffee
  • Guide To Virtual Coffee
    • Virtual Coffee Slack Channel Guide
    • What To Expect In Virtual Coffee
    • Coffee Table Groups
    • Monthly Challenges
    • Lunch & Learns
    • Lightning Talks
    • HacktoberFest
    • Giving Back To The Community
    • Keeping Up With Virtual Coffee
  • Get Involved
    • Paths to Leadership & Roles
    • Leading a Coffee Table Group
    • Lunch and Learns

Most of the new pages under "Guide to Virtual Coffee" can be created by removing content from the original guide and adding it as a new page. For instance - a new page called "Coffee Table Groups" that would be created from the content here.

If I'm still not explaining this well we can meet up if you want!

@adiati98
Copy link
Contributor

adiati98 commented May 11, 2023

I think I get the idea now, @danieltott 😊

Let me try and do it first and make a draft of PR. If anything, I'll let you know, and let's meet up whenever you're free tomorrow 😄

Thank you!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Content Content additions or updates
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants