Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create URL structure for Calendar #66

Closed
Me4ta opened this issue Mar 16, 2016 · 1 comment
Closed

Create URL structure for Calendar #66

Me4ta opened this issue Mar 16, 2016 · 1 comment

Comments

@Me4ta
Copy link
Collaborator

Me4ta commented Mar 16, 2016

We need to think this through, since we want our URL structure to be adequate from the beginning, current requirements are:

  • calendar name should be part of the url
  • url should be short
  • should state be part of url? (I think only if we need to have similarly named calendars for different states like rcn.io/cal/ca/racing and rcn.io/cal/ny/racing

Possible options:
rcn.io/cal/ncnca/2016 — name-centric, year is secondary
rcn.io/cal/2016/ncnca — year centric
rcn.io/cals/ncnca/2016 — same as above but "cal" is in plural

Current shema:
rcn.io/calendars/{id} (where id starts from cal- but we strip out cal-to make url better looking)

rcn.io/calendars/ncnca-216

@Me4ta Me4ta added this to the Internal MVP 1.0 milestone Mar 16, 2016
@Restuta
Copy link
Owner

Restuta commented Jun 8, 2016

So far we are using:

http://rcn.io/calendars/norcal-mtb

so it's calendars/{:id}/

for events it can be:
calendars/ncnca-2016/events/evt-afw23

for events it's rcn.io/events/evt-1234/ since event can be in multiple calendars and for rendering/app performance it's easier not to nest it under calendars/

Calendar can be referenced by short name or id if short name exists it should be treated as canonical URL and we should redirect, so if NCNCA 2016 calendar has internal id of cal-sdf234 then when we access calendars/cal-sdf234 we must redirect to calendars/ncnca-2016

I decided to take simpler approach, just strip out cal- part from id and let calendars have arbitrary ids that would cover nice ones like ncnca-2016 and any random ones like aff323

Todo:

  • figure out how to represent years, e.g. calendars/ncnca-2016/ is hardcoded into url, so year is part of the calendar itself
  • figure out how to represent "always up to date calendars" e.g. NCNCA calendar for each year should be accessible via calendars/ncnca and calendars/ncnca-2016/ or calendars/ncnca?year=2016 or else
    • it's probably not a good idea, it only helps to have one link to "current" calendar, but somebody will still have to update it or write code to point to "current year's calendar", imo not worth the trouble

@Restuta Restuta modified the milestones: Public MVP 1.0, Internal MVP 1.0 Jun 8, 2016
@Restuta Restuta added the info label Dec 27, 2016
@Restuta Restuta closed this as completed Dec 27, 2016
@Restuta Restuta added the Closed label Dec 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants