@djangocfg/layouts 2.1.264 → 2.1.267

package/src/layouts/PublicLayout/hooks/index.ts

@@ -1,2 +1,6 @@
 export { useMobileNavPanel } from './useMobileNavPanel';
-
+export { useDropdownMenu } from './useDropdownMenu';
+export type { UseDropdownMenuReturn } from './useDropdownMenu';
+export { useNavbarScroll } from './useNavbarScroll';
+export type { UseNavbarScrollOptions, UseNavbarScrollReturn } from './useNavbarScroll';
+export { useNavbarViewportVars } from './useNavbarViewportVars';

package/src/layouts/PublicLayout/hooks/useDropdownMenu.ts

@@ -0,0 +1,58 @@
+'use client';
+
+import { useCallback, useEffect, useRef, useState } from 'react';
+
+export interface UseDropdownMenuReturn {
+  openDropdownKey: string | null;
+  scheduleOpen: (key: string) => void;
+  scheduleClose: (key: string) => void;
+  closeDropdown: () => void;
+}
+
+/** Hover-based open/close with debounce timers for desktop dropdown menus. */
+export function useDropdownMenu(): UseDropdownMenuReturn {
+  const [openDropdownKey, setOpenDropdownKey] = useState<string | null>(null);
+  const openTimerRef = useRef<number | null>(null);
+  const closeTimerRef = useRef<number | null>(null);
+
+  const clearOpenTimer = useCallback(() => {
+    if (openTimerRef.current !== null) {
+      window.clearTimeout(openTimerRef.current);
+      openTimerRef.current = null;
+    }
+  }, []);
+
+  const clearCloseTimer = useCallback(() => {
+    if (closeTimerRef.current !== null) {
+      window.clearTimeout(closeTimerRef.current);
+      closeTimerRef.current = null;
+    }
+  }, []);
+
+  const scheduleOpen = useCallback((key: string) => {
+    clearOpenTimer();
+    clearCloseTimer();
+    openTimerRef.current = window.setTimeout(() => {
+      setOpenDropdownKey(key);
+    }, 80);
+  }, [clearOpenTimer, clearCloseTimer]);
+
+  const scheduleClose = useCallback((key: string) => {
+    clearOpenTimer();
+    clearCloseTimer();
+    closeTimerRef.current = window.setTimeout(() => {
+      setOpenDropdownKey((prev) => (prev === key ? null : prev));
+    }, 120);
+  }, [clearOpenTimer, clearCloseTimer]);
+
+  const closeDropdown = useCallback(() => setOpenDropdownKey(null), []);
+
+  useEffect(() => {
+    return () => {
+      clearOpenTimer();
+      clearCloseTimer();
+    };
+  }, [clearOpenTimer, clearCloseTimer]);
+
+  return { openDropdownKey, scheduleOpen, scheduleClose, closeDropdown };
+}

package/src/layouts/PublicLayout/hooks/useNavbarScroll.ts

@@ -0,0 +1,61 @@
+'use client';
+
+import { useEffect, useRef, useState } from 'react';
+
+export interface UseNavbarScrollOptions {
+  /** Slide navbar up on scroll-down, back on scroll-up. @default false */
+  hideNavOnScroll?: boolean;
+  /** Transparent at page top, opaque after threshold. @default false */
+  transparent?: boolean;
+  /** scrollY threshold for hide + transparent triggers. @default 40 */
+  transparentThreshold?: number;
+}
+
+export interface UseNavbarScrollReturn {
+  /** true → apply `-translate-y-full` to outer wrapper */
+  hidden: boolean;
+  /** true → scrollY >= threshold; drives opaque background */
+  scrolled: boolean;
+}
+
+export function useNavbarScroll(options: UseNavbarScrollOptions = {}): UseNavbarScrollReturn {
+  const { hideNavOnScroll = false, transparent = false, transparentThreshold = 40 } = options;
+
+  const [hidden, setHidden] = useState(false);
+  const [scrolled, setScrolled] = useState(false);
+  const lastScrollY = useRef(0);
+
+  useEffect(() => {
+    if (!hideNavOnScroll && !transparent) {
+      setHidden(false);
+      setScrolled(false);
+      return;
+    }
+
+    const handleScroll = () => {
+      const currentY = window.scrollY;
+      const delta = currentY - lastScrollY.current;
+
+      if (transparent) {
+        setScrolled(currentY >= transparentThreshold);
+      }
+
+      if (hideNavOnScroll) {
+        if (currentY > transparentThreshold) {
+          if (delta > 0) setHidden(true);
+          else if (delta < 0) setHidden(false);
+        } else {
+          setHidden(false);
+        }
+      }
+
+      lastScrollY.current = currentY;
+    };
+
+    handleScroll();
+    window.addEventListener('scroll', handleScroll, { passive: true });
+    return () => window.removeEventListener('scroll', handleScroll);
+  }, [hideNavOnScroll, transparent, transparentThreshold]);
+
+  return { hidden, scrolled };
+}

