Skip to content

Releases

Aegis 1.0.2

Choose a tag to compare

@alexdeborba alexdeborba released this 26 Oct 23:30

[1.0.2] - 2026-10-26

Added

  • Slide-through submenus on inline Navigation blocks. A block with the is-drilldown class and no overlay gets the same Back button, parent title, and nested panels as the mobile overlay menu. Inline menus do not trap Tab, and they return to the top level when something dispatches aegis:drilldown-reset. Drilldown rows use a 44px target.
  • Books Slider pattern (books): one book per view, a 2:3 cover, arrows outside the slide (is-arrows-outside), and the lightbox off.
  • Latest Posts Carousel pattern (latest-posts): post cards with the featured image, category, date, title, and excerpt, using the Pro query carousel (3 / 2 / 1 slides per view).
  • Pattern::parse_headers() reads a pattern file's header without running the file and returns the pattern with filePath instead of content. Pattern::register() registers an already parsed pattern and its categories.
  • aegis_template_tag_post_fields filter: the post fields that {field} template tags can print.
  • aegis_query_protected_meta_keys filter: the _-prefixed meta keys that Query Loop blocks can filter and sort by. It defaults to WooCommerce's product keys (_price, _regular_price, _sale_price, _stock, _wc_average_rating, _wc_review_count).
  • DOM::set_link_target() sets a link's target and rel from block attributes.

Changed

  • Theme patterns load lazily. Pattern::register_from_file() reads only the file header and registers the pattern with filePath, so WordPress runs a pattern file only when its content is used.
  • Pattern folder listings and parsed headers are cached in the aegis_pattern_headers option (not autoloaded). A folder is listed again when its modified time changes, which adding, removing, or renaming a pattern does. The editor, REST API, and WP-CLI re-read a file's header when the file's modified time changes. Front-end requests use the cached headers, and pattern content is always read from the file. If a template asks for a pattern slug that is not registered, that request re-checks every file, so a renamed slug works on the front end right away. The cache starts fresh when the active theme or its version changes, so theme updates never serve outdated pattern headers.
  • The icon library caches each icon folder's SVG file names in the aegis_icon_files option (not autoloaded) and lists the folder again when its modified time changes. Before, it listed about 5,700 SVG files on every request.
  • WooCommerce plugin patterns (woocommerce/) are removed right before the editor loads the pattern list, not on every init. Reading the whole pattern registry on init loaded every pattern file.
  • {field} template tags print public post fields only: title, excerpt, dates, author, status, slug, parent, post type, and comment count. Custom fields still work, except _-prefixed ones. Nothing is printed for password-protected posts or posts the visitor cannot read.
  • Meta Box block bindings skip _-prefixed fields, password-protected posts, and posts the visitor cannot read, the same as core's post meta binding.
  • Query Loop meta filters and meta sorting ignore _-prefixed keys unless the aegis_query_protected_meta_keys filter lists them.
  • Button and image links that open in a new tab always get rel="noopener". target accepts _blank or _self only.
  • Video embed facades only play YouTube (youtube.com, youtube-nocookie.com) and Vimeo (player.vimeo.com) player URLs over HTTPS. Other embeds render as before, without a facade.
  • Inline SVG replaces an image only when it points to an .svg file inside wp-content.
  • Inline styles built from block settings skip a value that contains ;, {, or } outside quotes or parentheses. Additional Styles saved by users without the unfiltered_html capability keep only the CSS properties WordPress allows in post content.
  • The onclick block setting is kept only when the user who saves the content has the unfiltered_html capability.

Removed

  • SVG uploads. The theme no longer adds SVG or SVGZ to the allowed upload types, so WordPress's default applies and SVG files cannot be uploaded to the Media Library. SVGs already in the Media Library stay where they are. The aegis_svg_settings filter and the svg_upload, svg_strip_colors, svg_strip_dimensions, and svg_strip_styles settings no longer do anything.
  • The unused data-ajax option on copy-to-clipboard buttons.

Reverted

  • Sticky site header from 1.0.1. settings.custom.header in theme.json is position: relative, top: 0px, and scrollPadding: 0px. Set position back to sticky and scrollPadding to 5rem to restore that behavior.
  • Home page hero (pages-home) buttons from 1.0.1. The hero shows Open Editor and Read Docs again, and Read Docs links to https://www.atmostfear-entertainment.com/docs/aegis/. The three-image layout stays, and the release badge stays removed.

