[docs] Broken link "/dav/subscriptions" on page "/dav/clients/ical"

[leso-kn]

The current docs page about the "iCal" client references a non-existent page about webcal subscriptions, resulting in a 404 upon navigation.

The two questions that come up here are:

1. Does sabre-io/dav support server-side webcal subscriptions? And following up on that
2. Should an according page be created or should the reference be removed / replaced?

Judging by the information on https://sabre.io/dav/clients/ical/#subscriptions it feels like subscriptions are supported and the docs page has just not been created?

[phil-davis]

AFAIK these docs are not really maintained any more. There have been a few contributions that fixed typos and so on in the last year, but that's all.

The https://sabre.io/support/ page links to Professional Support by https://fruux.com/ but I have no idea if they are still operating...
I know that I emailed to their sales contact email on that page a while ago to try and find out, but got no response.

So I don't think that the https://sabre.io site is being managed any more. For example, the latest item in News is from Feb 19, 2019.

I have been making various sabre releases as a volunteer in recent years, and have heard nothing from Fruux.

@DeepDiver1975 @staabm do you have any idea how the https://sabre.io/ keeps running - who is keeping a server running somewhere, keeping the domain name registered, and so on?

[staabm]

I think its a thing @DominikTo owns

[DominikTo]

Looks like this is an oversight and the doc page (for server side managed subscriptions) was never created.
There is https://sabre.io/dav/ics-export-plugin/, but that's about providing iCalendar feeds, not about server-side managed subscriptions.

Now that #138 seems to be fixed, it might make sense to add the missing releases to https://github.com/sabre-io/sabre.io/tree/master/source/_posts

[phil-davis]

Issue #138 has been finished. Changes to docs content and layout in this repo are now published/deployed when a PR is merge.
So anyone can make a PR to sort out this doc issue.