Renaming Files and Improving Editing in a Team
Over the past couple weeks, we were hard at work to improve the editor experience for our Git-backed content manager. Renaming files is just one of those updates. We also needed to improve notifications and indicators to make working in a team on Forestry easier.
Renaming Files ✍️
Freshly out — you can now change the name for your content files with Forestry. Jekyll and Hugo take the filename to create the default URL paths, so editors can now easily change the URL path with this new feature. Previously, filename changes could only be made directly in the repo.
Currently Being Edited by - Indicator 💁
As a Git-backed content manager, we need to prevent merge conflicts. That’s why Forestry only allows one editor to change a document at a time. Now you can see immediately who is currently editing a document and if it has unsaved changes.
Connection Lost 💔
Until now users were booted from the post they were editing if the connection was lost. Even though we saved those changes, it made for a less than optimal user experience. From now on, users will only see a bar at the top letting them know that the connection was lost and that we will try to reconnect as soon as possible.
Notification about Git-based or unsaved changes 🔔
Especially when setting up a new site, users are frequently pushing changes directly to the repo while they are being edited in Forestry. Users in Forestry will now be notified that a change has occurred in those cases.
Unsaved Changes - To make sure we use the right version, we will now also prompt users when we found unsaved changes for a file.
Caught a mistake or want to contribute to the blog? Edit this page on Github!