Repository navigation
Conversation
8 tasks
Deploying ui with
|
| Latest commit: |
58fa5fb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://34fae492.ui-6d0.pages.dev |
| Branch Preview URL: | https://docs-collaborative-artifact.ui-6d0.pages.dev |
horner
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Plan a collaborative component that handles almost all email display and composition work for mail clients: an IMAP client passes fetched raw message bytes to the component and receives complete-message output for host-owned draft-save/send adapters. MIME email is a first-class use case; MDY is the preferred format for hosts that do not need MIME.
The implementation plan includes message headers and MIME conventions, inline media/attachments, new messages, draft editing, reply/reply-all, and forwarding. It distinguishes source export, draft save, and delivery serialization, including the separate transport recipient envelope. A minimal mail-client integration with no caller MIME parsing or rewriting is an acceptance gate.
Eight phased milestones coordinate UI, Kerebron, Artipod, eSheet, and yorm. Shared Artipod storage, existing yorm DocumentSession, eSheet default Artifact scopes/question overrides, parallel implementation, and owner-approved migration/deprecation remain part of the plan.
Refs #755. That issue tracks implementation and stays open after this planning PR merges.
Checklist
git diff --checkpasses.pnpm lintandpnpm formatpass.pnpm typecheck && pnpm lint && pnpm format && pnpm testall pass.Initial local typecheck is blocked by the missing
@kerebron/extension-menupackage in the existing dependency installation. The same unresolved import blocks five test suites; 185 suites and 2,657 tests pass. These failures are recorded for transparency; this PR changes only the planning document and leaves source, dependencies, and submodule revisions out of the commit.Visual tests and RTL rendering checks are not applicable to this documentation-only change. Implementation examples, browser validation, and the multi-user acceptance scenarios are future milestone requirements in the plan.
The MIME/email clarification also passes document formatting, structure, terminology, and scope-diagram checks. The earlier source quality-gate results above remain applicable to the unchanged source tree.