Deneb ReactJs documentation

Updating

How to move from an earlier Deneb React version to 3.0, and how to keep your changes safe in future updates.

From an earlier version to 3.0

Version 3.0 is a full rebuild on Next.js. It is not an in-place update, so you cannot copy the new files over an old site.

The old version was a Vite app with React Bootstrap. It kept content in JavaScript and JSON files in src/. Version 3.0 keeps content in Markdown and YAML files in content/. Its folders, scripts and settings are all different.

To move:

  1. Download version 3.0 and run it in a new folder. See Install and run.
  2. Copy your words and details into the new files:
    • Site name, contact details and links go in content/site.yml.
    • Services go in content/services/, one file each.
    • Projects go in content/portfolio/, one file each.
    • Posts go in content/posts/, one file each, named YYYY-MM-DD-slug.md. Turn the old HTML post text into Markdown.
    • Pages are lists of sections in content/pages/.
  3. Copy your pictures into public/assets/img/.
  4. Move your colours and CSS into public/assets/css/custom.css. The old Sass variables are gone. See Branding.
  5. Connect the contact form again. See Forms and comments.
  6. Build with npm run build and upload out/.

Things that no longer exist in 3.0: comments, the Vite build folder (the output is now out/) and addresses such as /service-details/<name>. Services are now at /services/<name>/ and projects at /portfolio/<name>/. If the old site was live, set up redirects from the old addresses on your host, so links and search results still work.

Future updates

Your changes live in three places, so an update never has to touch them: content/, public/assets/css/custom.css and public/assets/img/.

When a new version of the theme comes out:

  1. Download it into a new folder.
  2. Copy your content/, custom.css and pictures over the new ones.
  3. Compare the other files you changed, such as components/ and app/, with the new version.
  4. Run npm install, then npm run build.

If you keep your project in Git, you can instead commit the new theme files and review what changed.

Do not edit deneb.css or deneb.rtl.css. Updates replace them.

Packages

package.json pins exact versions, for example next 16.4.6. Keep them as they are for a stable site. To update a package yourself, change its version, run npm install and test the build.