pacnpal/thrillwiki_django_no_react
1
1
Fork 0
mirror of https://github.com/pacnpal/thrillwiki_django_no_react.git synced 2025-12-20 07:11:08 -05:00
Code Issues Packages Projects Releases Wiki Activity

feat: Implement enhanced park list template with improved layout and accessibility features

Browse Source 
- Created a new enhanced park list template with a responsive design.
- Added skip navigation links for better accessibility.
- Introduced an enhanced header section with park statistics overview.
- Developed a sidebar for advanced filters and a search section.
- Implemented loading overlay and error handling for HTMX requests.
- Enhanced park results display with animations and improved empty states.
- Added pagination controls with improved UX for navigating park listings.
This commit is contained in:
pacnpal
2025-09-23 20:35:44 -04:00
parent fd42ee1161
commit 41fb41838c
14 changed files with 1716 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

55
.clinerules/thrillwiki-context.xml
View File

@@ -1,4 +1,5 @@
<thrillwiki_context>
<?xml version="1.0" encoding="UTF-8"?>
<thrillwiki_context version="1.0">
<!-- Core Project Information -->
<project_overview>
<name>ThrillWiki</name>
@@ -209,4 +210,56 @@
<database_management>Always use uv run for Django management commands</database_management>
<testing>All functionality must work with progressive enhancement</testing>
</workflow>
<!-- Context7 MCP Integration (MANDATORY) -->
<context7_usage>
<requirement>ALWAYS use Context7 MCP for documentation lookups before making changes</requirement>
<libraries_requiring_context7>
<library name="tailwindcss">Use for CSS utility classes, responsive design, and component styling</library>
<library name="django">Use for models, views, forms, URL patterns, and Django-specific patterns</library>
<library name="django-cotton">Use for component creation, template organization, and Cotton-specific syntax</library>
<library name="htmx">Use for dynamic updates, form handling, and AJAX interactions</library>
<library name="alpinejs">Use for client-side state management, reactive data, and JavaScript interactions</library>
<library name="django-rest-framework">Use for API design, serializers, viewsets, and DRF patterns</library>
<library name="postgresql">Use for database queries, PostGIS functions, and advanced SQL features</library>
<library name="postgis">Use for geographic data handling and spatial queries</library>
<library name="redis">Use for caching strategies, session management, and performance optimization</library>
</libraries_requiring_context7>
<workflow_steps>
<step order="1">Before editing/creating code: Query Context7 for relevant library documentation</step>
<step order="2">During debugging: Use Context7 to verify syntax, patterns, and best practices</step>
<step order="3">When implementing new features: Reference Context7 for current API and method signatures</step>
<step order="4">For performance issues: Consult Context7 for optimization techniques and patterns</step>
<step order="5">For geographic data handling: Use Context7 for PostGIS functions and best practices</step>
<step order="6">For caching strategies: Refer to Context7 for Redis patterns and best practices</step>
<step order="7">For database queries: Utilize Context7 for PostgreSQL best practices and advanced SQL features</step>
</workflow_steps>
<mandatory_scenarios>
<scenario>Creating new Django models or API endpoints</scenario>
<scenario>Implementing HTMX dynamic functionality</scenario>
<scenario>Writing AlpineJS reactive components</scenario>
<scenario>Designing responsive layouts with Tailwind CSS</scenario>
<scenario>Creating Django-Cotton components</scenario>
<scenario>Debugging CSS, JavaScript, or Django issues</scenario>
<scenario>Implementing caching or database optimizations</scenario>
<scenario>Handling geographic data with PostGIS</scenario>
<scenario>Utilizing Redis for session management</scenario>
<scenario>Implementing real-time features with WebSockets</scenario>
</mandatory_scenarios>
<context7_commands>
<resolve_library>Always call Context7:resolve-library-id first to get correct library ID</resolve_library>
<get_docs>Then use Context7:get-library-docs with appropriate topic parameter</get_docs>
<example_topics>
<topic library="tailwindcss">responsive design, flexbox, grid, animations</topic>
<topic library="django">models, views, forms, admin, signals</topic>
<topic library="django-cotton">components, templates, slots, props</topic>
<topic library="htmx">hx-get, hx-post, hx-swap, hx-trigger, hx-target</topic>
<topic library="alpinejs">x-data, x-show, x-if, x-for, x-model</topic>
<topic library="django-rest-framework">serializers, viewsets, routers, permissions</topic>
<topic library="postgresql">joins, indexes, transactions, window functions</topic>
<topic library="postgis">geospatial queries, distance calculations, spatial indexes</topic>
<topic library="redis">caching strategies, pub/sub, data structures</topic>
</example_topics>
</context7_commands>
</context7_usage>
</thrillwiki_context>