Privacy-first password manager with built-in email aliasing. Fully encrypted and self-hostable.
Update docs and UI (#2189)
Leendert de Borstaf20c7c63c22
diff --git a/docs/docs/contributing/index.md b/docs/docs/contributing/index.mdxsimilarity index 58%rename from docs/docs/contributing/index.mdrename to docs/docs/contributing/index.mdxindex 065dcdffa..f0ef76c93 100644--- a/docs/docs/contributing/index.md+++ b/docs/docs/contributing/index.mdx@@ -9,18 +9,24 @@ Thank you for your interest in contributing to AliasVault! There are many ways yHere are some common ways you can help the AliasVault project:-<div style="display: grid; grid-template-columns: repeat(auto-fit, minmax(250px, 1fr)); gap: 1rem; margin: 2rem 0;">- <div style="border: 2px solid #f49541; border-radius: 8px; padding: 1.5rem; background: linear-gradient(135deg, #f4954122 0%, #d6833822 100%);">- <h3 style="margin-top: 0; color: #f49541;">π Translate UI</h3>- <p>Help translate AliasVault's interface into your language using Crowdin.</p>- <a href="ui-translations" style="font-weight: bold;">Get Started β</a>- </div>-- <div style="border: 2px solid #d68338; border-radius: 8px; padding: 1.5rem; background: linear-gradient(135deg, #d6833822 0%, #b8702f22 100%);">- <h3 style="margin-top: 0; color: #d68338;">π€ Translate Identity Generator</h3>- <p>Provide name dictionaries to make the identity generator support your language.</p>- <a href="identity-generator" style="font-weight: bold;">Get Started β</a>- </div>+<div className="av-action-grid">+ <a className="av-action-card" href="./ui-translations">+ <div className="av-action-card__emoji">π</div>+ <div className="av-action-card__title">Translate UI</div>+ <p className="av-action-card__desc">+ Help translate AliasVault's interface into your language using Crowdin.+ </p>+ <span className="av-action-card__cta">Get Started</span>+ </a>++ <a className="av-action-card" href="./identity-generator">+ <div className="av-action-card__emoji">π€</div>+ <div className="av-action-card__title">Translate Identity Generator</div>+ <p className="av-action-card__desc">+ Provide name dictionaries to make the identity generator support your language.+ </p>+ <span className="av-action-card__cta">Get Started</span>+ </a></div>---diff --git a/docs/docs/installation/docker-compose/advanced/_category_.json b/docs/docs/installation/docker-compose/advanced/_category_.jsonindex fa338fd55..919568095 100644--- a/docs/docs/installation/docker-compose/advanced/_category_.json+++ b/docs/docs/installation/docker-compose/advanced/_category_.json@@ -1,4 +1,5 @@{"label": "Advanced",- "position": 2+ "position": 2,+ "link": null}diff --git a/docs/docs/installation/docker-compose/advanced/index.md b/docs/docs/installation/docker-compose/advanced/index.mddeleted file mode 100644index 3b5d1bd0d..000000000--- a/docs/docs/installation/docker-compose/advanced/index.md+++ /dev/null@@ -1,5 +0,0 @@-----sidebar_position: 2-----# Advanced Installation-The following guides provide more advanced installation options for AliasVault. These options are not required for the basic installation, but may be useful for advanced users.diff --git a/docs/docs/installation/docker-compose/index.md b/docs/docs/installation/docker-compose/index.mdindex c41d7e7e2..9658a96a9 100644--- a/docs/docs/installation/docker-compose/index.md+++ b/docs/docs/installation/docker-compose/index.md@@ -81,10 +81,10 @@ AliasVault includes a built-in email server that allows you to generate email al:::noteIf you skip this step, AliasVault will default to use public email domains offered by SpamOK. While this still works for creating aliases, it has privacy limitations. For complete privacy and control, we recommend setting up your own domain.-[Learn more about the differences between private and public email domains](../private-vs-public-email.md).+[Learn more about the differences between private and public email domains](../docs/private-vs-public-email).:::-### Requirements+### 3.1 Requirements- A **public IPv4 address** with ports 25 and 587 forwarded to your AliasVault server- Open ports **25** and **587** on your server firewall for email SMTP traffic (*NOTE: some residential IP's block this, check with your ISP*).@@ -100,7 +100,7 @@ telnet <your-server-public-ip> 25telnet <your-server-public-ip> 587```-### DNS configuration+### 3.2 DNS configurationChoose your configuration: primary domain vs subdomain. AliasVault can be configured under:- **A primary (top-level) domain**@@ -153,7 +153,7 @@ This keeps the email configuration of your primary domain (`example.com`) comple----### AliasVault server email domain configuration+### 3.3 AliasVault server email domain configurationAfter setting up your DNS, you have to configure AliasVault to let it know which email domains it should support. Update the `docker-compose.yml` file:```bash@@ -178,7 +178,7 @@ Important: DNS propagation can take up to 24-48 hours. During this time, email dIf you encounter any issues, feel free to join the [Discord chat](https://discord.gg/DsaXMTEtpF) to get help from other users and maintainers.-### Optional: SMTP advertised hostname+### 3.4 Optional: SMTP advertised hostnameWhen you expose SMTP (ports 25 and 587), remote clients see a **hostname** in the SMTP **banner** and **EHLO** responses. This value defaults to `aliasvault` which works fine for general email deliverability, but some diagnostic tools may check that this name is consistent with **reverse DNS (PTR)** with your email MX record.@@ -193,7 +193,7 @@ If you wish to set this value, update the `docker-compose.yml` file:Restart the container after changing this value.-### Optional: SMTP TLS (STARTTLS)+### 3.5 Optional: SMTP TLS (STARTTLS)By default, SMTP TLS is disabled (`SMTP_TLS_ENABLED: "false"`). This does NOT significantly impact email deliverability: most email providers will still deliver to your server. However, if you want to enable TLS for SMTP connections:diff --git a/docs/docs/installation/docker-compose/troubleshooting.md b/docs/docs/installation/docker-compose/troubleshooting.mdindex 10df2c28f..6de1365cf 100644--- a/docs/docs/installation/docker-compose/troubleshooting.md+++ b/docs/docs/installation/docker-compose/troubleshooting.md@@ -5,6 +5,7 @@ sidebar_label: "Troubleshooting"# TroubleshootingThis guide covers common issues and troubleshooting steps for AliasVault encountered during installation, updates or general maintenance.+---## Check Docker Container Statusdiff --git a/docs/docs/installation/private-vs-public-email.md b/docs/docs/installation/docs/private-vs-public-email.mdsimilarity index 100%rename from docs/docs/installation/private-vs-public-email.mdrename to docs/docs/installation/docs/private-vs-public-email.mddiff --git a/docs/docs/installation/index.md b/docs/docs/installation/index.mddeleted file mode 100644index 707dcecec..000000000--- a/docs/docs/installation/index.md+++ /dev/null@@ -1,105 +0,0 @@-----sidebar_position: 1-----# Self-host Install--AliasVault can be self-hosted on your own servers using two different installation methods. Both use Docker, but they differ in how much is automated versus how much you manage yourself.--## Which Installation Method to Choose?--### π **Option 1: Install Script**-The installer script is a **fully managed solution** that handles everything for you. Simply run it on a clean VM/LXC with Docker installed, and it will set up all required containers, configure SSL certificates and provide CLI helpers for easy updates and maintenance.--### π οΈ **Option 2: Docker Compose**-If you prefer manual setup and **have existing SSL infrastructure**, use the all-in-one Docker image via Docker Compose. It works with your existing SSL proxy (Traefik, HAProxy, Caddy, etc.) and gives you full control over the configuration. Note: because this install method does not include a CLI, future updates may require some manual migrations.--| | **Option 1: Install Script (multi-container)** | **Option 2: Docker Compose (single container)** |-|--------------------------|---------------------------------------------------|-----------------------------------------------|-| **Best for** | βοΈ VPS/VM/Proxmox, cloud hosts, DigitalOcean, AWS/Azure | π NAS/Synology/Unraid, Raspberry Pi, home servers |-| **Internet accessible** | Direct internet access with ports 80/443 | Behind existing infrastructure |-| **TLS/SSL** | Built-in reverse proxy + Let's Encrypt (automatic) | Bring your own (Traefik, Nginx, HAProxy, Caddy) |-| **Containers** | Multiple containers (client, api, postgres, task runner, smtp, admin, reverse proxy) | Single bundled container (all-in-one) |-| **Configuration** | Automatic docker-compose.yml setup | Standard Docker commands |-| **Updates** | `install.sh` assisted updates & migrations | `docker pull` (manual); occasional manual migrations |-| **Admin actions** | `install.sh` helpers for admin password reset | SSH into container for certain tasks (e.g. password reset) |-| **Setup style** | Managed, opinionated, production-ready defaults | Fits into existing homelab/stack tools (Portainer compatible) |-| **Build from source** | Supported | Pre-built container only |-| **Choose ifβ¦** | You want auto SSL and a managed stack | You already have TLS and prefer manual control |-| | [**Self-host via Install Script β**](./script) | [**Self-host via Docker β**](./docker-compose) |--### Quick Decision Guide--**Go with the Install Script if:**-- β You have a fresh VM or VPS dedicated to AliasVault-- β You want automatic SSL setup without hassle-- β You prefer managed updates and maintenance-- β You're new to Docker or want the simplest setup--**Go with Docker Compose if:**-- β You're already running other Docker containers on this host-- β You have existing SSL infrastructure (reverse proxy)-- β You want to integrate with your homelab tools (Portainer, etc.)-- β You prefer manual control over the configuration-------## Frequently Asked Questions--<details>-<summary>What's the difference between multi-container and single container?</summary>--| **Multi-container (Installer Script)** | **Single container (Manual Setup)** |-|----------------------------------------|-------------------------------------|-| Separates services into individual containers | All services bundled in one container |-| Easier to scale individual components | Simpler to manage with Docker commands |-| Uses docker-compose for orchestration | Lower resource overhead |-| Better for production deployments | Better for home labs and personal use |--</details>--<details>-<summary>Do I need to handle SSL/TLS certificates myself?</summary>--- **Installer Script**: No, it includes automatic Let's Encrypt certificates-- **Manual Setup**: Yes, you need your own reverse proxy for HTTPS--</details>--<details>-<summary>How do updates work?</summary>--| Method | Update Process |-|--------|---------------|-| **Installer Script** | Run `./install.sh update` for automated updates and migrations |-| **Manual Setup** | Use `docker pull` to get the latest image; manual migrations may be required |--</details>--<details>-<summary>Can I migrate between installation methods?</summary>--Yes! Both methods use the same bind mount directories (`/database`, `/certificates`, `/logs`, `/secrets`), making migration straightforward. Simply stop/uninstall via one method and follow the installation steps for the other - your data will be preserved.--</details>--<details>-<summary>What are the system requirements?</summary>--**Minimum requirements:**-- 64-bit Linux OS (Ubuntu or RHEL-based recommended)-- 1 vCPU, 1GB RAM, 16GB disk-- Docker CE (β₯ 20.10) and Docker Compose (β₯ 2.0)--**Network requirements:**-- Ports 80 and 443 available-- Optional: Ports 25 and 587 for private email domains--</details>--<details>-<summary>Can I build from source?</summary>--- **Installer Script**: Yes, optional build from source is supported-- **Manual Setup**: No, uses pre-built container images only--</details>diff --git a/docs/docs/installation/index.mdx b/docs/docs/installation/index.mdxnew file mode 100644index 000000000..4ca85af62--- /dev/null+++ b/docs/docs/installation/index.mdx@@ -0,0 +1,88 @@+---+sidebar_position: 1+hide_table_of_contents: true+---+# Self-host Install++AliasVault is self-hosted with Docker. There are two ways to install it β pick+based on **how much you want managed for you** versus how much you want to fit+into infrastructure you already run.++<div className="av-install-choice">+ <a className="av-install-card av-install-card--featured" href="./script">+ <div className="av-install-card__emoji">π</div>+ <div className="av-install-card__title">+ Install Script+ <span className="av-install-card__badge">Recommended</span>+ </div>+ <p className="av-install-card__tagline">+ A fully managed setup. One script spins up every container, gets HTTPS for+ you, and gives you CLI helpers for updates and maintenance.+ </p>+ <ul className="av-install-card__list">+ <li>Automatic HTTPS via Let's Encrypt</li>+ <li>Guided updates & migrations</li>+ <li>Production-ready defaults</li>+ </ul>+ <p className="av-install-card__tagline">+ <strong>Best for:</strong> a fresh VM or VPS dedicated to AliasVault.+ </p>+ <div className="av-install-card__cta">+ <span className="button button--primary button--lg">+ Install with the script β+ </span>+ </div>+ </a>++ <a className="av-install-card" href="./docker-compose">+ <div className="av-install-card__emoji">π οΈ</div>+ <div className="av-install-card__title">Docker Compose</div>+ <p className="av-install-card__tagline">+ A single all-in-one container you drop into your existing Docker stack.+ You bring your own reverse proxy and TLS, and keep full control.+ </p>+ <ul className="av-install-card__list">+ <li>Fits Portainer, Unraid, Synology & other homelab tools</li>+ <li>Bring your own TLS (Traefik, Nginx, HAProxy, Caddyβ¦)</li>+ <li>Updates via <code>docker pull</code> (occasional manual migrations)</li>+ </ul>+ <p className="av-install-card__tagline">+ <strong>Best for:</strong> a NAS or homelab that already runs a reverse proxy and/or other Docker containers.+ </p>+ <div className="av-install-card__cta">+ <span className="button button--secondary button--outline button--lg">+ Install with Docker β+ </span>+ </div>+ </a>+</div>++## Differences++The two methods install the same version AliasVault: they differ mainly in how TLS, updates, and the surrounding setup is handled.++| | π Install Script | π οΈ Docker Compose |+|------------------|---------------------------|------------------------------|+| **TLS/SSL** | Automatic (Let's Encrypt) | Bring your own reverse proxy |+| **Updates** | Guided via `install.sh` | Manual `docker pull` |+| **Containers** | Multiple (one per service)| Single all-in-one image |+| **Best for** | Dedicated VM / VPS | Existing homelab / NAS |+| **Build from source** | Supported | Pre-built image only |++:::tip+Not sure yet? You can switch later. Both methods use the same Docker bind-mount directories (/database, /certificates, /logs, /secrets), so migration is straightforward.+Stop or uninstall one method, then follow the installation steps for the other. Your data is preserved.+:::++## Frequently Asked Questions {#faq}++### What are the system requirements?+**Minimum:**+- 64-bit Linux OS (Ubuntu or RHEL-based recommended)+- 1 vCPU, 1 GB RAM, 16 GB disk+- Docker CE (β₯ 20.10) and Docker Compose (β₯ 2.0)++**Network:**+- Ports 80 and 443 available+- Optional: ports 25 and 587 for private email domains+diff --git a/docs/docs/installation/script/advanced/_category_.json b/docs/docs/installation/script/advanced/_category_.jsonindex c039890a0..40fd411b9 100644--- a/docs/docs/installation/script/advanced/_category_.json+++ b/docs/docs/installation/script/advanced/_category_.json@@ -1,4 +1,5 @@{"label": "Advanced",- "position": 4+ "position": 4,+ "link": null}diff --git a/docs/docs/installation/script/advanced/index.md b/docs/docs/installation/script/advanced/index.mddeleted file mode 100644index 9d074b751..000000000--- a/docs/docs/installation/script/advanced/index.md+++ /dev/null@@ -1,5 +0,0 @@-----sidebar_position: 4-----# Advanced Installation-The following guides provide more advanced installation options for AliasVault. These options are not required for the basic installation, but may be useful for advanced users.diff --git a/docs/docs/installation/script/index.md b/docs/docs/installation/script/index.mdindex 3d6b82e2f..40fc63618 100644--- a/docs/docs/installation/script/index.md+++ b/docs/docs/installation/script/index.md@@ -50,7 +50,7 @@ To generate a valid external TLS/SSL certificate for AliasVault, you can use Let- Port 80 and 443 on your server must be open and accessible from the internet- A registered domain name with an A record pointing to your server's public IP address (e.g. mydomain.com)-### Enable Let's Encrypt SSL+### 2.1 Enable Let's Encrypt SSL1. Run the install script with the `configure-ssl` option```bash@@ -58,7 +58,7 @@ To generate a valid external TLS/SSL certificate for AliasVault, you can use Let```2. Follow the prompts to configure Let's Encrypt.-### Reverting to self-signed TLS/SSL+### 2.2 Reverting to self-signed TLS/SSLIf at any point you would like to revert to the self-signed TLS/SSL certificate, run the install script again with the `configure-ssl` optionand then in the prompt choose option 2.@@ -69,10 +69,10 @@ and then in the prompt choose option 2.AliasVault includes a built-in email server that allows you to generate email aliases on-the-fly for every website you use, and receive + read the emails straight in AliasVault.:::note-If you skip this step, AliasVault will default to use public email domains offered by SpamOK. While this still works for creating aliases, it has privacy limitations. For complete privacy and control, we recommend setting up your own domain. [Learn more about the differences between private and public email domains](../private-vs-public-email.md).+If you skip this step, AliasVault will default to use public email domains offered by SpamOK. While this still works for creating aliases, it has privacy limitations. For complete privacy and control, we recommend setting up your own domain. [Learn more about the differences between private and public email domains](../docs/private-vs-public-email).:::-### Requirements+### 3.1 Requirements- A **public IPv4 address** with ports 25 and 587 forwarded to your AliasVault server- Open ports **25** and **587** on your server firewall for email SMTP traffic (*NOTE: some residential IP's block this, check with your ISP*).@@ -90,7 +90,7 @@ telnet <your-server-public-ip> 587If successful, you'll see a connection establishment message. Press Ctrl+C to exit the telnet session.-### DNS configuration+### 3.2 DNS configurationChoose your configuration: primary domain vs subdomain. AliasVault can be configured under:- **A primary (top-level) domain**@@ -143,7 +143,7 @@ This keeps the email configuration of your primary domain (`example.com`) comple----### AliasVault server email domain configuration+### 3.3 AliasVault server email domain configurationAfter setting up your DNS, continue with configuring AliasVault to let it know which email domains it should support.1. Run the email configuration script:@@ -167,7 +167,7 @@ Important: DNS propagation can take up to 24-48 hours. During this time, email dIf you encounter any issues, feel free to join the [Discord chat](https://discord.gg/DsaXMTEtpF) to get help from other users and maintainers.-### Optional: SMTP TLS (STARTTLS)+### 3.4 Optional: SMTP TLS (STARTTLS)By default, SMTP TLS is disabled. This does NOT significantly impact email deliverability: most email providers will still deliver to your server. However, if you want to enable TLS for SMTP connections:@@ -217,11 +217,11 @@ Disabling IP logging means the ability to monitor and track abusive users on you## 6. Troubleshooting-### Verbose output+### 6.1 Verbose outputIf you need more detailed output from the install script, you can run it with the `--verbose` option. This will print more information to the console.```bash./install.sh install --verbose```-### Troubleshooting guide+### 6.2 Troubleshooting guideFor more detailed troubleshooting information, please refer to the [troubleshooting guide](./troubleshooting.md).diff --git a/docs/docs/installation/script/troubleshooting.md b/docs/docs/installation/script/troubleshooting.mdindex 0bd5727ee..67098c690 100644--- a/docs/docs/installation/script/troubleshooting.md+++ b/docs/docs/installation/script/troubleshooting.md@@ -5,6 +5,7 @@ sidebar_label: "Troubleshooting"# TroubleshootingThis guide covers common issues and troubleshooting steps for AliasVault encountered during installation, updates or general maintenance.+---## Check Docker Container Statusdiff --git a/docs/docusaurus.config.ts b/docs/docusaurus.config.tsindex daa199897..b0c6ee312 100644--- a/docs/docusaurus.config.ts+++ b/docs/docusaurus.config.ts@@ -94,10 +94,13 @@ const config: Config = {'/installation/update/v0.23.0.html',],},- // private-vs-public-email moved from /misc into /installation.+ // private-vs-public-email moved from /misc into /installation, then+ // again under the /installation/docs/ category.{- to: '/installation/private-vs-public-email',+ to: '/installation/docs/private-vs-public-email',from: [+ '/installation/private-vs-public-email',+ '/installation/private-vs-public-email.html','/misc/private-vs-public-email','/misc/private-vs-public-email.html',],diff --git a/docs/sidebars.ts b/docs/sidebars.tsindex e3117a9dc..a115647bb 100644--- a/docs/sidebars.ts+++ b/docs/sidebars.ts@@ -37,7 +37,11 @@ const sidebars: SidebarsConfig = {},],},- 'installation/private-vs-public-email',+ {+ type: 'category',+ label: 'Docs',+ items: ['installation/docs/private-vs-public-email'],+ },{type: 'category',label: 'Browser Extensions',diff --git a/docs/src/css/custom.css b/docs/src/css/custom.cssindex 0f0a21f9f..dab1c01af 100644--- a/docs/src/css/custom.css+++ b/docs/src/css/custom.css@@ -217,6 +217,17 @@ article:not(:has(> nav.theme-doc-breadcrumbs)) > .theme-doc-markdown {font-weight: 600;}+/* --------------------------------------------- Self-host Install layout -- */++/* The install-method chooser page (/installation) hides its on-page ToC via+ * `hide_table_of_contents` frontmatter so the two side-by-side method cards get+ * the full width. Docusaurus then renders the content at full column width, but+ * our default 860px reading cap would still pinch it β so widen the reading+ * column for just this page (scoped via the route class on <html>). */+html[class*='docs-doc-id-installation/index'] .theme-doc-markdown {+ max-width: 1100px;+}+/* ----------------------------------------------------------------- Cards -- */.card {@@ -224,6 +235,210 @@ article:not(:has(> nav.theme-doc-breadcrumbs)) > .theme-doc-markdown {border: 1px solid var(--av-border);}+/* ------------------------------------------------ Install-method chooser -- */++/* Two side-by-side "pick a path" cards at the top of the install guide.+ * Collapses to a single column on narrow screens. */+.av-install-choice {+ display: grid;+ grid-template-columns: repeat(2, 1fr);+ gap: 1.25rem;+ margin: 2rem 0 1rem;+}++@media (max-width: 768px) {+ .av-install-choice {+ grid-template-columns: 1fr;+ }+}++/* Each card is a self-contained panel with the body and the CTA pinned to the+ * bottom, so both cards line up regardless of copy length. */+/* The whole card is an <a>, so reset link styling and let the body text read+ * normally. */+.av-install-card {+ display: flex;+ flex-direction: column;+ padding: 1.75rem;+ border: 1px solid var(--av-border);+ border-radius: 14px;+ background: var(--av-card-bg);+ color: var(--ifm-color-content);+ text-decoration: none;+ transition: transform 0.15s ease, border-color 0.15s ease,+ box-shadow 0.15s ease;+}++.av-install-card:hover {+ transform: translateY(-3px);+ border-color: var(--ifm-color-primary);+ box-shadow: 0 5px 24px rgba(244, 149, 65, 0.12);+ color: var(--ifm-color-content);+ text-decoration: none;+}++/* The recommended option gets a subtle primary-tinted border to draw the eye. */+.av-install-card--featured {+ border-color: var(--ifm-color-primary);+ box-shadow: 0 5px 24px rgba(244, 149, 65, 0.12);+}++.av-install-card__emoji {+ font-size: 2rem;+ line-height: 1;+ margin-bottom: 0.85rem;+}++.av-install-card__title {+ display: flex;+ align-items: center;+ gap: 0.6rem;+ font-size: 1.25rem;+ font-weight: 700;+ margin: 0 0 0.6rem;+}++.av-install-card__badge {+ font-size: 0.68rem;+ font-weight: 700;+ text-transform: uppercase;+ letter-spacing: 0.04em;+ color: var(--ifm-color-primary);+ background: rgba(244, 149, 65, 0.12);+ border-radius: 9999px;+ padding: 0.2rem 0.6rem;+}++.av-install-card__tagline {+ color: var(--ifm-color-content-secondary);+ margin-bottom: 1.1rem;+}++.av-install-card__list {+ list-style: none;+ padding: 0;+ margin: 0 0 1.5rem;+}++.av-install-card__list li {+ position: relative;+ padding-left: 1.6rem;+ margin-bottom: 0.55rem;+ line-height: 1.45;+}++.av-install-card__list li::before {+ content: 'β';+ position: absolute;+ left: 0;+ top: 0;+ color: var(--ifm-color-primary);+ font-weight: 700;+}++/* Push the CTA to the bottom edge so both cards' buttons align. */+.av-install-card__cta {+ margin-top: auto;+}++/* inline-flex + centering keeps the label optically centered in the pill. */+.av-install-card__cta .button {+ width: 100%;+ display: inline-flex;+ align-items: center;+ justify-content: center;+}++/* The markdown link text gets wrapped in a <p>, whose default bottom margin+ * sits inside the pill and pushes the label toward the top. Zero it so the+ * text is truly centered. */+.av-install-card__cta .button p {+ margin: 0;+}++/* The CTA pill is a <span>, not the link itself, so its :hover never fires β+ * the whole card is the anchor. Drive the pill's hover look from the card so it+ * still reacts when you point anywhere on the card. */+.av-install-card:hover .button--primary {+ background-color: var(--ifm-color-primary-dark);+}++.av-install-card:hover .button--secondary.button--outline {+ border-color: var(--ifm-color-primary);+ color: var(--ifm-color-primary);+}++/* ------------------------------------------------ Clickable action cards -- */++/* A responsive grid of "pick a task" cards where the *entire* card is one+ * clickable link (used on the Contributing page). Collapses to one column on+ * narrow screens. */+.av-action-grid {+ display: grid;+ grid-template-columns: repeat(auto-fit, minmax(260px, 1fr));+ gap: 1.25rem;+ margin: 2rem 0 1rem;+}++/* The whole card is an <a>. Reset link styling so the body text reads normally,+ * and lift + tint the border on hover to signal it's clickable. */+.av-action-card {+ display: flex;+ flex-direction: column;+ padding: 1.5rem;+ border: 1px solid var(--av-border);+ border-radius: 14px;+ background: var(--av-card-bg);+ color: var(--ifm-color-content);+ text-decoration: none;+ transition: transform 0.15s ease, border-color 0.15s ease,+ box-shadow 0.15s ease;+}++.av-action-card:hover {+ transform: translateY(-3px);+ border-color: var(--ifm-color-primary);+ box-shadow: 0 5px 24px rgba(244, 149, 65, 0.12);+ color: var(--ifm-color-content);+ text-decoration: none;+}++.av-action-card__emoji {+ font-size: 1.85rem;+ line-height: 1;+ margin-bottom: 0.85rem;+}++.av-action-card__title {+ font-size: 1.2rem;+ font-weight: 700;+ margin: 0 0 0.5rem;+ color: var(--ifm-heading-color);+}++.av-action-card__desc {+ color: var(--ifm-color-content-secondary);+ margin: 0 0 1.25rem;+ line-height: 1.5;+}++/* The CTA is pinned to the bottom so cards with different copy lengths line up.+ * The arrow nudges right on hover for a little affordance. */+.av-action-card__cta {+ margin-top: auto;+ font-weight: 600;+ color: var(--ifm-color-primary);+}++.av-action-card__cta::after {+ content: ' β';+ transition: margin-left 0.15s ease;+}++.av-action-card:hover .av-action-card__cta::after {+ margin-left: 0.25rem;+}+/* ----------------------------------------------------- Collapsibles / FAQ -- *//* Native <details> styled like the marketing FAQ accordion: a bordered card