About
About Blaskan: a theme-focused editorial resource for WordPress blogging layouts, typography decisions, accessibility practices, and practical customization guidance.

Blaskan is a WordPress blogging theme focused on readable layouts and practical content structure. This site exists as the central resource for the theme: documentation, a live demo environment, a pattern library, accessibility guidance, and editorial notes about what makes reading-focused WordPress themes work well over time.
The content here is written for people who use WordPress to run text-forward blogs, whether that means a personal writing site, a focused publication, a documentation resource, or any context where how the content reads matters more than visual spectacle.
What This Site Covers
The theme guide explains what kind of theme Blaskan is, what readers notice first about it, and how to evaluate whether the layout style fits a particular content type. This is the place to start if you are deciding whether Blaskan suits your site.
The documentation section is a practical handbook. Setup, menus, sidebars, featured images, responsive behavior, child theme basics, and the unit test checklist. Organized as reference material rather than a blog, so you can find what you need without reading sequentially.
The demo gives a guided walkthrough of the theme in a real content context. The live preview at demo.blaskan.net shows the theme applied to representative blog content with no staging caveats. The demo guide on this site explains each section of the preview environment in more detail.
The pattern bench documents recurring layout decisions: archive rhythm, excerpt handling, category label density, sidebar balance, and multi-column behavior. These are the structural choices that most theme documentation either skips or buries in a list of options without explaining the reasoning.
The accessibility section covers reading order, keyboard navigation, focus states, color contrast, line length, and heading structure. Not a compliance checklist. A practical explanation of how these properties affect the actual reading experience.
The journal collects longer-form observations about theme design: why some blog layouts age well and others do not, what makes a reading theme feel light, what a content-heavy site tests a theme on that a demo never does. These pieces are written when the thinking is clear enough to be useful, not on any particular schedule.
The Theme Itself
Blaskan is a responsive WordPress blogging theme built for clarity. The layout is a conventional single content column with an optional sidebar. The typography uses a serif for display headings and a refined sans for body text. The spacing is deliberate and generous. There are no hero sections, no card grid homepages, no full-screen overlays. The design gets out of the way.
The original theme was designed for blogs where writing is the point. That premise still holds. Most WordPress themes are now built with visual builders, startup aesthetics, and multipurpose flexibility as the primary design goals. Blaskan is not built for those use cases. It is built for people who want their content to read well, and who want the theme to stay out of the way of that.
The theme has been maintained over time with documentation improvements, accessibility refinements, and occasional compatibility updates. The changelog tracks these changes.
What This Site Is Not
This is not a theme marketplace. There are no download buttons, affiliate links, or upsell CTAs.
This is not a WordPress news site. There are no roundups, trend pieces, or release coverage.
This is not a generic web development resource. The content here stays within the specific subject of the Blaskan theme and the design decisions that surround it.
The scope is narrow deliberately. A focused resource for a specific theme is more useful than a broad site trying to be relevant to every WordPress user.
Contact
Use the contact page for theme-related questions that are not covered in the documentation or FAQ.
For support issues, start with the support page which covers the most common troubleshooting paths. The FAQ handles many specific questions directly. Reading those before sending a message usually resolves the issue faster.