ultimate-jekyll-manager 0.0.47 → 0.0.49

package/.claude/settings.local.json

@@ -0,0 +1,41 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(mv:*)",
+      "Bash(npm run build:*)",
+      "Bash(mkdir:*)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/lib/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/test/tags/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)",
+      "Read(/Users/ian/Developer/Repositories/ITW-Creative-Works/jekyll-uj-powertools/**)"
+    ],
+    "deny": []
+  }
+}

package/CLAUDE-pages.md

@@ -0,0 +1,19 @@
+CLAUDE
+
+I need help designing the flow of the page/theme/layout system.
+
+src/defaults/src/pages
+* These pages are copied over to new sites when they are setup with Ultimate Jekyll so the user can have a site up and running instantly.
+* For example, "src/defaults/src/pages/legal/terms.md" is copied to the consuming project so they have a terms of service page ready to go. You can see it uses the layout "blueprint/legal/terms"
+
+src/defaults/dist/_layouts/blueprint/legal/terms.md
+* This is the layout file for the terms of service page. It basically just has the ToS text.
+* You can see it uses the layout "themes/[ site.theme.id ]/frontend/core/minimal" (id is set in a gulp task)
+
+So: this means that every theme must have a "frontend/core/minimal" layout that can be used for the terms of service page.
+* This is a good system but can quickly get out of hand if we need many different layouts.
+* For example, I want to make a contact page. Now, we cant do it the same way because we need an actual contact form instead of just text.
+
+Side note: "src/defaults/dist/pages" these pages are copied to the consuming project AS DEFAULTS and anything in the user's project will override the defaults.
+
+My idea is that in the theme frontend folder, we can hve some "base" layouts like "src/defaults/dist/_layouts/themes/bootstrap/frontend/core/minimal.html" and then one for each complex page like "src/defaults/dist/_layouts/themes/bootstrap/frontend/contact.html".

package/CLAUDE-pages2.md

@@ -0,0 +1,18 @@
+I need help designing some pages for Ultimate Jekyll.
+
+Heres some notes
+* All pages you design should USE BOOTSTRAP 5.3.1 and be responsive. Use Bootstrap classes for layout and styling
+  * Layouts, grids, sectioons, dropdowns, buttons, etc.
+* Bootstrap is already included in the project, so you can use its classes directly.
+* Avoid using custom CSS unless absolutely necessary.
+* Use proper classes for light/dark mode support (avoid bg-light/bg-dark and use classes like bg-body-secondary, bg-body-tertiary, etc.)
+
+Page html location:
+* src/defaults/dist/_layouts/themes/bootstrap/frontend/pages/{page}.html
+* These pages hoist a layout that includes header and footer so JUST FOCUS ON THE CONTENT OF THE PAGE.
+
+Page JS location:
+* src/assets/js/pages/{page}/index.js
+
+Page CSS location:
+* src/assets/css/pages/{page}/index.scss

package/CLAUDE.md

