Can I create two distinct event sub-sites within a single plan on Webflow with separate navigation menus, branding, and domain redirects? How should I approach planning for these differentiators?

You can create two distinct event sub-sites within a single Webflow project using Folder or Page-Based Structures, but there are limitations. Here’s how to plan for separate navigation, branding, and domain redirects on the same Webflow plan.

1. Understand Webflow’s Single Project Structure

• A single Webflow project is one hosted site and typically uses one main domain or subdomain.
• You cannot assign multiple root-level custom domains (e.g., event1.com and event2.com) to different folders or pages inside the same project.
• You can use paths (e.g., yourdomain.com/event1 and yourdomain.com/event2) to differentiate sub-sites.

2. Plan Folder-Based Sub-Sites

• Create top-level folders in your Page structure (e.g., /event1/ and /event2/).
• Each folder can contain its own nested pages like intro, schedule, register, etc.

3. Create Unique Navigation Menus

• Use Symbols for global elements like navigation and footers, but create a separate Symbol for each sub-site.
• You can then assign Event 1 Nav to pages under /event1 and Event 2 Nav to pages under /event2.
• To auto-detect which nav to show, consider using page-specific Symbols rather than conditional logic (which isn’t natively supported in Webflow Designer).

4. Distinct Branding and Design

• You can apply different color schemes, fonts, and logos at the page or folder level using:
• Custom CSS classes
• Page-level custom code (add in Page Settings > Custom Code)
• Keep global styles modular so you can override them easily for each sub-site.

5. Redirect or Link Custom Domains (Limitations)

• Webflow currently supports only one primary custom domain per project.
• You can’t redirect event1.com to /event1 and event2.com to /event2 in the same project.
• Workarounds:
• Use external domain forwarding (e.g., from your domain registrar) to point event1.com → yourproject.com/event1.
• Alternatively, split into two separate projects if each event requires a unique root-level domain.

6. CMS Considerations (Optional)

• You can use CMS Collections for repeatable event content and filter items by category or event type.
• Use Collection templates for similar structure but apply classes and filters to mimic separate sub-sites.

Summary

You can create two distinct sub-sites within one Webflow project using folder structures and unique nav/branding per section. However, if you require separate root-level domain names, consider using two separate Webflow projects. Use Symbols, folders, and external domain forwarding to manage visual and structural differences within a single plan.