@leed-ai/cli 0.0.0-stage → 6.19.0

package/dist/static/templates/raw-content/README.md

@@ -0,0 +1,179 @@
+# Leed Site Management
+
+Thanks for choosing Leed!
+
+Managing your site is broken into two parts. The first is making changes here in your web browser. The second is much more advanced and provided for web developers.
+
+If you have any questions, please remember you can ask any time in our [discord server](https://discord.com/channels/1007477144630329424/1007477144630329427).
+
+## Web Browser Editing
+
+This allows you to edit your template files and directly control html, css and javascript that drives your site.
+
+Each time you save your files they will be pushed to your staging site. This may take about a minute after you hit save.
+
+After you validate that you are happy with the changes you have made you can promote your changes to production.
+
+The steps are as follows:
+
+1. Push the `Merge Changes to Prod` button
+2. The changes will be then be ready to go to the live site on the next site deployment.
+3. If you are ready for this to happen immediately you can go to the system settings and click `Force Publish`
+4. Your changes will be available on your primary website in approximately a minute.
+
+## Advanced Editing
+
+After completing this section you will be ready to develop your website locally.
+
+### Prerequisites
+
+1. Git **2.31 or newer** must be installed. Check with `git --version`. Your content repository access token is handed to git through its config environment, which older versions ignore — `leed site push` will tell you so and name the version if yours is too old.
+2. You must have [bun installed](https://bun.sh/docs/installation).
+
+### Installation
+
+Your developer access section (bottom left corner of the menu, under your personal profile) provides an installation script to run. It ensures your environment is setup correctly to use this cli. A few things are provided for your convenience:
+
+- **Claude Code skills** for AI-assisted site development
+- **VS Code workspace file** with project-specific settings
+- **VS Code tasks** for common build and development operations
+
+After installation, type `leed` at the command-line to verify it is available.
+
+The CLI itself is the public npm package `@leed-ai/cli`, so `npm i -g @leed-ai/cli` also installs it, with no access token. If you still have the old `@leed/site-management` package, replace it with `bun remove -g @leed/site-management && npm i -g @leed-ai/cli`.
+
+### Normal Workflow
+
+After getting your site setup with `leed site init` a normal workflow might look like this:
+
+* `leed site build` - Sanity check, to make sure your site is building as you would expect.
+* `leed site build --serve` - Builds your site and starts the server, which you can view your website at `http://localhost:8080`
+* Edit your templates, until you are happy with your changes.
+* Stop the server `<ctrl-c>`
+* `leed site validate` - Validate that your changes are all okay to move forward. Clear any errors and exceptions that may occur.
+* `leed site build` - This ensures that after you have fixed any potential validation issues your site is still working as you expect. This is your final chance to ensure you are happy with your changes.
+* `leed site commit -m "message explaining your changes"`
+* Now is when you use git. You will need to rebase and resolve any potential merge issues. Once this is complete you can proceed.
+* `leed site push` - This will push the changes and submit the change set to the CMS for the site to be updated.
+* Congratulations, you've just locally edited your website.
+
+#### Building Your Website
+
+```bash
+# run this command either in the site folder, or the raw-content folder
+leed site build
+```
+
+### Very Important Developer Details
+
+As we use a git repository to manage distribution of your site to you, it also provides the capability to handle things like merge conflicts, which you must be comfortable using git to handle.
+
+After you have made changes and tested them locally using `leed site validate` and `leed site build`, you can use `leed site commit` to save your changes.
+
+You can use most of the git commands directly. However these restrictions exist:
+
+* `git commit` => instead use `leed site commit`
+* `git add` => not needed, we automatically add all modified files after validation.
+* `git push` => instead use `leed site push`
+
+Any attempt to subvert using the `leed site commit` process is at your own risk, and it will be **your responsibility** if **you break your staging site** by **subverting our process** it will be up to you to fix your build for your staging site.
+
+After your changes are committed it is **your responsibility** to rebase and push your changes. We leave this task to you for the case where there are merge conflicts which need to be resolved by you. This is the price that must be paid for a local development environment.
+
+**Merge Commits** are not allowed into this repository. Rebase and fast-forward only commits are allowed.
+
+## Understanding the Folder Structure
+
+Within the `raw-content` folder, you will see a structure similar to the following:
+
+```bash
+src/
+    _data/              # data files used in providing data to render your website.
+        *.json
+
+    # Includes - these are *PARTIALS* or html fragments, and they are used in creating a complete webpage
+    _includes/
+        [file].hbs
+        header.hbs
+        footer.hbs
+
+    # Layouts - each of these should produce a complete webpage they will generally consist of using many other *PARTIALS*
+    _layouts/
+        empty.hbs       # The default layout: the page content and nothing else
+        ...
+        main.hbs
+        robots.hbs
+        sitemap.hbs
+
+    # EVERYTHING located in this folder gets a header placed on it - Cache-Control: immutable
+    static/
+        css/
+        images/
+        js/
+        webfonts/
+    [page-type]/        # One folder per page type, e.g. blog/ once you add a blog
+        title-of-a-page.md
+    404.hbs             # Layout for your website 404 page
+    index.hbs           # This is your home page
+    robots.hbs          # This is where you can specify how bots are allowed to interact with your site
+
+# Customize your tailwind configuration
+tailwind/
+    site.config.css
+
+# CI build pipeline (managed by Leed, do not modify)
+.ci/
+    build.sh
+```
+
+### _data
+
+All files here are read-only and only for reference for managing templates. You can modify them to test edge cases for your designs, but they cannot be committed and will be reverted.
+
+### Page Types
+
+A new site starts with a single page type, Root, which holds the pages at the top of your site. Add a blog or documentation with `/leed:create` in Claude, or create a page type in the CMS. When a page type has a path (e.g. `blog`), a folder will show up here named with that path. Everything in this folder is read-only, for reference purposes. When you create a new page by that page type, they will show up here after they are published, and not prior to that.
+
+### _includes
+
+All the `.hbs` files here are considered to be `partials`. This means that they are but a small part of what would be used to create an entire webpage on the website. For example, the `footer.hbs` contains only the part of the html that would end up at the bottom of every page on your site.
+
+### _layouts
+
+They are your actual layouts. Your site starts with `empty.hbs`, which renders the page content and nothing else, and it is the layout every new page type uses unless you choose another. The content comes from the CMS Page Editor; the html that makes a page type look the way you want lives here. The page type in the CMS sets which layout it uses, and that layout must exist in this folder: the CMS refuses a layout it cannot find, and `leed site validate` fails on one. `/leed:create` adds the layouts a blog or documentation needs. Name your own layouts whatever makes sense to you.
+
+### Tailwind
+
+We fully support using tailwind within your website. There are 2 starting files:
+
+* `site.config.css` - This is where you will put your custom css to be processed by tailwind. You can import from other files to keep your css organized.
+
+You can add more css files here. If you wanted to have your custom css for your menus in a separate file, like `menu.css`, you would add this line `@import "./menu.css";` to the very top of the `input.css`.
+
+### Editable Files
+
+You are allowed to add / edit the following:
+
+* Files ending with **.hbs**
+* All files in the ***static*** folder
+  * **EXCEPT:** *images/favicon-\**, *images/logo-\** - These are managed and stored via the CMS.
+* All files in the **tailwind** folder
+
+### READ-ONLY Files
+
+If you try to edit a file that is managed by the CMS, it will be rejected. Examples are:
+
+* All files in the **_data** folder
+* Generated **.html** files like those found in blog.
+* **\*.11tydata.json** files
+* All files in the root of `raw-content` (e.g. `bunfig.toml`)
+* The `.ci/` folder and its contents
+
+### Special Cases
+
+1. `/static` - Everything in this folder is permanently cached by a users web browser. All files located here will have a timestamp put on them to provided unique names to ensure files are not being modified in place.
+2. Font files: only woff2 are allowed. This is due to their compact and optimized nature. To add custom fonts for your website you can put them into `/static/fonts`. For more [information checkout wikipedia](https://en.wikipedia.org/wiki/Web_Open_Font_Format).
+3. Images: the purpose of images stored here should be for small little icons or special imagery like svg files which are on every page, located in the header or footer, and other similar use cases. If you are going to put an image into your header / footer, put them here. They need to be small.
+4. CSS: You are welcome to put custom css into `/static/css`, but remember the permanent caching note above.
+5. Any file over 500kb, will be rejected.
+6. If you are unsure if you should put something here, [just ask](https://discord.com/channels/1007477144630329424/1007477144630329427).

package/dist/static/templates/raw-content/_gitignore

@@ -0,0 +1,50 @@
+#
+# Primary dirs we control
+#
+.claude
+.vscode
+.husky
+
+#
+# Builder files
+#
+eleventyComputed.js
+src/_includes/leed
+leed-*.hbs
+leed-*.json
+# leed asset upload state, its .lock and .tmp-<pid> copies (hold resumable upload URLs)
+leed-assets*
+# The documented default source directory for `leed import markdown|html` (#406).
+# It is the user's own content, not site source: the import COPIES a cleaned set
+# into src/<pageTypeSlug>/ and leaves this directory read-only.
+leed-import/
+# Originals `leed import html` set aside: each <name>.html becomes <name>.md and
+# the original is renamed, so the site build does not pick it up. A derived
+# artifact of a conversion the user ran locally — `leed import clean` reverses it.
+# Suffixed on a real filename, so the glob is `*.html.bak`, not `.html.bak`.
+*.html.bak
+# Images a sandbox, /leed:design-import or site-migrate staged locally (#457). The
+# sandbox move uploads each one with `leed asset upload` and rewrites its references,
+# so an image staged here is never committed.
+src/static/images/tmp/
+src/static/js/l.*.js
+
+#
+# build artifacts / install files
+#
+.build
+node_modules
+package.json
+package-lock.json
+bun.lock
+
+#
+# Local AI agent configuration (leed mcp add)
+#
+.mcp.json
+
+#
+# Build result files
+#
+.leed-validation.json
+buildResults.json

package/dist/static/templates/raw-content/src/404.hbs

@@ -0,0 +1,21 @@
+---
+{
+    "title": "Page Not Found!",
+    "pageTypeId": "###PAGE_TYPE_ID###",
+    "pageId": "404",
+    "publishedAt": "###DATE###",
+    "modifiedAt": "###DATE###",
+    "permalink": "404.html"
+}
+---
+
+{{#>site-template}}
+
+{{!-- The page a missing URL lands on. Colors come from the site's --site-* tokens, which its theme points at its brand tokens. --}}
+<main class="px-6 py-16 text-center">
+    <h1 class="text-6xl font-bold text-(--site-header-1-color)">404</h1>
+    <h2 class="mt-4 text-2xl text-(--site-header-2-color)">Page Not Found!</h2>
+    <p class="mt-4 text-(--site-text-color)">The page you asked for is not here. It may have moved, or the link may be wrong.</p>
+</main>
+
+{{/site-template}}

package/dist/static/templates/raw-content/src/_data/autolink.json

@@ -0,0 +1 @@
+{}

package/dist/static/templates/raw-content/src/_data/ctaList.json

@@ -0,0 +1 @@
+{}

package/dist/static/templates/raw-content/src/_data/leedForms.json

@@ -0,0 +1 @@
+{}

package/dist/static/templates/raw-content/src/_data/menu.json

@@ -0,0 +1 @@
+{}

package/dist/static/templates/raw-content/src/_includes/footer.hbs

@@ -0,0 +1,18 @@
+{{!-- Start Footer Menu --}}
+<footer class="min-w-350 lg:px-16 mt-16 leed-colors" aria-labelledby="footer-heading">
+    <div class="flex border-t items-center justify-center leed-colors">
+
+        {{!-- This is an example of using tailwind css background image class provided in the tailwind.config.js --}}
+        <!--
+        <div class="flex footer-align space-x-6">
+            {{!-- This is a vanity shortlink that could point to your linkedin page --}}
+            <a href="/s/linkedin" target="_blank">
+                <span class="sr-only">LinkedIn</span>
+                <div class="w-6 h-6 svg-img bg-linkedin-light dark:bg-linkedin-dark hover:bg-linkedin-hover active:bg-linkedin-active"></div>
+            </a>
+        </div>
+        -->
+
+        <p class="py-6 px-6 mt-0 text-(--menu-footer-header-text-color)">© {{ year }} {{siteTitle}}. All rights reserved.</p>
+    </div>
+</footer>

package/dist/static/templates/raw-content/src/_includes/header-includes.hbs

@@ -0,0 +1,25 @@
+{{!--
+header-includes.hbs: the site's own additions to <head>, on every page.
+
+Leed's head partial, `leed/head.hbs`, renders this file first in <head>, on
+every page that calls it: the pages site-template.hbs wraps, Leed's
+unsubscribe pages, and the documentation and API pages. Those last are built
+on Leed's own documentation layouts, which are NOT wrapped in
+site-template.hbs, so a tag written there never reaches the documentation
+set. Written here, it reaches every page.
+
+There is nothing to turn on: no CMS flag and no plan tier. `leed/head.hbs`
+checks `templateExists "header-includes.hbs"`, so the file existing is what
+enables it.
+
+Put here what must be true on every page, docs included: a preload for a
+self-hosted web font (never a font host, which logs every visitor), site
+verification metas, analytics and
+other site-wide scripts (deferred), theme-color, the web manifest, and PNG
+and touch icon fallbacks. Tags only one kind of page needs go in that page
+type's layout. The description, canonical URL, social cards and the SVG
+favicon (the company favicon set in the CMS) are already written by
+`leed/head.hbs`.
+
+This file renders nothing until you add a tag below this comment.
+--}}

package/dist/static/templates/raw-content/src/_includes/header.hbs

@@ -0,0 +1,5 @@
+{{!-- Start Top Menu  --}}
+<header class="fixed w-full bg-[var(--site-header-bg-color,white)] grid justify-items-center z-40">
+    <!-- header menu goes here -->
+</header>
+{{!-- End Top Menu --}}

package/dist/static/templates/raw-content/src/_includes/site-template.hbs

@@ -0,0 +1,23 @@
+<!DOCTYPE html>
+<html lang="en" class="scroll-smooth js-focus-visible code-theme-atom-fruit font-noto-sans">
+
+<head>
+    <title>{{ title }} | {{ siteTitle }}</title>
+
+    <meta name="viewport" content="width=device-width">
+
+    {{> leed/head }}
+</head>
+<body class="flex flex-col h-screen antialiased text-base text-(--site-text-color) bg-(--site-bg-color)">
+{{> header }}
+
+{{!-- We need to set the top margin, because it changes based on the header height --}}
+<div class="grow mt-(--height-header)">
+{{!-- Start Body Content --}}
+{{> @partial-block}}
+{{!-- End Body Content --}}
+</div>
+
+{{> footer }}
+</body>
+</html>

package/dist/static/templates/raw-content/src/_includes/unsubscribe-DISABLED.hbs

@@ -0,0 +1,17 @@
+{{#>site-template}}
+{{!-- To enable customizing your unsubscribe page, rename this to unsubscribe.hbs --}}
+
+<main class="mt-12 mx-6 lg:mx-16">
+    <section id="unsubscribe" class="mx-auto max-w-3xl lg:max-w-7xl">
+        <div class="relative place-items-center mx-4 sm:mx-8">
+            <div class="content-box">
+                <h1 class="mb-8 text-center">{{ title }}</h1>
+                <div class="">
+                    {{> leed-unsubscribe-form }}
+                </div>
+            </div>
+        </div>
+    </section>
+</main>
+
+{{/site-template}}

package/dist/static/templates/raw-content/src/_includes/unsubscribed-DISABLED.hbs

@@ -0,0 +1,13 @@
+{{#>site-template}}
+{{!-- To enable customizing your unsubscribed page, rename this to unsubscribed.hbs --}}
+
+<main class="mt-12 mx-6 lg:mx-16">
+    <section id="unsubscribe" class="mx-auto max-w-5xl lg:max-w-8xl">
+        <div class="relative place-items-center mx-4 sm:mx-8">
+            <h1 class="mb-4 text-center">You've been unsubscribed.</h1>
+            <p class="text-center"><a href="/">Back to the homepage</a></p>
+        </div>
+    </section>
+</main>
+
+{{/site-template}}

package/dist/static/templates/raw-content/src/_layouts/empty.hbs

@@ -0,0 +1,2 @@
+{{!-- Empty Layout --}}
+{{{ process content }}}

package/dist/static/templates/raw-content/src/index.hbs

@@ -0,0 +1,21 @@
+---
+{
+  "title": "Your site is operational",
+  "publishedAt": "###DATE###",
+  "modifiedAt": "###DATE###",
+  "pageTypeId": "###PAGE_TYPE_ID###",
+  "pageId": "###NEW_PAGE_ID###"
+}
+---
+
+{{#>site-template}}
+
+{{!-- Links match GETTING_STARTED_LINKS in libs/data-types/src/automation/seeder/pages.ts --}}
+<h1>Your site is operational</h1>
+<p>{{ this.leedSiteEnv.env.domain }} is set up and publishing. Here is how to start building it:</p>
+<ul>
+  <li><a href="https://leed.ai/docs/getting-started/claude-plugin/">Get started with the Leed plugin for Claude</a></li>
+  <li><a href="https://leed.ai/docs/getting-started/cli/">Get started with the Leed CLI</a></li>
+</ul>
+
+{{/site-template}}

package/dist/static/templates/raw-content/src/robots.hbs

@@ -0,0 +1,9 @@
+---
+{
+    "permalink": "/robots.txt",
+    "eleventyExcludeFromCollections": true
+}
+---
+user-agent: *
+
+sitemap: {{ siteUrl }}/sitemap.xml

package/dist/static/templates/raw-content/tailwind/site/base.css

@@ -0,0 +1,44 @@
+/*
+  The default border color has changed to `currentColor` in Tailwind CSS v4,
+  so we've added these compatibility styles to make sure everything still
+  looks the same as it did with Tailwind CSS v3.
+
+  If we ever want to remove these styles, we need to add an explicit border
+  color utility to any element that depends on these defaults.
+*/
+h1 {
+  @apply font-extrabold text-4xl sm:text-6xl text-(--site-header-1-color);
+}
+
+h2 {
+  @apply font-bold text-3xl sm:text-4xl mt-6 text-(--site-header-2-color);
+}
+
+h3 {
+  @apply font-extrabold text-xl sm:text-2xl mt-5 text-(--site-header-3-color);
+}
+
+h4 {
+  @apply font-bold text-xl sm:text-xl mt-4 text-(--site-header-4-color);
+}
+
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+  letter-spacing: -0.025em;
+}
+
+p {
+  @apply mt-4;
+}
+
+a {
+  @apply text-(--site-anchor-text-color) hover:text-(--site-anchor-text-color-hover) active:text-(--site-anchor-text-color-active);
+}
+
+pre {
+  @apply mt-8;
+}

package/dist/static/templates/raw-content/tailwind/site.config.css

@@ -0,0 +1,3 @@
+@import "tailwindcss" source("../src");
+
+@import "./site/base.css" layer(base);

package/dist/static/templates/sandbox/_gitignore

@@ -0,0 +1,50 @@
+#
+# Primary dirs we control
+#
+.claude
+.vscode
+.husky
+
+#
+# Builder files
+#
+eleventyComputed.js
+src/_includes/leed
+leed-*.hbs
+leed-*.json
+# leed asset upload state, its .lock and .tmp-<pid> copies (hold resumable upload URLs)
+leed-assets*
+# The documented default source directory for `leed import markdown|html` (#406).
+# It is the user's own content, not site source: the import COPIES a cleaned set
+# into src/<pageTypeSlug>/ and leaves this directory read-only.
+leed-import/
+# Originals `leed import html` set aside: each <name>.html becomes <name>.md and
+# the original is renamed, so the site build does not pick it up. A derived
+# artifact of a conversion the user ran locally — `leed import clean` reverses it.
+# Suffixed on a real filename, so the glob is `*.html.bak`, not `.html.bak`.
+*.html.bak
+# Images a sandbox, /leed:design-import or site-migrate staged locally (#457). The
+# sandbox move uploads each one with `leed asset upload` and rewrites its references,
+# so an image staged here is never committed.
+src/static/images/tmp/
+src/static/js/l.*.js
+
+#
+# build artifacts / install files
+#
+.build
+node_modules
+package.json
+package-lock.json
+bun.lock
+
+#
+# Local AI agent configuration (leed mcp add)
+#
+.mcp.json
+
+#
+# Build result files
+#
+.leed-validation.json
+buildResults.json

package/dist/static/templates/sandbox/identity.json

@@ -0,0 +1 @@
+{ "companyId": "non-cms-company", "environment": "dev" }

package/dist/static/templates/sandbox/src/404.hbs

@@ -0,0 +1,21 @@
+---
+{
+    "title": "Page Not Found!",
+    "pageTypeId": "ph-pt-1",
+    "pageId": "404",
+    "publishedAt": "2026-01-01T00:00:00.000Z",
+    "modifiedAt": "2026-01-01T00:00:00.000Z",
+    "permalink": "404.html"
+}
+---
+
+{{#>site-template}}
+
+{{!-- The page a missing URL lands on. Colors come from the site's --site-* tokens, which its theme points at its brand tokens. --}}
+<main class="px-6 py-16 text-center">
+    <h1 class="text-6xl font-bold text-(--site-header-1-color)">404</h1>
+    <h2 class="mt-4 text-2xl text-(--site-header-2-color)">Page Not Found!</h2>
+    <p class="mt-4 text-(--site-text-color)">The page you asked for is not here. It may have moved, or the link may be wrong.</p>
+</main>
+
+{{/site-template}}

package/dist/static/templates/sandbox/src/_data/autolink.json

@@ -0,0 +1 @@
+[]

package/dist/static/templates/sandbox/src/_data/ctaList.json

@@ -0,0 +1 @@
+{}

package/dist/static/templates/sandbox/src/_data/labelList.json

@@ -0,0 +1,9 @@
+{
+  "ph-label-1": {
+    "name": "News",
+    "slug": "news",
+    "description": "Announcements and updates.",
+    "isSeries": false,
+    "visible": true
+  }
+}

package/dist/static/templates/sandbox/src/_data/leedForms.json

@@ -0,0 +1,20 @@
+{
+  "ph-form-1": {
+    "button": "Subscribe",
+    "formPrototype": "subscribe-blog",
+    "successCallback": "",
+    "failureCallback": "",
+    "leedAutofill": false,
+    "heading": "Our Newsletter",
+    "details": "Subscribe to receive our latest updates",
+    "fields": [
+      {
+        "name": "email",
+        "placeHolder": "Email",
+        "required": true,
+        "type": "email",
+        "value": ""
+      }
+    ]
+  }
+}

package/dist/static/templates/sandbox/src/_data/menu.json

@@ -0,0 +1,19 @@
+{
+  "Header Menu": {
+    "menuId": "ph-menu-1",
+    "items": [
+      {
+        "menuItemId": "ph-menuitem-1",
+        "name": "Home",
+        "title": "",
+        "target": "",
+        "href": "pageid:ph-page-1",
+        "submenu": []
+      }
+    ]
+  },
+  "Footer Menu": {
+    "menuId": "ph-menu-2",
+    "items": []
+  }
+}

package/dist/static/templates/sandbox/src/_data/pageTypeList.json

@@ -0,0 +1,14 @@
+{
+  "ph-pt-1": {
+    "slug": "",
+    "name": "Root Pages",
+    "layout": "empty.hbs",
+    "includeInFeeds": false,
+    "autolink": false,
+    "description": "Pages at the root of the website",
+    "sitemapPriority": 1,
+    "labelSiteMapPriority": 0.8,
+    "noRender": false,
+    "autopostNewPages": false
+  }
+}

package/dist/static/templates/sandbox/src/_data/searchIndexList.json

@@ -0,0 +1 @@
+{}

package/dist/static/templates/sandbox/src/_data/userList.json

@@ -0,0 +1,11 @@
+{
+  "ph-author-1": {
+    "firstName": "Sandbox",
+    "lastName": "Author",
+    "email": "author@example.com",
+    "biography": "A placeholder author. The move maps this record to a real user in your Leed account.",
+    "jobTitle": "Writer",
+    "visible": true,
+    "slug": "sandbox-author"
+  }
+}

package/dist/static/templates/sandbox/src/_includes/footer.hbs

@@ -0,0 +1,18 @@
+{{!-- Start Footer Menu --}}
+<footer class="min-w-350 lg:px-16 mt-16 leed-colors" aria-labelledby="footer-heading">
+    <div class="flex border-t items-center justify-center leed-colors">
+
+        {{!-- This is an example of using tailwind css background image class provided in the tailwind.config.js --}}
+        <!--
+        <div class="flex footer-align space-x-6">
+            {{!-- This is a vanity shortlink that could point to your linkedin page --}}
+            <a href="/s/linkedin" target="_blank">
+                <span class="sr-only">LinkedIn</span>
+                <div class="w-6 h-6 svg-img bg-linkedin-light dark:bg-linkedin-dark hover:bg-linkedin-hover active:bg-linkedin-active"></div>
+            </a>
+        </div>
+        -->
+
+        <p class="py-6 px-6 mt-0 text-(--menu-footer-header-text-color)">© {{ year }} {{siteTitle}}. All rights reserved.</p>
+    </div>
+</footer>