Fixed

  • Slider controls. On a single visible slide, arrows sit over the media. When more than one slide is visible, or the slider has is-arrows-outside, they sit in gutters beside the slides. Dots stay clear of the cards, except on full-bleed cover heroes. Chevrons and dots use Neutral 950.
  • Slide markup. Patterns that save only inner blocks still get a .splide__slide wrapper, with role="group" and the "slide" role description. Content that already has that wrapper is not wrapped again. The block can be renamed in the editor, and older saves are covered by deprecations so the editor does not throw on color supports.
  • Images inside slides. Circular avatars stay square and shrink-wrapped. Covers that set their own aspect ratio (the 2:3 book covers) are not forced to 1:1.
  • Hero, Features, Portfolio, and Team slider patterns use theme colors and image placeholders, with the lightbox off.
  • Page load times. The theme no longer lists every icon or runs every pattern file on each request, so pages load much faster on every host. The gain is largest on hosts that restrict file access with open_basedir, where each file check is costly.
  • WooCommerce's variation scripts (underscore, wp-util, and wc-add-to-cart-variation) loaded on every page, because running every pattern file enqueued them. They now load only where a variable product form needs them.
  • woocommerce/ patterns used in templates or content rendered empty on the front end, because they were removed on every request. They now render.
  • Copy-to-clipboard buttons copy code exactly as written, including text that looks like HTML.
  • Structured data (application/ld+json) for embeds, FAQ accordions, and countdowns escapes < and >.
  • aegis/pattern blocks with an unusual slug render the matching pattern instead of misreading the slug.
  • The block inserter's Patterns tab was empty, and GET /wp/v2/block-patterns/patterns returned a critical error. The Patterns utility pattern (utility/patterns.php) set a $patterns variable, and WordPress runs pattern files inside the pattern registry, where that name holds the registry's own list. The variable is now $category_patterns.
  • The Icon block's Icon library never showed any icons. WordPress's GET /wp/v2/icons reads and sanitizes every registered SVG (about 5,800 with the Aegis sets) before it filters by collection or search. Icons\RestIconsList now serves the two icon list routes. It filters first, then loads only the matching icons, and keeps each collection's sanitized SVGs in an aegis_icon_content_{collection} option (not autoloaded). The option is rebuilt when an icon is added, removed, or renamed, or when the theme version changes. Core's permission check, arguments, and response format are unchanged. On a local site, one collection now loads in under 0.1 s and the whole library in about 0.6 s, instead of 15 s.

Aegis 1.0.1

Choose a tag to compare

@alexdeborba alexdeborba released this 19 Oct 13:22
2984a2e

[1.0.1] - 2026-10-19

Added

  • Theme updates from GitHub releases through WordPress's native update screens. style.css declares Update URI: https://github.com/aegiswp/theme, and GitHubUpdater answers core's update_themes_github.com check with the latest release's aegis.zip, so new versions appear in Dashboard → Updates and on the Themes screen with "update now", auto-updates, and release notes. The repository is filterable via aegis_theme_update_repository.
  • Editor light/dark preview toggle: a top-bar button beside Settings and Styles (and "Preview in dark/light mode" in the View menu) switches the editor canvas between light and dark using the same tokens as the front end. The choice is saved per user; the WordPress interface itself is unchanged. Available in the post and Site Editor, and skipped when dark mode is disabled.
  • Audio block styling in theme.json: a card with the Neutral 100 background, the theme border radius, and inner padding. The player fills the card and can shrink below core's 300px minimum on narrow screens, and the caption sits inside the card. Supporting CSS loads only on pages with an Audio block.
  • Sticky site header: the header template part stays fixed at the top while scrolling, below the admin bar on desktop and at the very top on phones, with an opaque Neutral 0 background. Controlled by settings.custom.header in theme.json (position, top, zIndex, background).
  • Slide-through submenus in the mobile (overlay) menu: submenus start closed, and tapping a parent item or its arrow slides in a panel with its sub-items, a Back button, and the parent as a title link. Works for every Navigation block, including nested submenus and Page List items. Escape goes back one level, focus stays inside the menu, and the menu reopens at the top level. Without JavaScript the menu falls back to core's expanded list. The script (navigation-drilldown.js) loads only on pages with submenus.
  • Three-image hero on the Home page pattern: a centered main image on top, with two images behind it on either side (the side images are hidden on phones).

