Josh Smith

I think I actually prefer my last comment now.

My last comment would involve taking the `conversation-thread` and type switching in the `each` based on the context. We'd need to define an attribute on the `conversation-thread` that identifies it...

I agree with this. - `conversations/project/conversation-thread` - `conversations/user/conversation-thread` We could maybe refactor some things like: - `conversations/conversation-list-item-with-user` => `conversations/project/conversation-list-item` - `conversations/conversation-list-item-with-project` => `conversations/user/conversation-list-item` - `conversations/project-details` => `conversations/user/details-pane` - `conversations/user-details` =>...

I'm sure this logic can be refactored/simplified, especially since I'm tired now. It does seem like the hard parts are mostly figured out, though.

We'll handle the last one here once @daveconnis finishes his work on task assignment.

Referencing my own comment on the API side, we may want to hold off on this for awhile. The `temp-id` is likely to become `tid`, indicating the churn in JSON...

We should remove it. The demo components are going away.

Yeah if it's commented out, just blow away the file. The landing page will be entirely reworked soonish.

@snewcomer is there more progress that we need to make here? I'm not sure where to go from here.

Everything in one template definitely would make things a challenge. Is there also a way to prevent freestyle from being deployed (including the assets) alongside our application? i.e. I wouldn't...