A Call of Cthulhu Community Content Template

THE SHADOW OVER BRINDLEWOOD

An investigation in fog, brine, and inherited terror.

By Your Name Here

Credits

Author: Your Name

Editor: Editor Name

Proofreader: Proofreader Name

Interior Art: Artist Name / Source

Layout: Your Studio Name

Playtesters: Name, Name, Name

Special Thanks: Add any acknowledgements here.

Version: 1.0

Publication Date: 2026

Table of Contents

Introduction

Use this template for the principal text of the book. The main body is set in a two-column layout intended for screen reading and print export. The first paragraph under a heading should use the .body-no-indent class, with subsequent paragraphs using .body-indent.

The styling here is deliberately close to the original Word template: strong uppercase display headings, smaller subheads, justified body copy, compact indents, restrained rules, and table treatment intended to stand apart from narrative text.

Using the Template

Replace placeholder text, duplicate sections as needed, and keep major content inside the #main-content container so the table of contents script can index the headings automatically.

  • Keep major sections as h2.
  • Use h3 and h4 for nested structure.
  • Avoid very wide tables inside the two-column flow; use .full-width-block for wider elements.

Example Text Box

For example: this box is intended for Keeper guidance, worked examples, fictional illustrations, or explanatory inserts. It reproduces the spirit of the Word template’s tinted example text treatment while remaining web-safe and print-friendly.

Lists

Bulleted and numbered lists are set slightly inset from the measure, with restrained spacing so they remain visually integrated with the surrounding text.

  1. Use numbered lists when sequence matters.
  2. Use bullets for unordered material.
  3. Avoid a single orphaned list item when a short sentence will do the same work.

NPC Stat Blocks and Skills

For character summaries, use the stat block below. It is presented in a monospaced grid rather than tab stops, because HTML tab behaviour is inconsistent across browsers and print engines.

STR 40
CON 50
SIZ 50
DEX 45
INT 30
APP 30
POW 30
EDU 40
SAN 30
HP 10
DB 0
Build 0
Move 7
MP 6
Luck N/A

Attacks per round: 1

  • Brawl35% (17/7), damage 1D3
  • Shotgun 12-gauge40% (20/8), damage 4D6/2D6/1D6
  • Thompson SMG30% (16/6), damage 1D10+2

Armor: none.

Skills: none.

Tables

Tables are styled to stand apart from the body text, with a dark heading band, compact small caps emphasis, and clear row division. Apply .full-width-block when the table should span both columns.

Outcome Level Result
Fumble Out of position: take a penalty die on the next action.
Critical Prime position: add one bonus die to the character’s next action.

Subsections

Secondary and tertiary headings are included in the automatic contents list. This keeps the web edition navigable without requiring manual page-number maintenance.

A Note on Player Handouts

When practical, place handouts in a discrete appendix or at the end of the document so they can be printed or exported independently from Keeper-only material.

In HTML, that usually means isolating handouts into their own section, article, or file. For a print-PDF workflow, you can also apply page breaks before each handout.

A Note on Indexes

For short releases, an index is frequently unnecessary. For longer works, especially those with dense settings or rules reference material, it is often worth producing a separate appendix or linked web index.

Appendix

This section is a placeholder for further content. Duplicate this pattern as required for scenarios, appendices, handouts, or stat compilations.