Changed

  • Renamed admin and docs labels Image Compare → Compare and Image Lightbox → Lightbox (block names and settings keys unchanged).
  • bbPress framework styles: circular avatars, content-scale type, theme form fields, grid topic rows, WordPress-style breadcrumbs, Subscribe/Favorite alignment, My Account–style member layout.
  • Empty footer Navigation blocks no longer fall back to listing every page (NavigationFallback + footer pattern sample links).
  • Companion plugin notice now installs the Aegis plugin from the latest GitHub release (aegiswp/plugin) instead of WordPress.org, where it isn't listed. If installation fails, the notice links to the releases page for a manual download. The package URL is filterable via aegis_companion_package_url.
  • Default header: the People button is now a Contact button with a mail icon that links to the site's /contact/ page (hidden on phones), and the comment-author avatar button is removed.
  • Home page hero: the Read Docs button is now Get Plugin, linking to the Aegis plugin download page, and the release badge above the heading is removed.
  • Theme screenshot (screenshot.png, 1200×900) updated to show the new Home page: the sticky header with the Contact button, the Get Plugin hero, and the three-image layout.
  • Navigation submenus now open to the right of their parent item, including in right-aligned menus. In right-aligned menus, the last top-level item still opens toward the left so its submenu stays on screen.

Fixed

  • Captions on images, galleries, tables, embeds, video, and audio were too small to read comfortably (11px on most screens). They now use the 14px preset (13px on phones).
  • Mobile layout: full-width sections inside main now cancel the root padding (style.css), so nested full-width groups no longer stack side padding and squeeze or overflow content on phones.
  • theme.json: spacing presets sm through xxl are now fluid (for example, lg scales from 24px on phones to 48px on desktop), including the page's side padding.
  • theme.json: large font sizes (36px and up) scale down further on small screens (for example, 96px now goes down to 56px instead of 80px).
  • theme.json: added the 56, 42, 15, 13 and 11 font sizes used by patterns but previously undefined, so those blocks render at their intended size.
  • Patterns: 97 hard-coded spacing values (16px and up) in the footer, slider, team, Funnel Thank You, and Order Confirmation patterns now use the fluid spacing presets (xs, sm, md, 2xs), so they scale down on phones like the rest of the theme.
  • Patterns: replaced spacing and color presets that theme.json doesn't define (spacing 20–70; colors primary, contrast, background, gray-400, currentColor) with the closest theme presets. These blocks previously rendered without that padding or color.
  • Pro Tabs: aegis/tab blocks no longer show as invalid in the editor. The icon extension (icon-block-editor.js) no longer writes --wp--custom--icon--* variables into the tab's saved markup; tab icons are rendered in the tabs nav instead.
  • Layout injection hooks (aegis_before_{slug}, aegis_after_{slug}, aegis_before_content, aegis_after_content) fired twice per render, so hooked output printed twice. The duplicate DesignSystem\Hooks registration is removed; CoreBlocks\TemplatePart and CoreBlocks\PostContent fire each hook once.
  • Accessibility: text in dark mode meets WCAG AA contrast. Neutral 400 and 500 text is lighter in dark mode, Primary 500 uses the lighter shade, and sub-headings use Primary 600.
  • Accessibility: icons next to a button label are hidden from screen readers, so buttons are announced by their label only (for example "Get Plugin", not "Get Plugin Plugins Icon"). Icon-only buttons keep a name.
  • Accessibility: linked Icon blocks without a label are named after the site (home links) or the icon, so the header logo link has an accessible name.
  • Accessibility: icons no longer repeat the same id when used more than once on a page, and automatic heading IDs no longer clash with section anchors (a clash adds -2).
  • Accessibility: the closed WooCommerce mini-cart drawer is removed from the keyboard tab order.
  • Accessibility: in-page links and keyboard focus scroll clear of the sticky header (settings.custom.header.scrollPadding).
  • Removed an empty, hidden button from the default header.
  • WordPress 6.7+ no longer logs "translation loading for the aegis domain was triggered too early": framework services register their assets on init.
  • Marquee groups no longer show as invalid in the editor when the marquee speed or direction settings are off. Those settings still apply on the front end.
  • WooCommerce patterns and templates (shop, product archives, cart, Coming Soon) no longer show invalid filter, cart, and Coming Soon blocks in the editor.
  • Removed a console error in the editor when Inline SVG is turned off.
  • Without WooCommerce, the editor no longer shows "unsupported block" placeholders: header patterns drop the cart and account icons, and patterns built on WooCommerce blocks are hidden. Patterns that use the Aegis plugin's map block are hidden when the plugin is inactive (PatternDependencies).
  • Accessibility: sub-headings in sections with their own background and text color follow that text color, so they stay readable on dark sections.
  • Accessibility: outline buttons in dark sections keep a transparent background instead of the filled dark-section button style.
  • Accessibility: in dark mode, the soft Success, Warning, Error and Info backgrounds become dark tints, so notice text stays readable.
  • Accessibility: text in dark-styled event patterns (cinema, conference, workshop, music festival), the Hero Video overlay, the Wide footer search button and the Slider Hero outline button now meets WCAG AA contrast in light and dark mode.
  • Pages with a Tag Cloud block (including the Sidebar pattern) no longer stop with a fatal error on a site that has no tags yet. Curved Text and Social Link rendering also skip missing elements instead of failing.
  • Portfolio page pattern: the project cards use a 60% overlay so their white titles stay readable over light images.
  • Countdown block: its front-end styles (segment layout and spacing) now load. block.json pointed to a stylesheet the build never produced.
  • composer.json no longer sets a version field, so composer validate --strict in the release workflow passes.

