Routes

[drewroberts]

This package needs a unique route structure. It is different than the Location-Based Routes (TIPOFF/locations#85) and is really dependent on the Market (TIPOFF/locations#41). The easy part is that there is a fixed slug of "rooms" that will always be in the 2nd segment. It will either be under /company or under the market slug.

Under /company/rooms/{themes:slug} are dynamic routes of all the Themes by their slugs. Under /{market}/rooms/{market_scoped_themes:slug} are just the themes in that Market. They are pulled from the unique Themes in the Rooms model which is just Theme to Location. Some Locations have multiple Rooms of the same Theme and Markets may have multiple Locations.

Here are the routes:

• /company/rooms
• /company/rooms/{themes:slug}
• /{market}/rooms
• /{market}/rooms/{market_scoped_themes:slug}

We also need different Views for the /company/rooms page and the /{market}/rooms page.

[pdbreen]

Are these functional pages (ie, only needing to @extend('support::base)`)? Or, are these content pages that will need to support an amp flavor as well? If amp as well, what will determine which version should be returned?

[drewroberts]

We currently use the AMP framework for both of them, but it would be good to have the base structure as well. Thanks!

[drewroberts]

I guess we'll need to add a Layout (drewroberts/blog#60) relationship on the Theme model

[pdbreen]

The Theme model is going to have a layout for the company listing page, market listing page and theme detail page? They have to be different layouts since they're all different views.

And, how would that work for the listings? What happens if there are a mix of layouts on the themes in the list?

[pdbreen]

I think for now - to keep things moving - pushing the view into the config may be best. Can always move to something DB driven later on.

[drewroberts]

That's perfect. Thank you.