sojorn/migrations_archive/setup_cms.sql
Patrick Britton 3c4680bdd7 Initial commit: Complete threaded conversation system with inline replies
**Major Features Added:**
- **Inline Reply System**: Replace compose screen with inline reply boxes
- **Thread Navigation**: Parent/child navigation with jump functionality
- **Chain Flow UI**: Reply counts, expand/collapse animations, visual hierarchy
- **Enhanced Animations**: Smooth transitions, hover effects, micro-interactions

 **Frontend Changes:**
- **ThreadedCommentWidget**: Complete rewrite with animations and navigation
- **ThreadNode Model**: Added parent references and descendant counting
- **ThreadedConversationScreen**: Integrated navigation handlers
- **PostDetailScreen**: Replaced with threaded conversation view
- **ComposeScreen**: Added reply indicators and context
- **PostActions**: Fixed visibility checks for chain buttons

 **Backend Changes:**
- **API Route**: Added /posts/:id/thread endpoint
- **Post Repository**: Include allow_chain and visibility fields in feed
- **Thread Handler**: Support for fetching post chains

 **UI/UX Improvements:**
- **Reply Context**: Clear indication when replying to specific posts
- **Character Counting**: 500 character limit with live counter
- **Visual Hierarchy**: Depth-based indentation and styling
- **Smooth Animations**: SizeTransition, FadeTransition, hover states
- **Chain Navigation**: Parent/child buttons with visual feedback

 **Technical Enhancements:**
- **Animation Controllers**: Proper lifecycle management
- **State Management**: Clean separation of concerns
- **Navigation Callbacks**: Reusable navigation system
- **Error Handling**: Graceful fallbacks and user feedback

This creates a Reddit-style threaded conversation experience with smooth
animations, inline replies, and intuitive navigation between posts in a chain.
2026-01-30 07:40:19 -06:00

17 lines
1.5 KiB
SQL

-- Enable public collections in Directus by adding them to directus_collections
INSERT INTO directus_collections (collection, icon, note, display_template, hidden, singleton, translations, archive_field, archive_app_filter, archive_value, unarchive_value, sort_field, accountability)
VALUES
('profiles', 'account_circle', 'User Profiles', '{{handle}}', false, false, NULL, NULL, true, NULL, NULL, 'created_at', 'all'),
('posts', 'post_add', 'User Posts', '{{body}}', false, false, NULL, 'status', true, 'archived', 'active', 'created_at', 'all'),
('categories', 'category', 'Content Categories', '{{name}}', false, false, NULL, NULL, true, NULL, NULL, 'name', 'all'),
('comments', 'comment', 'Post Comments', '{{body}}', false, false, NULL, 'status', true, 'archived', 'active', 'created_at', 'all'),
('trust_state', 'verified', 'User Trust Scores', '{{harmony_score}}', false, false, NULL, NULL, true, NULL, NULL, NULL, 'all'),
('post_metrics', 'analytics', 'Post Analytics', '{{like_count}} likes', false, false, NULL, NULL, true, NULL, NULL, NULL, 'all'),
('users', 'lock', 'Auth Users', '{{email}}', false, false, NULL, NULL, true, NULL, NULL, 'created_at', 'all')
ON CONFLICT (collection) DO UPDATE
SET icon = EXCLUDED.icon, note = EXCLUDED.note, display_template = EXCLUDED.display_template;
-- Optional: Configure Display Fields (This is usually roughly done by Directus introspection but explicit fields help)
-- We won't inject into directus_fields blindly as that is complex, but the collections are the main step.