@@ -0,0 +1,46 @@
+# Identity
+This is Ultimate Jekyll, it is a template project that other "consuming" projects can use to build a Jekyll site. It comes installed as an NPM module and is helpful for setting up, configuring, and maintaining a Jekyll site with best practices in mind.
+
+It is not a stand-alone project, but rather a collection of components that can be used to build a Jekyll site quickly and efficiently.
+* You cannot use `npm start` or `npm run build` in this project.
+
+## Structure
+Ultimate Jekll has the following structure:
+src/gulp/tasks = Gulp tasks that are used to build the Jekyll site.
+src/defaults/src = Default source files that can be used as a starting point for a Jekyll site and ARE meant to be edited by the user. They are copied to the consuming project's "src" directory.
+src/defaults/dist = Default distribution files that can be used as a starting point for a Jekyll site and NOT meant to be edited by the user. They are copied to the consuming project's "dist" directory.
+
+The "consuming" project has the following structure:
+"src" = Compiled to "dist" with npm
+"dist" = Compiled to "_site" with Jekyll.
+
+Other Ultimate Jekyll Components:
+src/assets/css/ultimate-jekyll-manager.scss = Main stylesheet used by Ultimate Jekyll to style the site
+src/assets/css/global = Global styles that are used by Ultimate Jekyll
+src/assets/css/pages = Page-specific styles that are used by Ultimate Jekyll
+* If you are making a page, put the styles in this directory like so: `src/assets/css/pages/[page-name]/index.scss`
+
+src/assets/js/ultimate-jekyll-manager.js = Main JavaScript file used by Ultimate Jekyll to manage the site
+src/assets/js/pages = Page-specific JavaScript files that are used by Ultimate Jekyll
+* If you are making a page, put the JavaScript in this directory like so: `src/assets/js/pages/[page-name]/index.js`
+
+src/assets/themes = Theme scss and js files that are can be picked and used by the consuming project.
+
+## SOME SPECIAL LIQUID FUNCTIONS:
+* uj_content_format = A custom liquid filter that formats the content like so: first, it LIQUIFIES the content, then, if it's a markdown file, it runs MARKDOWNIFY.
+* iftruthy = a custom liquid tag that checks if a variable is truthy in JavaScript terms, meaning it checks if the variable is not null, undefined, or an empty string. Use it like this: `{% iftruthy variable %}`. But it DOES NOT SUPPORT any logical operators and does not support `else` statements. But you CAN put sub-statements inside it.
+* iffalsy = same but opposite of iftruthy.
+* page.resolved = a custom page object property of all site, layout, and page variables deeply merged together, with page variables taking precedence over layout, and layout variables taking precedence over site variables. This allows a system of site defaults, layout overrides, and page-specific overrides.
+
+### Specifics:
+* {% uj_icon icon-name, "fa-md" %} = Custom tag for inserting fontawesome icons. "icon-name" can be a string or a variable. If its a string, put it in quotes like "rocket" (dont include "fa-")
+
+## CSS
+DO NOT USE `bg-light`, `bg-dark`, `text-light`, or `text-dark`. We support BOTH light and dark mode, so instead use `bg-body`, `bg-body-secondary`, `bg-body-tertiary`, `text-body` and for buttons you can use `btn-adaptive` or `btn-outline-adaptive`.
+These classes adapt to light and dark mode automatically.
+
+## Audits
+I may ask you to help me fix problems identified by the AUDIT TASK (@src/gulp/tasks/audit.js)
+* In that case, please LOOK AT THE AUDIT FILES (Which I will provide the location to) and help me fix the issues ONE BY ONE.
+* Make a TODO list for each category in the audit, then read the ENTIRE AUDIT file and make a plan for what items in that category need to be fixed.
+* Remember, these are BIG AUDIT FILES, so you will have to tackle them in parts. DO NOT TRY TO FIX EVERYTHING AT ONCE.

package/README.md

@@ -69,7 +69,14 @@ Here are some examples:
 
 ### Run the `audit` task:
 ```bash
+# Run the audit task
 npx uj audit
+
+# Run with a Lighthouse URL (defaults to "/" if not provided)
+npx uj audit -- --lighthouseUrl="/contact"
+
+# Add autoExit to continue developing and testing AFTER the audit
+npx uj audit -- --lighthouseUrl="/contact" --autoExit=false
 ```
 
 ### Run the `translation` task:
@@ -79,6 +86,25 @@ GITHUB_REPOSITORY=XXX \
 UJ_TRANSLATION_CACHE=true \
 npx uj translation
 ```
+
+### Run the `imagemin` task:
+Test image optimization with GitHub cache in development mode:
+```bash
+# Test with GitHub cache (requires GH_TOKEN and GITHUB_REPOSITORY)
+GH_TOKEN=XXX \
+GITHUB_REPOSITORY=XXX \
+UJ_IMAGEMIN_CACHE=true \
+npx uj imagemin
+
+# Or run locally without cache
+npx uj imagemin
+```
+The imagemin task will:
+- Process images from `src/assets/images/**/*.{jpg,jpeg,png}`
+- Generate multiple sizes (1024px, 425px) and WebP formats
+- Cache processed images in `uj-imagemin` branch (when using GitHub cache)
+- Skip already processed images on subsequent runs
+
 <!-- Developing -->
 ## 🛠 Developing
 1. Clone the repo to your local machine.
@@ -87,3 +113,133 @@ npx uj translation
 npm install
 npm run prepare:watch
 ```
