Small Landing Page Improvements #2756
Conversation
web/src/components/Hero.js
Outdated
| <div> | ||
| <span | ||
| className={classNames( | ||
| 'font-jersey text-[4.5rem] sm:text-[8rem] lg:text-[6.35rem] font-normal text-yellow-500 ' |
There was a problem hiding this comment.
we could alternatively remove the Jersey 10 font from "Everything" and have it be the same font as the rest.
There was a problem hiding this comment.
So I am not super sold of "Full-stack Everything" -> I like how simple and let's say powerful it is, but I find it also confusing -> why "everything", what does that mean? Sounds like Wasp is a tool for converting stuff into Full stack or something. Sends me in the wrong direction off the very start. I don't know. Also jersey stile is cool, reminds me of games, but maybe a bit off the brand and I saw people in Discord saying they don't like it.
I like the initiative, and the direction, but I am thinking this is not exactly it. Not sure what it should be though.
"The modern full-stack framework". "Full-stack for real.". "Truly full-stack framework". "Full-full-stack web app framework". "Full^2-stack web-app framework". "Full-stack* web-app framework of the future" with a note right below "*Truly full-stack! Client <-> server <-> db <-> deployment".
Hmmm I actually like these ideas, do you like any of them?
| title="Wasp CLI" | ||
| url="/docs/general/cli" | ||
| description="All the handy commands at your fingertips." | ||
| title="Goodbye boilerplate" |
There was a problem hiding this comment.
Can we kick out this video? Learn more should either link to our docs, or to nothing else, this way we're adding links for the sake of fun, and it has SEO implications.
| Rails-like framework for React, Node.js and Prisma. Build your app | ||
| in a day and deploy it with a single CLI command. | ||
| <p className="mt-8 text-xl text-neutral-500 sm:mt-5 lg:text-xl lg:leading-relaxed"> | ||
| The Laravel alternative for JavaScript. |
There was a problem hiding this comment.
All of my comments are in the Notion, I'd like us to go there before we get back to it here.
SEO implications are huge, and these are breaking changes.
There was a problem hiding this comment.
Great @vincanger !
Some stuff is clear improvement, like the example apps and showcase gallery being updated with new stuff. I think we can merge those immediately.
As for the main copy -> I would say let's go for changes if we can agree to something, this is a good initiative you started here, instead of talking forever, we kickstart it with something concrete. I threw in some suggestions, maybe we can find something we both like right now.
| @@ -23,6 +23,98 @@ $ npm start | |||
| This command starts a local development server and opens up a browser window. | |||
| Most changes are reflected live without having to restart the server. | |||
|
|
|||
| ### Writing docs | |||
There was a problem hiding this comment.
Hm this pulled in the changes from Carlos's PR, that is kind of wrong! We don't want that in this PR really.
I think you branched from main and then made a PR toward release? You should instead branch from release and then make a PR toward release.
| @@ -79,7 +80,7 @@ const Features = () => { | |||
| title="Open Source" | |||
| url="https://github.com/wasp-lang/wasp" | |||
| description={` | |||
| This is the way. Wasp is fully open-source and you're welcome to contribute! | |||
| Fully open-source and you’re welcome to contribute! | |||
There was a problem hiding this comment.
Oh interesting, I don't even know how to type that character, the single quote thing that is not a single quote :D.
| @@ -88,7 +89,7 @@ const Features = () => { | |||
| title="Full-stack Auth" | |||
| url="/blog/2023/04/12/auth-ui" | |||
| description={` | |||
| Add login with social providers or email in a few lines of code with powerful UI helpers. No third party vendor lock-in. | |||
| Add email and social login in a few lines of code. Wasp manages everything from sessions to UI components. No boilerplate, no lock-in. | |||
There was a problem hiding this comment.
Maybe let's make it clearer it handles full stack? sessions to UI components -> sessions kind of indicate it is handling backend stuff, but I have to admit I myself woudln't be sure what that means all together. I would say "Wasp handles everything from UI components to sessions in the database, full stack.", something like that.
| @@ -103,29 +104,28 @@ const Features = () => { | |||
|
|
|||
| <Feature | |||
| Icon={Send} | |||
| title="Simple Deployment" | |||
| title="One-command Deploy" | |||
There was a problem hiding this comment.
suggestion(weak):
| title="One-command Deploy" | |
| title="Single-command Deploy" |
| url="/docs/deployment/intro" | ||
| description={` | ||
| Deploy your app to any platform. Wasp offers CLI helpers for the most popular options. | ||
| Deploy your entire app—from frontend to database—to platforms like Railway or Fly.io with just one command. |
There was a problem hiding this comment.
I thought app-from was one word or something. Btw these days this long hyphen is recognized as AI output :D, but maybe it fits this situation, I don't know.
| Deploy your entire app—from frontend to database—to platforms like Railway or Fly.io with just one command. | |
| Deploy your entire app — from frontend to database — to platforms like Railway or Fly.io with a single command. |
| description={` | ||
| Easily define, schedule and run specialized server tasks. | ||
| Persistent, retryable, delayable. | ||
| Just choose a provider and Wasp will handle the rest! |
There was a problem hiding this comment.
| Just choose a provider and Wasp will handle the rest! | |
| Just choose an email provider and Wasp will handle the rest! |
| description={` | ||
| All you need to do is connect an email provider and you can send emails! | ||
| Easily send emails, crunch data, and schedule tasks using the power of Postgres. |
There was a problem hiding this comment.
Hm I found the earlier desription clearer. I think you focused more on what you can do with it, but now it is less clear to me what it is, is it something specific for emails/data/scheudling or is it a general mechanism?
web/src/components/Hero.js
Outdated
| <div> | ||
| <span | ||
| className={classNames( | ||
| 'font-jersey text-[4.5rem] sm:text-[8rem] lg:text-[6.35rem] font-normal text-yellow-500 ' |
There was a problem hiding this comment.
So I am not super sold of "Full-stack Everything" -> I like how simple and let's say powerful it is, but I find it also confusing -> why "everything", what does that mean? Sounds like Wasp is a tool for converting stuff into Full stack or something. Sends me in the wrong direction off the very start. I don't know. Also jersey stile is cool, reminds me of games, but maybe a bit off the brand and I saw people in Discord saying they don't like it.
I like the initiative, and the direction, but I am thinking this is not exactly it. Not sure what it should be though.
"The modern full-stack framework". "Full-stack for real.". "Truly full-stack framework". "Full-full-stack web app framework". "Full^2-stack web-app framework". "Full-stack* web-app framework of the future" with a note right below "*Truly full-stack! Client <-> server <-> db <-> deployment".
Hmmm I actually like these ideas, do you like any of them?
| in a day and deploy it with a single CLI command. | ||
| <p className="mt-8 text-xl text-neutral-500 sm:mt-5 lg:text-xl lg:leading-relaxed"> | ||
| The Laravel alternative for JavaScript. | ||
| Truly full-stack. Batteries-included. Built on top of React, |
There was a problem hiding this comment.
Oh yeah I am liking this. "Truly full-stack" and "Batteries-included" are the terms we should have, 100%.
| Rails-like framework for React, Node.js and Prisma. Build your app | ||
| in a day and deploy it with a single CLI command. | ||
| <p className="mt-8 text-xl text-neutral-500 sm:mt-5 lg:text-xl lg:leading-relaxed"> | ||
| The Laravel alternative for JavaScript. |
There was a problem hiding this comment.
I am starting to think that we should mention Laravel and RoR, but that it shouldn't be the way we define ourselves. I would say, first you read what Wasp is, then you wonder "ok but what is that like in practice", and then we say "Imagine RoR or Laravel's DX, but reimagined from scratch for JS and beyond".
Description
Select what type of change this PR introduces:
Update Waspc ChangeLog and version if needed
If you did a bug fix, new feature, or breaking change, that affects
waspc, make sure you satisfy the following:ChangeLog.mdwith description of the change this PR introduces.waspcversion inwaspc.cabalto reflect changes I introduced, with regards to the version of the latest wasp release, if the bump was needed.Add a regression test if needed
If you did a bug fix, make sure you satisfy the following:
If you're unable to add a regression test, please explain why.
This likely indicates that our current testing setup needs improvement.
Update example apps if needed
If you did code changes and added a new feature, make sure you satisfy the following:
waspc/examples/todoAppand its e2e tests as needed and manually checked it works correctly.If you did code changes and updated an existing feature, make sure you satisfy the following:
waspc/examples/todoAppand its e2e tests as needed and manually checked it works correctly.Update starter apps if needed
If you did code changes and updated an existing feature, make sure you satisfy the following:
basicstarter as needed and manually checked it works correctly.todo-tsstarter as needed and manually checked it works correctly.embeddingsstarter as needed and manually checked it works correctly.saasstarter as needed and manually checked it works correctly.