jekyll-theme-centos 2.52.0.beta.84 → 2.52.0.beta.85

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 448a42486b828fbecd350515f5e057af86a319c9c9c30ccf3a7453987ecede97
-  data.tar.gz: 4a6cb2d918da78ce6878b9ebf7b1e55247e051165d41e98efba7df40a3798623
+  metadata.gz: 6b26c32164c0114ea621d445ceb40c7a569158712db0206f96f07c4aefc038d3
+  data.tar.gz: ab2ee634b6635b3f9c0e0ff52087b9256ec4727526b602c75781d213814b0e6e
 SHA512:
-  metadata.gz: 46997dc9b5bbf89c184eafa06f6f7200d543426bdb124c2dadfc22a13e33dbe30e7ed30e7c2a0c12f433ee40b46b0451fe5f4168c72d6a888e349f63259e2526
-  data.tar.gz: 254fd2c07eada323cf5ec6e734651880b55b13f2a8fd6efd4fad8c4b5b0c71870d2e3efbbad00329c90f230af99fc2cda1a8e005013bceec251213f006cac14c
+  metadata.gz: d36db093009d770ce36ab9490e8901f36e079d60294b60f922cd8d6ebdbebe49143f72706268b0ba948ad282ebc192be7b7c356a4b14a5ca63a5238a964cca20
+  data.tar.gz: 5d29d270aed80d3f1da128db0e1db86b23798f7b70b0a5495133bf16fd103d72b558cc4533f51675752d6a9e2e8cef3e284bb3c61adf635676d5a23e01d9be76

data/_config.yml

@@ -40,14 +40,6 @@ baseurl: ""
 # all you need to build jekyll sites with jekyll-theme-centos.
 theme: "jekyll-theme-centos"
 
-# site.component_data_dirname - Set the directory name where the navbar data
-# files is stored. For example, if the navbar file is at
-# `_data/base/navbar.yml', the value you need to provide here is `base'. For
-# consistency purposes, the value of this variable is overriden each time the
-# pipeline runs using the value of ${CI_PROJECT_NAME##jekyll-theme-centos-}
-# variable.
-#component_data_dirname: ""
-
 # site.defaults - Set global default values.
 defaults:
   # Asset files - prevent from being treated as pages and localized
@@ -79,6 +71,7 @@ defaults:
       with_project: false
       with_bits: false
       with_event: false
+      with_calendar: false
       with_title: true
       with_preamble: true
       with_toc: true

data/_data/base/calendar_schema.yml

