cranberryofdoom / the-cube Goto Github PK

The member model should have some sensible attributes: name, email, etc.
It should have_and_belong_to_many updates.
It should have_and_belong_to_many companies.

This way we can tag updates with the members they are related to. A members profile page can show all the updates related to them.

We do not need a members_controller. We can use ActiveAdmin for adding/editing/deleting. You just need to run:

rails generate active_admin:resource member

This looks like a good starting point: https://support.google.com/calendar/answer/41207?hl=en

We need to make the colors/theme match the rest of our site.

The navigation bar on the left is always visible. The links should go to their respective pages.

Ashley: You can now render the actual post objects on the home page! The erb works like this:

<% Post.all.each do |p| %>
    <%= render p %>
<% end %>

If you need to change or look at the html it's in app/views/posts/_post.html.erb.

@cranberryofdoom

The company model should have some basic attributes: name, what stage it is in, etc.
A company should have_and_belong_to_many members.
A company should have_and_belong_to_many updates.

This is so we can tag updates with the companies they are related to. Then when you visit a company profile page you get some news updates for that company.

We do not need a companies_controller. We can use ActiveAdmin for adding/editing/deleting. You just need to run:

rails generate active_admin:resource company

What should we add?

For a member I'm thinking maybe:

• link to blog
• link to github
• link to personal site / portfolio
• description

For company:

• link to website
• logo url (we can just use dropbox or S3 for these and do it manually)
• status (I'm not sure the best way to do this. Could choose one from "pre-prototype", "prototype", "growing/expanding", or something like that. Or it could just be a string and we let each company decide how to describe their own status.)
• funding
• revenue

Obviously those fields will be blank for some of us. Anything else we should add? What are your thoughts?

@cranberryofdoom @fabioberger

Use your sass/css skills to make it look purdy and match the rest of the site. As of now all the views are basically just plain html.