/*
Theme Name: Amazing Life
Theme URI: https://wordpress.org/themes/twentytwentyfive/
Author: the WordPress team
Author URI: https://wordpress.org
Description: Twenty Twenty-Five emphasizes simplicity and adaptability. It offers flexible design options, supported by a variety of patterns for different page types, such as services and landing pages, making it ideal for building personal blogs, professional portfolios, online magazines, or business websites. Its templates cater to various blog styles, from text-focused to image-heavy layouts. Additionally, it supports international typography and diverse color palettes, ensuring accessibility and customization for users worldwide.
Requires at least: 6.7
Tested up to: 6.7
Requires PHP: 7.2
Version: 1.0.1
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Text Domain: twentytwentyfive
Tags: one-column, custom-colors, custom-menu, custom-logo, editor-style, featured-images, full-site-editing, block-patterns, rtl-language-support, sticky-post, threaded-comments, translation-ready, wide-blocks, block-styles, style-variations, accessibility-ready, blog, portfolio, news
*/

/* Shared five-site look (BUILD 745) ~ the family design system that makes
   amazingunfilteredlife.com match a2bdayz.com, anchorflare.com,
   amazingepiclife.com and amazinglifevault.com: the moving colors, the type
   scale, the card shell. SSOT lives in a2bdayz-empire-os at
   packages/anchor-look/anchor-look.css and is vendored here by
   sync-anchor-look.mjs ~ edit the SSOT, never this copy.

   @import must stay above every rule in this file (CSS requires it), and the
   AUL palette (book-cover colours) is applied via [data-brand="aul"] inside
   anchor-look.css plus the body class rule below. */
@import url('./anchor-look.css');

/* WordPress renders no data-brand attribute of its own, so the AUL brand block
   is also bound to the theme's body class here ~ one line, no PHP needed. */
body.wp-site-blocks,
body {
	--al-accent: #9b30b5;
	--al-accent-2: #16b8c9;
	--al-hero-wash:
		radial-gradient(ellipse 70% 50% at 50% -5%, rgba(155, 48, 181, 0.20) 0%, transparent 65%),
		radial-gradient(ellipse 45% 40% at 14% 20%, rgba(22, 184, 201, 0.12) 0%, transparent 60%),
		radial-gradient(ellipse 45% 45% at 86% 30%, rgba(238, 85, 34, 0.08) 0%, transparent 62%);
}

/* Teri 2026-07-30, her word: "new violet" ~ the primary button takes the
   anchor-look violet (accent-1 in theme.json moves #FFA500 -> #9b30b5).

   This rule exists because the button's TEXT colour cannot be fixed in
   theme.json: the live button markup carries `has-base-color` as a class baked
   into the WordPress DATABASE content, and that class wins over any theme.json
   elements.button setting. On the old orange, dark base text read 8.72:1; on
   the violet it would fall to 2.86:1 ~ below the 4.5:1 AA floor and a plain
   readability regression on her own "bright on dark" law. Repainting the
   background without repainting the label would have shipped an unreadable
   button that still technically satisfied "new violet".

   Scoped to buttons that actually carry the accent-1 background, so no other
   use of the base colour anywhere on the site is touched. Result: 5.29:1.

   `!important` is REQUIRED here and is not laziness: WordPress emits its preset
   colour utilities as `.has-base-color{color:var(--wp--preset--color--base)
   !important;}`. A plain rule loses to it no matter how specific, which is
   exactly what happened on the first attempt ~ the violet painted and the label
   stayed dark at 2.86:1. Matching !important is the only way to win against a
   generated !important utility. */
.wp-block-button__link.has-accent-1-background-color.has-base-color,
.wp-block-button__link.has-accent-1-background-color {
	color: var(--wp--preset--color--contrast, #F0F0F0) !important;
}

/*
 * Link styles
 * https://github.com/WordPress/gutenberg/issues/42319
 */
a {
	text-decoration-thickness: 1px !important;
	text-underline-offset: .1em;
}

/* Focus styles */
:where(.wp-site-blocks *:focus) {
	outline-width: 2px;
	outline-style: solid;
}

/* Increase the bottom margin on submenus, so that the outline is visible. */
.wp-block-navigation .wp-block-navigation-submenu .wp-block-navigation-item:not(:last-child) {
	margin-bottom: 3px;
}

/* Increase the outline offset on the parent menu items, so that the outline does not touch the text. */
.wp-block-navigation .wp-block-navigation-item .wp-block-navigation-item__content {
	outline-offset: 4px;
}

/* Remove outline offset from the submenus, otherwise the outline is visible outside the submenu container. */
.wp-block-navigation .wp-block-navigation-item ul.wp-block-navigation__submenu-container .wp-block-navigation-item__content {
	outline-offset: 0;
}

/*
 * Progressive enhancement to reduce widows and orphans
 * https://github.com/WordPress/gutenberg/issues/55190
 */
h1, h2, h3, h4, h5, h6, blockquote, caption, figcaption, p {
	text-wrap: pretty;
}

/*
 * Change the position of the more block on the front, by making it a block level element.
 * https://github.com/WordPress/gutenberg/issues/65934
*/
.more-link {
	display: block;
}