Skip to content

Commit

Permalink
chore: make headings on the homepage link to the relevant sections (#115
Browse files Browse the repository at this point in the history
)

Felt wrong to not have the section headings link to the sections.
Fixed in this PR.

Signed-off-by: Xe Iaso <[email protected]>
  • Loading branch information
Xe authored Oct 4, 2024
1 parent 42d7454 commit 03dcf8f
Showing 1 changed file with 21 additions and 7 deletions.
28 changes: 21 additions & 7 deletions src/content/docs/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -36,36 +36,50 @@ import "/src/styles/docs/index.scss";

<CardGrid>
<Block>
<h4>Signup form protection</h4>
<a href="/signup-protection/concepts">
<h4>Signup form protection</h4>
</a>
Combine rate limiting, bot protection, and email validation to [protect your
signup forms from abuse](/signup-protection/concepts).
</Block>
<Block>
<h4>Rate limiting</h4>
<a href="/rate-limiting/concepts">
<h4>Rate limiting</h4>
</a>
[Set up rate limits](/rate-limiting/concepts) to prevent abuse of your
application.
</Block>
<Block>
<h4>Bot protection</h4>
<a href="/bot-protection/concepts">
<h4>Bot protection</h4>
</a>
[Manage traffic](/bot-protection/concepts) from automated clients and bots.
</Block>
<Block>
<h4>Email validation</h4>
<a href="/email-validation/concepts">
<h4>Email validation</h4>
</a>
[Validate & verify](/email-validation/concepts) email addresses to prevent
signup spam.
</Block>
<Block>
<h4>Shield</h4>
<a href="/shield/concepts">
<h4>Shield</h4>
</a>
Protect your application from common attacks using [Arcjet
Shield](/shield/concepts).
</Block>
<Block>
<h4>Sensitive information</h4>
<a href="/sensitive-info/concepts">
<h4>Sensitive information</h4>
</a>
[Protects against](/sensitive-info/concepts) clients sending you PII that
you do not wish to handle.
</Block>
<Block>
<h4>Architecture</h4>
<a href="/architecture">
<h4>Architecture</h4>
</a>
Learn about [how Arcjet works](/architecture).
</Block>
</CardGrid>

0 comments on commit 03dcf8f

Please sign in to comment.