|
|
|
|
|
|
by smt88
4319 days ago
|
|
|
Your landing page needs examples. I'm about 20% sure I understand exactly what the purpose of this is. Also, something like this should be marketed as, "You know that thing you've been doing the hard way? We're helping you do it the easy way." I don't really understand what it is I've been doing the hard way. If we haven't already been doing something that you're now making easier, you should go back to the drawing board. It's hard to create new behavior. |
|
|
When building this page, I definitely struggled with what to put where. The Steps 1, 2, 3 are hopefully clear about what action to take, but I agree that more motivation at the top would be great.
Here’s the thing we believe can be made easier:
When my co-founder and I built Pace [1], Offline [2], Shepherd [3], etc. [4], one of the problems we came across was that while we could get stars on GitHub, non-developers struggled to get the benefit from these projects. Often, the step they struggled with was adding the `<script>` or `<link>` tags to their page, and configuring any of the options these apps/widgets/plugins had.
Our About page [5] explains something to this effect, but bringing some of that motivation to this landing page seems like a good place to start. Thanks again! I hope this was helpful.
Perhaps in addition to:
“Anything you can include in a <script> tag can be installed through our UI.”
We could add:
“Example: You wrote a JavaScript library which works by having the user paste a `<script>` tag in their page. With Eager, instead you users can install your library by simply clicking a button.”
[1]: http://github.hubspot.com/pace/docs/welcome
[2]: http://github.hubspot.com/offline/docs/welcome
[3]: http://github.hubspot.com/shepherd/docs/welcome
[4]: http://github.hubspot.com
[5]: https://eager.io/about