jesseposner / launchpad Goto Github PK

@Chebotarev I'm considering altering my component hierarchy so that every component belongs to a single "App" parent component for the entire website. It seems like this might make it a little easier to manage state by being able to pass props to any of the components, such as the log-in status of the current user.

Do you have any suggestions for weighing the pros and cons of an entirely single page architecture solely routed by the React router from one page (i.e. "/") versus a few core pages routed by Rails with different root React components for each page (i.e. "/" page for the SplashCarouselApp, "/explore" page for the BrowserApp, "/explore/:id" page for the CompanyDetailApp, and "/launch" page for the FormApp)?

I think these will be a great guide as you go through your project.

If this is the price of the investment, couldn't you calculate that from the listed price for the offering and the number of shares?