[{"data":1,"prerenderedAt":239},["ShallowReactive",2],{"page:\u002Fdocumentation\u002F":3},{"id":4,"title":5,"body":6,"dateModified":224,"datePublished":224,"description":225,"extension":226,"heroAlt":227,"heroImage":228,"layout":229,"meta":230,"navigation":231,"ogDescription":232,"ogImage":228,"ogTitle":233,"path":234,"schema":235,"seo":236,"stem":237,"__hash__":238},"content\u002Fdocumentation.md","Documentation",{"type":7,"value":8,"toc":211},"minimark",[9,13,18,21,24,27,31,40,43,46,49,53,56,64,72,80,88,92,100,103,106,109,113,116,119,122,125,129,132,139,142,145,149,152,198,201,205,208],[10,11,12],"p",{},"This page is the Blaskan documentation handbook. It covers the full path from a fresh theme install to a configured, tested site. The search intent here spans several starting points: first-time setup, specific customization questions, responsive layout troubleshooting, accessibility review, and theme unit testing. This documentation is written from direct experience building and configuring blog-focused WordPress themes over more than ten years of production use. Rather than a feature index, the organization follows what you are likely to be doing at each stage of working with the theme. The sections below map to five paths: setup, customization, responsiveness, accessibility, and unit testing. Each path has a dedicated article linked from this page, and each article is self-contained.",[14,15,17],"h2",{"id":16},"how-the-documentation-is-organized","How the Documentation Is Organized",[10,19,20],{},"Most WordPress theme documentation is organized around features. You get a list of what the theme has and where to find each option in the Customizer. That structure is fast to produce and slow to use. You often know what you need to accomplish but not what the theme calls the relevant setting.",[10,22,23],{},"Blaskan's documentation is organized around tasks and decisions. The assumption is that you are moving through a process: installing the theme, making layout and navigation decisions, configuring the sidebar, checking responsive behavior across devices, verifying accessibility, and testing against the full WordPress content set. Each stage in that process has its own documentation page.",[10,25,26],{},"This handbook page is the entry point. If you are starting fresh, work through the sections in order. If you are returning to address a specific question, go directly to the relevant section and follow the link to the dedicated article.",[14,28,30],{"id":29},"setup-path","Setup Path",[10,32,33,34,39],{},"Before you can configure anything, the theme needs to be installed and activated. The ",[35,36,38],"a",{"href":37},"\u002Fdocumentation\u002Fgetting-started\u002F","getting started guide"," covers the complete setup sequence: downloading Blaskan from the WordPress theme directory, installing it through the WordPress admin, activating it, and completing the initial configuration steps that have an immediate effect on what visitors see.",[10,41,42],{},"Those initial steps include assigning a menu to the primary navigation location, adding widgets to the sidebar, and verifying that the site title or logo appears correctly in the header. Each of these requires action in the WordPress admin that goes beyond clicking Activate.",[10,44,45],{},"A common setup mistake is skipping the menu assignment step. Blaskan registers a primary navigation location in the header. WordPress does not automatically populate it with a menu. If you have not gone to Appearance > Menus or the Customizer navigation section and assigned a menu to the primary location, the header navigation area will appear empty. This is expected behavior, not a bug. The getting started guide walks through this explicitly so you do not spend time troubleshooting it.",[10,47,48],{},"The guide also identifies a small number of plugins that improve the Blaskan experience for specific site types. The theme works without plugins. The plugin notes in the getting started guide explain what each one adds and why it is optional rather than required.",[14,50,52],{"id":51},"customization-path","Customization Path",[10,54,55],{},"Once the theme is running, most visual configuration happens through the WordPress Customizer. Blaskan exposes its core options there: logo upload, header layout, color settings, and widget area management. The Customizer preview updates live as you make changes, which makes it straightforward to assess the effect of a configuration decision before saving it.",[10,57,58,59,63],{},"Navigation setup and drop-down behavior are covered in the ",[35,60,62],{"href":61},"\u002Fdocumentation\u002Fmenus-and-interaction\u002F","menus and interaction documentation",". This guide explains how to configure the primary navigation menu, what the supported menu depth is, how drop-down behavior works at desktop widths, and what the mobile menu pattern looks like for keyboard and touch users. If you are building a menu with submenus, the interaction guide covers the expected behavior and the practical limits.",[10,65,66,67,71],{},"The ",[35,68,70],{"href":69},"\u002Fdocumentation\u002Fsidebar-balance-and-widget-density\u002F","sidebar balance and widget density guide"," covers the sidebar widget area in depth. The sidebar is a significant part of the Blaskan layout. How many widgets you place in it, and what types of content they display, affects the visual balance of every page on the site. Adding too many widgets creates a visually dense sidebar that competes with the content column. The guide covers which widget types work well and explains the density tradeoffs clearly.",[10,73,74,75,79],{},"Archive layout is addressed in the ",[35,76,78],{"href":77},"\u002Fdocumentation\u002Ffeatured-images-excerpts-and-archive-rhythm\u002F","featured images, excerpts, and archive rhythm documentation",". Post cards in the archive are affected by whether featured images are present, how long excerpts run, and whether image dimensions are consistent across posts. This guide addresses each of those variables and provides recommendations for maintaining a consistent archive layout when content varies.",[10,81,82,83,87],{},"For deeper modifications, the ",[35,84,86],{"href":85},"\u002Fdocumentation\u002Fchild-theme-basics\u002F","child theme basics guide"," covers how to set up a child theme that inherits from Blaskan, which types of changes belong in a child theme rather than the Customizer, and the standard patterns for overriding template files without editing the parent theme directly. Any modification that survives a theme update needs to be in a child theme.",[14,89,91],{"id":90},"responsiveness-path","Responsiveness Path",[10,93,94,95,99],{},"Blaskan handles responsive behavior through CSS media queries applied at specific breakpoints. There is no JavaScript-driven layout switching and no separate mobile theme file. The ",[35,96,98],{"href":97},"\u002Fdocumentation\u002Fresponsive-breakpoints-and-layout-logic\u002F","responsive breakpoints and layout logic documentation"," maps the full breakpoint structure and explains what layout changes occur at each point.",[10,101,102],{},"This guide is most useful when you are adding custom CSS and need to integrate with the theme's existing breakpoint structure. Adding responsive rules without knowing the existing breakpoints leads to conflicts. The documentation identifies each breakpoint, what layout change it triggers, and which CSS properties are affected at that width.",[10,104,105],{},"The responsiveness guide also covers the relationship between featured image dimensions and content column width at different viewport sizes. Featured images that are significantly wider or narrower than the content column create visual tension at specific breakpoints. The guide provides dimension recommendations for the most common use cases.",[10,107,108],{},"If you are making layout modifications in a child theme, the responsiveness documentation explains which layout properties are breakpoint-sensitive and which apply uniformly across all widths. This distinction matters when overriding layout styles.",[14,110,112],{"id":111},"accessibility-path","Accessibility Path",[10,114,115],{},"Blaskan treats accessibility as a foundational requirement built into the template structure, not a feature layered on afterward. The accessibility documentation covers what the theme does by default across the full range of accessibility concerns: DOM reading order, keyboard navigation, focus states, color contrast, line length, spacing, heading hierarchy, and link styles.",[10,117,118],{},"Reading order and heading structure are closely related. A heading hierarchy that makes visual sense also needs to make sense in the order the DOM presents it to screen readers and keyboard navigators. Blaskan's templates enforce a consistent heading hierarchy. The accessibility documentation explains what that hierarchy is and what to watch for when post content or custom templates disrupt it.",[10,120,121],{},"Focus states are visible on all interactive elements by default. The documentation describes how the default focus styles are implemented and identifies common ways that custom CSS can unintentionally suppress focus visibility. If you are auditing a Blaskan-based site for accessibility compliance, the focus state section gives you the specific checklist items to verify.",[10,123,124],{},"The accessibility documentation also covers color contrast ratios in the default palette, the line length characteristics of the content column, and what spacing choices contribute to readable page structure.",[14,126,128],{"id":127},"unit-test-path","Unit Test Path",[10,130,131],{},"The WordPress theme unit test content set is the most thorough way to verify that Blaskan handles the full range of content types it will encounter on a real site. The unit test data covers headings at all six levels, ordered and unordered lists, nested lists, blockquotes, inline elements, tables, images at various sizes, captions, galleries, audio embeds, video embeds, and code blocks.",[10,133,66,134,138],{},[35,135,137],{"href":136},"\u002Fdocumentation\u002Ftheme-unit-test-checklist\u002F","theme unit test checklist"," walks through each category of the unit test content and describes what correct rendering looks like for Blaskan. It also documents the common failure patterns: images that overflow their containers, blockquotes that lose their indent, code blocks that wrap instead of scrolling, and tables that break the content column width.",[10,140,141],{},"Running the unit test after any child theme modification is a practical habit. Template overrides can introduce regressions in content types that were not directly modified. The checklist provides a structured way to catch those regressions before they appear on a live site.",[10,143,144],{},"The unit test content set is maintained by the WordPress theme review team and can be imported into any WordPress installation using the standard XML import tool under Tools > Import.",[14,146,148],{"id":147},"documentation-index","Documentation Index",[10,150,151],{},"These are all the dedicated Blaskan documentation articles:",[153,154,155,162,168,174,180,186,192],"ul",{},[156,157,158,161],"li",{},[35,159,160],{"href":37},"Getting Started",": Installation, activation, and initial configuration including menu assignment and widget setup.",[156,163,164,167],{},[35,165,166],{"href":61},"Menus and Interaction",": Primary navigation configuration, drop-down behavior, mobile menu patterns, and keyboard interaction.",[156,169,170,173],{},[35,171,172],{"href":69},"Sidebar Balance and Widget Density",": Sidebar widget area setup, widget selection guidance, and maintaining visual balance.",[156,175,176,179],{},[35,177,178],{"href":77},"Featured Images, Excerpts, and Archive Rhythm",": Post card structure in archive views and how featured image handling affects the archive layout.",[156,181,182,185],{},[35,183,184],{"href":85},"Child Theme Basics",": Setting up a child theme and making durable modifications to the parent theme structure.",[156,187,188,191],{},[35,189,190],{"href":97},"Responsive Breakpoints and Layout Logic",": The full breakpoint structure and what layout changes occur at each breakpoint.",[156,193,194,197],{},[35,195,196],{"href":136},"Theme Unit Test Checklist",": Full unit test verification with pass criteria for each content type.",[10,199,200],{},"Each article covers its specific topic fully. They can be read in order as a complete handbook or used individually as reference documents when a specific question comes up.",[14,202,204],{"id":203},"a-note-on-versions","A Note on Versions",[10,206,207],{},"This documentation covers the current version of Blaskan. If you are running an older version, some option locations and default values may differ from what is described here. Updating to the current version before following this documentation will prevent most version-related discrepancies.",[10,209,210],{},"Blaskan is open source. If a specific configuration question is not addressed in the documentation, the theme source code is the authoritative reference. The template files are straightforward PHP and HTML with no build tool required to read them.",{"title":212,"searchDepth":213,"depth":214,"links":215},"",2,3,[216,217,218,219,220,221,222,223],{"id":16,"depth":213,"text":17},{"id":29,"depth":213,"text":30},{"id":51,"depth":213,"text":52},{"id":90,"depth":213,"text":91},{"id":111,"depth":213,"text":112},{"id":127,"depth":213,"text":128},{"id":147,"depth":213,"text":148},{"id":203,"depth":213,"text":204},null,"Blaskan WordPress theme documentation covering setup, customization, responsive behavior, accessibility, and unit testing. A practical handbook for getting the most from the theme.","md","Blaskan documentation overview showing the theme handbook structure","\u002Fimages\u002Fhero\u002Fdocumentation-1600x900.jpg","default",{"heroLabel":5},true,"Blaskan WordPress theme documentation covering setup, customization, responsive behavior, accessibility, and unit testing.","Blaskan Documentation","\u002Fdocumentation","collection",{"title":5,"description":225},"documentation","jTsLubJJxd2jU9f2-4whV_WSuih8-zt5QOhptunEOn4",1775942364836]