/*
Theme Name: Blocksy Child (BASIC-256)
Theme URI: https://github.com/uglymike17/basic256
Description: Child theme of Blocksy for the BASIC-256 project website. Provides a custom, self-contained front page based on the approved mockup.
Author: MyBasic256
Template: blocksy
Version: 1.29.3
Text Domain: blocksy-child
*/

/* Landing-page styles live in assets/css/landing.css and are enqueued only on the front page. */

/* =========================================================================
   Blocksy design tokens.

   Blocksy reads its colours from CSS variables that it normally compiles from
   the Customizer into wp-content/uploads/blocksy/css/global.css — a file that
   lives in the database's shadow, not in this repository. A site built from
   this theme alone therefore has none of them, and the difference is not
   subtle: Blocksy paints headings with

       h1 { color: var(--theme-heading-color,
                   var(--theme-heading-1-color,
                   var(--theme-headings-color))) }

   and with all three undefined that computes to `unset`, so every heading the
   theme does not colour explicitly falls back to inheriting `.b256`'s dark
   body colour — dark navy headings on the black hero, invisible in practice.

   Declaring the tokens here makes the theme self-sufficient: the same files
   render the same site on any install, with nothing to configure in wp-admin.
   The values are the ones the Customizer was set to on the build machine.

   Scoped to .b256 (the body class, passed to body_class() in
   template-parts/site-header.php) rather than :root deliberately. Blocksy's bundle loads *after* this stylesheet, so a
   :root block here could be outbid by one there; a body class outranks :root
   whatever the order, and every page of this site carries it.

   Consequence worth knowing: this makes Appearance → Customize → Colors inert.
   Change colours here, not there.
   ========================================================================= */
.b256 {
	/* Palette, in Blocksy's numbering. */
	--theme-palette-color-1: #39A751;
	--theme-palette-color-2: #2f9946;
	--theme-palette-color-3: #d2d7dc;
	--theme-palette-color-4: #ffffff;
	--theme-palette-color-5: #1e2b1a;
	--theme-palette-color-6: #0e0e0e;
	--theme-palette-color-7: #161d15;
	--theme-palette-color-8: #000000;

	/* The one that actually bites: headings default to white, because the
	   design puts most of them on dark bands. Sections on a light background
	   override it themselves in landing.css and friends. */
	--theme-headings-color: var(--theme-palette-color-4);

	--theme-text-color: var(--theme-palette-color-3);
	--theme-link-initial-color: var(--theme-palette-color-1);
	--theme-link-hover-color: var(--theme-palette-color-2);
	--theme-border-color: var(--theme-palette-color-7);
	--theme-selection-text-color: #ffffff;
	--theme-selection-background-color: var(--theme-palette-color-1);

	/* Fluent Forms draws the contact form with these. Without them the fields
	   come out as Blocksy's light defaults on a dark page. */
	--theme-form-field-background-initial-color: rgba(0, 0, 0, 0.3);
	--theme-form-field-background-focus-color: rgba(0, 0, 0, 0.3);
	--theme-form-field-border-initial-color: var(--theme-border-color);
	--theme-form-field-border-focus-color: var(--theme-palette-color-1);
	--theme-form-field-border-width: 2px;
	--theme-form-field-border-radius: 10px;
	--theme-form-field-height: 45px;

	--theme-button-text-initial-color: #ffffff;
	--theme-button-text-hover-color: #ffffff;
	--theme-button-background-initial-color: var(--theme-palette-color-1);
	--theme-button-background-hover-color: var(--theme-palette-color-2);
	--theme-button-border-radius: 7px;
}
