You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was walking this evening and got to thinking a bit about the message we’re trying to portray with this site, and how it should inform how we layout content and features. There were a few important things that I felt we want to stress:
We organize on Meetup, and we’d like people to join.
We have events regularly, and you should RSVP to them if you plan on coming.
We have a community that’s active outside of our events.
We’re a community that listens to what people have to say and are open to suggestions.
We’re a community that writes code, at all skill levels.
I feel like these fit pretty well into three categories:
Community
Stream of tweets from @nodedc.
IRC chat history and ability to drop into a conversation/ask a question to IRC from the site.
“Join the community on Meetup”-style button, maybe a summary of the group, a link to Events?
Code
We can help you learn to code.
We manage a number of projects on GitHub.
We have projects that members of our community maintain. This was a feature of the old GitHub pages site, and I’d like to see it come back:
Events
An agenda-view list of upcoming events, including our meetups and important events in the surrounding community (I think it’d be nice to link to things that some/many of us may be attending, like NationJS). I’m imagining an intermingled list, with a quick summary and a call-to-action button that’s descriptive of the event type: “RSVP on Meetup”, “Buy Ticket”, etc.
“Don’t see the kind of event you’d like to attend?”-style way to submit ideas of both ideas for specific subjects of talks as well as types of events. The form should guilt the submitter a bit — say, include a checkbox that says “I’d be willing to speak about/lead this idea.”
Our homepage would be pretty simple — I love the animation that we have there now. I say we keep that, and add some really simple high-level hero-style message. Something like a short version of our twitter profile: “Friendly humans and robots that talk about Node.js and other things.”
I have a few ideas that might be better sketched, so I’m going to put some ink to paper and attach those shortly.
What do you think? Yes, you reading this. Drop a comment!
The text was updated successfully, but these errors were encountered:
Cool stuff. Just some nit-picky stuff that should be discussed more:
The "more materials" section should really be columns describing community, code, and events I think. Events should be more prominently displayed in order to get more bodies in the events.
I don't really like embedded IRCs myself, and I'd rather have a community blog (advertising events, projects, etc.) in the prominent section of that instead.
I guess this way, the events page doesn't seem like it does much, but I think if it gets updated before every event to be specific to the event and provide details of activities, location/venue, directions, etc. it would be full functioning separate from the community page.
I don't know if my ideas are any good, hopefully we can take any good ideas out and dump the bad ones.
I was walking this evening and got to thinking a bit about the message we’re trying to portray with this site, and how it should inform how we layout content and features. There were a few important things that I felt we want to stress:
I feel like these fit pretty well into three categories:
Community
@nodedc
.Code
Events
Our homepage would be pretty simple — I love the animation that we have there now. I say we keep that, and add some really simple high-level hero-style message. Something like a short version of our twitter profile: “Friendly humans and robots that talk about Node.js and other things.”
I have a few ideas that might be better sketched, so I’m going to put some ink to paper and attach those shortly.
What do you think? Yes, you reading this. Drop a comment!
The text was updated successfully, but these errors were encountered: