Keep the record connected.
Dates, bylines, sections and useful relationships between stories stay visible instead of becoming a pile of old posts.
A publication needs a good reading experience and a sensible way to publish. We design both, from the front page to the article your readers share.
Tell us about your publication ↗
Room for a lead story, a useful section structure and the next thing worth reading.
Some days there is one story that matters most. On others, readers need a broader view. We give your editors a homepage structure they can work with.
Lead stories, topic sections and recent coverage get a clear order. Every story does not need to compete at the same size.
Comfortable type, useful image captions and clear author and date information keep the focus on the reporting.
The website should fit the way your team publishes. We agree the everyday workflow before choosing the modules and editing fields.
Defined article fields for headlines, summaries, images, captions and author details help editors know what belongs where.
Useful sections, tags and homepage controls keep the site organised as the archive grows.
Publication dates, updates and bylines belong in the article layout. Your editorial team controls the reporting and corrections.
The next story should not bury the last one.
For an existing publication, migration is part editorial structure and part technical housekeeping. We inspect the supplied export before agreeing the move, so articles, authors, images, sections and URLs arrive with a clear place to live.
Dates, bylines, sections and useful relationships between stories stay visible instead of becoming a pile of old posts.
We map the agreed URL changes and redirects around the migration scope, with search and reader journeys in mind.
Newsletter tools, advertising and paywalls are scoped around the systems you use, without crowding the reading experience on smaller screens.
Choose a publishing scope, then confirm the sections, editorial workflow and archive work with us.
A new publication with a small editorial desk.
A busier publication covering more subjects.
An established archive or a broader editorial operation.
Starting prices in EUR for a one-off build. The final quote depends on the agreed scope. Hosting, domain registration, paid licences and applicable taxes are separate. Journalism, editorial production, subscription-platform fees and ad operations are separate. Imports use one agreed, clean data source; larger or inconsistent archives need a separate quote.
A few things to settle before the next version of your publication.
Ask us about your project ↗It is a design and build service. We plan the publication’s structure, design its key layouts and configure the agreed WordPress editing setup. These packages are not the sale of a downloadable theme.
Yes. Editors can use the agreed article layouts, categories, authors and homepage modules from WordPress. We run through that workflow at handover and keep the routine publishing steps straightforward.
Yes, within the agreed import scope. We first inspect a sample export, including authors, dates, images, categories and URLs. Large or inconsistent archives, media recovery and complex redirects need a separate migration plan.
We can scope those around a supported subscription system. Payment rules, subscriber accounts, access restrictions and the cost of the platform are separate from the base publishing plans.
That is not guaranteed. We can build clear article pages, author and date information, crawlable sections and appropriate article markup. Search and news systems decide whether and where a publication appears.
Yes. We agree the ad positions and supported integration before building them. Advertising account approval, campaign management and ad revenue are outside the design scope. We also review how the agreed placements affect reading on smaller screens.
Choose what you need now. You can move between services later.
Contact details and important information about Blyfa.