Shawn Erquhart

Definitely - are you up for opening a PR for that? Happy to support for sure.

I'll leave it open in case someone is up to it 👍 Thanks for raising!

@matthew-dean I think he means a small website/app with styles written in less and a watch task in place via npm-scripts/grunt/gulp.

I'm honestly not certain what the original intent was, but the use cases mentioned here are sensible and should be supported. That said, and as @barthc points out, field validation...

@marcojakob totally agree, that was always the long term plan when we implemented Deploy Preview Links. @calebmisclevitz I see your point, but this is the standard at the moment -...

No movement, needs planning.

The issue is handling this in a way that is not Netlify specific. We could also open an API for provider specific plugins, then you could get the Netlify plugin...

My only concern here is paginated backends, where the entire collection may not be readily available (not sure if that's ever the case at this point with our current pagination...

This is absolutely fantastic, awesome work @austincondiff!!

We're showing a lot of things at once, that's the core problem. We're trying to solve it by making boundaries and hierarchy clear yet subtle. What if we tried showing...