What Is Dynamic Data? Real-World Examples

Dynamic data is content loaded from a database or an external source, not hard-coded into the page. Static content stays the same until someone edits it.

Example: a Facebook comment. When you submit a comment, it’s saved to a database. The page then fetches it from there and displays it.

In Bricks, that database is WordPress. Posts, pages, users, and custom fields all live in the WordPress database.

Live counters. Numbers like “Active Projects” or “Events in the last 24 hours” update on their own as data changes. Updating them by hand would be impossible to keep up with.

Not everything needs to be dynamic. Marketing copy like “100% GDPR compliant” can stay static. Some static content just looks dynamic.

Dynamic data tags show values. They pull a single piece of data, such as a title, date, excerpt, featured image or custom field, into an element.

Query loops show lists. They repeat one design for every item, like a blog grid. A new post appears in the list automatically.

Templates control layout. In Bricks, you can build single post, archive, header, footer, and popup templates. Every blog post or customer story shares one template and only the data changes.

Archive vs. single:

• Archive: the list of all items, like the blog page or the customer stories page.

• Single: the page for one item, like a single post or a single customer profile.

Custom post types (CPTs) go beyond WordPress’s built-in posts and pages. Examples: Customers, Projects, Case Studies. They’re usually set up with plugins like ACF or Meta Box.

External data. You can fetch data from outside services through their APIs, such as GitHub stars, and display it with a query loop.

Example: a feedback board. Users submit ideas to the database, admins approve, reject, draft, or trash them, and visitors can upvote them. It’s a full dynamic data cycle.

Takeaway: On any website you visit, ask what’s static and what’s coming from a database. That habit makes the rest of the course easier to follow.