/` - PropertyOwnerDetailView with slug redirect support
-
-## Template Usage Patterns
-
-### Template Structure
-- **parks/park_detail.html**: Comprehensive park display with operator/property owner links
-- **operators/operator_detail.html**: Shows operated parks with park links
-- **property_owners/property_owner_detail.html**: Shows owned properties with operator info
-
-### Key Template Features
-- Cross-linking between parks, operators, and property owners
-- Conditional display of property owner (only if different from operator)
-- Status badges with Tailwind CSS classes
-- Photo galleries and location maps
-- History tracking display
-
-## Shared Functionality Patterns
-
-### Slug Generation
-All models use consistent slug generation:
-- Auto-generated from name field in `save()` method
-- Uses Django's `slugify()` function
-- Historical slug tracking via `HistoricalSlug` model
-
-### History Tracking
-Implemented via two mechanisms:
-1. **pghistory**: Automatic tracking with `@pghistory.track()` decorator
-2. **Manual tracking**: `HistoricalSlug` model for slug changes
-3. **DiffMixin**: Provides `diff_against_previous()` method for change comparison
-
-### Slug Redirect Support
-All detail views use `SlugRedirectMixin` and implement `get_by_slug()` classmethod:
-- Checks current slug first
-- Falls back to pghistory events
-- Falls back to `HistoricalSlug` records
-- Returns tuple of (object, was_redirect_needed)
-
-### Base Classes
-- **TrackedModel**: Provides `created_at`, `updated_at`, and history integration
-- **SlugRedirectMixin**: Handles historical slug redirects in views
-
-## Key Findings
-
-### Strengths
-1. **Consistent patterns**: All models follow similar slug generation and history tracking patterns
-2. **Comprehensive history**: Both automatic (pghistory) and manual (HistoricalSlug) tracking
-3. **Good separation of concerns**: Clear distinction between operators and property owners
-4. **Rich relationships**: Proper foreign key relationships with appropriate related_names
-
-### Issues
-1. **Artificial separation**: Three apps that are always used together
-2. **Duplicated code**: Similar admin configurations and view patterns across apps
-3. **Complex imports**: Cross-app imports create coupling
-4. **Template redundancy**: Similar template patterns across apps
-
-### Entity Relationship Compliance
-The current implementation follows the specified entity relationship rules:
-- ✅ Parks have required Operator relationship
-- ✅ Parks have optional PropertyOwner relationship
-- ✅ No direct Company entity references
-- ✅ Proper foreign key relationships with null/blank settings
-
-## Consolidation Recommendations
-
-Based on the analysis, I recommend consolidating the three apps into a single `parks` app with the following structure:
-
-```
-parks/
-├── models/
-│ ├── __init__.py # Import all models here
-│ ├── park.py # Park, ParkArea models
-│ ├── operators.py # Operator model
-│ └── owners.py # PropertyOwner model
-├── admin/
-│ ├── __init__.py # Register all admin classes
-│ ├── park.py # Park and ParkArea admin
-│ ├── operators.py # Operator admin
-│ └── owners.py # PropertyOwner admin
-├── views/
-│ ├── __init__.py # Import all views
-│ ├── parks.py # Park and ParkArea views
-│ ├── operators.py # Operator views
-│ └── owners.py # PropertyOwner views
-├── templates/parks/
-│ ├── parks/ # Park templates
-│ ├── operators/ # Operator templates
-│ └── owners/ # Property owner templates
-└── urls.py # All URL patterns
-```
-
-### Benefits of Consolidation
-1. **Reduced complexity**: Single app to manage instead of three
-2. **Eliminated duplication**: Shared admin mixins, view base classes, and template components
-3. **Simplified imports**: No cross-app dependencies
-4. **Better cohesion**: Related functionality grouped together
-5. **Easier maintenance**: Single location for park domain logic
-
-### Migration Strategy
-1. Create new model structure within parks app
-2. Move existing models to new locations
-3. Update all imports and references
-4. Consolidate admin configurations
-5. Merge URL patterns
-6. Update template references
-7. Run Django migrations to reflect changes
-8. Remove empty apps
-
-This consolidation maintains all existing functionality while significantly improving code organization and maintainability.
\ No newline at end of file
diff --git a/parks_listing_comprehensive_documentation.md b/parks_listing_comprehensive_documentation.md
deleted file mode 100644
index 79cecabf..00000000
--- a/parks_listing_comprehensive_documentation.md
+++ /dev/null
@@ -1,313 +0,0 @@
-# Parks Listing Page - Comprehensive Documentation
-
-## Overview
-
-The parks listing page is the primary interface for browsing and discovering theme parks in ThrillWiki. It provides search, filtering, and listing capabilities with both grid and list view modes.
-
-## Current Architecture
-
-### Models
-
-#### Park Model (`parks/models/parks.py`)
-The core Park model contains these key fields:
-- **Basic Info**: `name`, `slug`, `description`, `status`
-- **Operations**: `opening_date`, `closing_date`, `operating_season`
-- **Metadata**: `size_acres`, `website`, `average_rating`
-- **Statistics**: `ride_count`, `coaster_count` (manual fields)
-- **Relationships**:
- - `operator` (ForeignKey to Company)
- - `property_owner` (ForeignKey to Company)
- - `photos` (GenericRelation)
- - `location` (OneToOneField via ParkLocation reverse relation)
-
-#### Park Status System
-The status system uses predefined choices with corresponding CSS classes:
-
-**Status Options:**
-- `OPERATING`: "Operating" - Green badge (`bg-green-100 text-green-800`)
-- `CLOSED_TEMP`: "Temporarily Closed" - Yellow badge (`bg-yellow-100 text-yellow-800`)
-- `CLOSED_PERM`: "Permanently Closed" - Red badge (`bg-red-100 text-red-800`)
-- `UNDER_CONSTRUCTION`: "Under Construction" - Blue badge (`bg-blue-100 text-blue-800`)
-- `DEMOLISHED`: "Demolished" - Gray badge (`bg-gray-100 text-gray-800`)
-- `RELOCATED`: "Relocated" - Purple badge (`bg-purple-100 text-purple-800`)
-
-**Status Badge Implementation:**
-```html
-
- {{ park.get_status_display }}
-
-```
-
-**CSS Classes:**
-```css
-.status-badge {
- @apply inline-flex items-center px-3 py-1 text-sm font-medium rounded-full;
-}
-
-.status-operating {
- @apply text-green-800 bg-green-100 dark:bg-green-700 dark:text-green-50;
-}
-
-.status-closed {
- @apply text-red-800 bg-red-100 dark:bg-red-700 dark:text-red-50;
-}
-
-.status-construction {
- @apply text-yellow-800 bg-yellow-100 dark:bg-yellow-600 dark:text-yellow-50;
-}
-```
-
-#### ParkLocation Model (`parks/models/location.py`)
-Handles geographic data with PostGIS support:
-- **Coordinates**: `point` (PointField with SRID 4326)
-- **Address**: `street_address`, `city`, `state`, `country`, `postal_code`
-- **Trip Planning**: `highway_exit`, `parking_notes`, `best_arrival_time`, `seasonal_notes`
-- **OSM Integration**: `osm_id`, `osm_type`
-
-### Views
-
-#### ParkListView (`parks/views.py:212-272`)
-Inherits from `HTMXFilterableMixin` and `ListView`:
-- **Template**: `parks/park_list.html` (full page) or `parks/partials/park_list_item.html` (HTMX)
-- **Pagination**: 20 items per page
-- **Filter Class**: `ParkFilter`
-- **Context**: Includes `view_mode`, `is_search`, `search_query`
-- **Error Handling**: Graceful degradation with error messages
-
-**Key Methods:**
-- `get_template_names()`: Returns different templates for HTMX requests
-- `get_view_mode()`: Handles grid/list toggle
-- `get_queryset()`: Uses `get_base_park_queryset()` with filters applied
-- `get_context_data()`: Adds view mode and search context
-
-#### Supporting View Functions
-- `add_park_button()`: Returns add park button partial
-- `park_actions()`: Returns park actions partial
-- `get_park_areas()`: Dynamic area options for select elements
-- `location_search()`: OpenStreetMap Nominatim API integration
-- `reverse_geocode()`: Coordinate to address conversion
-- `search_parks()`: HTMX search endpoint
-
-### Templates
-
-#### Main Template (`parks/templates/parks/park_list.html`)
-Extends `search/layouts/filtered_list.html` with these sections:
-
-**List Actions Block:**
-- Page title ("Parks")
-- View mode toggle (Grid/List) with HTMX
-- Add Park button (authenticated users only)
-
-**Filter Section Block:**
-- Search autocomplete with Alpine.js
-- Filter form with HTMX updates
-- Loading indicators and accessibility features
-
-**Results List Block:**
-- Contains park results container
-- Includes `park_list_item.html` partial
-
-#### Park List Item Partial (`parks/templates/parks/partials/park_list_item.html`)
-Displays individual park cards:
-- **Grid Layout**: 3-column responsive grid (`md:grid-cols-2 lg:grid-cols-3`)
-- **Card Design**: White background, shadow, hover transform
-- **Content**: Park name (linked), status badge, operator link
-- **Empty State**: Helpful message with option to add parks
-- **Error Handling**: Error display with icon
-
-### Filtering System
-
-#### ParkFilter (`parks/filters.py`)
-Comprehensive filter system with validation:
-
-**Core Filters:**
-- `search`: Multi-field search (name, description, location fields)
-- `status`: Operating status dropdown
-- `operator`: Operating company selector
-- `has_operator`: Boolean filter for operator presence
-
-**Numeric Filters:**
-- `min_rides`: Minimum ride count with validation
-- `min_coasters`: Minimum coaster count with validation
-- `min_size`: Minimum size in acres with validation
-
-**Date Filters:**
-- `opening_date`: Date range filter
-
-**Location Filters:**
-- `location_search`: Search by city, state, country, address
-- `near_location`: Proximity search with geocoding
-- `radius_km`: Search radius (used with near_location)
-- `country_filter`: Country-specific filtering
-- `state_filter`: State/region filtering
-
-**Advanced Features:**
-- Custom `qs` property ensures base queryset with annotations
-- Geocoding integration with OpenStreetMap Nominatim
-- Distance calculations with PostGIS
-- Input validation with custom validators
-
-#### Base Queryset (`parks/querysets.py`)
-Optimized query with:
-- **Relationships**: `select_related('operator', 'property_owner', 'location')`
-- **Prefetches**: `photos`, `rides`
-- **Annotations**:
- - `current_ride_count`: Live count from related rides
- - `current_coaster_count`: Live count of roller coasters
-- **Ordering**: Alphabetical by name
-
-### Forms
-
-#### ParkForm (`parks/forms.py:54-312`)
-Comprehensive form for park creation/editing:
-- **Model Fields**: All Park model fields
-- **Location Fields**: Separate fields for coordinates and address
-- **Widgets**: Tailwind CSS styled with dark mode support
-- **Validation**: Coordinate range validation and precision handling
-- **Location Integration**: Automatic ParkLocation creation/update
-
-#### ParkAutocomplete (`parks/forms.py:11-38`)
-Search autocomplete functionality:
-- **Search Attributes**: Park name matching
-- **Related Data**: Includes operator and owner information
-- **Formatting**: Status and location display in results
-
-### Styling & Design
-
-#### Theme System
-Based on Tailwind CSS v4 with custom design tokens:
-- **Primary Color**: `#4f46e5` (Vibrant indigo)
-- **Secondary Color**: `#e11d48` (Vibrant rose)
-- **Accent Color**: `#8b5cf6`
-- **Font**: Poppins sans-serif
-- **Dark Mode**: Class-based toggle support
-
-#### Card Design Pattern
-Consistent across the application:
-```css
-.card {
- @apply p-6 bg-white border rounded-lg shadow-lg dark:bg-gray-800 border-gray-200/50 dark:border-gray-700/50;
-}
-
-.card-hover {
- @apply transition-transform transform hover:-translate-y-1;
-}
-```
-
-#### Grid System
-Adaptive grid with responsive breakpoints:
-```css
-.grid-cards {
- @apply grid grid-cols-1 gap-6 md:grid-cols-2 lg:grid-cols-3;
-}
-
-.grid-adaptive {
- @apply grid gap-6;
- grid-template-columns: repeat(auto-fit, minmax(280px, 1fr));
-}
-```
-
-#### Status Badges
-Semantic color coding with dark mode support:
-- Consistent padding: `px-3 py-1`
-- Typography: `text-sm font-medium`
-- Shape: `rounded-full`
-- Colors: Contextual based on status type
-
-### JavaScript Integration
-
-#### HTMX Features
-- **Dynamic Loading**: Park list updates without page refresh
-- **Search**: Real-time search with debouncing (300ms delay)
-- **Filters**: Form submission with URL state management
-- **View Modes**: Toggle between grid/list with state preservation
-- **Pagination**: Seamless page navigation
-- **Error Handling**: Custom error displays with HX-Trigger events
-
-#### Alpine.js Components
-- **Search Interface**: Query state management and escape key handling
-- **Filter Integration**: Form state synchronization
-- **Accessibility**: ARIA attributes for screen readers
-
-### API Integration
-
-#### OpenStreetMap Nominatim
-- **Search Endpoint**: Location autocomplete with 10 result limit
-- **Geocoding**: Address to coordinate conversion
-- **Reverse Geocoding**: Coordinate to address lookup
-- **Error Handling**: Graceful fallbacks for API failures
-- **Rate Limiting**: 5-second timeout for requests
-
-#### Location Utilities
-- **Coordinate Normalization**: Precision handling for lat/lng
-- **English Name Extraction**: Multi-language support
-- **Address Parsing**: Comprehensive address component handling
-
-### Performance Optimizations
-
-#### Database Queries
-- **Select Related**: Minimize N+1 queries for relationships
-- **Prefetch Related**: Efficient loading of many-to-many relations
-- **Annotations**: Database-level calculations for counts
-- **Distinct**: Prevent duplicate results from joins
-
-#### Frontend Performance
-- **HTMX**: Partial page updates reduce bandwidth
-- **Debouncing**: Search input optimization
-- **Lazy Loading**: Progressive content loading
-- **Caching**: Template fragment caching where appropriate
-
-### Accessibility Features
-
-#### Screen Reader Support
-- **Semantic HTML**: Proper heading hierarchy and landmarks
-- **ARIA Labels**: Descriptive labels for interactive elements
-- **Focus Management**: Keyboard navigation support
-- **Loading States**: Screen reader announcements for dynamic content
-
-#### Keyboard Navigation
-- **Escape Key**: Closes search suggestions
-- **Tab Order**: Logical focus sequence
-- **Enter/Space**: Activates buttons and links
-
-### Error Handling
-
-#### Graceful Degradation
-- **Query Failures**: Empty queryset with error message
-- **Filter Errors**: Form validation with user feedback
-- **API Timeouts**: Fallback to basic functionality
-- **JavaScript Disabled**: Basic form submission still works
-
-#### User Feedback
-- **Loading Indicators**: Spinner animations during requests
-- **Error Messages**: Clear, actionable error descriptions
-- **Empty States**: Helpful guidance when no results found
-- **Success States**: Confirmation of actions taken
-
-## Current Strengths
-
-1. **Comprehensive Filtering**: Rich set of filter options for various use cases
-2. **Performance**: Optimized queries with proper relationships and annotations
-3. **User Experience**: Smooth HTMX interactions with instant feedback
-4. **Responsive Design**: Works well on all device sizes
-5. **Accessibility**: Good screen reader and keyboard support
-6. **Status System**: Clear, well-designed status indicators
-7. **Location Integration**: PostGIS-powered geographic capabilities
-8. **Search Experience**: Real-time search with autocomplete
-9. **Error Handling**: Graceful degradation and user feedback
-10. **Dark Mode**: Consistent theming across light/dark modes
-
-## Areas for Enhancement
-
-1. **Location Filtering**: Hierarchical location filtering (Country → State → City)
-2. **Advanced Search**: More sophisticated search capabilities
-3. **Map Integration**: Geographic visualization of results
-4. **Bulk Operations**: Multi-select actions for parks
-5. **Export Functionality**: CSV/JSON export of filtered results
-6. **Bookmarking**: Save filter combinations
-7. **Recent Searches**: Search history functionality
-8. **Advanced Sorting**: Multiple sort criteria
-9. **Preview Mode**: Quick preview without navigation
-10. **Comparison Tools**: Side-by-side park comparisons
-
-This documentation provides a comprehensive foundation for understanding the current parks listing implementation and serves as a baseline for planning improvements while preserving the existing strengths and design patterns.
diff --git a/parks_listing_improvement_plan.md b/parks_listing_improvement_plan.md
deleted file mode 100644
index 648301e7..00000000
--- a/parks_listing_improvement_plan.md
+++ /dev/null
@@ -1,700 +0,0 @@
-# Parks Listing Page - Comprehensive Improvement Plan
-
-## Executive Summary
-
-This document outlines a comprehensive improvement plan for the ThrillWiki parks listing page, focusing on enhanced location-based filtering with a hierarchical Country → State → City approach, while preserving the current design theme, park status implementation, and user experience patterns.
-
-## Primary Focus: Hierarchical Location Filtering
-
-### 1. Enhanced Location Model Structure
-
-#### 1.1 Country-First Approach
-**Objective**: Implement a cascading location filter starting with countries, then drilling down to states/regions, and finally cities.
-
-**Current State**:
-- Flat location fields in `ParkLocation` model
-- Basic country/state/city filters without hierarchy
-- No standardized country/region data
-
-**Proposed Enhancement**:
-```python
-# New model structure to support hierarchical filtering
-class Country(models.Model):
- name = models.CharField(max_length=100, unique=True)
- code = models.CharField(max_length=3, unique=True) # ISO 3166-1 alpha-3
- region = models.CharField(max_length=100) # e.g., "Europe", "North America"
- park_count = models.IntegerField(default=0) # Denormalized for performance
-
- class Meta:
- verbose_name_plural = "Countries"
- ordering = ['name']
-
-class State(models.Model):
- name = models.CharField(max_length=100)
- country = models.ForeignKey(Country, on_delete=models.CASCADE, related_name='states')
- code = models.CharField(max_length=10, blank=True) # State/province code
- park_count = models.IntegerField(default=0)
-
- class Meta:
- unique_together = [['name', 'country']]
- ordering = ['name']
-
-class City(models.Model):
- name = models.CharField(max_length=100)
- state = models.ForeignKey(State, on_delete=models.CASCADE, related_name='cities')
- park_count = models.IntegerField(default=0)
-
- class Meta:
- verbose_name_plural = "Cities"
- unique_together = [['name', 'state']]
- ordering = ['name']
-
-# Enhanced ParkLocation model
-class ParkLocation(models.Model):
- park = models.OneToOneField('parks.Park', on_delete=models.CASCADE, related_name='location')
-
- # Hierarchical location references
- country = models.ForeignKey(Country, on_delete=models.PROTECT)
- state = models.ForeignKey(State, on_delete=models.PROTECT, null=True, blank=True)
- city = models.ForeignKey(City, on_delete=models.PROTECT, null=True, blank=True)
-
- # Legacy fields maintained for compatibility
- country_legacy = models.CharField(max_length=100, blank=True)
- state_legacy = models.CharField(max_length=100, blank=True)
- city_legacy = models.CharField(max_length=100, blank=True)
-
- # Existing fields preserved
- point = models.PointField(srid=4326, null=True, blank=True)
- street_address = models.CharField(max_length=255, blank=True)
- postal_code = models.CharField(max_length=20, blank=True)
-
- # Trip planning fields (preserved)
- highway_exit = models.CharField(max_length=100, blank=True)
- parking_notes = models.TextField(blank=True)
- best_arrival_time = models.TimeField(null=True, blank=True)
- seasonal_notes = models.TextField(blank=True)
-
- # OSM integration (preserved)
- osm_id = models.BigIntegerField(null=True, blank=True)
- osm_type = models.CharField(max_length=10, blank=True)
-```
-
-#### 1.2 Data Migration Strategy
-**Migration Phase 1**: Add new fields alongside existing ones
-**Migration Phase 2**: Populate new hierarchical data from existing location data
-**Migration Phase 3**: Update forms and views to use new structure
-**Migration Phase 4**: Deprecate legacy fields (keep for backwards compatibility)
-
-### 2. Advanced Filtering Interface
-
-#### 2.1 Hierarchical Filter Components
-
-**Location Filter Widget**:
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-#### 2.2 Enhanced Filter Classes
-```python
-class AdvancedParkFilter(ParkFilter):
- # Hierarchical location filters
- location_country = ModelChoiceFilter(
- field_name='location__country',
- queryset=Country.objects.annotate(
- park_count=Count('states__cities__parklocation')
- ).filter(park_count__gt=0),
- empty_label='All Countries',
- label='Country'
- )
-
- location_state = ModelChoiceFilter(
- method='filter_location_state',
- queryset=State.objects.none(), # Will be populated dynamically
- empty_label='All States/Regions',
- label='State/Region'
- )
-
- location_city = ModelChoiceFilter(
- method='filter_location_city',
- queryset=City.objects.none(), # Will be populated dynamically
- empty_label='All Cities',
- label='City'
- )
-
- # Geographic region filters
- geographic_region = ChoiceFilter(
- method='filter_geographic_region',
- choices=[
- ('north_america', 'North America'),
- ('europe', 'Europe'),
- ('asia_pacific', 'Asia Pacific'),
- ('latin_america', 'Latin America'),
- ('middle_east_africa', 'Middle East & Africa'),
- ],
- empty_label='All Regions',
- label='Geographic Region'
- )
-
- def filter_location_state(self, queryset, name, value):
- if value:
- return queryset.filter(location__state=value)
- return queryset
-
- def filter_location_city(self, queryset, name, value):
- if value:
- return queryset.filter(location__city=value)
- return queryset
-
- def filter_geographic_region(self, queryset, name, value):
- region_mapping = {
- 'north_america': ['USA', 'Canada', 'Mexico'],
- 'europe': ['United Kingdom', 'Germany', 'France', 'Spain', 'Italy'],
- # ... more mappings
- }
- if value in region_mapping:
- countries = region_mapping[value]
- return queryset.filter(location__country__name__in=countries)
- return queryset
-```
-
-### 3. Enhanced User Experience Features
-
-#### 3.1 Smart Location Suggestions
-```javascript
-// Enhanced location autocomplete with regional intelligence
-class LocationSuggestionsSystem {
- constructor() {
- this.userLocation = null;
- this.searchHistory = [];
- this.preferredRegions = [];
- }
-
- // Prioritize suggestions based on user context
- prioritizeSuggestions(suggestions) {
- return suggestions.sort((a, b) => {
- // Prioritize user's country/region
- if (this.isInPreferredRegion(a) && !this.isInPreferredRegion(b)) return -1;
- if (!this.isInPreferredRegion(a) && this.isInPreferredRegion(b)) return 1;
-
- // Then by park count
- return b.park_count - a.park_count;
- });
- }
-
- // Add breadcrumb navigation
- buildLocationBreadcrumb(country, state, city) {
- const breadcrumb = [];
- if (country) breadcrumb.push({type: 'country', name: country.name, id: country.id});
- if (state) breadcrumb.push({type: 'state', name: state.name, id: state.id});
- if (city) breadcrumb.push({type: 'city', name: city.name, id: city.id});
- return breadcrumb;
- }
-}
-```
-
-#### 3.2 Location Statistics Display
-```html
-
-
-
Browse by Location
-
-
- {% for country in top_countries %}
-
-
-
- {% endfor %}
-
-
-
-
-
-
-
-
-
-
- {% if park.distance %}
- {{ park.distance|floatformat:1 }}km away
- {% endif %}
- {% if park.search_score %}
- {{ park.search_score|floatformat:0 }}% match
- {% endif %}
-
-
-
-
-
-
-
-
-
-