Open
Conversation
a first step towards setting up the landing page
✅ Deploy Preview for snowplow-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
- Hero Area - Navigation Structure - Placeholder Trust logo banner
Writing Quality ReviewThank you for working on the new landing page! I've reviewed the content against the Snowplow documentation style guide. Here are my suggestions to align the writing with our established conventions: ✅ What's Working Well
📝 Suggested Changes1. Marketing Language (Critical)The style guide explicitly states: "Never use marketing language." Several phrases need revision: Line 248-250 (Hero headline): - From Raw Behavior Data
- to AI powered Fuel
+ From raw behavior to intelligent actionLine 306 (Subheadline): - We are the leader in customer data infrastructure (CDI)—including advanced analytics, real-time personalization engines, and AI agents.
+ Snowplow provides customer data infrastructure for analytics, real-time personalization, and AI applications.(Use "Snowplow" not "we"; avoid "leader" and "advanced" as marketing terms) Line 379 (CDI subtitle): - Governed, AI-ready behavioral data — in your warehouse
+ Governed behavioral data in your warehouseLine 408 (Signals subtitle): - Real-time customer intelligence — for AI-powered applications
+ Real-time customer context for applications2. Tone & Exclamation MarksLine 551 (Footer CTA): - Ready to own your behavioral data?
+ Own your behavioral data(The style guide says "Never use exclamation marks" and to avoid rhetorical questions in professional technical docs) 3. EmojisLines 482, 493, 504, etc. (Start Here section): The decorative emojis (📘, 🔧, ⚡, etc.) throughout the page should be removed or replaced with proper icons/images. 4. Technical Term FormattingLine 382 (CDI builds list): - Composable analytics & BI
+ Composable analytics and BI(Style guide: Use "and", never "&") Line 436 (Better Together section): - CDI captures and governs your data. Signals serves it to your applications in real-time.
+ CDI captures and governs your data. Signals serves it to your applications in real time.("real time" as a noun; "real-time" as an adjective only) 5. Capitalization After ColonsThe style guide states: "After a colon within a list item, continue lowercase." Line 38 & 42 (PathCard component): - <p className="text-xs uppercase tracking-wider text-gray-500 mb-2">Built for</p>
+ <p className="text-xs uppercase tracking-wider text-gray-500 mb-2">Built for:</p>
- <p className="text-xs uppercase tracking-wider text-gray-500 mb-3">You'll build</p>
+ <p className="text-xs uppercase tracking-wider text-gray-500 mb-3">You'll build:</p>(Lists should be introduced with a sentence ending in a colon) Line 381 (CDI forText): - Data Engineers · Analytics Engineers · Platform Teams
+ data engineers, analytics engineers, and platform teams(Use lowercase after the colon, use Oxford comma) Same for line 410 (Signals forText). 6. Terminology ConsistencyLine 380 (CDI description): - Collect event-level data from every touchpoint. Validate against schemas at collection — not after. Deliver to your warehouse, lake, or stream in seconds, with complete ownership.
+ Collect event-level data from every touchpoint. Validate against schemas at collection. Deliver to your warehouse, lake, or stream in seconds.(Remove marketing phrases like "complete ownership"; keep technical and factual) 🎯 Priority FixesIf time is limited, focus on these high-impact changes first:
📚 Resources
These changes will ensure the landing page maintains the professional, technical tone consistent with the rest of the documentation. Happy to discuss any of these suggestions! |
- Updated floating navigation: Simplified to CDI, Signals, Tutorials, Get Started (primary button) - Fixed button styling: All navigation items now use shadcn Button components with proper theming - Updated links: Fixed Tutorials link (/tutorials/) and Signals link (/docs/signals/) - Removed login button: Cleaned up navigation focus - Added text color fixes: Used text-muted-foreground for consistent theming Hero Section Redesign - New developer-focused headline: "Build Data Apps with AI superpowers" (with gradient text) - Updated subheadline: Now mentions MCP integration and AI-powered development workflow - Enhanced visual appeal: Added gradient text effects for key messaging Tutorial Integration - Replaced placeholder cards: Integrated real tutorial data using existing TutorialGrid component - Filtered content: Shows only "Solution accelerator" and "Signals implementation" tutorials - Seamless integration: Uses same card design and animations as main tutorials page Infinite Logo Slider Fixes - Resolved animation issues: Fixed choppy animations and jumping at loop end - Implemented seamless scrolling: Used precise width calculations and CSS animations - Added proper theming: Updated to use shadcn theme variables throughout - Enhanced fade effects: Proper gradient overlays that match theme Snowplow MCP Integration - New Snippet component: Created /src/components/ui/snippet.tsx with copy-to-clipboard functionality - MCP Installation section: Interactive code snippets for Claude Desktop and npm installation - Updated CSS: Added all required custom properties, animations, and utility classes for Snippet component - Theme support: Full light/dark theme compatibility FAQ Section Overhaul - MCP-focused content: Converted all FAQ questions to focus on Snowplow MCP - New layout: Two-column design with installation guide + FAQ side-by-side - Updated headlines: "🤖 Supercharge Your Workflow with AI" section header - Documentation links: Added links to MCP documentation 📁 Files Modified: 1. /src/pages/index.js - Main landing page with all new components and content 2. /src/components/ui/floating-navbar.jsx - Simplified navigation with shadcn theming 3. /src/components/ui/infinite-logo-slider.jsx - Fixed infinite scroll animations 4. /src/components/ui/snippet.tsx - New component for interactive code snippets 5. /src/css/custom.css - Added Snippet component styles, animations, and utility classes 🎨 Key Features Added: - Interactive copy-to-clipboard code snippets - Real tutorial data integration - MCP-focused FAQ and installation guide - Developer-exciting headlines with gradient effects - Seamless infinite logo carousel - Full shadcn theme integration throughout 🔧 Technical Improvements: - Fixed infinite scroll animation gaps and choppiness - Proper TypeScript support for new components - Responsive design with proper breakpoints - Enhanced accessibility and semantic HTML - Performance optimizations with memoized tutorial filtering Ready for commit: All components are properly themed, responsive, and follow existing code patterns.
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
2 participants
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.
a first step towards setting up the landing page