Build a Responsive Website for our Community

[AlexandroPerez]

So I decided to use the name "fcc-community" for this project, so that any member of FCC, regardless of where they live can use the website to share and be part of events, project contribution and much more. We will have to make it so that members can find relevant events based on distance, but that's an issue to address later on. So now we need to come up with a Responsive Design for the site. So far I think the site will need the following pages:

Home | Meetups | Video Conferences | Project Contribution | Coding Camp Regime

• The Home page will show highlights of upcoming events from each category.
• The Coding Camp Regime should allow members to form groups and should have tools that will help them achieve their goals (like making a schedule, keep track of their progress, etc).
• All other pages should allow members to create, edit and delete events for each category, with all relevant information required.

[zenware]

I think that it's not really an issue to address later on but perhaps an integral component. I also don't think that having someone working on design prevents someone working on features.

Some of the features you mention here seem like things that maybe we can add to FreeCodeCamp directly on their github repo https://github.com/FreeCodeCamp/FreeCodeCamp (which is also open to beginner contributions)

[AlexandroPerez]

I guess that by addressing the issue later I meant that after discussing the stack we'll be using, and the way we'll handle the features (single app, individual APIs, etc,) we can open new issues and have members work on them.

As for adding features to the FCC repo, that's why I decided to name the project this way. Basically, once we get a working project, I think it should be easy to port it to www.frecodecamp.com/community, or something similar 👍

But for now since newbies (including myself) will be collaborating, I think is safe to think of this as a playground first... BTW, when time allows, we need to discuss branch naming (like a branch for testing, beta and stable releases?) and other things that I may be missing.