From ec9c9c72bc6c3a4406a7b360590dd056a4095ac7 Mon Sep 17 00:00:00 2001 From: ZDDC Date: Mon, 8 Jun 2026 15:16:22 -0500 Subject: [PATCH] fix(landing): trailing slash on working/staging/reviewing project links MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit These three are virtual party-aggregator folders — the trailing slash serves their dir_tool (the browse folder-nav listing of parties INSIDE the folder), while the no-slash form served the browse tool scoped at the project level. Land the user inside the folder. archive/ keeps the no-slash form (its default_tool is the archive tool, which is the intended landing there). Co-Authored-By: Claude Opus 4.8 (1M context) --- landing/js/landing.js | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/landing/js/landing.js b/landing/js/landing.js index c6f1a23..6124da6 100644 --- a/landing/js/landing.js +++ b/landing/js/landing.js @@ -684,9 +684,12 @@ var p = encodeURIComponent(project); var stages = [ { id: 'stageArchive', href: '/' + p + '/archive' }, - { id: 'stageWorking', href: '/' + p + '/working' }, - { id: 'stageStaging', href: '/' + p + '/staging' }, - { id: 'stageReviewing', href: '/' + p + '/reviewing' }, + // working/staging/reviewing get a trailing slash so the user lands + // INSIDE the folder (the dir_tool browse listing of parties), + // not on the browse tool scoped at the project level. + { id: 'stageWorking', href: '/' + p + '/working/' }, + { id: 'stageStaging', href: '/' + p + '/staging/' }, + { id: 'stageReviewing', href: '/' + p + '/reviewing/' }, ]; for (var i = 0; i < stages.length; i++) { var a = document.getElementById(stages[i].id);