Thread

My clients RFP has the following requirements:

User arrives on landing page and chooses their location (location within the state)
The user is then directed to a “site” (same TLD) that has content specific to their location
Location-specific admins can deal with their own content for their portion of the site

I’m wondering if it’s the right choice for me to use EE for this?  Here’s what I was thinking:

http://www.example.com/ <—redirect based on cookie or dropdown
http://www.example.com/locationA
http://www.example.com/locationB

Each of these “locations” could be template groups - then I could use the template group name as the prefix to the weblog names or something like that?

Then maybe the visitors would go to some common areas - but specific to their location:

http://www.example.com/locationA/about
http://www.example.com/locationA/stores
http://www.example.com/locationA/coupons

the same would exist for locationB, C, D… etc

Ideas?  Suggestions?  Am I on the right track?

I would probably handle that with subdomains instead and the old multiple sites solution.
You would get something like
http://locationa.example.com/about/
http://locationa.example.com/stores/
http://locationa.example.com/coupons/

Then you set your location specific variables in the path.php for each subdomain;
$global_vars = array(‘location_name’ => ‘locationA’, ‘location_category’ => ‘18’);

Use {location_name} and {location_category} in your EE tags to fetch the corresponding data.

I would probably use custom statuses or categories to separate content by location.

Good luck!