Skip to content
Mickey Liechtenstein
All cases

Stock publication with bespoke content types

Vækstaktier

A publication on Danish growth companies, built on the same block theme and plugin as its sister site. Company profiles, insider trades and a reporting calendar as structured content types rather than articles with tables in them.

Vækstaktier covers Danish growth companies on First North, Spotlight and the main exchange. The site was rebuilt from scratch alongside its sister site Unge Investorer: a new WordPress installation, a shared block theme and one shared custom plugin.

A different audience and a different look, built from the same theme and the same plugin as the sister site.
A different audience and a different look, built from the same theme and the same plugin as the sister site.

Same code, different site

The two publications share a codebase, but not a look or an audience. Vækstaktier speaks to private investors following particular companies, and that asks for different things than a beginners' publication does.

So the functionality is written as modules switched on per site. Vækstaktier uses company profiles, insider trades, a reporting calendar and a weekly letter. The sister site uses a shop, a podcast and calculators. The same code sits underneath both, and a fix in the shared part reaches both sites at once.

Content that is not articles

A stock publication is not only text. A reader following a company wants to see that company gathered in one place: the news about it, the accounts and the trades.

So each company has its own page, and insider trades have their own overview. These are content types with structured fields, not articles with tables in them, so they can appear in several places without being maintained more than once.

Almost no plugins

Beyond analytics, the site runs one functional plugin: the custom one. No page builder and no collection of small plugins. Every plugin is a dependency that has to be updated and can stop working — and when the functionality is written for the job, there is one place to look when something misbehaves.

The migration

The site had several thousand addresses that had to survive the switch. All of them were checked after go-live and still answer. The old WordPress stayed behind an access block, the old tables were left untouched, and full backups were taken both before and during the switch, with matching checksums. Rolling back was one script.

Operations

The site runs on the client's own hosting. The code lives in a private Git repository with tests, and updates go through a release rather than by editing on the server.

Shall we have a chat?

Tell me briefly about your task — I will get back to you with an honest take on what makes sense.

Write to me

Describe your task in a few lines and I will get back to you — usually the same day.

Your details are used only to reply — no newsletter.