Implement visitor-facing dashboard with visitor_featured content filtering #733
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the goal of this PR and why is this important?
Enable unauthenticated visitors to access the dashboard at the root URL, seeing curated content marked for public viewing. Previously, visitors were immediately redirected to login.
How did you approach the change?
Database & Models
visitor_featuredboolean column to workshops, resources, stories, community_news, and events tablesvisitor_featuredscope to all five modelsAuthentication & Routing
ApplicationControllerto allow public access todashboard#indexviapublic_page?checkunauthenticated_rootroute from login page to dashboardvisitor_featuredfor visitors,featuredfor authenticated usersUI & Forms
visitor_featuredExample controller logic:
Anything else to add?
After merging, run
rails db:migrateand mark initial content with "Visitor Featured?" checkbox to populate the public dashboard.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.