London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
You could just use access rights to prevent unauthorized user to see the new content before it is finished.
From my experience, some editors find the project feature hard to understand. My advice is to avoid it, if you can.
We have a need to roll out around a large amount of pages over the course of a few months (aprox 10,000). We are thinking of launching pages in batches of ~500 at a time, on a weekly staggered timeline.
I am thinking that this is the perfect use-case for Projects in Episerver. Please let me know if you disagree.
The current plan is to (every week)…
We’re thinking of spawning a new project every week to handle this, so really we’ll have 4-5 active projects at a time with batches of content that are being rolled out and published on a staggered timeline. We do not plan on doing any edits to existing pages within the project, only rolling out new pages (although some human error is inevitable).
For example:
Obviously there’s some dependency on content authoring velocity, but this aside from this…