+
+### Run the `blogify` task:
+Create 12 test blog posts in the `_posts` directory with the `blogify` task. This is useful for testing and development purposes.
+```bash
+npx uj blogify
+```
+
+## Page Frontmatter
+You can add the following frontmatter to your pages to customize their behavior:
+
+### All pages
+```yaml
+---
+# Layout and Internals
+layout: themes/[ site.theme.id ]/frontend/core/minimal # The layout to use for the page, usually 'default' or 'page'
+permalink: /path/to/page # The URL path for the page, can be relative
+
+# Control the page's meta tags
+meta:
+  index: true # Set to false to disable indexing by search engines
+  title: 'Page Title' # Custom meta title for the page
+  description: 'Page description goes here.' # Custom meta description for the page
+  breadcrumb: '' # Custom breadcrumb for the page
+
+# Control the page's theme and layout
+theme:
+  nav:
+    enabled: true # Enable theme's nav on the page
+  footer:
+    enabled: true # Enable theme's footer on the page
+  body:
+    class: '' # Add custom classes to the body tag
+    main:
+      class: '' # Add custom classes to the main tag
+  head:
+    content: '' # Injected at the end of the head tag
+  foot:
+    content: '' # Injected at the end of the foot tag (inside <body>)
+---
+```
+
+### Post pages
+```yaml
+---
+# Post pages
+post:
+  title: "Post Title" # Custom post title for the page
+  description: "Post description goes here." # Custom post description for the page
+  author: "author-id" # ID of the author from _data/authors.yml
+  id: 1689484669 # Unique ID for the post, used for permalink
+---
+```
+
+### Team Member pages
+```yaml
+---
+# Team Member pages
+member:
+  id: "member-id" # ID of the team member from _data/team.yml
+  name: "Member Name" # Name of the team member
+---
+```
+
+### Special Class
+`uj-signin-btn`: Automatically handles signin (just add `data-provider="google.com"` to the button)
+`uj-signup-btn`: Automatically handles signup (just add `data-provider="google.com"` to the button)
+
+`uj-language-dropdown`:
+`uj-language-dropdown-item`
+
+### Special Query Parameters
+
+#### Authentication
+* `authReturnUrl`: Redirects to this URL after authentication.
+
+#### Testing Parameters
+
+##### Account Page (`/account`)
+* `_test_subscription`: Override subscription data for testing (e.g., `_test_subscription=premium`)
+* `_test_prefill=true`: Adds fake test data for development:
+  - Inserts fake referral data in the Referrals section
+  - Inserts fake session data in the Security section (active sessions)
+
+##### Checkout Page (`/payment/checkout`)
+* `_test_appId`: Override the application ID for testing (e.g., `_test_appId=test-app`)
+* `_test_trialEligible`: Force trial eligibility status:
+  - `_test_trialEligible=true`: User is eligible for trial
+  - `_test_trialEligible=false`: User is not eligible for trial
+* `_test_cardProcessor`: Force a specific payment processor for testing (e.g., `_test_cardProcessor=stripe` or `_test_cardProcessor=paypal`)
+
+### Icons
+* Fontawesome
+  * https://fontawesome.com/search
+* Flags
+  * https://www.freepik.com/icon/england_4720360#fromView=resource_detail&position=1
+* More
+  * Language
+    * https://www.freepik.com/icon/language_484531#fromView=family&page=1&position=0&uuid=651a2f0f-9023-4063-a495-af9a4ef72304
+
+### Webpack
+## Dev Flags
+Add this to any js file to ONLY run in development mode (it will be excluded in production builds):
+```
+  /* @dev-only:start */
+  {
+    // Your development-only code goes here
+  }
+  /* @dev-only:end */
+```
+
+> This project is "ultimate-jekyll", an NPM module that helps   │
+│   streamline development of Jekyll websites. A "consuming       │
+│   project" will require this NPM module to take advantage of    │
+│   its features like automatic folder structure setup, themes,   │
+│   and default pages to get a website up and running in          │
+│   seconds, while allowing further customization down the line.  │
+│   Right now i am struggling on the theme portion of this        │
+│   project. I want the user to be able to define the theme in    │
+│   their _config.yml (which currently they do by setting         │
+│   theme.id). I have some themes from the official bootstrap     │
+│   team. usually a theme comes with a frontend, a backend/admin  │
+│   dashboard, and docs. these 3 subparts of the theme have       │
+│   different html structure and css and js requirements. so i    │
+│   need a super easy system that allows me to make a file in     │
+│   the consuming project, say its the index.html for example,    │
+│   and i should easily be able to put which subseciton (or       │
+│   target as i call it) of the theme to use. so for an agency    │
+│   website i will probably use the frontend target, while for a  │
+│   chat app i will probably use the backend target. however, i   │
+│   need to be able to use

