Add multi-section organization home page#42
Merged
Conversation
Replace the bare org-subdomain home with a six-section landing page (hero, pillars, scenario example, stories, questions, FAQ) built from static partials and existing Tailwind tokens. Hero shows a sign up / log in CTA when signed out and "Explore options" when signed in, and the nav gains signed-out Log in / Explore links. Also makes Organization#website required so the "Contact us" buttons always have a destination, and updates the affected model and home controller tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replaces the bare org-subdomain home page with a polished six-section landing page — hero, "Explore/Reflect/Plan" pillars, an example legacy-allocation breakdown with a CSS stacked bar chart, legacy stories, a Have Questions section, and a native
<details>FAQ accordion — built from static ERB partials and the existing Tailwind design tokens. The hero shows a Sign up / Log in call-to-action when signed out and an "Explore options" link when signed in, and the nav gains signed-out Log in / Explore links.Organization#websiteis now required so the "Contact us" buttons always have a destination, and the model and home controller tests are updated to match the new page. Note: the example donor quote is intentionally wrapped in a temporary red dashed placeholder marker to be replaced before launch.🤖 Generated with Claude Code