-
Forte Board View Step 3 Development Plan
docs/plans/archive/forte_board_view_step3_development_plan.md Plans Plans and history
-
Forte Board View Step 4 Implementation Summary
docs/plans/archive/forte_board_view_step4_implementation_summary.md Plans Plans and history
-
Forte Compose Thread — Step 1: Solution Assessment
The board toolbar's "New" button exists in Forte's markup but is permanently disabled, wired to nothing — there's no way to start a new thread from within Fort…
docs/plans/archive/forte_compose_thread_step1_solution_assessment.md Plans Plans and history
-
Forte Compose Thread — Step 2: Feature Description
Forte's board toolbar has a "New" button that's permanently disabled — there's no way to start a new thread from within Forte at all, only to reply to existing…
docs/plans/archive/forte_compose_thread_step2_feature_description.md Plans Plans and history
-
Forte Compose Thread — Step 3: Development Plan
docs/plans/archive/forte_compose_thread_step3_development_plan.md Plans Plans and history
-
Forte Compose Thread — Step 4: Implementation Summary
docs/plans/archive/forte_compose_thread_step4_implementation_summary.md Plans Plans and history
-
Forte CSS Isolation Step 1 Solution Assessment
Forte's paned-reader styles live inside site.css alongside the classic UI's themeable rules, so every .paned- selector must out-specificity or override the sit…
docs/plans/archive/forte_css_isolation_step1_solution_assessment.md Plans Plans and history
-
Forte CSS Isolation Step 2 Feature Description
Forte's paned-reader rules live inside site.css next to the classic UI's themeable rules, so every Forte selector has to defensively out-specificity the classi…
docs/plans/archive/forte_css_isolation_step2_feature_description.md Plans Plans and history
-
Forte CSS Isolation Step 3 Development Plan
docs/plans/archive/forte_css_isolation_step3_development_plan.md Plans Plans and history
-
Forte CSS Isolation Step 4 Implementation Summary
docs/plans/archive/forte_css_isolation_step4_implementation_summary.md Plans Plans and history
-
Forte Deprecate Single-Thread View — Step 1: Solution Assessment
Forte has two views: the single-thread reader (/threads/{id}/forte) and the board view (/forte).
docs/plans/archive/forte_deprecate_single_thread_view_step1_solution_assessment.md Plans Plans and history
-
Forte Deprecate Single-Thread View — Step 2: Feature Description
The single-thread Forte reader (/threads/{id}/forte) is a fully duplicate, unreachable view — the board view (/forte) already does everything it does and is th…
docs/plans/archive/forte_deprecate_single_thread_view_step2_feature_description.md Plans Plans and history
-
Forte Deprecate Single-Thread View — Step 3: Development Plan
docs/plans/archive/forte_deprecate_single_thread_view_step3_development_plan.md Plans Plans and history
-
Forte Deprecate Single-Thread View — Step 4: Implementation Summary
docs/plans/archive/forte_deprecate_single_thread_view_step4_implementation_summary.md Plans Plans and history
-
Forte Hidden Content Permalinks — Step 1: Solution Assessment
Activity-view links to identity/bootstrap/approval-only content fall back to the classic (non-Forte) /posts///threads/ pages, because those threads are exclude…
docs/plans/archive/forte_hidden_content_permalinks_step1_solution_assessment.md Plans Plans and history
-
Forte Hidden Content Permalinks — Step 2: Feature Description
Clicking a content link from the Forte Activity view leaves Forte for the classic interface whenever the underlying content is identity/bootstrap/approval-only…
docs/plans/archive/forte_hidden_content_permalinks_step2_feature_description.md Plans Plans and history
-
Forte Hidden Content Permalinks — Step 3: Development Plan
docs/plans/archive/forte_hidden_content_permalinks_step3_development_plan.md Plans Plans and history
-
Forte Hidden Content Permalinks — Step 4: Implementation Summary
docs/plans/archive/forte_hidden_content_permalinks_step4_implementation_summary.md Plans Plans and history
-
Forte Identity Signing — Step 1: Solution Assessment
Forte's reply composer never loads the browser-key signing scripts, so every reply posted from Forte is silently anonymous even for readers with a signed ident…
docs/plans/archive/forte_identity_signing_step1_solution_assessment.md Plans Plans and history
-
Forte Identity Signing — Step 2: Feature Description
Forte's board-view reply composer never loads the browser-key signing scripts, so every reply posts as anonymous "guest" even for readers with an existing sign…
docs/plans/archive/forte_identity_signing_step2_feature_description.md Plans Plans and history
-
Forte Identity Signing — Step 3: Development Plan
docs/plans/archive/forte_identity_signing_step3_development_plan.md Plans Plans and history
-
Forte Identity Signing — Step 4: Implementation Summary
docs/plans/archive/forte_identity_signing_step4_implementation_summary.md Plans Plans and history
-
Forte Keyboard Navigation Step 1 Solution Assessment
As a keyboard user, I want to Tab between Forte's panes (and clickable elements in the content pane), and use arrow keys to move the selection within the tags…
docs/plans/archive/forte_keyboard_navigation_step1_solution_assessment.md Plans Plans and history
-
Forte Keyboard Navigation Step 2 Feature Description
Forte's panes (folder tree, thread/reply list, content pane) aren't reachable or operable by keyboard today — the list rows aren't focusable at all, so Tab ski…
docs/plans/archive/forte_keyboard_navigation_step2_feature_description.md Plans Plans and history
-
Forte Keyboard Navigation Step 3 Development Plan
docs/plans/archive/forte_keyboard_navigation_step3_development_plan.md Plans Plans and history
-
Forte Keyboard Navigation Step 4 Implementation Summary
docs/plans/archive/forte_keyboard_navigation_step4_implementation_summary.md Plans Plans and history
-
Forte New Thread Dialog Status — Step 1: Solution Assessment
Now that the New Thread dialog runs the full compose JS, every in-flight/error status message (setStatus, e.g.
docs/plans/archive/forte_new_thread_dialog_status_step1_solution_assessment.md Plans Plans and history
-
Forte New Thread Dialog Status — Step 2: Feature Description
The New Thread dialog now runs the full compose JS, but it has no status line to render into, so signing/identity progress and error feedback are silently drop…
docs/plans/archive/forte_new_thread_dialog_status_step2_feature_description.md Plans Plans and history
-
Forte New Thread Dialog Status — Step 3: Development Plan
docs/plans/archive/forte_new_thread_dialog_status_step3_development_plan.md Plans Plans and history
-
Forte New Thread Dialog Status — Step 4: Implementation Summary
docs/plans/archive/forte_new_thread_dialog_status_step4_implementation_summary.md Plans Plans and history
-
Forte Post Permalink — Step 1: Solution Assessment
Forte has no shareable direct link to one specific post — classic has /posts/{id}, but Forte's own board can only ever be linked at the thread level (/forte?se…
docs/plans/archive/forte_post_permalink_step1_solution_assessment.md Plans Plans and history
-
Forte Post Permalink — Step 2: Feature Description
Forte has no shareable direct link to one specific post — only a thread-level link (/forte?selected={threadId}), with no way to point at one specific post or r…
docs/plans/archive/forte_post_permalink_step2_feature_description.md Plans Plans and history
-
Forte Post Permalink — Step 3: Development Plan
docs/plans/archive/forte_post_permalink_step3_development_plan.md Plans Plans and history
-
Forte Post Permalink — Step 4: Implementation Summary
docs/plans/archive/forte_post_permalink_step4_implementation_summary.md Plans Plans and history
-
Forte Profiles — Step 1: Solution Assessment
Forte has no user directory and no Forte-native profile page; author names already link out to classic's /profiles/{slug}//user/{username} (inherited for free…
docs/plans/archive/forte_profiles_step1_solution_assessment.md Plans Plans and history
-
Forte Profiles — Step 2: Feature Description
Forte has no user directory and no Forte-native profile destination; author names link out to classic today, inherited for free via a shared template helper.
docs/plans/archive/forte_profiles_step2_feature_description.md Plans Plans and history
-
Forte Profiles — Step 3: Development Plan
Amended after Stage 1: /forte/user/{username} turned out to be a materially different, bigger page than assumed (classic's username.php aggregates across every…
docs/plans/archive/forte_profiles_step3_development_plan.md Plans Plans and history
-
Forte Profiles — Step 4: Implementation Summary
(Stage numbers below reflect the Step 3 amendment recorded after this stage — see that doc's note.)
docs/plans/archive/forte_profiles_step4_implementation_summary.md Plans Plans and history
-
Forte Reactions — Step 1: Solution Assessment
Forte's board has no Like/Flag reactions; classic already has this via /api/applythreadtag / /api/applyposttag + threadreactions.js, but that script's thread-l…
docs/plans/archive/forte_reactions_step1_solution_assessment.md Plans Plans and history
-
Forte Reactions — Step 2: Feature Description
Forte's board has no way to Like a thread or Flag a post; classic already supports both, but the classic Like/Flag implementation assumes it's only ever showin…
docs/plans/archive/forte_reactions_step2_feature_description.md Plans Plans and history