src/data/pages/. Each file declares the page’s SEO metadata and an ordered array of sections — typed, data-carrying building blocks that the renderer assembles into the final layout. Editing a page is as simple as updating that JSON file, then rebuilding or letting Studio auto-save the change for you.
Page File Structure
A page file has four top-level keys:The meta Object
The meta object controls the <title> and <meta name="description"> tags for the page. Keep titles between 50–60 characters and descriptions between 130–155 characters for best SEO results.
Sections
Each entry in thesections array is an object with three keys:
The settings Object
The settings object lets you adjust the vertical breathing room around any section without touching CSS.
Available Pages
The table below lists every page shipped with next-dev-portfolio, its URL path, and the JSON file you edit to change it.Available Section Types
Editing a Page
You can edit pages in two ways:1
Open the JSON file directly
Navigate to
src/data/pages/ in your editor and open the file for the page you want to change (for example, home.json). Edit the meta fields or the data payload of any section, then save.2
Rebuild to apply changes
Run the build command to bake your updated JSON into Alternatively, start the development server and view changes live:
public/:3
Or use Studio
Navigate to
/admin in your running dev server to open the visual Studio editor. Edit sections using the form UI and click Save. When Save2Repo is active, Studio writes the JSON directly to src/data/pages/ and triggers an automatic bake — no manual build step required.After editing JSON files directly (outside Studio), always run
npm run build before deploying. Studio with Save2Repo active handles this automatically on every save.Complete Example: Editing the Home Page Hero
The example below shows a completehome.json with all five sections from the default template. The data shape for each section type is shown as-is — edit only the field values, not the field names.