decaporg / decap-cms

A Git-based CMS for Static Site Generators
https://decapcms.org
MIT License
17.93k stars 3.04k forks source link

Show build status #2324

Open marcojakob opened 5 years ago

marcojakob commented 5 years ago

It would be really helpful for non-technical users to get information about what's going on during the build to know if the post is already live. Depending (it seems) on how busy the Netlify bots are, we're seeing short and also very long build times. This is very confusing for authors since they are never sure if something went wrong or if it just takes more time.

Would something like the preview links for published content be possible also for the live version? A check build status?

marcojakob commented 5 years ago

I guess the question is how to get information about the build status from Netlify.

A very basic mechanism would be something like the deploy status badges.

export for blog@2x

calebmisclevitz commented 5 years ago

I came here to suggest the same thing! I have no idea how to go about building something like this, but the additional feedback for users would be a good UX improvement.

One of the hesitations I have using static site generators with clients is the confusion about the publishing latency, since most of them have learned from wordpress/twitter/etc to expect instant feedback. Showing something like Changes Submitted | Building: 65% would be a lot clearer.

calebmisclevitz commented 5 years ago

Related, I think the progress bar and messaging publishing..., published is misleading, since it refers primarily to the status of the commit, rather than the build. If the commit succeeds, the content is not necessarily "published".

erquhart commented 5 years ago

@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 - you'll see the same verbiage in Contentful, for example. But if we can get deploy status checks working, that verbiage can definitely be improved đź‘Ť

andrevandal commented 5 years ago

Any update?

erquhart commented 5 years ago

No movement, needs planning.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

marcojakob commented 5 years ago

Stackbit just released a Netlify status. Could serve as inspiration: https://www.stackbit.com/control-center/

unnamed

erquhart commented 5 years ago

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 for Netlify CMS. And deploy it on Netlify. (Insert “yo dawg” meme here.)

Sent with GitHawk

dashpilot commented 4 years ago

Inspired by the Stackbit widget, I created a little widget that shows the current Netlify build status and integrates into Netlify CMS & Netlify Identity. You press save in Netlify CMS, visit your site, and you'll see the current build status of your site (only if you're logged in with Netlify Identity). In the background the widget polls the (included) Netlify function for the current build status. It includes detailed instructions on how to use it. I welcome any feedback on the implementation, because it's been a while since I've released anything ;-) Netlify Build Status Widget

Check it out: https://github.com/dashpilot/netlify-build-status-widget

kylekirkby commented 4 years ago

It would be great to have the build status shown in the nav of NetlifyCMS (next to the "Deploy preview" link). We should defnitely look at adding the ability to prevent a publish if any of the status checks fail on the GitHub PR. For instance, we've got a custom link checker that we've been using on our sites for the past 3 years and religiously do not merge if links fail.

adunkman commented 2 years ago

Currently running into a confusing issue on a site which is most likely caused by preview URLs being re-used, and therefore users of NetlifyCMS need to wait for a build to complete before looking at the preview. Without knowing build status… it’s kind of a shot in the dark on what that timing looks like.