tti/tti-ux
Watch
31
1
Fork
You've already forked tti-ux
 0
Code Issues 1 Pull requests 14 Projects Releases Packages 1 Wiki Activity Actions

feat(ui): complete editorial rebrand, numberless navigation, smooth accordions, and mobile responsiveness #69

Open
A-Guevara wants to merge 5 commits from feat/marcom-ui-polish into main
pull from: feat/marcom-ui-polish
merge into: tti:main
Conversation 4 Commits 5 Files changed 28 +496 -123
A-Guevara commented 2026-10-07 18:19:27 +00:00
Owner
Copy link

Summary

This PR completes the editorial overhaul, Marcom visual rebrand polish, and responsive UX enhancements across the entire TTI-UX (TUX 3.0) library and portal.

Highlights:

  • Editorial Navigation Overhaul: Removed all numbered/batch prefixes (00 //, 01 //, 03a //, etc.) from desktop sidebars, mobile drawers, and catalog categories. Sidebar headers are now clean, human-readable editorial titles.
  • Smooth Accordion Animations & Scroll Alignment: Added smooth animated expansions to sidebar sections, in-page component accordions (TuxAccordion.vue), and synchronized category filtering on /components with smooth viewport scrolling directly to #component-catalog-grid.
  • Mobile & Tablet Responsiveness: Fixed viewport padding, side-rail visibility, breadcrumb text wrapping, and mobile drawer transitions.
  • 3D Corridor Visualizer: Repaired 3D roadway perspective defaults and reactive panel controls on desktop.
  • Verification: 100% WCAG 2.2 AAA accessibility compliance (0 violations), 100% test pass rate (218 Nuxt test suites / 677 tests, 26 React suites / 87 tests), and static generation across all 502 routes verified.
## Summary This PR completes the editorial overhaul, Marcom visual rebrand polish, and responsive UX enhancements across the entire TTI-UX (TUX 3.0) library and portal. ### Highlights: - **Editorial Navigation Overhaul**: Removed all numbered/batch prefixes (`00 //`, `01 //`, `03a //`, etc.) from desktop sidebars, mobile drawers, and catalog categories. Sidebar headers are now clean, human-readable editorial titles. - **Smooth Accordion Animations & Scroll Alignment**: Added smooth animated expansions to sidebar sections, in-page component accordions (`TuxAccordion.vue`), and synchronized category filtering on `/components` with smooth viewport scrolling directly to `#component-catalog-grid`. - **Mobile & Tablet Responsiveness**: Fixed viewport padding, side-rail visibility, breadcrumb text wrapping, and mobile drawer transitions. - **3D Corridor Visualizer**: Repaired 3D roadway perspective defaults and reactive panel controls on desktop. - **Verification**: 100% WCAG 2.2 AAA accessibility compliance (0 violations), 100% test pass rate (218 Nuxt test suites / 677 tests, 26 React suites / 87 tests), and static generation across all 502 routes verified.
style(ui): polish badges, buttons, chips, charts, and 3D items for Marcom rebrand geometry and mobile responsiveness
Some checks failed
scan / trivy-fs (push) Failing after 1m4s
Details
baseline-security / baseline (push) Failing after 1m13s
Details
c863482512
fix(ui): resolve 3D roadway perspective defaults, logo router navigation, doctrine breadcrumbs, navbar layout, and CMS builder fallback
Some checks failed
baseline-security / baseline (push) Failing after 1m32s
Details
scan / trivy-fs (push) Failing after 54s
Details
cc2ba8bfab
feat(navigation): streamline mobile drawer, fix 3D control labels, and resolve breadcrumbs nowrap
Some checks failed
baseline-security / baseline (push) Failing after 1m33s
Details
scan / trivy-fs (push) Failing after 1m16s
Details
1fb384bc94
feat(navigation): omit numbered prefixes, add smooth accordion expansion and catalog scroll sync
Some checks failed
baseline-security / baseline (push) Failing after 1m21s
Details
scan / trivy-fs (push) Failing after 1m1s
Details
ai-review / review (pull_request) Successful in 54s
Details
baseline-security / baseline (pull_request) Failing after 1m24s
Details
scan / trivy-fs (pull_request) Failing after 1m11s
Details
95c462f71c
forgejo-actions commented 2026-10-07 18:38:33 +00:00
Copy link

AI review · advisory

The AI panel couldn't review this change right now (it will review the next push). Details for admins: panel HTTP 401: {"error": {"message": "missing Forgejo credential", "type": "auth", "code": 401}}

### AI review · advisory _The AI panel couldn't review this change right now (it will review the next push). Details for admins: panel HTTP 401: {"error": {"message": "missing Forgejo credential", "type": "auth", "code": 401}}_
forgejo-actions commented 2026-10-07 18:39:56 +00:00
Copy link

🔧 Security-gate fix map

The gate failed on these dependency findings — fastest path to green for each:

finding package installed → fixed do this
CVE-2026-63671 (HIGH) @nuxtjs/mdc 0.21.1 → 0.22.1 merge #59 — fix(security): @nuxtjs/mdc ^0.22.2 (CVE-2026-63671) — hold f
CVE-2026-102829 (CRITICAL) @simple-git/argv-parser 1.1.1 → 2.0.1 no fix PR yet — npm update argv-parser --package-lock-only
GHSA-g2v6-rqmx-r4w6 (HIGH) @vue/server-renderer 3.5.40 → 3.5.42, 3.6.0-rc.6 no fix PR yet — npm update server-renderer --package-lock-only
CVE-2026-102276 (HIGH) brace-expansion 5.0.9 → 5.0.10, 3.0.7, 2.1.5, 1.1.19 merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s
CVE-2026-102278 (HIGH) brace-expansion 5.0.9 → 5.0.11, 3.0.8, 2.1.6, 1.1.20 merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s
CVE-2026-93687 (HIGH) braces 3.0.3 → ? no fix PR yet — npm update braces --package-lock-only
CVE-2026-92708 (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
GHSA-mcm9-63f2-9j32 (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
GHSA-r9w8-h9r3-54w4 (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
GHSA-x5rw-q4pp-hg5g (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
CVE-2026-84375 (HIGH) js-yaml 4.3.1 → 4.3.2, 3.15.2 no fix PR yet — npm update js-yaml --package-lock-only
CVE-2026-85393 (HIGH) node-forge 1.4.0 → ? no fix PR yet — npm update node-forge --package-lock-only
CVE-2026-104846 (CRITICAL) seroval 1.5.6 → 1.6.2 no fix PR yet — npm update seroval --package-lock-only
CVE-2026-104845 (HIGH) seroval 1.5.6 → 1.6.3 no fix PR yet — npm update seroval --package-lock-only
GHSA-rgj7-g3m4-5g8c (HIGH) sharp 0.35.3 → 0.35.4 no fix PR yet — npm update sharp --package-lock-only
GHSA-wq5f-xc86-pv6w (HIGH) sharp 0.35.3 → 0.35.5 no fix PR yet — npm update sharp --package-lock-only
CVE-2026-102422 (CRITICAL) shell-quote 1.10.0 → 1.11.0 no fix PR yet — npm update shell-quote --package-lock-only
CVE-2026-102828 (CRITICAL) simple-git 3.36.0 → 4.0.1 no fix PR yet — npm update simple-git --package-lock-only
CVE-2026-102826 (HIGH) simple-git 3.36.0 → 4.0.0 no fix PR yet — npm update simple-git --package-lock-only
CVE-2026-102827 (HIGH) simple-git 3.36.0 → 4.0.0 no fix PR yet — npm update simple-git --package-lock-only
CVE-2026-93749 (HIGH) source-map-js 1.2.1 → 1.2.2 no fix PR yet — npm update source-map-js --package-lock-only
CVE-2026-84370 (HIGH) svgo 4.0.2 → 2.8.4, 3.3.5, 4.1.0 no fix PR yet — npm update svgo --package-lock-only
CVE-2026-19534 (HIGH) undici 8.10.0 → 6.28.1, 7.29.1, 8.10.2 no fix PR yet — npm update undici --package-lock-only
CVE-2026-84961 (HIGH) undici 8.10.0 → 7.29.1, 8.10.2 no fix PR yet — npm update undici --package-lock-only
CVE-2026-85152 (HIGH) undici 8.10.0 → 8.10.2 no fix PR yet — npm update undici --package-lock-only

⚠ main is itself red right now — this PR likely inherits the backlog rather than adding it. Fixing main (rows above) unblocks every open PR at once.

Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.

### 🔧 Security-gate fix map <!-- tti-fixmap:95c462f71c804c7ba271fe9e333247ef9f2c188f --> The gate failed on these dependency findings — fastest path to green for each: | finding | package | installed → fixed | do this | |---|---|---|---| | CVE-2026-63671 (HIGH) | `@nuxtjs/mdc` | 0.21.1 → 0.22.1 | merge #59 — fix(security): @nuxtjs/mdc ^0.22.2 (CVE-2026-63671) — hold f | | CVE-2026-102829 (CRITICAL) | `@simple-git/argv-parser` | 1.1.1 → 2.0.1 | no fix PR yet — `npm update argv-parser --package-lock-only` | | GHSA-g2v6-rqmx-r4w6 (HIGH) | `@vue/server-renderer` | 3.5.40 → 3.5.42, 3.6.0-rc.6 | no fix PR yet — `npm update server-renderer --package-lock-only` | | CVE-2026-102276 (HIGH) | `brace-expansion` | 5.0.9 → 5.0.10, 3.0.7, 2.1.5, 1.1.19 | merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s | | CVE-2026-102278 (HIGH) | `brace-expansion` | 5.0.9 → 5.0.11, 3.0.8, 2.1.6, 1.1.20 | merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s | | CVE-2026-93687 (HIGH) | `braces` | 3.0.3 → ? | no fix PR yet — `npm update braces --package-lock-only` | | CVE-2026-92708 (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | GHSA-mcm9-63f2-9j32 (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | GHSA-r9w8-h9r3-54w4 (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | GHSA-x5rw-q4pp-hg5g (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | CVE-2026-84375 (HIGH) | `js-yaml` | 4.3.1 → 4.3.2, 3.15.2 | no fix PR yet — `npm update js-yaml --package-lock-only` | | CVE-2026-85393 (HIGH) | `node-forge` | 1.4.0 → ? | no fix PR yet — `npm update node-forge --package-lock-only` | | CVE-2026-104846 (CRITICAL) | `seroval` | 1.5.6 → 1.6.2 | no fix PR yet — `npm update seroval --package-lock-only` | | CVE-2026-104845 (HIGH) | `seroval` | 1.5.6 → 1.6.3 | no fix PR yet — `npm update seroval --package-lock-only` | | GHSA-rgj7-g3m4-5g8c (HIGH) | `sharp` | 0.35.3 → 0.35.4 | no fix PR yet — `npm update sharp --package-lock-only` | | GHSA-wq5f-xc86-pv6w (HIGH) | `sharp` | 0.35.3 → 0.35.5 | no fix PR yet — `npm update sharp --package-lock-only` | | CVE-2026-102422 (CRITICAL) | `shell-quote` | 1.10.0 → 1.11.0 | no fix PR yet — `npm update shell-quote --package-lock-only` | | CVE-2026-102828 (CRITICAL) | `simple-git` | 3.36.0 → 4.0.1 | no fix PR yet — `npm update simple-git --package-lock-only` | | CVE-2026-102826 (HIGH) | `simple-git` | 3.36.0 → 4.0.0 | no fix PR yet — `npm update simple-git --package-lock-only` | | CVE-2026-102827 (HIGH) | `simple-git` | 3.36.0 → 4.0.0 | no fix PR yet — `npm update simple-git --package-lock-only` | | CVE-2026-93749 (HIGH) | `source-map-js` | 1.2.1 → 1.2.2 | no fix PR yet — `npm update source-map-js --package-lock-only` | | CVE-2026-84370 (HIGH) | `svgo` | 4.0.2 → 2.8.4, 3.3.5, 4.1.0 | no fix PR yet — `npm update svgo --package-lock-only` | | CVE-2026-19534 (HIGH) | `undici` | 8.10.0 → 6.28.1, 7.29.1, 8.10.2 | no fix PR yet — `npm update undici --package-lock-only` | | CVE-2026-84961 (HIGH) | `undici` | 8.10.0 → 7.29.1, 8.10.2 | no fix PR yet — `npm update undici --package-lock-only` | | CVE-2026-85152 (HIGH) | `undici` | 8.10.0 → 8.10.2 | no fix PR yet — `npm update undici --package-lock-only` | > ⚠ `main` is itself red right now — this PR likely **inherits** the backlog rather than adding it. Fixing `main` (rows above) unblocks every open PR at once. <sub>Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.</sub>
chore(release): v3.0.1 — editorial numberless navigation, smooth accordion scrolling, and mobile UX polish
Some checks failed
baseline-security / baseline (push) Failing after 1m59s
Details
scan / trivy-fs (push) Failing after 1m26s
Details
ai-review / review (pull_request) Successful in 1m16s
Details
baseline-security / baseline (pull_request) Failing after 1m35s
Details
scan / trivy-fs (pull_request) Failing after 1m4s
Details
publish-package / publish (push) Failing after 52s
Details
5b9f47f578
forgejo-actions commented 2026-10-07 20:09:16 +00:00
Copy link

AI review · advisory

The AI panel couldn't review this change right now (it will review the next push). Details for admins: panel HTTP 401: {"error": {"message": "missing Forgejo credential", "type": "auth", "code": 401}}

### AI review · advisory _The AI panel couldn't review this change right now (it will review the next push). Details for admins: panel HTTP 401: {"error": {"message": "missing Forgejo credential", "type": "auth", "code": 401}}_
forgejo-actions commented 2026-10-07 20:10:17 +00:00
Copy link

🔧 Security-gate fix map

The gate failed on these dependency findings — fastest path to green for each:

finding package installed → fixed do this
CVE-2026-63671 (HIGH) @nuxtjs/mdc 0.21.1 → 0.22.1 merge #59 — fix(security): @nuxtjs/mdc ^0.22.2 (CVE-2026-63671) — hold f
CVE-2026-102829 (CRITICAL) @simple-git/argv-parser 1.1.1 → 2.0.1 no fix PR yet — npm update argv-parser --package-lock-only
GHSA-g2v6-rqmx-r4w6 (HIGH) @vue/server-renderer 3.5.40 → 3.5.42, 3.6.0-rc.6 no fix PR yet — npm update server-renderer --package-lock-only
CVE-2026-102276 (HIGH) brace-expansion 5.0.9 → 5.0.10, 3.0.7, 2.1.5, 1.1.19 merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s
CVE-2026-102278 (HIGH) brace-expansion 5.0.9 → 5.0.11, 3.0.8, 2.1.6, 1.1.20 merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s
CVE-2026-93687 (HIGH) braces 3.0.3 → ? no fix PR yet — npm update braces --package-lock-only
CVE-2026-92708 (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
GHSA-mcm9-63f2-9j32 (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
GHSA-r9w8-h9r3-54w4 (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
GHSA-x5rw-q4pp-hg5g (HIGH) devalue 5.8.2 → 5.9.3 no fix PR yet — npm update devalue --package-lock-only
CVE-2026-84375 (HIGH) js-yaml 4.3.1 → 4.3.2, 3.15.2 no fix PR yet — npm update js-yaml --package-lock-only
CVE-2026-85393 (HIGH) node-forge 1.4.0 → ? no fix PR yet — npm update node-forge --package-lock-only
CVE-2026-104846 (CRITICAL) seroval 1.5.6 → 1.6.2 no fix PR yet — npm update seroval --package-lock-only
CVE-2026-104845 (HIGH) seroval 1.5.6 → 1.6.3 no fix PR yet — npm update seroval --package-lock-only
GHSA-rgj7-g3m4-5g8c (HIGH) sharp 0.35.3 → 0.35.4 no fix PR yet — npm update sharp --package-lock-only
GHSA-wq5f-xc86-pv6w (HIGH) sharp 0.35.3 → 0.35.5 no fix PR yet — npm update sharp --package-lock-only
CVE-2026-102422 (CRITICAL) shell-quote 1.10.0 → 1.11.0 no fix PR yet — npm update shell-quote --package-lock-only
CVE-2026-102828 (CRITICAL) simple-git 3.36.0 → 4.0.1 no fix PR yet — npm update simple-git --package-lock-only
CVE-2026-102826 (HIGH) simple-git 3.36.0 → 4.0.0 no fix PR yet — npm update simple-git --package-lock-only
CVE-2026-102827 (HIGH) simple-git 3.36.0 → 4.0.0 no fix PR yet — npm update simple-git --package-lock-only
CVE-2026-93749 (HIGH) source-map-js 1.2.1 → 1.2.2 no fix PR yet — npm update source-map-js --package-lock-only
CVE-2026-84370 (HIGH) svgo 4.0.2 → 2.8.4, 3.3.5, 4.1.0 no fix PR yet — npm update svgo --package-lock-only
CVE-2026-19534 (HIGH) undici 8.10.0 → 6.28.1, 7.29.1, 8.10.2 no fix PR yet — npm update undici --package-lock-only
CVE-2026-84961 (HIGH) undici 8.10.0 → 7.29.1, 8.10.2 no fix PR yet — npm update undici --package-lock-only
CVE-2026-85152 (HIGH) undici 8.10.0 → 8.10.2 no fix PR yet — npm update undici --package-lock-only

⚠ main is itself red right now — this PR likely inherits the backlog rather than adding it. Fixing main (rows above) unblocks every open PR at once.

Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.

### 🔧 Security-gate fix map <!-- tti-fixmap:5b9f47f5785f4888f81e1fe22feca7cfc6fa9584 --> The gate failed on these dependency findings — fastest path to green for each: | finding | package | installed → fixed | do this | |---|---|---|---| | CVE-2026-63671 (HIGH) | `@nuxtjs/mdc` | 0.21.1 → 0.22.1 | merge #59 — fix(security): @nuxtjs/mdc ^0.22.2 (CVE-2026-63671) — hold f | | CVE-2026-102829 (CRITICAL) | `@simple-git/argv-parser` | 1.1.1 → 2.0.1 | no fix PR yet — `npm update argv-parser --package-lock-only` | | GHSA-g2v6-rqmx-r4w6 (HIGH) | `@vue/server-renderer` | 3.5.40 → 3.5.42, 3.6.0-rc.6 | no fix PR yet — `npm update server-renderer --package-lock-only` | | CVE-2026-102276 (HIGH) | `brace-expansion` | 5.0.9 → 5.0.10, 3.0.7, 2.1.5, 1.1.19 | merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s | | CVE-2026-102278 (HIGH) | `brace-expansion` | 5.0.9 → 5.0.11, 3.0.8, 2.1.6, 1.1.20 | merge #62 — chore(deps): update dependency brace-expansion to v5.0.12 [s | | CVE-2026-93687 (HIGH) | `braces` | 3.0.3 → ? | no fix PR yet — `npm update braces --package-lock-only` | | CVE-2026-92708 (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | GHSA-mcm9-63f2-9j32 (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | GHSA-r9w8-h9r3-54w4 (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | GHSA-x5rw-q4pp-hg5g (HIGH) | `devalue` | 5.8.2 → 5.9.3 | no fix PR yet — `npm update devalue --package-lock-only` | | CVE-2026-84375 (HIGH) | `js-yaml` | 4.3.1 → 4.3.2, 3.15.2 | no fix PR yet — `npm update js-yaml --package-lock-only` | | CVE-2026-85393 (HIGH) | `node-forge` | 1.4.0 → ? | no fix PR yet — `npm update node-forge --package-lock-only` | | CVE-2026-104846 (CRITICAL) | `seroval` | 1.5.6 → 1.6.2 | no fix PR yet — `npm update seroval --package-lock-only` | | CVE-2026-104845 (HIGH) | `seroval` | 1.5.6 → 1.6.3 | no fix PR yet — `npm update seroval --package-lock-only` | | GHSA-rgj7-g3m4-5g8c (HIGH) | `sharp` | 0.35.3 → 0.35.4 | no fix PR yet — `npm update sharp --package-lock-only` | | GHSA-wq5f-xc86-pv6w (HIGH) | `sharp` | 0.35.3 → 0.35.5 | no fix PR yet — `npm update sharp --package-lock-only` | | CVE-2026-102422 (CRITICAL) | `shell-quote` | 1.10.0 → 1.11.0 | no fix PR yet — `npm update shell-quote --package-lock-only` | | CVE-2026-102828 (CRITICAL) | `simple-git` | 3.36.0 → 4.0.1 | no fix PR yet — `npm update simple-git --package-lock-only` | | CVE-2026-102826 (HIGH) | `simple-git` | 3.36.0 → 4.0.0 | no fix PR yet — `npm update simple-git --package-lock-only` | | CVE-2026-102827 (HIGH) | `simple-git` | 3.36.0 → 4.0.0 | no fix PR yet — `npm update simple-git --package-lock-only` | | CVE-2026-93749 (HIGH) | `source-map-js` | 1.2.1 → 1.2.2 | no fix PR yet — `npm update source-map-js --package-lock-only` | | CVE-2026-84370 (HIGH) | `svgo` | 4.0.2 → 2.8.4, 3.3.5, 4.1.0 | no fix PR yet — `npm update svgo --package-lock-only` | | CVE-2026-19534 (HIGH) | `undici` | 8.10.0 → 6.28.1, 7.29.1, 8.10.2 | no fix PR yet — `npm update undici --package-lock-only` | | CVE-2026-84961 (HIGH) | `undici` | 8.10.0 → 7.29.1, 8.10.2 | no fix PR yet — `npm update undici --package-lock-only` | | CVE-2026-85152 (HIGH) | `undici` | 8.10.0 → 8.10.2 | no fix PR yet — `npm update undici --package-lock-only` | > ⚠ `main` is itself red right now — this PR likely **inherits** the backlog rather than adding it. Fixing `main` (rows above) unblocks every open PR at once. <sub>Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.</sub>
Some checks failed
baseline-security / baseline (push) Failing after 1m59s
Details
scan / trivy-fs (push) Failing after 1m26s
Details
ai-review / review (pull_request) Successful in 1m16s
Details
baseline-security / baseline (pull_request) Failing after 1m35s
Required
Details
scan / trivy-fs (pull_request) Failing after 1m4s
Details
publish-package / publish (push) Failing after 52s
Details
This pull request has changes conflicting with the target branch.
  • CHANGELOG.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/marcom-ui-polish:feat/marcom-ui-polish
git switch feat/marcom-ui-polish
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
idea
Feature suggestion — shows on the repo's Ideas tab

  
points
1
 Estimate: 1 point

  
points
13
 Estimate: 13 points

  
points
2
 Estimate: 2 points

  
points
3
 Estimate: 3 points

  
points
5
 Estimate: 5 points

  
points
8
 Estimate: 8 points

  
priority
p0
 Drop everything

  
priority
p1
 High

  
priority
p2
 Medium

  
priority
p3
 Low

  
state
blocked
 Blocked — see dependencies

  
state
done
 Complete

  
state
in-progress
 Being worked

  
state
ready
 Ready to start

  
state
review
 In review

  
state
triage
 Needs triage

  
status
declined
 Not planned — see the closing comment

  
status
in-progress
 Actively being built

  
status
planned
 Accepted — on the roadmap

  
status
proposed
 New suggestion, not yet reviewed

  
status
shipped
 Delivered

  
status
under-review
 Being evaluated by maintainers

  
type
bug
 Defect in existing behaviour

  
type
epic
 Large body of work spanning multiple stories

  
type
feature
 Shippable capability under an epic

  
type
spike
 Time-boxed investigation / research

  
type
story
 User-facing increment, points-estimated

  
type
task
 Implementation unit under a story

No labels
idea
points
1
points
13
points
2
points
3
points
5
points
8
priority
p0
priority
p1
priority
p2
priority
p3
state
blocked
state
done
state
in-progress
state
ready
state
review
state
triage
status
declined
status
in-progress
status
planned
status
proposed
status
shipped
status
under-review
type
bug
type
epic
type
feature
type
spike
type
story
type
task
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
tti/tti-ux!69
No description provided.