Aegis 1.0.0

Choose a tag to compare

@alexdeborba alexdeborba released this 14 Oct 13:55

Initial release.

v1.0.0-rc.3

v1.0.0-rc.3 Pre-release
Pre-release

Choose a tag to compare

@alexdeborba alexdeborba released this 02 May 01:01

Aegis 1.0.0-rc.3

Third release candidate for Aegis — a native block framework engineered for raw velocity.

Highlights

Zero-asset baseline — Aegis loads no CSS, JavaScript, or font assets by default, giving you a clean architectural foundation with nothing to undo.

60 style variations — From Amber to Zinc, each variation ships as a complete theme.json preset ready to activate from the Site Editor.

Deep block controls — The framework extends core blocks with animation, box shadow, text shadow, CSS filters, backdrop blur, opacity, transforms, inline SVG, copy-to-clipboard, sub-headings, template tags, and more — all without plugins.

Advanced Query Loop — Enhanced query parameters including custom post types, taxonomy queries, meta queries, include/exclude lists, offsets, sticky post handling, and extended ordering options.

Block variations — Accordion lists, counters, curved text, grids, icons, marquees, newsletters, and inline SVGs built on top of core blocks.

WooCommerce-ready — Dedicated templates for cart, checkout, my account, wishlist, product archives, and order confirmation.

26 pattern categories — Hero, CTA, FAQ, pricing, testimonial, team, portfolio, commerce, slider, and more — all using native blocks.

Plugin integrations — Optional support for WooCommerce, ACF, Rank Math, Co-Authors Plus, LearnDash, LifterLMS, Sensei LMS, Meta Box, Fluent Forms, Fluent Booking, Code Block Pro, and Bunny CDN. Each integration activates only when the plugin is present.

GitHub auto-updater — Receive theme updates directly from this repository.

Companion Plugin

Some features require the free Aegis plugin, which extends the theme with:

  • Admin panel — Conditional logic settings for toggling block features and integrations
  • Custom blocks — Editor blocks beyond what the framework provides
  • Breadcrumbs — Configurable breadcrumb navigation block
  • Multi-step checkout — Step-based WooCommerce checkout flow
  • Navigation overlay — Full-screen mobile navigation
  • Responsive controls — Per-breakpoint visibility and layout adjustments
  • Analytics — Built-in site analytics dashboard
  • Co-Authors Plus — Extended multi-author support

Requirements

  • WordPress 6.6+
  • PHP 8.1+
  • Tested up to WordPress 6.9

