Move your site into src/custom/site

Older versions of Arc CMS had no website folder of the app's own, so a site changed its home page, header, footer, templates and styles by editing files in public/. Those are Arc CMS's files now. npm run arc:own-site moves your changes into src/custom/site/ and puts Arc CMS's files back, so later updates merge cleanly.

Is this you?

Yes, if your copy has edits in any of these. npm run check:core lists them, and points here.

Files you never changed stay Arc CMS's, so you keep getting its improvements to them.

Move it

1. Merge the newer Arc CMS, as on Upgrade Arc CMS. Leave conflicts in public/ open: the command settles them.

   git merge upstream/main

2. See the plan. Nothing changes yet:

   npm run arc:own-site

   It lists each file and where it goes, how many of Arc CMS's files it puts back, and what to check by hand.

3. Do it:

   npm run arc:own-site -- --write

   A file that already exists in src/custom/site/ is never overwritten; the command names it instead.

4. Look at the site with npm run dev next to the live one, and fix what the plan listed under "Check by hand".

5. Check and commit:

   npm run check:core

   No file in public/ should be listed now. Finish the merge commit.

6. Deploy everything, so the published pages are built from the new files. Run the guided deploy and choose Everything:

   npm run deploy

   After the website deploy it publishes every page again by itself. If you deploy the website with options instead (npm run deploy -- --only hosting), it keeps the published pages but does not publish them again: run npm run seed:dev afterwards for the default project, or npm run seed:prod, which always publishes to the production project.

Your home page

The old home page was an Angular template. The command turns it into a plain HTML page (see Build your home page):

• [contentType]="'articles'" becomes content-type="articles", and the same for other fixed values;
• ngSrc becomes src, and assets/… becomes /assets/…, so images also load at /hi/;
• it gets a <head> with the title and description it had: from index.html, or for another language from its old home component;
• if you never edited main.css, the old main.css it was styled with comes along as src/custom/site/assets/home.css, linked from the page. If you did edit it, your whole main.css becomes src/custom/site/site.css instead, which every page loads, and there is no home.css. Arc CMS's own main.css now styles only the body, header and footer.

Angular syntax with no plain HTML version, such as {{ … }}, (click) or @if, is left in place and listed with its line number. Replace it with plain HTML, a data-arc-t text or your own script.

What it leaves to you

• An edit to an Arc CMS file the site folder cannot replace, such as public/assets/js/arc-search.js: the command puts Arc CMS's file back and names it. Your version is still in git history. If you need the change, ask for it in Arc CMS as an option (see Keep core untouched).
• Old home components for other languages in src/app/pages/home-i18n/: delete them and their routes in src/app/app.routes.ts. A home page in another language is now just home.{lang}.html.
• Template overrides saved in the database by very old versions are no longer read. The templates in use are the files: Content, Templates shows them.

Next

Keep editing the site in its new place: Build your home page and Design templates.