Redesign site to include chapters, event listings, organizer tips

[mikeal]

I'd like to see a program, similar to NodeSchool, that helps people run small workshops in their local communities.

There's a ton of resources we can copy/fork.

• Organizer Checklist
• How to start a NodeSchool Chapter

We should also copy the org structure. This was an incredible innovation.

• Every local "chapter" gets a repo in the org.
• This automatically gives them a site at "chaptername.nodeschool.io" via ghpages.
• They add all the participants of the meetup to their repo which gives them a support channel / mailing list / forum.

Action Items

• Figure out where to put these (discourse wiki page, html page on the website made via markdown).
• Draft all the early practices.
• Create the org - now at https://github.com/protoschool
• move this repo to the new org, making sure we follow the naming convention that makes it the homepage of the github.io site
• Create some seed chapters that get their own pages in the new org (check meetup list for good candidates)
• Include list of all existing chapters
• Include help repo
• Include organizers repo

[terichadbourne]

@mikeal Is it the code for all of ProtoSchool that needs to be moved to a new org (an alternative to ipfs-shipyard) for this to work? Does the org itself need to be named protoschool?

[terichadbourne]

@mikeal Would you like conversations about the redesign of the proto.school site to accommodate event lists, instructions for organizing local workshops, etc. to go here, or should I create a new issue to share updates and request feedback on that?

[mikeal]

Let's talk about it here just because this is already linked to in a few places, but feel free to edit the title and body if appropriate.

[terichadbourne]

I've started a rough outline of the redesigned site in Mural per @olizilla's suggestion so we can collaborate on brainstorming, and we can later switch to a more official wireframing tool. https://app.mural.co/t/protocollabs6957/m/protocollabs6957/1540842761075/ecf9cfbea79053429cfb5e2c8c26be9bd0bea8c7

I'd love feedback from @mikeal and @olizilla on whether the main page contains the right elements and whether the subpages mentioned there look appropriate before I create outlines of those subpages.

[olizilla]

Looks reasonable to me! I think we can follow https://nodeschool.io/ pretty closely.

[mikeal]

I would remove "Upcoming Events" for now. It's a whole project on its own to keep an accurate and up to date list of events. I'm also skeptical that it's all that useful given that people can only really attend events they are near. I'd rather focus on improving the local chapter listing in the first release.

[terichadbourne]

@mikeal Is there such a thing as a chapter right now, so that there will already be something to list here, or will people start creating them once this redesign is live? If they exist, where can I find a current list and/or links?

[mikeal]

People will start creating them once we are live. One of the things we will have in the launch is a guide for creating chapters :)

We can launch with some already there though, I can commit to a starting a San Francisco chapter :)

[terichadbourne]

Okay, I've updated the mural to reflect the event listings as belonging to a future version.

@mikeal Any reaction to what we'd like in a footer across the whole website? Right now the ProtoSchool website is totally self-contained and there's no way to link out to related resources, the IPFS or PL sites, etc.

Some options for footer content include:

• Smaller version of ProtoSchool logo
• IPFS logo
• Link to PL site
• Link to project site(s): IPFS, IPLD, etc.
• Link to documentation
• Link to the upcoming blog (in a future iteration)
• Contact/social info (Twitter, GH, etc.)
• Contributing section (link to open an issue?)
• Code of conduct (though a case could be made for surfacing this higher if we plan to have one)

[terichadbourne]

@mikeal What would be the most helpful way to collaborate on the text content of the community portions of the site? We can separate that process out from the development using Google Docs or something along those lines, or I can build a branch with a rough version of the site that will look a little sketchy as I'm figuring out the Vue and CSS but would have the text in GH to be adjusted there. My gut is that the GoogleDocs approach might be most effective for right now to keep things moving. What's convenient for you?

[mikeal]

Let's start with a Google Doc and go from there.

At some point we'll need to stick the final products in some markdown files for the site but Google Docs are easier to iterate and comment on.

[terichadbourne]

Sounds good. I'll share a link once I have a draft started.

…

On Fri, Nov 2, 2018 at 2:37 PM Mikeal Rogers ***@***.***> wrote: Let's start with a Google Doc and go from there. At some point we'll need to stick the final products in some markdown files for the site but Google Docs are easier to iterate and comment on. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#51 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASSIiaRR7bhT5-SmsZG0naEoGhwbQCCUks5urJDlgaJpZM4Wbsss> .

-- *Teri Chadbourne, CMP* Community Manager Protocol Labs <https://protocol.ai/> Twitter <https://twitter.com/eventteri> | GitHub <https://github.com/terichadbourne>

[terichadbourne]

Regarding having some chapters seeded when we launch, it might be worth taking a look at the meetup groups that PL appears to be managing or co-managing and seeing who's taking the lead on each and whether they want to add themselves to the list. I got access to our Meetup login and see the following groups listed:

[terichadbourne]

I've started a Google Doc for iterating on potential text content for the redesigned site: https://docs.google.com/document/d/1HbLoOujxSW0QybmVNFd8ikVqIf1nwcvr3schQk3gkSs/edit?usp=sharing

[terichadbourne]

New org has been created at https://github.com/ProtoSchool but migration of site content will happen later.

[terichadbourne]

I've added a few items to the "Action Items" list above to ensure everything mentioned in the now-defunct 1.0 release tracking issue is captured elsewhere, since we've decided to use GitHub Milestones instead. I may break this issue out into more specific ones as well moving forward.

[terichadbourne]

Repos needed in the new org:

• "protoschool.github.io" main repo that hosts protoschool website
• "organizing" - provides advice and steps for those who already run chapters or want to
• various chapter ones created by community