ShaanCoding
CopyWriting Tasks
Feature Details
For Home Page to Add:
- [ ] Project sponsorship section i.e. Kofi, Buy me a coffee, github, pateron
- [ ] Add Github Star option / CTA
- [ ] Add Copywriting information
- [ ] Add Twitter CTA / Contributing CTA
- [ ] Producthunt CTA (soon)
- [ ] Add Contribution logos via Shadcn icons on page somewhere
Add list of icons for contributors, dynamically generated
Feedback from Twitter:
Landing Page from @GJShepard
Dont like:
- The secondary line in the hero needs to be shorter, try to be concise so in the first 15 seconds on the page I know what you do
- Featured templates area looks really cluttered and I have a hard time to know what to look at
- Spice up the testimonials area, add pic
Like:
- Flow of what content you show
- Colors are different but fun
- Decent use of white space
- The preview image, not sure what it is showing but it is nice, maybe put some text on it to explain what I am looking at
Feeback from Reddit
From bmarshall110
Product Understanding
Critiques:
Clear Introduction: The landing page effectively introduces the purpose of the product — to create and manage README.me files with ease using templates. This is clearly communicated through the headline and introductory text.
Feature Description: The page does well in listing key features such as customizable templates and an intuitive user interface, enhancing product understanding.
Visual Aid: The use of relevant icons and imagery helps visualize the product's usage, but there could be more direct screenshots or video demonstrations of the actual product in use.
Recommendations:
Expand Feature Details: Provide more in-depth information or interactive elements that explain how specific features like the GPT-3 integration will enhance the user experience.
Demonstration Video: Include a demonstration video or animated walkthrough showing the step-by-step process of creating a README using the platform.
Use Cases and Scenarios: Highlight specific use cases or scenarios where makeread.me excels, such as in projects requiring quick setup or for users with minimal markdown expertise.
Customer Persona
Critiques:
Target Audience Clarity: The content is clearly designed for developers, particularly those involved in frequent project documentation tasks.
Engagement Strategy: The calls to action like “Start Generating ReadMEs Now!” are prominently placed, encouraging immediate interaction.
Social Proof: The testimonials section effectively uses feedback from users to build trust and demonstrate the value of the product.
Recommendations:
Persona-Specific Content: Include content that appeals to both novice and advanced users, showing how makeread.me can benefit each group differently.
Enhanced CTA Variations: Experiment with different CTA placements and messaging to optimize conversions, especially lower on the page after users have consumed more information.
Dynamic User Testimonials: Integrate a rotating carousel or a more dynamic way to present testimonials to keep the content engaging.
Branding
Critiques:
Consistent Visual Identity: The consistent use of a modern, minimalist design and typography aligns well with a tech-oriented audience.
Brand Messaging: The language used is professional yet accessible, fitting well for the intended developer audience.
Cohesive Aesthetic Elements: The branding, including the logo and color scheme, is consistent across the page, which enhances brand recognition.
Recommendations:
Storytelling Elements: Integrate a section about the team behind makeread.me or the story of its creation to create a deeper connection with users.
Interactive Brand Elements: Introduce interactive branding elements like animated logos or hover effects on icons for a more dynamic user experience.
Refined Visuals: Update and refine graphical elements periodically to keep the visual appeal fresh and engaging.
Visual Hierarchy and Accessibility
Critiques:
Logical Layout: The page's layout effectively guides users through different sections, from introduction to features, and finally to calls to action.
Accessibility Features: Basic accessibility features are present, but detailed specifics such as alt text descriptions could be more comprehensive.
Responsive Design: The design adapts well across different devices, ensuring a good user experience.
Recommendations:
Improve Visual Hierarchy: Use more varied text sizes and colors to draw attention to key messages or features.
Enhance Accessibility: Conduct a thorough accessibility audit to ensure the site meets all current standards, including keyboard navigability and screen reader accessibility.
Optimize for Mobile Interaction: Ensure interactive elements are easy to use on mobile devices to enhance the experience for touchscreen users.
#62, covered in #41
Feature Details
- Suggested on twitter, but try changing the Copywriting on the home page to include a row of templates (popular ones) as removing the onboarding hurdle and visual view.
Suggested by c0delemons on Twitter. Thanks!
Also in this ticket review / update the copywriting to have a CTA to Star the repository
Discord:
Anonymised for privacy
Great project, and can see themselves using this.
Only critique is the template cards / template page is a bit rough in design, some added whitespace & not having as much information on them would make it easier to read
Would also recommend doing Code Block & Preview Tabs instead of 50:50 split or the option to change layouts as it's a bit overwhelming
Also likes the old UI proposed design opposed to shadcn/ui we did i.e.
Good enough for an OSS project, if people have further additions for this, feel free to raise a PR