2 food blog examples built with Ghost

Someone visiting a bread newsletter’s website may want the next letter from its author. Someone looking for a coffee brewing method may want an older guide on that subject. A food publication’s homepage can make either route the starting point.

These two sites from the Aspire Themes showcase use Ghost and themes I make.

Wordloaf

Wordloaf introduces Andrew Janjigian’s bread newsletter before the post archive. A large bread photograph sits beside the introduction and email form. New visitors can learn what it covers and subscribe from the same opening.

The navigation also includes Index and Archive. Readers can use these links to find earlier writing. The homepage does not need to list every subject. Featured and recent posts continue below the introduction.

This is a useful model when an ongoing letter is the main reason to return. The opening explains who writes it and what it covers. Readers looking for past letters can use the archive. Compare more signup layouts in the newsletter website examples.

Theme: Ubud.

Rua do Café

Rua do Café publishes in Portuguese. It gives visitors several routes into its coffee stories. Its navigation separates Café, Para Produtores (for producers) and Experiências (experiences). It also has a separate Comunidade (community) destination.

The post grid then offers individual articles. Readers can choose a subject before opening a particular guide. For stories about coffee production, choose Para Produtores. Readers do not have to start with the newest article.

The site also links to a separate shop. The separate shop is not a store or shopping cart inside the Ghost theme. This example shows the publication and its subject navigation.

Theme: Penang.

Wordloaf puts its writer and signup form first. It is a model for a food newsletter that readers return to for the writer’s work. Rua do Café gives readers routes by subject. It suits a publication they consult for a guide or a specific interest. Before choosing a layout, decide which visit your homepage needs to serve first.