package/src/layouts/PublicLayout/hooks/useNavbarViewportVars.ts

@@ -0,0 +1,46 @@
+'use client';
+
+import { type RefObject, useEffect } from 'react';
+
+/**
+ * Tracks the bottom edge of the navbar outer element and writes CSS vars:
+ *   --public-navbar-mobile-drawer-top
+ *   --public-navbar-mobile-drawer-max-height
+ *
+ * @param navOuterRef - ref on the outermost navbar wrapper div
+ * @param deps        - values that should re-trigger observer setup (position, variant, containerClassName)
+ */
+export function useNavbarViewportVars(
+  navOuterRef: RefObject<HTMLDivElement | null>,
+  deps: readonly unknown[],
+): void {
+  useEffect(() => {
+    const update = () => {
+      const root = document.documentElement;
+      const navEl = navOuterRef.current;
+      if (!navEl) return;
+
+      const rect = navEl.getBoundingClientRect();
+      const top = Math.max(0, Math.round(rect.bottom + 8));
+      const maxHeight = Math.max(240, window.innerHeight - top - 12);
+
+      root.style.setProperty('--public-navbar-mobile-drawer-top', `${top}px`);
+      root.style.setProperty('--public-navbar-mobile-drawer-max-height', `${maxHeight}px`);
+    };
+
+    update();
+    const navEl = navOuterRef.current;
+    const observer = navEl ? new ResizeObserver(update) : null;
+    if (navEl && observer) observer.observe(navEl);
+    window.addEventListener('resize', update);
+    window.addEventListener('scroll', update, { passive: true });
+
+    return () => {
+      if (navEl && observer) observer.unobserve(navEl);
+      observer?.disconnect();
+      window.removeEventListener('resize', update);
+      window.removeEventListener('scroll', update);
+    };
+    // eslint-disable-next-line react-hooks/exhaustive-deps
+  }, deps);
+}

package/src/layouts/PublicLayout/index.ts

@@ -10,7 +10,11 @@ export type {
   PublicNavbarVariant,
   PublicNavbarPosition,
   PublicNavbarShellConfig,
+  PublicNavLayout,
+  PublicNavbarHeight,
 } from './navbarTypes';
