[docs] Sign-in side template image not loading (503 error) about material-ui

[mbrookes]

https://source.unsplash.com/random?wallpapers

I imagine it's a transient error and will come back...

[zanivan]

Hey @onlinejudge95 nice catch! As @mbrookes said, it seems to be an issue with the Unsplash URL, and hopefully, it'll come back.

Fortunately, this has been fixed on the revamped templates—however, it's only available on the next branch for now. Is it worth adding a fix in the master branch if the Unsplash URL doesn't return @mnajdova @DiegoAndai?

[mnajdova]

Fortunately, this has been fixed on the revamped templates—however, it's only available on the next branch for now. Is it worth adding a fix in the master branch if the Unsplash URL doesn't return @mnajdova @DiegoAndai?

I would honestly avoid this. If we do this, we will have to update the styled() calls to match the syntax for v5 (I mean the one compatible with ^5.0.0). I honestly do not think it's worth it.

[onlinejudge95]

@mbrookes Unsplash team replied that they are not going to fix this API(sources.unsplash.com), and instead want to onboard to a separate API `

@mnajdova then I would suggest any one of these

• Use the updated Unsplash API
• Remove the demo
• Rename the demo

API links

• https://unsplash.com/developers
• https://help.unsplash.com/en/collections/1451694-api-guidelines
• https://unsplash.com/documentation

[onlinejudge95]

@zanivan I did raise the same to the Unsplash team, let's see if they revert, nevertheless v5 is not going to be deprecated and since this is present in the Getting Started section of the doc, I would be in favor of fixing this.

[mnajdova]

Use the updated Unsplash API

@zanivan it makes sense to do this

[zanivan]

Would a static image work instead? I wonder if it's worth using an API just to randomize the wallpaper in the template. Maybe a local static image would be more future-proof, in my opinion.

[onlinejudge95]

It is better to use a local image.

I tried updating the doc with the new API but the Unsplash team has made this an authenticated route now, I don't see the point of integrating an authenticated API just for a template in the demo site.