In this phase, all new pages are still created in the legacy editor. We rollout very gradually to specific groups of customers based on their usage patterns, size, type of content created, and many other factors - in a process designed to accelerate learning while minimizing the surface area so that we can respond to feedback as quickly and effectively as possible.įor each group of customers we rollout the editor to, there is roughly a 6-8 weeks rollout process from phases 1 → 3, and this is how we sequence the rollout process at a high level: The roadmap is a living document, and we’ll update it based on your feedback weekly. If you find something is missing or is inaccurate, please comment on one of the tickets or on this community post. We opened this roadmap up publically a bit earlier than actually felt comfortable for us, but that was intentional since we preferred to start learning from you and getting valuable feedback sooner rather than later. Even if we aren’t able to comment and respond to everything, we track all feedback and take it to heart, so please don’t take our silence as not listening or caring. For example, these tickets are what helped us prioritize adding back full width and all the layout options into the new editor. If something seems off, the best way to impact the roadmap is to comment, vote, and watch the public facing tickets as they are a great source of feedback that we use to evaluate priorities over time. It contains an exhaustive list of all features in the new editor compared to the legacy editor it includes our future plans and links to the relevant public tickets for you to jump in on and watch for full visibility. We decided to open our roadmap and connect it to public facing tickets for as much transparency and ease of tracking as possible. I’ll do my absolute best to follow one of Atlassian’s company value’s of Open Company, No Bull***t and explain each of the above areas in as much detail and transparency as possible. Plans for migrating content in the future One of the biggest pieces of feedback we’ve gotten is to increase the transparency into: And thanks to all of your incredible feedback, we are finding ways to improve and to make the transition from the legacy editor to the new one a smoother and more valuable experience for you both as admins and as end users of the product. We’ve learned a lot over the past year - what’s worked, what hasn’t worked. This change impacts our customers deeply as one of the main tasks in Confluence is content creation, with the editor being at the heart of it. The rollout of the new editor is probably one of the biggest changes we’ve been rolling out gradually during the past year or so. Avinoam here from Confluence Cloud product management - I work on the new editor in Confluence.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |