Summary
Artefacts can be shared through three publishing mechanisms, each with different visibility and access control.
Publishing Methods
1. Global Publish
- Artefact appears in a public artefact directory
- Discoverable by all users of the platform
- Name "global" is a working title — needs a better name
- The directory itself needs design work (search, categories, featured, etc.)
2. Link Sharing
- Generates a unique URL for the artefact
- Anyone with the link can view a read-only version
- No authentication required to view
- The read-only view should be clean and presentable (think: shared Google Doc in view mode)
- Links can be revoked
3. Team/Organisation Sharing
- Share with specific users or teams within the user's organisation
- Requires the teams & organisations feature (see 09-teams-organisations.md)
- Recipients see the artefact in their own artefacts section (or a "shared with me" view)
- Permissions TBD (view only? comment? duplicate?)
Multiple Publishing Methods
An artefact can be published via multiple methods simultaneously:
- Published globally AND shared via link AND shared with a team
- Each method can be independently enabled/disabled
Published Artefacts View
The artefacts section should include a dedicated area showing:
- All currently published artefacts
- Which publishing methods are active for each
- Share links (copyable)
- Quick actions to unpublish or modify sharing
Read-Only View (Link Sharing)
When someone opens a shared link, they see:
- The artefact content in a clean, readable format
- Artefact metadata (title, author, date)
- No editing capabilities
- Possibly a "Sign up" or "Learn more" CTA for non-users
Open Questions
- What does the global directory look like? Categories? Search? Featured?
- Should globally published artefacts be indexed by search engines?
- Can link-shared artefacts have password protection?
- Should there be analytics on shared artefacts? (view count, who viewed)
- Can shared artefacts be commented on by recipients?
- What's the naming convention for the global publish feature?
- Should there be an approval flow for global publishing?
- How do we handle artefact updates after publishing? (Auto-update? New version? Notification to viewers?)