package/TODO-Claude.rtf

@@ -0,0 +1,105 @@
+{\rtf1\ansi\ansicpg1252\cocoartf2822
+\cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fnil\fcharset0 Menlo-Regular;\f1\fnil\fcharset0 .AppleSystemUIFontMonospaced-Regular;}
+{\colortbl;\red255\green255\blue255;\red0\green0\blue0;\red155\green162\blue177;\red197\green136\blue83;
+\red136\green185\blue102;}
+{\*\expandedcolortbl;;\csgray\c0;\cssrgb\c67059\c69804\c74902;\cssrgb\c81961\c60392\c40000;
+\cssrgb\c59608\c76471\c47451;}
+\margl1440\margr1440\vieww23520\viewh15940\viewkind0
+\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural\partightenfactor0
+
+\f0\fs22 \cf2 \CocoaLigature0 I want to build a jekyll template called ultimate jekyll and i need your help putting it together.\
+\
+to start things off, i want to have a theme system. in _config.yml, we specify the theme like \
+\
+theme:\
+	id: 'front'\
+	mode: 'frontend'\
+\
+the theme is a bootstrap theme. the theme comes with a frontend for users and an backend admin portal.\
+\
+next some pages will use "placeholders". for example i might make a file called pages/terms.html that just looks like this\
+---\
+layout: placeholders/terms\
+---\
+\
+That way, every new website i set up has a terms and conditions thats preset in _layouts/placeholders/terms.html. however, this is where things get tricky. \
+\
+here is _layouts/placeholders/terms.html\
+---\
+layout: themes/[ site.theme.id ]/frontend/default\
+---\
+This is where the TOS text will be\
+\
+notice the dynamic site.theme.id. i already have gulp set up to automatically replace that part. i dont need you to work on that part. just assume it works already\
+\
+themes/front/frontend/default.html looks like this\
+---\
+layout: main/base.html\
+---\
+\{% include project/header.html %\}\
+\{\{ content\}\}\
+\{% include project/footer.html %\}\
+\
+main/base.html looks like this\
+---\
+layout: null\
+---\
+// HEAD TAG with a bunch of important meta tags\
+<body>\
+\{\{ content \}\}\
+\
+</body>\
+\
+\
+so you can see how there are many nested templates to deal with. a lot of it is meant to keep me from writing repetitive code in new projects. i am struggling wiht how to deal with project/header.html. i dont want to actually use html in this file, preferably JSON so i can do quick things like \
+\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural\partightenfactor0
+
+\f1\fs26 \cf3 \CocoaLigature1 \{\
+  \cf4 "logo"\cf3 : \{\
+    \cf4 "src"\cf3 : \cf5 "/assets/logo.svg"\cf3 ,\
+    \cf4 "alt"\cf3 : \cf5 "MyWebsite Logo"\cf3 ,\
+    \cf4 "href"\cf3 : \cf5 "/"\cf3 \
+  \},\
+  \cf4 "links"\cf3 : [\
+    \{\
+      \cf4 "label"\cf3 : \cf5 "Home"\cf3 ,\
+      \cf4 "href"\cf3 : \cf5 "/"\cf3 \
+    \},\
+    \{\
+      \cf4 "label"\cf3 : \cf5 "Services"\cf3 ,\
+      \cf4 "href"\cf3 : \cf5 "/services"\cf3 ,\
+      \cf4 "children"\cf3 : [\
+        \{\
+          \cf4 "label"\cf3 : \cf5 "Web Development"\cf3 ,\
+          \cf4 "href"\cf3 : \cf5 "/services/web-development"\cf3 \
+        \},\
+        \{\
+          \cf4 "label"\cf3 : \cf5 "Marketing"\cf3 ,\
+          \cf4 "href"\cf3 : \cf5 "/services/marketing"\cf3 ,\
+          \cf4 "children"\cf3 : [\
+            \{\
+              \cf4 "label"\cf3 : \cf5 "SEO"\cf3 ,\
+              \cf4 "href"\cf3 : \cf5 "/services/marketing/seo"\cf3 \
+            \},\
+          ]\
+        \}\
+      ]\
+    \},\
+    \{\
+      \cf4 "label"\cf3 : \cf5 "Blog"\cf3 ,\
+      \cf4 "href"\cf3 : \cf5 "/blog"\cf3 \
+    \},\
+    \{\
+      \cf4 "label"\cf3 : \cf5 "Contact"\cf3 ,\
+      \cf4 "href"\cf3 : \cf5 "/contact"\cf3 \
+    \}\
+  ],\
+  \cf4 "cta"\cf3 : \{\
+    \cf4 "label"\cf3 : \cf5 "Sign Up"\cf3 ,\
+    \cf4 "href"\cf3 : \cf5 "/signup"\cf3 \
+  \}\
+\}
+\f0\fs22 \cf2 \CocoaLigature0 \
+\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural\partightenfactor0
+\
+and have it constructed using a theme file (maybe _layouts/themes/front/templates/header.html?) and then eventually it will actually become project/header.html so jekyll can obviosuly include it in the build.}

