Most client sites need a set of things with a listing page and a detail page. Case studies, team members, properties, a blog. In Delta this is one job, and it is smaller than it looks.
“Add a Portfolio section: projects with a client name, a year, and a project type taxonomy. Build the listing and the project page to match the site.”
What you get
A content type, and three templates: a card for one project, an archive that lays the cards out, and a single page for the project itself. Display conditions point the last two at the Portfolio.
That is the whole structure. Project number seven is one entry: no template work, nothing to repeat. Six hand-built pages would have cost you six edits every time the design changed.
A blog is the same job with the first step removed, since WordPress already has posts.
The one interruption
Delta has no post types of its own. It drives a fields plugin instead, so the agent will name one, usually Advanced Custom Fields, and stop until you answer. It does not install plugins on its own initiative.
Once the plugin is active, the agent creates the type, the taxonomy and the fields, then adds the field maps that turn your custom fields into placeholders the design can use.
For developers
Delta seeds one designated default per hierarchy type. Edit that default rather than adding a second template, unless a subset genuinely needs to override it.
Conditions: archive → post_type_archive with the post type; single → post_type with the post type; blog home → the blog condition on an archive template. In archive markup use {{#posts}}; on a page’s own HTML there is no main query, so use {{#query:slug}}.