v1.0.0-rc.2

v1.0.0-rc.2 Pre-release
Pre-release

Choose a tag to compare

@alexdeborba alexdeborba released this 28 Jan 16:10
3a67952

Summary of changes added:

🏗 Framework Enhancements

  • 9 Block Variations (Accordion List, Counter, Curved Text, Grid, Icon, Marquee, Newsletter, Related Posts, SVG) refinements
  • Modular Architecture refinements
  • Enhanced Autoloading
  • Strict Type Safety

✨ New Features

  • 35 Enhanced Core Blocks

🔌 Integrations

  • 10 plugin integrations (ACF, Code Block Pro, Fluent Booking, Fluent Forms, LearnDash, LifterLMS, Rank Math, Sensei LMS, Syntax Highlighting Code Block, WooCommerce)
  • 1 service integration (BunnyCDN)

🐛 Improvements

  • Performance, Accessibility, SEO, Security, Editor Experience, and Code Documentation

Full Changelog: v1.0.0-rc.1...v1.0.0-rc.2

v1.0.0-rc.1

v1.0.0-rc.1 Pre-release
Pre-release

Choose a tag to compare

@atmostfear-entertainment atmostfear-entertainment released this 17 Jan 16:42
2bad9a9

v1.0.0-rc.1: The Framework Rewrite

This release marks a complete re-architecture of the Aegis codebase. We have rewritten the theme from the ground up, implementing a new modular framework designed for scalability, performance, and stricter adherence to WordPress Full Site Editing (FSE) standards.

⚠️ Note for existing users: Due to the complete refactoring of the codebase, this update may introduce breaking changes for child themes relying on legacy CSS classes. Please review your customizations before updating.

🏗 Framework Implementation

  • Modular Architecture: The codebase has been completely refactored into a modular system. Logic is now separated from presentation, ensuring a cleaner developer experience.
  • Refactored theme.json: Rebuilt the global styles engine from scratch to support the new "Calibrated Neutrality" color system and fluid typography scaling.
  • Optimization: Removed legacy assets and dependencies. The theme now runs on a zero-bloat, native-block foundation.

✨ New Features

  • Expanded Pattern Library: Introduced the new pattern categories.
  • Enhanced Block Support: Added custom, lightweight styling for 30+ core blocks, including specific support for the new "Dark Mode" inverse contexts.
  • Typography System: Fully integrated Lexend (Variable) and JetBrains Mono with new fluid sizing rules.

🔌 Integrations

  • Fluent Forms Support: Added native integration for Fluent Forms. Forms now automatically inherit the theme's typography, spacing, and button styles for a seamless "out-of-the-box" experience.

🐛 Improvements

  • Performance: Significant reduction in DOM size and CSS payload.
  • Accessibility: Audit and overhaul of color contrast ratios across all default patterns.
  • Editor Experience: Improved back-end editor styles to match the front-end rendering 1:1.

Aegis v1.0.0-beta.3

Aegis v1.0.0-beta.3 Pre-release
Pre-release

Choose a tag to compare

@alexdeborba alexdeborba released this 28 Feb 22:21
b659acb

The Aegis version 1.0.0-beta.3 has been officially released and is now available for download and testing. This release signifies a pivotal milestone in the project's development cycle. We invite all developers, users, and interested parties to engage with this version. Consistent with Aegis's overarching guidelines, adherence to established testing best practices is essential to facilitate effective collaboration and garner comprehensive feedback.

The Aegis Block Theme is presently in its development phase. It is highly advised against installing, running, or testing this theme on production or mission-critical websites. For a comprehensive evaluation of the theme's capabilities, it is recommended to have WooCommerce installed during testing. Evaluations of the Beta version are best conducted on a dedicated test server and site, ensuring safety and efficient debugging throughout the development process.

Furthermore, engagement in issue testing plays a pivotal role in software development, offering a significant avenue for contribution irrespective of one's expertise. This methodology not only guarantees the software's stability but also propels its progression, rendering contributions in this realm profoundly influential.

