shift-org / shift-org/shift-docs

Calendar - links to public event listings from edit page for published events

Open
#402 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement frontend
Dominant language
JavaScript
Stars
30
Forks
25
Avg merge
9m
Merged PRs (30d)
1

Description

Once you publish an event, there isn't a way to jump from the private edit page to the public listing. Being able to see it on the public calendar would help you get the URL and copy it, confirm the listing looks right, etc. (There is a "preview" function on the edit form but currently a few things about it are different than the real listing.)

This would likely be simple enough for single occurrence events. For events with multiple occurrences it would be a little trickier, especially if you add or change occurrences. (New occurrences won't have a public link yet until you save the form.) Related, multi-occurrence events don't have a single public link which shows all occurrences. If such a thing existed we could possibly use it here. (Perhaps it could implemented via a general search API which allows searching by specific fields, using something like ?calevent_id=99999; see also #335.)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the edit page's existing preview function and the public event listing, comparing how single- and multi-occurrence events are represented. Read the discussion in #335 for the proposed search API direction. Done means published events have a usable public link from the edit page, with behavior defined for newly changed or multiple occurrences.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.