mirror of
https://github.com/pacnpal/thrillwiki_django_no_react.git
synced 2025-12-22 09:11:09 -05:00
66 lines
2.1 KiB
Markdown
66 lines
2.1 KiB
Markdown
# Active Context
|
|
|
|
## Current Focus
|
|
- Database schema synchronization and fixes
|
|
- Parks model and pghistory integration
|
|
- Ensuring model-database consistency
|
|
|
|
## Recent Changes
|
|
Fixed critical database schema mismatch in parks app:
|
|
- Updated Park model to include operator and property_owner fields
|
|
- Added missing owner_id column to parks_parkevent table
|
|
- Fixed pghistory triggers that were failing due to missing columns
|
|
- Resolved park detail page errors (parks/magic-kingdom/ now working)
|
|
|
|
### Schema Updates Made
|
|
- parks/models.py: Added operator and property_owner ForeignKey fields
|
|
- parks/migrations/0006_auto_20250920_0944.py: Added owner_id column to parks_parkevent table
|
|
- Database now properly supports all three ownership relationships: owner, operator, property_owner
|
|
|
|
## Active Files
|
|
|
|
### Moderation System
|
|
- moderation/models.py
|
|
- moderation/urls.py
|
|
- moderation/views.py
|
|
- templates/moderation/dashboard.html
|
|
- templates/moderation/partials/
|
|
- submission_list.html
|
|
- moderation_nav.html
|
|
- dashboard_content.html
|
|
|
|
## Next Steps
|
|
1. Review and enhance moderation dashboard functionality
|
|
2. Implement remaining submission review workflows
|
|
3. Test moderation system end-to-end
|
|
4. Document moderation patterns and guidelines
|
|
|
|
## Current Development State
|
|
- Using Django for backend framework
|
|
- HTMX for dynamic interactions
|
|
- AlpineJS for client-side functionality
|
|
- Tailwind CSS for styling
|
|
- Python manage.py tailwind runserver for development
|
|
|
|
## Testing Requirements
|
|
- Verify all moderation workflows
|
|
- Test submission review process
|
|
- Validate user role permissions
|
|
- Check notification systems
|
|
|
|
## Deployment Notes
|
|
- Site runs at http://thrillwiki.com
|
|
- Changes must be committed to git and pushed to main
|
|
- HTMX templates located in partials folders by model
|
|
|
|
## Active Issues/Considerations
|
|
- Ensure proper separation of moderation partials
|
|
- Maintain consistent HTMX patterns
|
|
- Follow established Git workflow
|
|
- Keep documentation updated
|
|
|
|
## Recent Decisions
|
|
- Using partial templates for modular HTMX components
|
|
- Implementing dedicated moderation dashboard
|
|
- Structured submission review process
|