Should any issues emerge, they are anticipated during the Beta phase of development. Individuals who come across bugs or other discrepancies are encouraged to promptly report them by creating a GitHub Issue. For those adept at crafting reproducible bug reports, GitHub remains the preferred platform for submitting these comprehensive accounts. Before proceeding with formal reporting, it is advisable to cross-check any identified issues against a list of previously recognized bugs.

Contributions are not limited solely to coding. There are multiple avenues for participation, including testing, issue triage, discussions, and contributions to design patterns and templates. A special focus is directed towards improving accessibility, in line with the theme's objective to cater to individuals with visual impairments. Those looking to contribute are encouraged to explore open issues on GitHub, aligning with areas of their expertise and comfort.

Aegis 1.0.0-beta.2

Aegis 1.0.0-beta.2 Pre-release
Pre-release

Choose a tag to compare

Warning

When you download the theme from GitHub and extract it, the default folder name will be aegis-1.0.0-beta.2. Before installing, please rename this folder to aegis. Also, avoid using the original zipped file with WordPress' default theme installer to prevent any errors.

The Aegis version 1.0.0-beta.2 has been officially released and is now available for download and evaluation. This release signifies a pivotal milestone in the project's development cycle. We invite all developers, users, and interested parties to engage with this version. Consistent with Aegis's overarching guidelines, adherence to established testing best practices is essential to facilitate effective collaboration and garner comprehensive feedback.

The Aegis block theme is presently in its development phase. It is highly advised against installing, running, or testing this on production or mission-critical websites. For a comprehensive evaluation of the theme's capabilities, it is recommended to have WooCommerce installed during testing. Evaluations of the Beta version are best conducted on a dedicated test server and site, ensuring safety and efficient debugging throughout the development process.

Furthermore, engagement in issue testing plays a pivotal role in software development, offering a significant avenue for contribution irrespective of one's expertise. This methodology not only guarantees the software's stability but also propels its progression, rendering contributions in this realm profoundly influential.

Should any issues emerge, they are anticipated during the Alpha phase of development. Individuals who come across bugs or other discrepancies are encouraged to promptly report them by creating a GitHub Issue. For those adept at crafting reproducible bug reports, GitHub remains the preferred platform for submitting these comprehensive accounts. Before proceeding with formal reporting, it is advisable to cross-check any identified issues against a list of previously recognized bugs.

Contributions are not limited solely to coding. There are multiple avenues for participation, including testing, issue triage, discussions, and contributions to design patterns and templates. A special focus is directed towards improving accessibility, in line with the theme's objective to cater to individuals with visual impairments. Those looking to contribute are encouraged to explore open issues on GitHub, aligning with areas of their expertise and comfort.

1.0.0-beta.1

1.0.0-beta.1 Pre-release
Pre-release

Choose a tag to compare

@atmostfear-entertainment atmostfear-entertainment released this 22 Dec 22:07
e5c88a6

Warning

When you download the theme from GitHub and extract it, the default folder name will be aegis-1.0.0-beta.1. Before installing, please rename this folder to aegis. Also, avoid using the original zipped file with WordPress' default theme installer to prevent any errors.

The Aegis version 1.0.0-beta.1 has been officially released and is now available for download and evaluation. This release signifies a pivotal milestone in the project's development cycle. We invite all developers, users, and interested parties to engage with this version. Consistent with Aegis's overarching guidelines, adherence to established testing best practices is essential to facilitate effective collaboration and garner comprehensive feedback.

The Aegis theme is presently in its development phase. It is highly advised against installing, running, or testing this on production or mission-critical websites. For a comprehensive evaluation of the theme's capabilities, it is recommended to have WooCommerce installed during testing. Evaluations of the Beta version are best conducted on a dedicated test server and site, ensuring safety and efficient debugging throughout the development process.

Furthermore, engagement in issue testing plays a pivotal role in software development, offering a significant avenue for contribution irrespective of one's expertise. This methodology not only guarantees the software's stability but also propels its progression, rendering contributions in this realm profoundly influential.

Should any issues emerge, they are anticipated during the Beta phase of development. Individuals who come across bugs or other discrepancies are encouraged to promptly report them by creating a GitHub Issue. For those adept at crafting reproducible bug reports, GitHub remains the preferred platform for submitting these comprehensive accounts. Before proceeding with formal reporting, it is advisable to cross-check any identified issues against a list of previously recognized bugs.

