-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Lucia blog post #2237
Add Lucia blog post #2237
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! just a few requested changes.
web/blog/2024-08-13-how-to-add-auth-with-lucia-to-your-react-nextjs-app.md
Outdated
Show resolved
Hide resolved
web/blog/2024-08-13-how-to-add-auth-with-lucia-to-your-react-nextjs-app.md
Show resolved
Hide resolved
web/blog/2024-08-13-how-to-add-auth-with-lucia-to-your-react-nextjs-app.md
Outdated
Show resolved
Hide resolved
web/blog/2024-08-13-how-to-add-auth-with-lucia-to-your-react-nextjs-app.md
Outdated
Show resolved
Hide resolved
web/blog/2024-08-13-how-to-add-auth-with-lucia-to-your-react-nextjs-app.md
Outdated
Show resolved
Hide resolved
|
||
--- | ||
|
||
## Looking for more? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember @matijaSos saying that we can remove the more generic "follow us"/"star us" CTAs from our own blog, but leave them for Dev.to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd keep the cta, but we need to agree on whether we want to ask people to subscribe to our newsletter, or to star us on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok. Just make sure to change the CTA format, i.e. remove the Dev.to specific { % cta ... % }
syntax.
And between asking for newsletter signups or stars, I'm not really sure. Our goal has always been stars, so stick with stars? What do you think @mmaksimovic @matijaSos?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Emotional blackmailing I did 😄
I think from the marketing perspective - we need more people on our email list, that's the only thing we really own.
Other than that, stars are a nice vanity metric, that might get others to get interested in our project. So... let's try this for some time?
Or stick with just one.... I know 2 are a lot, but if they don't want to leave their email, starring us is easy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. I like it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. I like the updated intro, too.
Wasp will handle the rest, also updating UI components and ensuring a smooth and secure authentication flow. | ||
|
||
```tsx | ||
//main.wasp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mmaksimovic @vincanger I noticed that the Wasp file is not highlighted correctly since tsx
is used and we are using a comment to provide a title.
We have support for highlighting Wasp files and there is a nicer way to provide a title:
```wasp title="main.wasp
// stuff
Description
Add Lucia blog post