gitana/alpaca

JSDoc is broken (Documentation page link or resource)

Opened this issue · 4 comments

Jasata commented

This seems to be an annual issue, as I see still open ones for 2016, 2017 and 2018. So, let me make one for 2019 before this year closes.

The link to JSDoc in the documentation page is either outdated or the resource is broken.

<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>5001CB1018C4A7DA</RequestId>
<HostId>
eGaisg+WIVdHYYT8DwF6EnnqgXNZtrfIAE/q1T6Bbt2cDdTRxer9cgkA1QR8IN8alsWleQmGlUQ=
</HostId>
</Error>
WhileTrueEndWhile commented

Looks like it's more broken now compared to #648

This link does not work either now:
https://code.cloudcms.com/alpaca/1.5.0/jsdoc/index.html

Jasata commented

Just my 2 cents worth, but... If this is a reoccurring issue, could the documentation have automatically updated link .../alpaca/jsdoc/latest/index.html and link to that, solving this particular issue for good?

obenausd commented

I am also looking for the JSDoc.
I hope this will be fixed as soon as possible.

Maybe this project is no longer maintained?
Are there any other recommendations?

Jasata commented

Maybe this project is no longer maintained?
Are there any other recommendations?

After half a year without even a label on this issue, only one very minor commit during past month and just by looking at the last commits column in the repository listing ... last real changes being over 13 months old ... AND considering this issue which is not a feature request but a request to fix broken documentation - I think it is fair to say that this is no longer maintained (let alone developed).

As for alternatives... Everyone and their dog have gone the way of large frameworks and smart components like this are now - if not already dead - a dying breed. Or in other words, I do not have any reasonable alternative to give. Instead of this, in my hour of need, I chose JSONForm instead. It has quirks and documentation is lacking in some areas, but for me it felt easier to hammer into submission. Pun intended. That's one of the major issues of JSONForm... you need to implement some JavsScript trickery to disable POST submission to be able to send JSON to an API endpoint instead. (To create a JSON form ... and kind forget that traffic goes both ways...??). I don't know - it could be just a bug in form rendering as well. Didn't bother to look into it.

For me, creating about one very small site every 2 to 3 years, having to learn frameworks feels VERY unpleasant. They have too many rules and specifics for a casual user and I am guaranteed to have forgotten them by the time I need it again - not to mention that they die and new flavors for some months keep popping up much too fast for someone like me, who does not work with websites nor cares to become too involved.

I am sad to see the era of website building components (such as this) to wither and die.

  • 😕1