WordPress Themes

This section is the working reference for the WordPress themes maintained in the tbskit GitHub account and used on live sites. Each theme gets its own page here, and whatever is written is taken from sources that can be checked — the theme repository, its style.css header, its README, or the WordPress installation on the server.

What this documentation is for

Reader	Question	Where it is answered
Operator / site admin	What is this theme, and what does it need?	the theme page (specification table)
Operator / site admin	How do I install and activate it?	the theme’s Installation page
Operator / site admin	How do I load the sample content?	the theme’s Importing the Sample Content page
Operator / site admin	How do I change the logo, site name or header menu?	the theme’s Logo, Favicon, Site Name & Header Navigation page
Developer	What ships in the theme, and how is it built?	the theme’s Introduction, plus the file structure on the theme page
Anyone	What is still unknown?	the Not documented yet list at the end of each page

How a theme is documented here

Every theme follows the same shape, so pages are predictable:

Theme page — specification (name, slug, version, minimum WP/PHP, parent theme, text domain), file structure, install pointer, and links to the sub-pages.
Introduction — what the theme is (and is not), how it is designed, what ships in it, and what it requires.
Installation — how to obtain it (ZIP or repository), what must be active (for Blogtail General: the WindPress plugin), permissions, and how to verify.
Importing the Sample Content — demo content, new WordPress only, plus how the importer works.
Logo, Favicon, Site Name & Header Navigation — the branding and menu steps, with the theme’s actual behaviour spelled out (breakpoints, menu locations, fallbacks).

Themes in this section

Theme	State
Blogtail General 1.0.4 — classic starter for `wptheme1.tbskit.com`, Tailwind via the WindPress plugin	documented (theme page + 4 sub-pages)

Not documented yet — these repositories exist in the same account:

Repository	Likely scope
`tbskit/generatepress-child`	GeneratePress child theme (classic), rebuilt “General Blog” design
`tbskit/general-blog`	empty block theme starter, distributed as a ZIP
`tbskit/wptheme1`	custom block theme for the wptheme1 site
`tbskit/wpstack-template`	not a theme: WordPress + MariaDB + Cloudflare Tunnel stack template

Scope and boundaries

In scope: theme behaviour that affects the site (templates, script/style loading, menu locations, fallbacks), the admin steps to operate it, and the facts a developer needs to work on it.

Out of scope (for now): hosting and platform operations — Docker, networks, Cloudflare Tunnel, backups — and the internals of third-party plugins (WindPress is only described as far as the theme depends on it).

Conventions

Bilingual. English is the default language (served at /), Indonesian at /id/. A translation is a sibling file with the .id.md suffix.
Facts, with a source line. Pages that describe a theme start with a note such as “Source: tbskit/<repo> — style.css header (v…), README.md, verified ”.
Gaps are stated, not guessed. Anything unverified goes into Not documented yet.
No secrets. Only the location of credentials is documented, never the value.
Sidebar order comes from weight in each file’s front matter.

Where the documentation itself lives

Item	Value
Source repository	`tbskit/documentation` (private)
Published site	https://doc.tbskit.com — Hugo + Hextra, built on Cloudflare Pages
Workflow	edit markdown → commit → push to `main` → Pages rebuilds automatically

Adding a theme means adding one page plus, where it makes sense, its sub-pages — the sidebar builds itself from the folder structure. See the repository README for the full conventions and build commands.