-
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
-
Forte Reactions — Step 3: Development Plan
docs/plans/archive/forte_reactions_step3_development_plan.md Plans Plans and history
-
Forte Reactions — Step 4: Implementation Summary
docs/plans/archive/forte_reactions_step4_implementation_summary.md Plans Plans and history
-
Forte Reply — Step 1: Solution Assessment
Forte's paned reader has a disabled "Reply" toolbar button (templates/pages/forte.php:10-13) with no way to compose a reply to the selected post, while the cla…
docs/plans/archive/forte_reply_step1_solution_assessment.md Plans Plans and history
-
Forte Reply — Step 2: Feature Description
Forte's paned reader has a disabled "Reply" toolbar button and no way to compose a reply to the selected post without leaving the paned window for the classic…
docs/plans/archive/forte_reply_step2_feature_description.md Plans Plans and history
-
Forte Reply — Step 3: Development Plan
docs/plans/archive/forte_reply_step3_development_plan.md Plans Plans and history
-
Forte Reply — Step 4: Implementation Summary
docs/plans/archive/forte_reply_step4_implementation_summary.md Plans Plans and history
-
Forte Session-Recovery Routes: Step 1 Solution Assessment
When a PHP session is absent, valid Forte routes are rejected as nonexistent before their handlers or the shared reauthentication-resume flow can run.
docs/plans/archive/forte_session_recovery_routes_step1_solution_assessment.md Plans Plans and history
-
Forte Session-Recovery Routes: Step 2 Feature Description
Valid Forte URLs can be classified as nonexistent when the member session is absent, preventing the existing reauthentication-recovery experience.
docs/plans/archive/forte_session_recovery_routes_step2_feature_description.md Plans Plans and history
-
Forte Session-Recovery Routes: Step 3 Development Plan
docs/plans/archive/forte_session_recovery_routes_step3_development_plan.md Plans Plans and history
-
Forte Session-Recovery Routes: Step 4 Implementation Summary
docs/plans/archive/forte_session_recovery_routes_step4_implementation_summary.md Plans Plans and history
-
Forte Shared Toolbar — Step 1: Solution Assessment
Forte's three paned views have inconsistent toolbars — Board has the full button set, Activity has only "Board" + a disabled "Refresh", and Users has no toolba…
docs/plans/archive/forte_shared_toolbar_step1_solution_assessment.md Plans Plans and history
-
Forte Shared Toolbar Step 2 Feature Description
Forte's three paned views render different toolbars - Board has the full button set, Activity has only "Board" + a disabled "Refresh", and Users has no toolbar…
docs/plans/archive/forte_shared_toolbar_step2_feature_description.md Plans Plans and history
-
Forte Shared Toolbar Step 3 Development Plan
docs/plans/archive/forte_shared_toolbar_step3_development_plan.md Plans Plans and history
-
Forte Shared Toolbar Step 4 Implementation Summary
docs/plans/archive/forte_shared_toolbar_step4_implementation_summary.md Plans Plans and history
-
Forte Step 1 Solution Assessment
Users want to explore a Usenet/Forte Agent-like interface using the existing forum backend and frontend capabilities.
docs/plans/archive/forte_step1_solution_assessment.md Plans Plans and history
-
Forte Step 2 Feature Description
Users want a two-pane, Forte-Agent-styled thread reader — a nested-reply title list in one pane and a content pane for the selected post in the other — built f…
docs/plans/archive/forte_step2_feature_description.md Plans Plans and history
-
Forte Step 3 Development Plan
docs/plans/archive/forte_step3_development_plan.md Plans Plans and history
-
Forte Step 4 Implementation Summary
docs/plans/archive/forte_step4_implementation_summary.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 1: Solution Assessment
Selecting a thread on Forte's board never updates the URL (only tag/sort changes do), so reloading the page loses the current thread selection.
docs/plans/archive/forte_thread_selection_url_sync_step1_solution_assessment.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 2: Feature Description
Selecting a thread on Forte's board never updates the URL — only tag/sort changes do — so reloading or sharing a link loses the current thread selection.
docs/plans/archive/forte_thread_selection_url_sync_step2_feature_description.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 3: Development Plan
docs/plans/archive/forte_thread_selection_url_sync_step3_development_plan.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 4: Implementation Summary
docs/plans/archive/forte_thread_selection_url_sync_step4_implementation_summary.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 1: Solution Assessment
The Forte Users page (/forte/users/) is a single flat list, while Board and Activity already offer a filter pane + listing pane + detail pane, and we want User…
docs/plans/archive/forte_users_three_pane_step1_solution_assessment.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 2: Feature Description
The Forte Users page is a flat list of names, unlike Board and Activity's filter + listing + detail layout, so admins can't filter or inspect a user without le…
docs/plans/archive/forte_users_three_pane_step2_feature_description.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 3: Development Plan
Supersedes the alphabetical filter (Stages 2/4/5 above) per the Step 2 addendum.
docs/plans/archive/forte_users_three_pane_step3_development_plan.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 4: Implementation Summary
Per the Step 2/Step 3 addenda, replacing the alphabetical filter with semantic categories.
docs/plans/archive/forte_users_three_pane_step4_implementation_summary.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 1 Solution Assessment
A newly created browser key can fail its first signed identity-bootstrap verification even though a reload successfully publishes the same key, forcing users t…
docs/plans/archive/identity_bootstrap_signature_recovery_step1_solution_assessment.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 2 Feature Description
First-time browser-key setup can report an identity-bootstrap signature failure even when reloading lets the same key publish successfully.
docs/plans/archive/identity_bootstrap_signature_recovery_step2_feature_description.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 3 Development Plan
docs/plans/archive/identity_bootstrap_signature_recovery_step3_development_plan.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 4 Implementation Summary
docs/plans/archive/identity_bootstrap_signature_recovery_step4_implementation_summary.md Plans Plans and history
-
Invite Destination Selector — Step 1: Solution Assessment
On the invites page, destination entry should appear only when opted in and offer a typeable choice of recently used internal locations.
docs/plans/archive/invite_destination_selector_step1_solution_assessment.md Plans Plans and history
-
Invite Destination Selector — Step 2: Feature Description
The invites page always shows a disabled destination input and makes members type every destination, even when they are repeatedly inviting people to common or…
docs/plans/archive/invite_destination_selector_step2_feature_description.md Plans Plans and history
-
Invite Destination Selector — Step 3: Development Plan
docs/plans/archive/invite_destination_selector_step3_development_plan.md Plans Plans and history
-
Invite Destination Selector — Step 4: Implementation Summary
docs/plans/archive/invite_destination_selector_step4_implementation_summary.md Plans Plans and history
-
Invite Session Authentication: Step 1 Solution Assessment
On a public instance, the Account page can show an approved browser identity and the Invite link, while the invitation route cannot read that authenticated ses…
docs/plans/archive/invite_session_authentication_step1_solution_assessment.md Plans Plans and history
-
Invite Session Authentication: Step 2 Feature Description
On a public instance, an approved member with a saved browser key is not consistently recognized after their server session expires.
docs/plans/archive/invite_session_authentication_step2_feature_description.md Plans Plans and history