Why JSON configuration matters
Most themes force you to edit component files to change simple things — a menu item, a footer link, a headline.
That is slow and error-prone. One wrong edit and the site breaks.
Finance App takes a different approach. Content and layout are controlled through JSON files in src/data/. You edit the JSON, the site updates.
What you can configure
Two files control most of the site:
src/data/config.json— navbar menus, footer content, site title, social linkssrc/data/home/home.json— landing page sections (hero, features, pricing, CTA)
Everything else is Markdown.
Example: adding a navbar link
Open src/data/config.json and find the nav_list array:
{
"nav": "About",
"icon": "/img/icon/nav-about.svg",
"link": "/about"
}Save, refresh, done. No component editing.
Example: changing the hero text
Open src/data/home/home.json and find the info_title and info_description fields:
{
"info_title": "Build modern sites with Astro JS",
"info_description": "Finance App is a multipurpose Astro JS theme..."
}Change the text. Save. The landing page updates.
Why this is useful
- For developers — clients can update content without touching code
- For teams — writers and marketers can edit the site directly
- For freelancers — faster project handoff, fewer support requests
- For buyers — no need to learn Astro to update a menu
What still needs code
JSON handles content and layout. If you need new components, new pages with unique structure, or custom logic, you will edit .astro files.
But for most updates — text, links, menus, images, section titles — JSON is enough.
Get Finance App
One-time purchase. Lifetime updates included. No subscriptions.
