How I build an unpublish and archive workflow in Sanity
That's fine for a quick takedown, but it doesn't tell you why the document is off the site, and it gives editors no way to distinguish 'needs rework' from 'permanently retired'. Here's the three-action workflow I land on for most client projects: Unpublish, Archive, and Restore — all without touching the delete button. Why not just delete Deletion is irreversible without a dataset export.
- ▪That's fine for a quick takedown, but it doesn't tell you why the document is off the site, and it gives editors no way to distinguish 'needs rework' from 'permanently retired'.
- ▪Here's the three-action workflow I land on for most client projects: Unpublish, Archive, and Restore — all without touching the delete button.
- ▪Why not just delete Deletion is irreversible without a dataset export.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 2638501) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Nayan Kyada Posted on Jun 30 • Originally published at nayankyada.com How I build an unpublish and archive workflow in Sanity #sanitycms #groq #sanitystudio #nextjs The default Sanity unpublish document action does one thing: it unpublishes and leaves a draft sitting in the Studio. That's fine for a quick takedown, but it doesn't tell you why the document is off the site, and it gives editors no way to distinguish 'needs rework' from 'permanently retired'.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