Contributions are not limited solely to coding. There are multiple avenues for participation, including testing, issue triage, discussions, and contributions to design patterns and templates. A special focus is directed towards improving accessibility, in line with the theme's objective to cater to individuals with visual impairments. Those looking to contribute are encouraged to explore open issues on GitHub, aligning with areas of their expertise and comfort.

Aegis incorporates ten headers, three of which offer a sticky functionality coupled with a mega menu feature. Additionally, there are four footers available, and users can effortlessly toggle between them using the Header and Footer Builder. Among its Patterns, Aegis offers the following:

  • 9 Headers (three sticky) with integrated Mega Menu
  • 3 Heros
  • 3 About Us
  • 2 Teams
  • 2 Testimonials
  • 1 Pricing Tables
  • 2 FAQs
  • 1 Contact Us
  • 4 eCommerce
  • 8 Blog Archives

In total, it features 35 Block Patterns for now. Subsequent Beta releases will progressively introduce new Patterns and complete Pages.

In addition to 6 new Block Patterns, this latest release also brings a host of bug fixes, performance enhancements, and elevates the code to higher standards of quality.

In conclusion, the strides made in the Aegis 1.0.0-beta.1 version underscore our commitment to excellence and innovation in this project.

1.0.0-alpha.3

1.0.0-alpha.3 Pre-release
Pre-release

Choose a tag to compare

@atmostfear-entertainment atmostfear-entertainment released this 10 Nov 14:45
768dc7f

Warning

When you download the theme from GitHub and extract it, the default folder name will be aegis-1.0.0-alpha.3. Before installing, please rename this folder to aegis. Also, avoid using the original zipped file with WordPress' default theme installer to prevent any errors.

The Aegis version 1.0.0-alpha.3 has been officially released and is now available for download and evaluation. This release signifies a pivotal milestone in the project's development cycle. We invite all developers, users, and interested parties to engage with this version. Consistent with Aegis's overarching guidelines, adherence to established testing best practices is essential to facilitate effective collaboration and garner comprehensive feedback.

The Aegis theme is presently in its development phase. It is highly advised against installing, running, or testing this on production or mission-critical websites. For a comprehensive evaluation of the theme's capabilities, it is recommended to have WooCommerce installed during testing. Evaluations of the Alpha version are best conducted on a dedicated test server and site, ensuring safety and efficient debugging throughout the development process.

Furthermore, engagement in issue testing plays a pivotal role in software development, offering a significant avenue for contribution irrespective of one's expertise. This methodology not only guarantees the software's stability but also propels its progression, rendering contributions in this realm profoundly influential.

Should any issues emerge, they are anticipated during the Alpha phase of development. Individuals who come across bugs or other discrepancies are encouraged to promptly report them by creating a GitHub Issue. For those adept at crafting reproducible bug reports, GitHub remains the preferred platform for submitting these comprehensive accounts. Before proceeding with formal reporting, it is advisable to cross-check any identified issues against a list of previously recognized bugs.

Contributions are not limited solely to coding. There are multiple avenues for participation, including testing, issue triage, discussions, and contributions to design patterns and templates. A special focus is directed towards improving accessibility, in line with the theme's objective to cater to individuals with visual impairments. Those looking to contribute are encouraged to explore open issues on GitHub, aligning with areas of their expertise and comfort.

Aegis incorporates eight headers, three of which offer a sticky functionality coupled with a mega menu feature. Additionally, there are four footers available, and users can effortlessly toggle between them using the Header and Footer Builder. Among its Patterns, Aegis offers the following:

  • 8 Headers (three sticky) with integrated Mega Menu
  • 3 Heros
  • 3 About Us
  • 1 Team
  • 2 Testimonials
  • 1 Pricing Tables
  • 1 FAQ pattern
  • 1 Contact Us
  • 4 eCommerce
  • 5 Blog Archives

In total, it features 29 Block Patterns for now. Subsequent Beta releases will progressively introduce new Patterns and complete Pages.

In addition to 5 new Block Patterns, this latest Alpha release also brings a host of bug fixes, performance enhancements, and elevates the code to higher standards of quality.

In conclusion, the strides made in the Aegis 1.0.0-alpha.3 version underscore our commitment to excellence and innovation in this project.