package/TODO-FileStructure.md

@@ -0,0 +1,249 @@
+⏺ Based on my analysis, here's my comprehensive naming and organization proposal for your Ultimate Jekyll
+  template system:
+
+  Proposed Naming Convention
+
+  1. Layouts Structure
+
+  _layouts/
+  ├── core/              # (was: main/global/)
+  │   └── root.html      # (was: default.html) - Base HTML skeleton
+  ├── themes/            # Keep as-is - theme-specific layouts
+  │   └── {theme}/
+  │       ├── shell.html # (was: base.html) - Theme's main wrapper
+  │       ├── page.html  # (was: default.html) - Standard pages
+  │       ├── legal.html # Keep as-is - Legal pages
+  │       ├── blog.html  # Blog layouts
+  │       └── modal.html # (was: fullscreen.html) - Modal/overlay layouts
+  └── blueprints/        # (was: placeholder/) - Content templates
+      ├── legal/
+      │   ├── terms.md
+      │   └── privacy.md
+      └── blog/
+          ├── index.html
+          └── post.html
+
+  2. Includes Structure
+
+  _includes/
+  ├── parts/             # (was: components/global/) - Core page parts
+  │   ├── head.html
+  │   ├── body.html
+  │   ├── foot.html
+  │   ├── nav.html
+  │   └── footer.html
+  ├── widgets/           # (was: modules/) - Reusable components
+  │   ├── ads/           # (was: adunits/)
+  │   ├── forms/         # Contact forms, signups
+  │   ├── cards/         # Card components
+  │   └── media/         # Images, videos, embeds
+  └── themes/            # Keep as-is - theme-specific includes
+      └── {theme}/
+          └── blocks/    # (was: sections/) - Theme blocks
+
+  3. Assets Structure
+
+  assets/
+  ├── themes/
+  │   ├── _base/         # (was: _template/) - Base theme template
+  │   │   ├── theme.js   # (was: _theme.js)
+  │   │   ├── theme.scss # (was: _theme.scss)
+  │   │   ├── js/
+  │   │   └── scss/
+  │   └── {theme}/       # Actual themes
+  │       ├── theme.js
+  │       ├── theme.scss
+  │       ├── js/
+  │       └── scss/
+  ├── css/
+  │   ├── core.scss      # (was: ultimate-jekyll-manager.scss)
+  │   ├── main.scss      # User's main styles
+  │   └── pages/         # Page-specific styles
+  └── js/
+      ├── core.js        # (was: ultimate-jekyll-manager.js)
+      ├── main.js        # User's main scripts
+      └── pages/         # Page-specific scripts
+
+  Key Benefits of New Names
+
+  1. core/root.html - Makes it clear this is the foundational HTML document
+  2. shell.html - Better describes a theme's outer wrapper than "base"
+  3. blueprints - Clearer than "placeholder" for content templates
+  4. parts - More intuitive than "components" for page sections
+  5. widgets - Better describes reusable UI components than "modules"
+  6. blocks - Clearer than "sections" for theme-specific content blocks
+  7. _base - More descriptive than "_template" for the theme template
+
+  Hierarchy Flow Example
+
+  Using the terms page example:
+  1. src/pages/legal/terms.md → uses layout blueprints/legal/terms
+  2. blueprints/legal/terms.md → uses layout themes/bootstrap/legal
+  3. themes/bootstrap/legal.html → uses layout themes/bootstrap/shell
+  4. themes/bootstrap/shell.html → uses layout core/root
+  5. core/root.html → includes parts/head, parts/body, parts/foot
+
+  Additional Organizational Improvements
+
+  1. Remove __temp directory - Clean up legacy files
+  2. Standardize file extensions - Use .html consistently (no .html copy)
+  3. Create a docs/architecture.md - Document the naming system
+  4. Add .keep files - In empty directories to maintain structure
+  5. Theme consistency - Ensure all themes follow the same structure
+
+  This naming system uses single, descriptive words that clearly indicate each component's purpose while
+  maintaining the flexibility for users to create their own layouts without conflicts.
+
+⏺ Update Todos
+  ⎿  ☒ Analyze current template structure and naming patterns
+     ☒ Examine the layout hierarchy and component relationships
+     ☒ Propose new naming conventions for layouts, includes, and components
+     ☒ Suggest organizational improvements for the directory structure
+
+> ok what should i name "src/defaults/dist/_layouts/modules/redirect.html"? I have
+  "src/defaults/dist/_includes/modules/adunits/adsense.html" notice how it is in an adsense subfolder. give me subfolder name
+
+⏺ Looking at your structure and the new naming convention I proposed, for src/defaults/dist/_layouts/modules/redirect.html, I would
+   suggest:
+
+  src/defaults/dist/_layouts/utilities/redirect/redirect.html
+
+  Or if you want to keep it flatter:
+
+  src/defaults/dist/_layouts/utilities/redirect.html
+
+  The reasoning:
+  - utilities better describes technical/functional layouts (like redirects) vs content layouts
+  - It follows the pattern of your _includes/modules/adunits/adsense.html where the subfolder (adunits) categorizes the type
+  - Other utilities might include: utilities/error/404.html, utilities/maintenance/maintenance.html, etc.
+
+  If you specifically want just the subfolder name: utilities
+
+╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ >                                                                                                                           │
+╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+  ? for shortcuts                                                                                          ◯ IDE disconnected
+
+
+
+NEW
+
+⏺ Great question! For organizing layouts within a theme's frontend folder, I suggest a hybrid approach that groups related
+   layouts while keeping commonly-used ones at the root level:
+
+  src/defaults/dist/_layouts/themes/bootstrap/frontend/
+  ├── base.html          # Keep at root - the main theme wrapper
+  ├── page.html          # Keep at root - standard content pages
+  ├── modal.html         # Keep at root - fullscreen/modal layouts
+  ├── pages/             # Specific page-type layouts
+  │   ├── legal.html     # Legal pages (terms, privacy)
+  │   ├── contact.html   # Contact form pages
+  │   ├── error.html     # Error pages (404, 500)
+  │   ├── blog.html      # Blog listing/archive
+  │   └── post.html      # Individual blog posts
+  └── formats/           # Alternative content formats
+      ├── bare.html      # Minimal layout (no nav/footer)
+      ├── print.html     # Print-optimized layout
+      └── embed.html     # For embedded content
+
+  Rationale:
+  1. Root level - Keep the most fundamental layouts (base, page, modal) easily accessible
+  2. pages/ subfolder - Group content-specific layouts that correspond to actual page types
+  3. formats/ subfolder - Group presentation variants that could apply to any content
+
+  This way:
+  - base.html remains the foundation all others extend from
+  - Common layouts are easy to find at the root
+  - Specific page layouts are logically grouped
+  - It's clear where to add new layouts as the theme grows
+
+  For your current files:
+  - legal.html → pages/legal.html
+  - fullscreen.html → modal.html (at root, since it's a common pattern)
+
+
+
+
+
+
+
+
+
+
+
+ok so for the theme-specific layouts, theres a  couple things and that leads me to a question
+
+So a theme's layouts will live in a folder like (for frontend) "src/defaults/dist/_layouts/themes/bootstrap/frontend"
+- A theme will always have a base.html layout that is the main layout for all pages in that theme
+- However, the placeholder/blueprint pages will need to use specific layouts like legal.html "src/defaults/dist/_layouts/themes/bootstrap/frontend/legal.html" and eventually even more like a 404 layout, a contact layout etc.
+- but there are also some more generic layouts like "src/defaults/dist/_layouts/themes/bootstrap/frontend/fullscreen.html"
+
+HOW DO I ORGANIZE THESE LAYOUTS inside a theme?
+
+
+
+
+
+
+
+
+
+I need help re-organizing some things in my lib.
+
+Review "src/gulp/tasks/webpack.js" to see how the files are being bundled and loaded and the path aliases used.
+
+src/assets/js/ultimate-jekyll-manager.js
+* This is the file that the CONSUMING project will load
+
+src/assets/js/utilities
+* This directory is DIRECTLY COPIED to the CONSUMING project so that scripts SUCH AS "src/assets/js/utilities/popupads.js" can be DIRECTLY LOADED IN A SCRIPT TAG (no webpack is run on these files)
+
+src/assets/js/libs
+* This directory is not copied to the consuming project OR packed with webpack. It is JUST FILES THAT ARE IMPORTED BY THE ULTIMATE JEKYLL LIBRARY ITSEF. An example is "src/assets/js/libs/dev.js" which is imported during development and has some logging and debugging features.
+
+NOW HERES THE PART I NEED HELP WITH:
+
+1. I have "src/assets/js/redirect.js" which is loaded by "src/defaults/dist/_layouts/modules/utilities/redirect.html". I would like it to be WEBPACKED but i want to put it in a folder that is AUTOMATICALLY WEBPACKED that is distinctly separate from the main library. I need help naming that folder or deciding on a better strategy for this.
+2. While youre at it, help me decide if "src/assets/js/libs" and "src/assets/js/utilities" are good names or if they should be changed.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+{% assign page-url-stripped = page.url | replace: 'index.html', '' %}
+{%- if page-url-stripped == '/' -%}
+  {% assign page-url-stripped = '' %}
+{% endif %}
+
+page.canonical: {{ page.canonical }}|
+
+            {% capture action_icon %}{% if action.icon %}{{ site.icons[action.icon] }}{% endif %}{% endcapture %}
+
+METHOD 1
+html class=h-100
+body class=d-flex flex-column h-100
+main class=flex-shrink-0
+footer class=mt-auto
+
+METHOD 2
+html class=
+body class=d-flex flex-column min-vh-100
+main class=flex-fill
+footer class=
+
+
+DONT FORGET THE FLOW (goes from top to bottom)
+
+│   src/defaults/dist/_layouts/placeholder/app.html\                                                    │
+│   src/defaults/dist/_layouts/themes/bootstrap/frontend/fullscreen.html\                               │
+│   src/defaults/dist/_layouts/themes/bootstrap/frontend/core/base.html\                                     │
+│   src/defaults/dist/_layouts/core/root.html\