Document the reasons for not using Workspaces for saving in 0.2.0

Created on 12 March 2025, 6 months ago

Overview

This should have been done earlier, but better late than never.

Proposed resolution

Add an ADR around auto-save

User interface changes

πŸ“Œ Task
Status

Active

Version

0.0

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @tedbow
  • πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA
  • Merge request !777Draft: #3512616 add adr doc β†’ (Open) created by tedbow
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Excellent first pass β€” curious about @effulgentsia's thoughts, but already posted a review with a few questions and suggestions.

  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί
  • Assigned to effulgentsia
  • Status changed to Needs review 4 months ago
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    @effulgentsia: please prioritize this ASAP, because the decisions here need to be properly documented, given that proposals are starting to surface to change it: [#3524298.

  • πŸ‡ΊπŸ‡ΈUnited States effulgentsia

    Initially we were only planning to postpone Workspaces to a later 0.x version, but now we're postponing it till after 1.0.0, so re-titling this issue, and we may want to adjust the language in the MR as well.

    Where Workspaces will become increasingly crucial is for editing individual nodes within XB, but that's also something we're postponing until after 1.0.0. 1.0.0 will just be for Pages and Content Templates.

    I agree in principle that ADRs are valuable and that they're more valuable sooner than later, so I'll try to make time for this when I'm able to, but we're not going to block a stable release on getting this ADR published.

Production build 0.71.5 2024