sdarbinyan/marketplaces
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
4ebc15fff846e6249315037f00526412384a6201
marketplaces/src/app/features/project-editor/sections/footer-section.component.scss

97 lines
2.2 KiB
SCSS
Raw Normal View History

feat(builder): visual footer builder with drag-and-drop columns Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> P0 user feedback: footer static pages were comma-separated text; no way to add extra phones/emails for different countries. - New FooterColumnConfig/FooterLinkConfig model (footer-config.model.ts): columns of links, each link pointing at an existing static page (resolved by key, so it survives route renames) or a custom URL - Footer Builder UI: add/remove columns and links, per-link toggle between 'existing page' (dropdown of real static pages) and 'custom URL', drag-and-drop reordering of both columns and links via @angular/cdk/drag-drop (same primitive already used by the homepage section builder) - Wired FooterResolverService (the service the real storefront footer actually renders through) to read footer.columns as the primary source when present - without this the builder would have saved data nobody ever displayed. Falls back to the existing legacy static-page auto-grouping when no columns are configured, so existing sites are unaffected - CompanyContactConfig gains additionalPhones/additionalEmails (primary phone/email field unchanged) with add/remove UI for country-specific support lines - Old comma-separated staticPageKeys input removed from the UI; field kept on the model as deprecated/read-compat only - New builder.* i18n keys (en/ru/hy); fixed an accidental duplicate-key collision with pre-existing navigation-section addLink/removeLink keys during the rename pass - Verified in browser: added column, added link, switched link source page->custom, added phone number - all reactive and error-free
2026-07-19 13:58:57 +04:00
.contact-row {
display: flex;
align-items: center;
gap: 8px;
margin-bottom: 6px;
app-input { flex: 1; }
}
.contact-row__remove {
border: none;
background: transparent;
cursor: pointer;
color: var(--text-secondary, #6b7280);
style(design-system): roll out font-size scale across storefront/builder/backoffice Mechanical, value-preserving substitution: every literal font-size declaration across src/app (89 files) that matched one of the 9 typography scale steps introduced earlier (--font-size-xs..4xl) was replaced with var(--font-size-STEP, <same-or-nearest-step-value>). Values within ~0.03rem/1px of a scale step were snapped to that step (e.g. 0.85rem and 0.8rem both -> --font-size-sm/0.8125rem; 0.9rem and 0.875rem -> --font-size-base/0.875rem) to consolidate roughly 15 near-duplicate sizes down to the 9-step scale, per the RC design-system finalization brief. This eliminates most of the font-size fragmentation found across the app (previously: 0.7/0.72/0.75/0.78/0.8/0.8125/0.85/ 0.875/0.9/0.9375/0.95/1/1.05/1.1/1.125/1.15/1.2/1.25/1.3/1.35/1.4/1.5/ 1.75/2rem all in live use simultaneously). Not touched (deliberately, see docs/UI-DESIGN-REVIEW.md): 3rem+ display sizes (too large a jump to any existing step, would need a --font-size-5xl addition), font-size values expressed via clamp()/calc(), and any component listed as intentionally distinct (code-editor syntax tokens, theme brand colors).
2026-07-20 03:26:17 +04:00
font-size: var(--font-size-lg, 1rem);
feat(builder): visual footer builder with drag-and-drop columns Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> P0 user feedback: footer static pages were comma-separated text; no way to add extra phones/emails for different countries. - New FooterColumnConfig/FooterLinkConfig model (footer-config.model.ts): columns of links, each link pointing at an existing static page (resolved by key, so it survives route renames) or a custom URL - Footer Builder UI: add/remove columns and links, per-link toggle between 'existing page' (dropdown of real static pages) and 'custom URL', drag-and-drop reordering of both columns and links via @angular/cdk/drag-drop (same primitive already used by the homepage section builder) - Wired FooterResolverService (the service the real storefront footer actually renders through) to read footer.columns as the primary source when present - without this the builder would have saved data nobody ever displayed. Falls back to the existing legacy static-page auto-grouping when no columns are configured, so existing sites are unaffected - CompanyContactConfig gains additionalPhones/additionalEmails (primary phone/email field unchanged) with add/remove UI for country-specific support lines - Old comma-separated staticPageKeys input removed from the UI; field kept on the model as deprecated/read-compat only - New builder.* i18n keys (en/ru/hy); fixed an accidental duplicate-key collision with pre-existing navigation-section addLink/removeLink keys during the rename pass - Verified in browser: added column, added link, switched link source page->custom, added phone number - all reactive and error-free
2026-07-19 13:58:57 +04:00
fix(builder): composition audit fixes for project editor sections - Reset-section button: raw <button> with hardcoded colors -> app-button variant="danger" - section.shared.scss: raw button/input/select colors switched to CSS theme vars (--primary-color, --bg-primary, --bg-secondary, --error-color) instead of bare hex - save-bar scss referenced nonexistent CSS vars (--surface, --border, --warning, --danger, --muted-foreground, --info-bg, --info) that always fell back to hardcoded hex; renamed to the real theme vars (--bg-primary, --border-color, --warning-color, --error-color, --text-secondary, --info-color) so the save bar is actually theme-aware - footer/homepage/widgets section scss: nonexistent --danger-color var renamed to --error-color - static-pages-editor: replaced dead `.editor-section-card` wrapper class (removed from shared stylesheet in the Sprint 30 redesign, never migrated here) with app-section-card, restoring the card chrome every sibling editor section has - widgets-section: empty state (no widgets) rendered nothing; added app-empty-state - homepage-section: empty state (no homepage page) rendered nothing; added app-empty-state - navigation-section: header/footer nav move-up/move-down buttons had no accessible name (bare uarr/darr glyphs); added aria-label - Added builder.widgetsEmptyTitle/Desc and builder.homepageEmptyTitle/Desc i18n keys (en/ru/hy) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 10:47:37 +04:00
&:hover { color: var(--error-color, #c0392b); }
feat(builder): visual footer builder with drag-and-drop columns Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> P0 user feedback: footer static pages were comma-separated text; no way to add extra phones/emails for different countries. - New FooterColumnConfig/FooterLinkConfig model (footer-config.model.ts): columns of links, each link pointing at an existing static page (resolved by key, so it survives route renames) or a custom URL - Footer Builder UI: add/remove columns and links, per-link toggle between 'existing page' (dropdown of real static pages) and 'custom URL', drag-and-drop reordering of both columns and links via @angular/cdk/drag-drop (same primitive already used by the homepage section builder) - Wired FooterResolverService (the service the real storefront footer actually renders through) to read footer.columns as the primary source when present - without this the builder would have saved data nobody ever displayed. Falls back to the existing legacy static-page auto-grouping when no columns are configured, so existing sites are unaffected - CompanyContactConfig gains additionalPhones/additionalEmails (primary phone/email field unchanged) with add/remove UI for country-specific support lines - Old comma-separated staticPageKeys input removed from the UI; field kept on the model as deprecated/read-compat only - New builder.* i18n keys (en/ru/hy); fixed an accidental duplicate-key collision with pre-existing navigation-section addLink/removeLink keys during the rename pass - Verified in browser: added column, added link, switched link source page->custom, added phone number - all reactive and error-free
2026-07-19 13:58:57 +04:00
}
.footer-columns {
display: flex;
flex-wrap: wrap;
gap: 12px;
margin: 8px 0;
}
.footer-column {
display: grid;
gap: 8px;
width: 260px;
padding: 10px;
border: 1px solid var(--border-color, #d3dad9);
border-radius: var(--radius-sm);
background: var(--bg-secondary, #f7f8f8);
&.cdk-drag-preview { box-shadow: 0 4px 12px rgba(0, 0, 0, 0.15); }
&.cdk-drag-placeholder { opacity: 0.4; }
}
.footer-column__head {
display: flex;
align-items: center;
gap: 6px;
app-input { flex: 1; }
}
.footer-column__grip { cursor: grab; color: var(--text-secondary, #6b7280); }
.footer-column__remove {
border: none;
background: transparent;
cursor: pointer;
color: var(--text-secondary, #6b7280);
style(design-system): roll out font-size scale across storefront/builder/backoffice Mechanical, value-preserving substitution: every literal font-size declaration across src/app (89 files) that matched one of the 9 typography scale steps introduced earlier (--font-size-xs..4xl) was replaced with var(--font-size-STEP, <same-or-nearest-step-value>). Values within ~0.03rem/1px of a scale step were snapped to that step (e.g. 0.85rem and 0.8rem both -> --font-size-sm/0.8125rem; 0.9rem and 0.875rem -> --font-size-base/0.875rem) to consolidate roughly 15 near-duplicate sizes down to the 9-step scale, per the RC design-system finalization brief. This eliminates most of the font-size fragmentation found across the app (previously: 0.7/0.72/0.75/0.78/0.8/0.8125/0.85/ 0.875/0.9/0.9375/0.95/1/1.05/1.1/1.125/1.15/1.2/1.25/1.3/1.35/1.4/1.5/ 1.75/2rem all in live use simultaneously). Not touched (deliberately, see docs/UI-DESIGN-REVIEW.md): 3rem+ display sizes (too large a jump to any existing step, would need a --font-size-5xl addition), font-size values expressed via clamp()/calc(), and any component listed as intentionally distinct (code-editor syntax tokens, theme brand colors).
2026-07-20 03:26:17 +04:00
font-size: var(--font-size-lg, 1rem);
feat(builder): visual footer builder with drag-and-drop columns Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> P0 user feedback: footer static pages were comma-separated text; no way to add extra phones/emails for different countries. - New FooterColumnConfig/FooterLinkConfig model (footer-config.model.ts): columns of links, each link pointing at an existing static page (resolved by key, so it survives route renames) or a custom URL - Footer Builder UI: add/remove columns and links, per-link toggle between 'existing page' (dropdown of real static pages) and 'custom URL', drag-and-drop reordering of both columns and links via @angular/cdk/drag-drop (same primitive already used by the homepage section builder) - Wired FooterResolverService (the service the real storefront footer actually renders through) to read footer.columns as the primary source when present - without this the builder would have saved data nobody ever displayed. Falls back to the existing legacy static-page auto-grouping when no columns are configured, so existing sites are unaffected - CompanyContactConfig gains additionalPhones/additionalEmails (primary phone/email field unchanged) with add/remove UI for country-specific support lines - Old comma-separated staticPageKeys input removed from the UI; field kept on the model as deprecated/read-compat only - New builder.* i18n keys (en/ru/hy); fixed an accidental duplicate-key collision with pre-existing navigation-section addLink/removeLink keys during the rename pass - Verified in browser: added column, added link, switched link source page->custom, added phone number - all reactive and error-free
2026-07-19 13:58:57 +04:00
fix(builder): composition audit fixes for project editor sections - Reset-section button: raw <button> with hardcoded colors -> app-button variant="danger" - section.shared.scss: raw button/input/select colors switched to CSS theme vars (--primary-color, --bg-primary, --bg-secondary, --error-color) instead of bare hex - save-bar scss referenced nonexistent CSS vars (--surface, --border, --warning, --danger, --muted-foreground, --info-bg, --info) that always fell back to hardcoded hex; renamed to the real theme vars (--bg-primary, --border-color, --warning-color, --error-color, --text-secondary, --info-color) so the save bar is actually theme-aware - footer/homepage/widgets section scss: nonexistent --danger-color var renamed to --error-color - static-pages-editor: replaced dead `.editor-section-card` wrapper class (removed from shared stylesheet in the Sprint 30 redesign, never migrated here) with app-section-card, restoring the card chrome every sibling editor section has - widgets-section: empty state (no widgets) rendered nothing; added app-empty-state - homepage-section: empty state (no homepage page) rendered nothing; added app-empty-state - navigation-section: header/footer nav move-up/move-down buttons had no accessible name (bare uarr/darr glyphs); added aria-label - Added builder.widgetsEmptyTitle/Desc and builder.homepageEmptyTitle/Desc i18n keys (en/ru/hy) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 10:47:37 +04:00
&:hover { color: var(--error-color, #c0392b); }
feat(builder): visual footer builder with drag-and-drop columns Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> P0 user feedback: footer static pages were comma-separated text; no way to add extra phones/emails for different countries. - New FooterColumnConfig/FooterLinkConfig model (footer-config.model.ts): columns of links, each link pointing at an existing static page (resolved by key, so it survives route renames) or a custom URL - Footer Builder UI: add/remove columns and links, per-link toggle between 'existing page' (dropdown of real static pages) and 'custom URL', drag-and-drop reordering of both columns and links via @angular/cdk/drag-drop (same primitive already used by the homepage section builder) - Wired FooterResolverService (the service the real storefront footer actually renders through) to read footer.columns as the primary source when present - without this the builder would have saved data nobody ever displayed. Falls back to the existing legacy static-page auto-grouping when no columns are configured, so existing sites are unaffected - CompanyContactConfig gains additionalPhones/additionalEmails (primary phone/email field unchanged) with add/remove UI for country-specific support lines - Old comma-separated staticPageKeys input removed from the UI; field kept on the model as deprecated/read-compat only - New builder.* i18n keys (en/ru/hy); fixed an accidental duplicate-key collision with pre-existing navigation-section addLink/removeLink keys during the rename pass - Verified in browser: added column, added link, switched link source page->custom, added phone number - all reactive and error-free
2026-07-19 13:58:57 +04:00
}
.footer-column__links {
display: grid;
gap: 6px;
min-height: 20px;
}
.footer-link {
display: grid;
grid-template-columns: auto 1fr auto;
grid-template-areas:
"grip label remove"
"source source source"
"target target target";
gap: 4px 6px;
align-items: center;
padding: 6px;
border: 1px solid var(--border-color, #d3dad9);
border-radius: var(--radius-sm);
background: #fff;
&.cdk-drag-preview { box-shadow: 0 4px 12px rgba(0, 0, 0, 0.15); }
&.cdk-drag-placeholder { opacity: 0.4; }
}
.footer-link__grip { grid-area: grip; cursor: grab; color: var(--text-secondary, #6b7280); }
.footer-link app-input:first-of-type { grid-area: label; }
.footer-link__remove {
grid-area: remove;
border: none;
background: transparent;
cursor: pointer;
color: var(--text-secondary, #6b7280);
}
.footer-link__source { grid-area: source; }
.footer-link app-input[type="url"], .footer-link select:not(.footer-link__source) { grid-area: target; }
.cdk-drag-animating { transition: transform 200ms cubic-bezier(0, 0, 0.2, 1); }
Reference in New Issue Copy Permalink