Skip to content
Back to documentationGetting started

BrutalSoft — Documentation and setup checklist

Start here: installation, demo import, homepage, software, translation and maintenance.

English · 简体中文

Applies to BrutalSoft 2.2.2 / Core 1.1.2.

BrutalSoft is a neo-brutalist WordPress software directory and blog theme. The theme supplies presentation, navigation and colours; BrutalSoft Core supplies software/community content, download sources, wishes, feedback, SEO/GEO and demo import. These bilingual guides cover theme 2.2.2 and Core 1.1.2. Documentation is public and does not require a purchase key.

Recommended first-run sequence

  1. Back up the database, themes, plugins and media. Start on a staging site.
  2. Upload the installable theme ZIP, activate the theme, then explicitly install and activate Core from BrutalSoft Settings → Install plugins.
  3. Import the demo if needed, or create the home, blog and Software Hub pages manually.
  4. Set site identity, Reading settings and menus. Configure the homepage and catalogue separately.
  5. Add real applications, downloads, screenshots and community destinations. Review both interface languages.
  6. Check forms, downloads, search, mobile navigation and password protection while signed out before launch.

Guide index

How the theme and Core work together

When BrutalSoft is active, appearance and business controls share the top-level BrutalSoft Settings menu. With another theme, Core keeps a standalone administration screen. Deactivating Core does not erase records, but software, download and wish features require Core to be reactivated.

BrutalSoft does not implement a WooCommerce checkout workflow. Store, purchase-key or signed-update instructions written for other Ryn Code themes should not be applied to BrutalSoft; follow the actual workflow in these guides.

Before going live

  • Replace sample titles, articles, descriptions, versions, statistics and download sources.
  • Review buttons, menus, community invitations, footer copy and English variants.
  • Verify hosting email, backups, HTTPS and cache configuration.
  • Keep development error output out of public pages and retain server logs for diagnosis.

Documentation index

Still need a hand?

Send the product, version, and reproduction steps and we will help you continue.

Contact support