You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+31-36Lines changed: 31 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,64 +1,59 @@
1
1
# magiclinksdev
2
2
3
-
You can find the documentation for this project on the [docs site](https://docs.magiclinks.dev). This site contains
4
-
resources for implementing a client and self-hosting the project.
5
-
6
-
You can find the SaaS landing page at [https://magiclinks.dev](https://magiclinks.dev). Use of the SaaS platform is not
7
-
required, but it's very inexpensive and may be cheaper than deploying yourself.
8
-
9
-
# Getting started
10
-
11
-
The **magiclinksdev** project is an authentication service that uses magic links to authenticate users. A typical use
12
-
case would involve sending a magic link to a user via email. After the user clicks the link, a new authenticated session
13
-
is created for that user. Sometimes **magiclinksdev** is abbreviated as "mld".
14
-
15
-
## About
16
-
17
-
This project is a magic link authentication service. It serves use cases like:
3
+
The **magiclinksdev** project is an authentication service for magic link and One-Time Password (OTP) use cases. There
4
+
is built-in email support through Amazon SES and SendGrid.
18
5
6
+
Use cases include:
19
7
* Sign up
20
8
* Log in
21
9
* Password resets
22
10
* Email verification
23
11
* And more authentication use cases
24
12
25
-
It can be used to supplement password authentication or replace it entirely.
13
+
This project can be used to supplement password authentication or replace it entirely.
14
+
15
+
If your project has an alternate secure means of communication, you can use generate magic links and OTPs without
16
+
sending emails. An example would be mobile push notifications.
26
17
27
-
A typical use case involves sending a magic link to a user via email. After the user clicks the link, a new
28
-
authenticated session is created for that user.
18
+
## Getting started
19
+
20
+
To get started implementing a client application that uses **magiclinksdev** for authentication, the recommended path
21
+
is:
22
+
1. Do the [quickstart](https://docs.magiclinks.dev/self-host-quickstart)
23
+
2. Find a [pre-built SDK](https://docs.magiclinks.dev/client-sdk) or [generate one from the formatted API specification](https://docs.magiclinks.dev/client-api-specification#generate-code)
24
+
3. Choose the [magic link](https://docs.magiclinks.dev/client-magic-link-workflow) or [OTP](https://docs.magiclinks.dev/client-otp-workflow) workflow
25
+
4. Review the [implementation tips](https://docs.magiclinks.dev/client-implementation-tips) for recommendations and best practices
29
26
30
27
## Screenshots
31
28
32
-
The built-in email template is populated on a per-request basis. It adapts to the device's theme automatically. This
33
-
template was built using [maizzle](https://maizzle.com/).
29
+
The built-in email templates are friendly to mobile and desktop screens. They also adapt to light/dark mode
30
+
automatically. The templates are built using [maizzle](https://maizzle.com/).
The **magiclinksdev** project is open-source and can be self-hosted. Check out the [**Quickstart**](https://docs.magiclinks.dev/self-host-quickstart) page
50
+
to get started in minutes. For reference on configuring your self-hosted instance, check out the
0 commit comments