When News and Events share the same WordPress content structure, editorial workflows and frontend presentation can become difficult to manage. In one project, the site needed a dedicated News area that could be maintained independently from Events while still fitting the existing custom theme.
The final implementation used a dedicated News custom post type registered through Advanced Custom Fields (ACF), a public /news/ archive, a dedicated single-news template, an ACF Flexible Content News Grid, configurable archive content, featured images, excerpts, authors, and optional manual author overrides. The News section was tested on staging, refined to match the site’s existing Events presentation, and then deployed to production.
Issue background
The WordPress site already had an Events section, but the content team wanted a separate place for company announcements, technical updates, and other news content.
The initial idea was to use categories to distinguish News from Events if the existing structure could support that cleanly. A dedicated custom post type was also considered if stronger separation was needed.
The team wanted the new section to support:
- A public News archive.
- Individual News article pages.
- Categories.
- Featured images.
- Excerpts.
- Author information.
- A reusable News grid that editors could place through ACF Flexible Content.
- Header and footer navigation links to both News and Events.
The site used a custom theme built around ACF rather than a visual page builder, so the implementation needed to fit that framework.
Diagnosis
The developer reviewed the existing Events structure and determined that a dedicated News custom post type would be cleaner than trying to force all content into one shared post type with category filtering.
The custom theme was more complex than a standard off-the-shelf theme, but the existing Events implementation provided a useful reference. The News section could reuse the same overall design language while simplifying the parts that were specific to event content.
The developer also confirmed that the site’s standard WordPress Posts area was not otherwise being used, but the final implementation still moved forward with a dedicated News post type rather than relying on Posts.
Two other requests appeared in the broader project notes but were explicitly separated from this work:
- A possible future drag-and-drop builder transition.
- An earlier heading/breadcrumb sizing issue.
The project manager later clarified that development time for this task should be spent only on the News section. The builder request was deferred, and the prior heading issue was handled separately.
Resolution steps
The documented News implementation included the following:
- Register a dedicated News custom post type with ACF. The new post type was public and supported an archive, categories, featured images, excerpts, and authors.
- Create the News archive. A dedicated archive was added at
/news/with article cards and pagination. - Create a single-news template. Individual News items received a dedicated article view with metadata, ACF content, and author information.
- Build a reusable News Grid in ACF Flexible Content. Editors could add a News Grid to supported content areas and configure options such as the heading, article count, and View All link.
- Add default-image support. The News Grid was designed to handle articles that did not have a featured image.
- Enable ACF page-section support for News. This let News entries use the site’s existing flexible content system rather than requiring a separate editor experience.
- Add staging-only sample content for testing. An admin-only seeder was created to generate temporary News items for development and QA. Those sample posts were not intended for production.
- Update frontend assets. The compiled theme assets were refreshed to support the new News presentation.
- Update header and footer navigation. The site navigation was changed so visitors could reach News and Events as separate destinations.
- Refine the breadcrumb spacing. During staging review, the breadcrumb area was moved farther from the navigation header for better visual balance.
- Add manual author override fields. The client wanted the author area to support technical experts who might not correspond to a WordPress user account. Optional ACF fields were added so editors could manually enter an author name and expertise blurb while preserving the existing author-section design.
- Move archive description content below the hero. The client wanted the News hero to match the Events style without descriptive text inside the hero itself, so descriptive copy was moved into the body above the article grid.
- Match the News archive styling to Events. The archive header and overall layout were revised so News felt visually consistent with the existing Events section.
- Add editable archive settings. A News Archive settings area was added through ACF so the archive presentation could be maintained without editing template files directly.
- Deploy the News section to production. After staging approval and a coordinated launch window, the implementation was pushed live.
- Fix a responsive overlap discovered after launch. A text overlap appeared at smaller viewport widths on newly created News content. The responsive styling was adjusted, cache was cleared, and the revised layout was confirmed to look better.
The source task confirms that the production News archive would remain empty until real News articles were added. The temporary staging articles were only test content and were not migrated to production.
Final outcome
The site gained a fully separate News publishing workflow alongside Events.
Editors could create News items with categories, featured images, excerpts, author information, and flexible ACF content, while the public site received a dedicated News archive, single-news template, reusable News Grid, and navigation links.
The client also gained more flexible author presentation through manual override fields, and the archive styling was aligned with the existing Events section before launch.
After production deployment, a small responsive overlap was corrected and the cached output was refreshed.
The broader lesson is that categories are not always enough when two content types need different templates, archives, editorial fields, and navigation behavior. A dedicated ACF-registered custom post type can provide cleaner separation while still reusing the design and content systems already present in a custom WordPress theme.
If your WordPress site needs a dedicated News section separate from Events, Resources, or other content types, contact Freshy. Our WordPress team can design the custom post type, ACF fields, archive, templates, and reusable content modules around your existing site architecture.
