EnergyAE / Knowledge Base

News & Regulations Feed

A news feed section within the Intelligence Platform that surfaces relevant regulatory updates, scheme changes, and industry news for heat pump water heaters across the Australian and New Zealand mark

Overview

A news feed section within the Intelligence Platform that surfaces relevant regulatory updates, scheme changes, and industry news for heat pump water heaters across the Australian and New Zealand markets. The primary users are EnergyAE staff and potentially registered manufacturer/importer clients. The feed saves users from manually monitoring multiple sources and ensures compliance-critical updates are not missed.

User Stories

As an EnergyAE staff member, I want to see recent regulatory updates relevant to VEU, ESS, and SRES so I can stay current without manually checking multiple websites. As a logged-in manufacturer client, I want to see news relevant to my market (AU or NZ or both) so I don’t have to filter out irrelevant content. As a user, I want to know when an article was published and where it came from so I can assess its credibility and recency.

Sources to Monitor

The feed should aggregate content from the following sources. This list will grow over time so the architecture should make adding new sources straightforward. Regulatory bodies:

DELWP / Victorian Energy Upgrades (VEU) scheme updates NSW ESS (Energy Savings Scheme) bulletins EECA (NZ) news and publications MBIE (NZ) energy policy updates Australian federal DCCEEW energy efficiency announcements Clean Energy Regulator (SRES/STCs)

Standards:

Standards Australia new publications or amendments relevant to AS/NZS 4234, AS/NZS 5125 Standards New Zealand equivalent

Industry:

AIRAH (Australian Institute of Refrigeration, Air Conditioning and Heating) news Heat pump industry association announcements

Functional Requirements Feed display:

Articles displayed as cards in reverse chronological order (newest first) Each card shows: headline, source name, publication date, a 2-3 sentence summary, and a link to the original article Feed is paginated or infinite scroll - to be proposed by the developer

Filtering:

User can filter by market: All / Australia / New Zealand

User can filter by category: Regulatory / Standards / Industry Filters can be combined Default view shows all categories, all markets

Freshness:

Feed should update at least once per 24 hours

Timestamp showing when feed was last refreshed should be visible

Saving / bookmarking:

User can bookmark an article for later reference

Bookmarked articles accessible from a separate saved view Bookmarks persist across sessions (stored against user account)

Basic keyword search across headlines and summaries within the feed

Out of scope for v1: full-text search of linked articles

Out of Scope (v1)

Email or push notifications for new articles AI summarisation of articles (consider for v2) User-configurable source preferences Comments or annotation on articles Automatic scheme change alerts (separate feature)

Data Model (indicative)

the developer to propose final schema, but at minimum each article record should store:

id headline summary (2-3 sentences, either scraped or AI-generated) source_name source_url published_date fetched_date market (AU / NZ / both) category (regulatory / standards / industry) is_bookmarked (per user)

Architecture Notes

Fetching logic should run as a scheduled background job (cron or equivalent), not on page load Sources that don’t have RSS feeds will require scraping - the developer to flag which sources need this and propose approach before building Summaries: where no summary exists in the source, the developer to propose whether to truncate body text or use an LLM call to generate one. Discuss before implementing. No authentication required to view the feed if the user is already logged into the platform

UI / UX Direction

Clean card-based layout, scannable at a glance

Source logo or favicon displayed on each card if available Unread indicator (bold or dot) for articles added since user’s last visit - optional, the developer to advise if complexity is high Mobile-responsive No specific design mockup provided for v1 - the developer to propose a wireframe before building

Acceptance Criteria The feature is done when:

Feed displays articles from at least 5 of the listed sources Articles are sorted newest first Market and category filters work correctly and can be combined Last-refreshed timestamp is visible and accurate User can bookmark an article and retrieve it from the saved view Keyword search returns relevant results Feed updates automatically on a 24-hour schedule without manual intervention Layout is mobile-responsive the developer has documented which sources use RSS vs scraping, and scraping logic is maintainable

Open Questions (to resolve before build starts)

Should the feed be visible to all logged-in users, or only EnergyAE staff in v1? Do we want AI-generated summaries from the start, or plain truncated text? Which sources have RSS feeds vs require scraping? the developer to audit and report back. Should bookmarks be per-user or shared across the EnergyAE team?