@@ -0,0 +1,156 @@
+title: Event Calendar Addon Configuration
+description: >-
+  Schema for configuring the external Event Calendar JS library addon
+  (@event-calendar/build, formerly vkurko/calendar), used to render
+  interactive calendar views (month, week, list) from event data.
+type: object
+properties:
+  with_calendar:
+    type: boolean
+    default: false
+    description: >-
+      Enables or disables the Event Calendar addon. Set to `true` (default)
+      to load the necessary CSS and JavaScript files; set to `false` to
+      disable.
+  with_calendar_data:
+    type: object
+    description: >-
+      The configuration object containing version, integrity checks, and
+      default behavior settings for the Event Calendar library.
+    properties:
+      version:
+        type: string
+        default: "5.12.0"
+        description: >-
+          The @event-calendar/build version to load from jsDelivr
+          (e.g., `5.12.0`). This value is sourced from the package's
+          [npm releases](https://www.npmjs.com/package/@event-calendar/build).
+      css_integrity:
+        type: string
+        default: "sha384-5OjKEq4IUsR96wC/J0fB3WgMd7ZdsjiPyid1vtIlPlvF/+ejb/2FzrZvaFaBT0mj"
+        description: >-
+          The Subresource Integrity (SRI) CSS checksum (`sha384-...`) for
+          the specific Event Calendar version used. This is essential for
+          ensuring the integrity of the loaded CSS resource.
+      script_integrity:
+        type: string
+        default: "sha384-BCmNKxNY/4PzGJZW9hkN1WE25izUyjMcuzOoWcxqgiDD7iSdNxI4PYVYzaTsvDig"
+        description: >-
+          The Subresource Integrity (SRI) JavaScript checksum (`sha384-...`)
+          for the specific Event Calendar version used. This ensures the
+          integrity of the loaded JavaScript file.
+      view:
+        type: string
+        default: "dayGridMonth"
+        description: >-
+          The default calendar view (e.g., `dayGridMonth`, `timeGridWeek`,
+          `listWeek`).
+      header_toolbar_start:
+        type: string
+        default: "title"
+        description: >-
+          Content of the header toolbar's start section. See the Event
+          Calendar header toolbar documentation for valid content (view
+          names joined by commas, `title`, `today`, `prev`, `next`).
+      header_toolbar_center:
+        type: string
+        default: ""
+        description: Content of the header toolbar's center section.
+      header_toolbar_end:
+        type: string
+        default: "dayGridMonth,timeGridWeek,timeGridDay,listMonth today prev,next"
+        description: Content of the header toolbar's end section.
+      button_text_month:
+        type: string
+        default: "Month"
+        description: Label for the `dayGridMonth` view button.
+      button_text_week:
+        type: string
+        default: "Week"
+        description: Label for the `timeGridWeek` view button.
+      button_text_day:
+        type: string
+        default: "Day"
+        description: Label for the `timeGridDay` view button.
+      button_text_list:
+        type: string
+        default: "List"
+        description: Label for the `listMonth` view button.
+      button_text_today:
+        type: string
+        default: "Today"
+        description: Label for the "today" button.
+      events:
+        type: array
+        description: >-
+          Optional calendar-specific event data, in the same item shape as
+          the event component's `with_event_data` (see
+          `src/YAML/event_schema.yml`). Set this to make the calendar
+          self-contained — it takes priority over the shared
+          `with_event_data`, which the calendar still falls back to when
+          this is absent. See the event data contract for the full
+          `events` → Event Calendar field mapping (identical either way).
+        items:
+          type: object
+          properties:
+            title:
+              type: string
+              description: The name or title of the event. This field is required.
+            description:
+              type: string
+              default: ""
+              description: A brief description of the event. Not used by the calendar view.
+            start:
+              type: string
+              description: >-
+                The event start, in ISO 8601 format: `YYYY-MM-DD` for an
+                all-day event, or `YYYY-MM-DDTHH:MM` to give it a specific
+                start time on that same day. Required.
+            end:
+              type: string
+              default: ""
+              description: >-
+                The event's inclusive end, in the same ISO 8601 format as
+                `start` (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`). Omit for
+                single-day events — it defaults to `start`. For a timed
+                event, use the same date as `start` with the end clock time.
+            location:
+              type: string
+              default: ""
+              description: The city and country where the event takes place. Not used by the calendar view.
+            color:
+              type: string
+              default: secondary
+              description: >-
+                Sets the calendar pill's color via `var(--bs-<color>)`.
+                Defaults to `secondary`.
+              enum:
+                - primary
+                - secondary
+                - info
+                - warning
+                - danger
+                - success
+                - dark
+                - light
+            icon:
+              type: string
+              default: "fa-solid fa-calendar"
+              description: Not used by the calendar view.
+            link:
+              type: string
+              format: uri-reference
+              default: ""
+              description: >-
+                The URL the calendar event navigates to on click.
+          required:
+            - title
+            - link
+            - start
+          additionalProperties: false
+    required:
+      - version
+      - css_integrity
+      - script_integrity
+    additionalProperties: false
+additionalProperties: false

data/_data/base/card_schema.yml

@@ -113,10 +113,18 @@ properties:
           type: string
           default: ""
           description: Visible label text for the action button.
-        url:
+        link:
           type: string
           default: ""
-          description: Target URL the action button links to.
+          description: >-
+            The target URL the action button points to. This can be a relative
+            path (prefixed by site URL settings), a path using `../` (e.g.,
+            `../some-page`), or an absolute URL (e.g., `https://example.com`).
+            If omitted, an anchor link is generated from the `name` parameter
+            by converting to lowercase, replacing spaces with hyphens, and
+            removing the characters `"`, `'`, `?`, `&`, `#`, and `/` (e.g.,
+            "Back to Top" becomes "#back-to-top"), enabling in-page navigation
+            to section headings.
         icon:
           type: string
           default: ""

data/_data/base/event_schema.yml

@@ -28,29 +28,32 @@ properties:
           type: string
           default: ""
           description: A brief description of the event.
-        address:
+        start:
           type: string
-          default: ""
-          description: The street address of the event venue.
-        city:
+          description: >-
+            The event start, in ISO 8601 format: `YYYY-MM-DD` (e.g.
+            `2025-09-19`) for an all-day event, or `YYYY-MM-DDTHH:MM` (e.g.
+            `2025-09-19T14:00`) to give it a specific start time on that same
+            day. Used both to build the displayed date text and, when the
+            `calendar` component reads the same `with_event_data`, to place
+            the event on the calendar. Required.
+        end:
           type: string
           default: ""
-          description: The city where the event takes place.
-        date:
-          type: string # Changed from 'date' to 'string' for flexibility
-          default: ""
           description: >-
-            The event start and end date range as a readable string (e.g.,
-            `September 19 - 20, 2025`).
+            The event's inclusive end, in the same ISO 8601 format as
+            `start` (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`). For an all-day
+            event this is the last day the event runs; omit for single-day
+            events — it defaults to `start`. For a timed event, include the
+            same date as `start` with the end clock time — see the
+            `calendar` component's
+            [event data contract](/components/calendar/#event-data-contract)
+            for how each case converts to that component's own end
+            semantics.
         location:
           type: string
           default: ""
           description: The city and country where the event takes place (e.g., `Boston, USA`).
-        image_url:
-          type: string
-          format: uri
-          default: ""
-          description: The absolute or relative URL of an image related to the event (e.g., a banner or logo).
         color:
           type: string
           default: secondary
@@ -80,51 +83,9 @@ properties:
           description: >-
             The URL (relative or absolute) that the "Know more" button
             will link to, providing additional details about the event.
-        presentations:
-          type: array
-          description: A list of objects detailing the individual talks or sessions associated with this event.
-          items:
-            type: object
-            properties:
-              name:
-                type: string
-                description: The title of the presentation or talk.
-              summary:
-                type: string
-                description: A concise summary or abstract describing what the presentation is about.
-              author:
-                type: string
-                description: The name of the person who created or is delivering the presentation.
-              author_email:
-                type: string
-                format: email
-                description: The author's email address.
-              author_webiste:
-                type: string
-                format: uri
-                description: The author's website or profile URL.
-              date:
-                type: string
-                format: date-time
-                description: The presentation date and time (e.g., ISO 8601 format).
-              slides_url:
-                type: string
-                format: uri
-                description: The URL to the presentation slides (e.g., PDF or Google Slides link).
-              video_url:
-                type: string
-                format: uri
-                description: The URL to the presentation video recording.
-              information_url:
-                type: string
-                format: uri
-                description: A general URL for more information about the presentation.
-            required:
-              - name
-              - author
-            additionalProperties: false
       required:
         - title
         - link
+        - start
       additionalProperties: false
 additionalProperties: false

data/_data/base/project_schema.yml

@@ -22,7 +22,12 @@ properties:
         default: flex-column text-bg-dark bg-project
         description: >-
           Custom Bootstrap classes for the main project container, controlling
-          alignment, background, and text colors (e.g., `padding`, `bg-image`).
+          alignment, background, and text colors. The `bg-project` class is required
+          — it supplies the responsive background image (see src/SASS/_customization.scss)
+          that renders behind the card content; removing it leaves the container with
+          no background image, only whatever background color the remaining classes
+          (such as `text-bg-dark`) supply. For example, `flex-column` and `text-bg-dark`
+          control flex alignment and text/background colors respectively.
       content_class:
         type: string
         default: flex-column align-items-center py-5

data/_includes/base/bits.html.liquid

@@ -115,7 +115,7 @@ Component Layout:
             class         = ""
             icon          = "fa-solid fa-arrow-right"
             icon_position = "end"
-            url           = upstream_bit_index_page_url
+            link          = upstream_bit_index_page_url
             %}
           </div>
         {% endif %}
@@ -127,7 +127,7 @@ Component Layout:
       {%- for downstream_bit in downstream_bits | limit: 3 %}
         <div class="card border-{{ upstream_bit_color }}-subtle m-1">
           <div class="bg-{{ upstream_bit_color }} rounded-top">
-            <img src="{{ site.url }}{{ site.baseurl }}/assets/img/{{ downstream_bit.screenshot }}" class="card-img-top" alt="{{ downstream_bit.screenshot }}">
+            <img src="{{ site.baseurl }}/assets/img/{{ downstream_bit.screenshot }}" class="card-img-top" alt="{{ downstream_bit.screenshot }}">
           </div>
           <div class="card-body">
             <p class="h5 card-title">{{ downstream_bit.name }}</p>
@@ -135,7 +135,7 @@ Component Layout:
             {% for action in downstream_bit.actions | limit: 1 %}
               {% include base/link.html.liquid
               name          = action.name
-              url           = action.link
+              link          = action.link
               class         = upstream_bit_btn_class
               icon          = action.icon
               icon_position = action.icon_position

data/_includes/base/calendar-events.html.liquid

@@ -0,0 +1,49 @@
+{% comment %}
+================================================================================
+Template: Calendar Event Data Bridge
+Purpose: Emits the SAME event data the `event` component reads (with_event_data)
+as a JSON script tag, so a page can populate an Event Calendar instance
+without hand-writing (and duplicating) a separate JS events array. Data
+loading only — mapping this JSON into the Event Calendar library's own event
+shape, and calling EventCalendar.create(), stays the responsibility of
+whatever page or layout uses it (see calendar.html.liquid, which follows the
+same "loading only" split for the library itself).
+
+Design Logic:
+- Data bridge only: re-emits with_event_data as JSON, no field mapping or
+  rendering — see calendar-init.html.liquid for the mapping/rendering step
+- Shared data source: reuses event.html.liquid's exact fallback chain, so
+  both components always agree on the same resolved events
+- JSON script tag output: consumable by inline JS without hand-duplicating
+  the events array
+- Multi-instance support: "id" override lets multiple bridges coexist on
+  one page
+
+Optional Inputs:
+- id: script tag id (default: "centos-calendar-events") — override to run
+  more than one instance of this bridge on the same page (see
+  calendar-init.html.liquid, which derives a unique id per instance).
+
+Data Source Hierarchy (priority) — identical to event.html.liquid, so this
+bridge always reflects whatever with_event_data the page actually resolved:
+1. include.data
+2. page.with_event_data
+3. site.data.event
+4. site.data.base.event
+
+Output: <script type="application/json" id="...">, holding the with_event_data
+array unchanged (title, start, end, color, icon, link, description,
+location) — see the calendar component's event data contract documentation
+for how a page maps these fields into Event Calendar events.
+================================================================================
+{% endcomment %}
+
+{%- assign with_event_data = include.data
+| default: page.with_event_data
+| default: site.data.event
+| default: site.data.base.event
+%}
+
+{%- assign calendar_events_id = include.id | default: "centos-calendar-events" %}
+
+<script type="application/json" id="{{ calendar_events_id }}">{{ with_event_data | jsonify | replace: '</', '<\/' }}</script>

data/_includes/base/calendar-init.html.liquid

@@ -0,0 +1,148 @@
+{% comment %}
+================================================================================
+Template: Calendar Instance Initializer
+Purpose: Renders a ready-to-use Event Calendar instance — the events data
+(via calendar-events.html.liquid), a container element, and the
+initialization script that maps that data into the library's own event
+shape (see the calendar component's event data contract documentation) and
+calls EventCalendar.create(). Configured entirely from with_calendar_data /
+calendar_schema.yml, so customizing view, toolbar, or button labels is a
+front matter change — no script editing required.
+
+Design Logic:
+- Composition: wires together the events bridge, a container element, and
+  the initialization script — each piece stays a separate, single-purpose
+  include
+- Self-contained with graceful fallback: works standalone via
+  with_calendar_data.events, or falls back to the event component's
+  with_event_data when that's absent (see Event data source, below)
+- Config-driven: view, toolbar, and button labels all come from
+  with_calendar_data — no script editing required
+- Multi-instance support: a distinct "id" per include call renders
+  independent calendars on one page
+- Security: blocks javascript:/data:/vbscript: URIs before eventClick
+  navigation
+
+Required Inputs (per event item, from whichever event data source resolves
+below — the init script below reads event.title/event.start directly):
+- title: Event name/title
+- start: Event start (YYYY-MM-DD for an all-day event, or
+  YYYY-MM-DDTHH:MM to give it a specific start time on that same day)
+
+Optional Inputs:
+- id: container element id (default: "centos-calendar")
+- data: with_calendar_data override
+- event_data: explicit per-instance event array — highest priority, mainly
+  for running multiple independent calendars on one page (see below).
+  Forwarded to calendar-events.html.liquid's own "data" param.
+
+Data Source Hierarchy (priority) — identical to calendar.html.liquid:
+1. include.data
+2. page.with_calendar_data
+3. site.data.calendar
+4. site.data.base.calendar
+
+Event data source (priority) — this is what makes the component
+self-contained: a calendar-only page never has to touch with_event_data,
+but pages that already use the event component keep working unchanged:
+1. include.event_data — explicit override for this include call.
+2. with_calendar_data.events — calendar-specific events, resolved above.
+3. with_event_data — the event component's own data (via
+   calendar-events.html.liquid's own fallback chain: include.data (unused
+   here) → page.with_event_data → site.data.event → site.data.base.event).
+
+Multiple instances per page: pass a distinct id to each include call. The
+events bridge id is derived from it ("<id>-events"), so each instance's
+event data (and the events script tag emitting it) stays independent. Pass
+event_data (or a distinct with_calendar_data.events via data=) alongside a
+distinct id when instances should show different events; omit both to have
+every instance fall back to the same shared event source.
+================================================================================
+{% endcomment %}
+
+{%- assign with_calendar = include.with_calendar
+| default: page.with_calendar
+%}
+
+{%- if with_calendar %}
+
+{%- assign calendar_id = include.id | default: "centos-calendar" %}
+{%- assign calendar_events_id = calendar_id | append: "-events" %}
+
+{%- assign with_calendar_data = include.data
+| default: page.with_calendar_data
+| default: site.data.calendar
+| default: site.data.base.calendar
+%}
+
+{%- assign with_calendar_schema = site.data.base.calendar_schema.properties.with_calendar_data.properties %}
+
+{%- comment %} --- Defaults --- {% endcomment %}
+{%- assign calendar_view           = with_calendar_data.view                 | default: with_calendar_schema.view.default %}
+{%- assign calendar_toolbar_start  = with_calendar_data.header_toolbar_start  | default: with_calendar_schema.header_toolbar_start.default %}
+{%- assign calendar_toolbar_center = with_calendar_data.header_toolbar_center | default: with_calendar_schema.header_toolbar_center.default %}
+{%- assign calendar_toolbar_end    = with_calendar_data.header_toolbar_end    | default: with_calendar_schema.header_toolbar_end.default %}
+{%- assign calendar_btn_month      = with_calendar_data.button_text_month     | default: with_calendar_schema.button_text_month.default %}
+{%- assign calendar_btn_week       = with_calendar_data.button_text_week      | default: with_calendar_schema.button_text_week.default %}
+{%- assign calendar_btn_day        = with_calendar_data.button_text_day       | default: with_calendar_schema.button_text_day.default %}
+{%- assign calendar_btn_list       = with_calendar_data.button_text_list      | default: with_calendar_schema.button_text_list.default %}
+{%- assign calendar_btn_today      = with_calendar_data.button_text_today     | default: with_calendar_schema.button_text_today.default %}
+
+{%- assign calendar_events_data = include.event_data | default: with_calendar_data.events %}
+
+{% include base/calendar-events.html.liquid id=calendar_events_id data=calendar_events_data %}
+<div id="{{ calendar_id }}"></div>
+<script>
+document.addEventListener('DOMContentLoaded', function () {
+  var raw = JSON.parse(document.getElementById('{{ calendar_events_id }}').textContent);
+  var events = raw.map(function (event) {
+    var timed = event.start.indexOf('T') !== -1;
+    var start = event.start;
+    var end, allDay;
+    if (timed) {
+      end = event.end || event.start;
+      allDay = false;
+    } else {
+      var exclusiveEnd = new Date((event.end || event.start) + 'T00:00:00');
+      exclusiveEnd.setDate(exclusiveEnd.getDate() + 1);
+      end = exclusiveEnd.toISOString().slice(0, 10);
+      allDay = true;
+    }
+    return {
+      title: event.title,
+      start: start,
+      end: end,
+      allDay: allDay,
+      backgroundColor: 'var(--bs-' + (event.color || 'secondary') + ')',
+      extendedProps: { url: event.link }
+    };
+  });
+
+  EventCalendar.create(document.getElementById('{{ calendar_id }}'), {
+    view: {{ calendar_view | jsonify }},
+    headerToolbar: {
+      start: {{ calendar_toolbar_start | jsonify }},
+      center: {{ calendar_toolbar_center | jsonify }},
+      end: {{ calendar_toolbar_end | jsonify }}
+    },
+    buttonText: {
+      dayGridMonth: {{ calendar_btn_month | jsonify }},
+      timeGridWeek: {{ calendar_btn_week | jsonify }},
+      timeGridDay: {{ calendar_btn_day | jsonify }},
+      listMonth: {{ calendar_btn_list | jsonify }},
+      today: {{ calendar_btn_today | jsonify }}
+    },
+    events: events,
+    eventClick: function (info) {
+      // --- Security: block javascript:/data:/vbscript: URIs before navigation ---
+      var url = info.event.extendedProps.url;
+      var normalized = url ? String(url).replace(/[\x00-\x20]/g, '') : '';
+      if (url && !/^(javascript|data|vbscript):/i.test(normalized)) {
+        window.location.href = url;
+      }
+    }
+  });
+});
+</script>
+
+{%- endif %}

data/_includes/base/calendar.html.liquid

@@ -0,0 +1,70 @@
+{% comment %}
+================================================================================
+Template: Event Calendar Library Initialization Component
+Purpose: Loads the Event Calendar JS library (@event-calendar/build, formerly
+vkurko/calendar) from CDN with SRI integrity checks. Library loading only —
+initializing a calendar instance (mounting an element and supplying its
+events data) is the responsibility of whatever page or layout uses it.
+================================================================================
+
+Design Logic:
+- Library loading only: does not mount or configure a calendar instance —
+  see calendar-init.html.liquid for that
+- Split head/script output: "type" selects the CSS <link> (head) or JS
+  <script> (body) tag, capturing both fragments once and rendering by type
+- CDN-hosted with Subresource Integrity (SRI): version-pinned, integrity-
+  checked delivery
+
+Optional Inputs:
+- type: "head" for CSS include, "script" for JavaScript
+- version: Event Calendar version (e.g., "5.12.0")
+- css_integrity, script_integrity: SRI integrity hashes
+- data: Event Calendar configuration object
+
+Data Source Hierarchy (priority):
+1. include.data
+2. page.with_calendar_data
+3. site.data.calendar
+4. site.data.base.calendar
+================================================================================
+{% endcomment %}
+
+{%- assign with_calendar = include.with_calendar
+| default: page.with_calendar
+%}
+
+{%- assign with_calendar_data = include.data
+| default: page.with_calendar_data
+| default: site.data.calendar
+| default: site.data.base.calendar
+%}
+
+{%- assign with_calendar_schema = site.data.base.calendar_schema.properties.with_calendar_data.properties %}
+
+{%- if with_calendar %}
+
+{%- comment %} === Presentation === {% endcomment %}
+{%- comment %} --- Defaults --- {% endcomment %}
+{%- assign calendar_version          = with_calendar_data.version          | default: with_calendar_schema.version.default %}
+{%- assign calendar_css_integrity    = with_calendar_data.css_integrity    | default: with_calendar_schema.css_integrity.default %}
+{%- assign calendar_script_integrity = with_calendar_data.script_integrity | default: with_calendar_schema.script_integrity.default %}
+
+{%- capture html_calendar_head %}
+  <link href="https://cdn.jsdelivr.net/npm/@event-calendar/build@{{ calendar_version }}/dist/event-calendar.min.css" rel="stylesheet" integrity="{{ calendar_css_integrity }}" crossorigin="anonymous" referrerpolicy="no-referrer" />
+{%- endcapture %}
+
+{%- capture html_calendar_script %}
+  <!-- Event Calendar Library -->
+  <script src="https://cdn.jsdelivr.net/npm/@event-calendar/build@{{ calendar_version }}/dist/event-calendar.min.js" integrity="{{ calendar_script_integrity }}" crossorigin="anonymous" referrerpolicy="no-referrer" defer></script>
+{%- endcapture %}
+
+{%- comment %} --- HTML --- {% endcomment %}
+{%- assign type = include.type %}
+{%- case type %}
+{%- when "head" %}
+  {{ html_calendar_head }}
+{%- when "script" %}
+  {{ html_calendar_script }}
+{%- endcase %}
+
+{%- endif %}

data/_includes/base/card.html.liquid

@@ -17,7 +17,7 @@ Optional Inputs:
 - color: Color scheme for styling (default: "primary")
 - image, icon, screenshot: Visual elements
 - name, description: Text content
-- actions: Array of action buttons [{name, url, icon}]
+- actions: Array of action buttons [{name, link, icon}]
 - All image/icon/name/description have customizable CSS classes
 
 Data Source:
@@ -90,7 +90,7 @@ Data Source:
       class         = card_actions_btn_class
       role          = "button"
       name          = action.name
-      url           = action.url
+      link          = action.link
       icon          = action.icon
       icon_position = action.icon_position
       -%}