+export type { UseNavbarScrollOptions, UseNavbarScrollReturn } from './hooks/useNavbarScroll';
+export type { UseDropdownMenuReturn } from './hooks/useDropdownMenu';
 export type {
   PublicDesktopDropdownRenderer,
   PublicDesktopDropdownRenderProps,

package/src/layouts/PublicLayout/navbarTypes.ts

@@ -6,6 +6,23 @@ export type PublicNavbarVariant = 'floating' | 'flush';
 
 export type PublicNavbarPosition = 'sticky' | 'fixed' | 'static';
 
+/**
+ * Desktop nav layout variant.
+ * - `default`     — brand left | nav **centered** (absolute) | actions right
+ * - `brand-left`  — brand left | nav immediately after brand | actions pushed right
+ * - `centered`    — brand + nav + actions all centered in one row
+ * - `split`       — brand left | actions right | no desktop nav (drawer only)
+ */
+export type PublicNavLayout = 'default' | 'brand-left' | 'centered' | 'split';
+
+/**
+ * Navbar vertical padding / height.
+ * - `sm` → py-2
+ * - `md` → py-3.5  (default, matches current)
+ * - `lg` → py-5
+ */
+export type PublicNavbarHeight = 'sm' | 'md' | 'lg';
+
 export interface PublicNavbarSurface {
   variant: PublicNavbarVariant;
   position: PublicNavbarPosition;

package/src/utils/pathMatcher.ts

@@ -105,12 +105,15 @@ export function matchesPath(pathname: string, enabledPath?: string | string[]):
   if (!enabledPath) return false;
 
   const matchSinglePath = (path: string): boolean => {
+    // Normalize both sides — strip trailing slash (except root)
+    const normalPath = pathname.length > 1 ? pathname.replace(/\/+$/, '') : pathname;
+    const normalPattern = path.length > 1 ? path.replace(/\/+$/, '') : path;
     // If pattern contains glob characters, use pattern matching
-    if (path.includes('*')) {
-      return matchGlobPattern(pathname, path);
+    if (normalPattern.includes('*')) {
+      return matchGlobPattern(normalPath, normalPattern);
     }
     // Otherwise, exact or prefix match
-    return pathname === path || pathname.startsWith(path + '/');
+    return normalPath === normalPattern || normalPath.startsWith(normalPattern + '/');
   };
 
   if (typeof enabledPath === 'string') {

package/src/layouts/ProfileLayout/.claude/.sidecar/activity.jsonl

@@ -1,2 +0,0 @@
-{"ts":"2026-03-15T05:27:58.550593Z","action":"update_check","tokens":0,"model":"deepseek/deepseek-v3.2","details":{}}
-{"ts":"2026-03-15T05:28:21.054276Z","action":"review","tokens":1533,"model":"deepseek/deepseek-v3.2","details":{"items_found":5}}

package/src/layouts/ProfileLayout/.claude/.sidecar/history/2026-03-15.md

@@ -1,35 +0,0 @@
-# Sidecar Review -- 2026-03-15T05:28:21.052657+00:00
-
-## Staleness
-
-- [?] Cannot assess staleness because documentation contents are unavailable. However, given the high commit activity (20 commits in 2 days), any documentation older than 30 days is almost certainly stale and contradictory to the current codebase state (e.g., new 'debuger', 'monitor', and OTP features).
-  Files: Documentation referenced in file list
-  Action: Provide documentation content to check modification dates against commit history. Update all documentation to reflect recent changes like the debug panel, monitoring integration, and OTP brute-force protection.
-  (id: 46040dd3aace)
-
-## Contradictions
-
-- [~] The commit 'updaded rq' (2026-03-14) has a typo and inconsistent formatting compared to other commits (e.g., 'chore(deps): bump django-rq version to 4.0.0'). This suggests poor documentation practices in commit messages, which can lead to confusion about project changes.
-  Files: Commit history analysis
-  Action: Enforce a commit message convention (e.g., Conventional Commits) and consider amending the 'updaded rq' commit for clarity. Ensure future commits are consistently formatted.
-  (id: 6e3e54dfac9f)
-
-## Missing Documentation
-
-- [!] No documentation content was provided for analysis. The provided metadata lists documentation files but their contents are unavailable, making it impossible to verify accuracy, check for staleness, or identify contradictions with the codebase.
-  Files: All documentation files
-  Action: Provide the actual content of the documentation files listed in the metadata (e.g., README.md, API docs, configuration guides) to enable a proper analysis for staleness, contradictions, and gaps.
-  (id: fb1ef89d45a4)
-
-- [?] The top-level source directories '__tests__' and 'components' have no associated documentation content provided. Recent commits mention features like 'debuger', 'monitor', 'accounts', and 'otp', which likely reside in these directories, but their documentation cannot be verified.
-  Files: __tests__, components
-  Action: Review and provide documentation for the '__tests__' and 'components' directories, ensuring it covers the features mentioned in recent commits (e.g., debug panel, OTP brute-force protection, monitoring integration).
-  (id: d538d5624ebb)
-
-- [!] No dependencies were detected, but recent git commits show active dependency management (e.g., 'bump django-cfg version to 1.7.77', 'bump django-rq version to 4.0.0'). This indicates a contradiction between the reported state and project activity, and documentation for these key dependencies is missing.
-  Files: Dependency files (e.g., pyproject.toml, requirements.txt)
-  Action: Provide the actual dependency files (pyproject.toml, package.json, or requirements.txt) to check for contradictions with documentation and ensure all critical packages like 'django-cfg' and 'django-rq' are documented.
-  (id: fe7c9fa20e8b)
-
----
-Model: deepseek/deepseek-v3.2 | Tokens: 1533

package/src/layouts/ProfileLayout/.claude/.sidecar/review.md

@@ -1,35 +0,0 @@
-# Sidecar Review -- 2026-03-15T05:28:21.052657+00:00
-
-## Staleness
-
-- [?] Cannot assess staleness because documentation contents are unavailable. However, given the high commit activity (20 commits in 2 days), any documentation older than 30 days is almost certainly stale and contradictory to the current codebase state (e.g., new 'debuger', 'monitor', and OTP features).
-  Files: Documentation referenced in file list
-  Action: Provide documentation content to check modification dates against commit history. Update all documentation to reflect recent changes like the debug panel, monitoring integration, and OTP brute-force protection.
-  (id: 46040dd3aace)
-
-## Contradictions
-
-- [~] The commit 'updaded rq' (2026-03-14) has a typo and inconsistent formatting compared to other commits (e.g., 'chore(deps): bump django-rq version to 4.0.0'). This suggests poor documentation practices in commit messages, which can lead to confusion about project changes.
-  Files: Commit history analysis
-  Action: Enforce a commit message convention (e.g., Conventional Commits) and consider amending the 'updaded rq' commit for clarity. Ensure future commits are consistently formatted.
-  (id: 6e3e54dfac9f)
-
-## Missing Documentation
-
-- [!] No documentation content was provided for analysis. The provided metadata lists documentation files but their contents are unavailable, making it impossible to verify accuracy, check for staleness, or identify contradictions with the codebase.
-  Files: All documentation files
-  Action: Provide the actual content of the documentation files listed in the metadata (e.g., README.md, API docs, configuration guides) to enable a proper analysis for staleness, contradictions, and gaps.
-  (id: fb1ef89d45a4)
-
-- [?] The top-level source directories '__tests__' and 'components' have no associated documentation content provided. Recent commits mention features like 'debuger', 'monitor', 'accounts', and 'otp', which likely reside in these directories, but their documentation cannot be verified.
-  Files: __tests__, components
-  Action: Review and provide documentation for the '__tests__' and 'components' directories, ensuring it covers the features mentioned in recent commits (e.g., debug panel, OTP brute-force protection, monitoring integration).
-  (id: d538d5624ebb)
-
-- [!] No dependencies were detected, but recent git commits show active dependency management (e.g., 'bump django-cfg version to 1.7.77', 'bump django-rq version to 4.0.0'). This indicates a contradiction between the reported state and project activity, and documentation for these key dependencies is missing.
-  Files: Dependency files (e.g., pyproject.toml, requirements.txt)
-  Action: Provide the actual dependency files (pyproject.toml, package.json, or requirements.txt) to check for contradictions with documentation and ensure all critical packages like 'django-cfg' and 'django-rq' are documented.
-  (id: fe7c9fa20e8b)
-
----
-Model: deepseek/deepseek-v3.2 | Tokens: 1533

package/src/layouts/ProfileLayout/.claude/.sidecar/scan.log

@@ -1,3 +0,0 @@
-Review generated: 5 items found
-Tokens used: 1533 (deepseek/deepseek-v3.2)
-Converted 5 items to tasks

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-001.md

@@ -1,18 +0,0 @@
----
-context_files:
-- All documentation files
-created_at: '2026-03-15T05:28:21.056182Z'
-id: T-001
-priority: high
-source: sidecar_review
-source_item_id: fb1ef89d45a4
-status: pending
-title: '[gap] No documentation content was provided for analysis. The provided metadata
-  lists'
----
-
-No documentation content was provided for analysis. The provided metadata lists documentation files but their contents are unavailable, making it impossible to verify accuracy, check for staleness, or identify contradictions with the codebase.
-
-**Files:** All documentation files
-
-**Action:** Provide the actual content of the documentation files listed in the metadata (e.g., README.md, API docs, configuration guides) to enable a proper analysis for staleness, contradictions, and gaps.

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-002.md

@@ -1,19 +0,0 @@
----
-context_files:
-- __tests__
-- components
-created_at: '2026-03-15T05:28:21.057118Z'
-id: T-002
-priority: medium
-source: sidecar_review
-source_item_id: d538d5624ebb
-status: pending
-title: '[gap] The top-level source directories ''__tests__'' and ''components'' have
-  no associated'
----
-
-The top-level source directories '__tests__' and 'components' have no associated documentation content provided. Recent commits mention features like 'debuger', 'monitor', 'accounts', and 'otp', which likely reside in these directories, but their documentation cannot be verified.
-
-**Files:** __tests__, components
-
-**Action:** Review and provide documentation for the '__tests__' and 'components' directories, ensuring it covers the features mentioned in recent commits (e.g., debug panel, OTP brute-force protection, monitoring integration).

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-003.md

@@ -1,18 +0,0 @@
----
-context_files:
-- Dependency files (e.g., pyproject.toml, requirements.txt)
-created_at: '2026-03-15T05:28:21.057738Z'
-id: T-003
-priority: high
-source: sidecar_review
-source_item_id: fe7c9fa20e8b
-status: pending
-title: '[gap] No dependencies were detected, but recent git commits show active dependency
-  man'
----
-
-No dependencies were detected, but recent git commits show active dependency management (e.g., 'bump django-cfg version to 1.7.77', 'bump django-rq version to 4.0.0'). This indicates a contradiction between the reported state and project activity, and documentation for these key dependencies is missing.
-
-**Files:** Dependency files (e.g., pyproject.toml, requirements.txt)
-
-**Action:** Provide the actual dependency files (pyproject.toml, package.json, or requirements.txt) to check for contradictions with documentation and ensure all critical packages like 'django-cfg' and 'django-rq' are documented.

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-004.md

@@ -1,18 +0,0 @@
----
-context_files:
-- Documentation referenced in file list
-created_at: '2026-03-15T05:28:21.058352Z'
-id: T-004
-priority: medium
-source: sidecar_review
-source_item_id: 46040dd3aace
-status: pending
-title: '[staleness] Cannot assess staleness because documentation contents are unavailable.
-  However,'
----
-
-Cannot assess staleness because documentation contents are unavailable. However, given the high commit activity (20 commits in 2 days), any documentation older than 30 days is almost certainly stale and contradictory to the current codebase state (e.g., new 'debuger', 'monitor', and OTP features).
-
-**Files:** Documentation referenced in file list
-
-**Action:** Provide documentation content to check modification dates against commit history. Update all documentation to reflect recent changes like the debug panel, monitoring integration, and OTP brute-force protection.

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-005.md

@@ -1,18 +0,0 @@
----
-context_files:
-- Commit history analysis
-created_at: '2026-03-15T05:28:21.059002Z'
-id: T-005
-priority: low
-source: sidecar_review
-source_item_id: 6e3e54dfac9f
-status: pending
-title: '[contradiction] The commit ''updaded rq'' (2026-03-14) has a typo and inconsistent
-  formatting comp'
----
-
-The commit 'updaded rq' (2026-03-14) has a typo and inconsistent formatting compared to other commits (e.g., 'chore(deps): bump django-rq version to 4.0.0'). This suggests poor documentation practices in commit messages, which can lead to confusion about project changes.
-
-**Files:** Commit history analysis
-
-**Action:** Enforce a commit message convention (e.g., Conventional Commits) and consider amending the 'updaded rq' commit for clarity. Ensure future commits are consistently formatted.

package/src/layouts/ProfileLayout/.claude/.sidecar/usage.json

@@ -1,5 +0,0 @@
-{
-  "date": "2026-03-15",
-  "tokens": 1533,
-  "calls": 1
-}