Stunning photo & video albums for WordPress.
StackFolio shows a filterable grid of album covers. Click a cover and the whole album (photos, Media Library videos, YouTube, YouTube playlists and Vimeo) opens in a lightGallery popup. Use it as a Gutenberg block, an Elementor widget or the [stackfolio] shortcode.
StackFolio is the successor of Album Station and migrates its albums automatically.
| Path | What it does |
|---|---|
stackfolio.php |
Plugin bootstrap |
includes/class-stackfolio-post-type.php |
stackfolio_album post type, stackfolio_category taxonomy |
includes/class-stackfolio-meta-box.php |
Album edit screen: media picker, video links |
includes/class-stackfolio-album.php |
Album data and lightbox items |
includes/class-stackfolio-videos.php |
YouTube / playlist / Vimeo parsing and cached remote data |
includes/class-stackfolio-renderer.php |
Shared grid markup for block, widget and shortcode |
includes/class-stackfolio-block.php, blocks/album-grid/ |
Gutenberg block (plain JS, no build step) |
includes/elementor/ |
Elementor widget (+ hidden Album Station compatibility widget) |
includes/class-stackfolio-shortcode.php |
[stackfolio] and legacy [feature_album] |
includes/class-stackfolio-migration.php |
One-time Album Station migration |
assets/vendor/ |
lightGallery 2.9.0 and Isotope 3.0.6 (GPLv3), Vimeo Player API 2.30.4 (MIT) |
Open the demo in WordPress Playground: it installs the latest release with six sample albums and a demo page. (Playground downloads releases/latest/download/stackfolio.zip, so it needs at least one release.)
issue → branch → pull request (Closes #N) → squash merge to main → automatic release → deploy (if enabled)
mainis protected. Changes go through pull requests, merged with squash. Repository admins can still bypass the rules.- Every PR closes an issue. The Linked issue check fails a PR without
Closes #N. One request with several changes = one issue per change, delivered in one PR. - CI runs on every PR and must pass: PHP 7.4–8.5 syntax and unit tests, PHPCS, PHPStan, JS/CSS lint and WordPress Plugin Check. Plugin Check fails when
Tested up toinreadme.txtis behind the latest WordPress, so bump it after testing each new WordPress version. - Releases are automatic. On each merge to
main, the Release workflow releases only if the plugin zip would change (everything.distignoredoesn't exclude). It bumps the version (patch by default, or minor/major with therelease:minor/release:majorlabel), writes the changelog (one line per closed issue) and the version intoreadme.txtand the plugin header, commits that tomain, tags it and publishes a GitHub release withstackfolio.zip. - Deploys are off. The Deploy workflow targets WordPress.org SVN (
DEPLOY_METHOD=wporg) and runs only while the repo variableDEPLOY_ENABLEDistrue. Turn it on once the plugin is approved on WordPress.org and theSVN_USERNAME/SVN_PASSWORDsecrets are set.
composer install && npm ci| Command | What it checks |
|---|---|
composer lint |
PHP syntax |
composer phpcs |
WordPress Coding Standards (composer phpcbf fixes most issues) |
composer phpstan |
Static analysis |
composer test |
Unit tests |
npm run lint |
JS and CSS (Node 22.12 or newer) |
A local site: cp .env.example .env && docker compose up -d, then open http://localhost:8000.
stackfolio_post_type_args,stackfolio_taxonomy_args– change registration argumentsstackfolio_query_args– change the album querystackfolio_album_items– change an album's lightbox itemsstackfolio_grid_html– change the grid markupstackfolio_playlist_max_videos– videos loaded per YouTube playlist (max 50)
GPL-3.0-or-later. See LICENSE.