3
6 Comments

Please Provide Feedback on my Landing Page

PopQuote enables community collaboration on static sites (Gatsby, Hugo, Jekyll, etc) by abstracting Git away from users. Looking for feedback on my landing page. Thank you all!

https://popquote.io/

on July 17, 2020
  1. 1

    Hey csthompson,

    I made a Loom video with a few major design changes.
    (If you do not like my design changes, feel free to reject it 😅)

    https://www.loom.com/share/eccb55aaf8bf486aadb7b8a170a7d221

    My design changes:-

    1. Reduced header size and logo
    2. Removed powered by git

    My feedback:-

    1. My first impression I am confused I know you are dealing with static sites but I have no idea what is the use case for your service.

    2. You placed powered by git which may be confusing for a lot of people maybe if your audience knows git not a problem. (This is the reason I removed git in my loom video)

    3. Feel like it is a great idea. If I understood your service correctly static site powered by markdown files right? (Correct me if I am wrong)

    In the future, if you need any feedback for your landing page
    use this thread (I've also pinned this post on my profile)
    https://www.indiehackers.com/post/send-me-your-landing-page-and-i-will-make-it-cooler-0b1432ee6e

  2. 1

    I think I understand the rough idea - I know that Git can be complicated for non-technical people. I see some value in creating a higher-level abstraction that usually exists in CMS, but not for static websites.

    What I find a bit difficult to understand is what is the use-case exactly? I don't want anybody else to be able to change my website... I guess you mean a website in a bigger organization, where non-technical people want to propose changes or edit directly? Maybe you can put some example use-cases to make this more clear.

    I would also remove the Powered by Git line... I think the only people that will understand it are people that already know Git and this doesn't seem to be your audience. Maybe something like this will be better: "The power of CMS for static sites".

    What I see on the screenshot is essentially a Git branch graph. I understand it because I know Git, the question is if this is the right abstraction level for people that don't know it. I think it will be really cool, if you can also do some kind of live-demo, where I could click around to get a better feeling about your product.

    And some cosmetic issues:

    • The navigation bar is way too big. When I scroll down it covers something like a quarter of my screen! I like the big logo in the beginning, but you should definitely make it smaller, when the user starts scrolling down.
    • There is no explanation for the screenshot. Maybe add something there to clarify.
    • There is so much fine print below the subscription form, that it actually makes me suspicious. I think you should just put one sentence that you will notify people about new products and services and that's it.
    • Why do you need my name for this? I would just ask for e-mail, because you are creating additional friction in the subscription process. And I don't think the names provide you any value.

    I hope this helps!

    1. 1

      Thank you very much for the constructive feedback!

  3. 1

    I would change the hero text. "Collaborate. Share. Grow together" could be used to describe any social media network, photo sharing app, or groupware product.

    The overall concept is clear, but I still have three questions about the product after reading the landing page:

    A) does it work for ANY content on a static site, or just the comments section?
    B) does the contributor need to know the underlying tech used to build the static site? If not, how does one raise a PR to change a typo smack in the middle of a core content page?
    C) does the contributor need to have a GitHub/gitlab account? Where is the contributor's git branch stored till the time it is merged?

    1. 1

      Thank you for the feedback! And just FYI (I will be sure to answer the questions with the page as well)
      A.) Yes. Any content that is developed for the static site with markdown can be edited. This allows readers to actually contribute to the content.
      B.) No not at all. The PRs are handled behind the scenes. A contributor actually doesn't need to know anything about the technology itself.
      C.) Initially, I will most likely do OAuth through Github/Gitlab. Branches are stored in the author's/site's version control system

  4. 1

    Hey @csthompson, I think I can do more than just provide feedback. Are you open to me doing a redesign for the landing page of PopQuote? Send me an email with details if you're interested :)