Hi there, Dale. Thank you for walking us through your scenario!
We recommend to install, save, and publish on a local hard drive since working on a shared drive can cause erratic behavior—such as file corruption, an inability to save changes, and a loss of project resources.
I have heard folks work from a network drive without any issues, but we do not recommend this since it can cause those erratic issues due to latency. If going this route, be sure to save a backup file in another location and follow these tips to mitigate the risk.
With Articulate 360, you also have access to Rise 360: an online authoring tool where you can create fully responsive courses right in your web browser. That way, there's no need to save work to a drive.
If there's anything else I can answer. I'm happy to help!
1 Reply
Hi there, Dale. Thank you for walking us through your scenario!
We recommend to install, save, and publish on a local hard drive since working on a shared drive can cause erratic behavior—such as file corruption, an inability to save changes, and a loss of project resources.
I have heard folks work from a network drive without any issues, but we do not recommend this since it can cause those erratic issues due to latency. If going this route, be sure to save a backup file in another location and follow these tips to mitigate the risk.
With Articulate 360, you also have access to Rise 360: an online authoring tool where you can create fully responsive courses right in your web browser. That way, there's no need to save work to a drive.
If there's anything else I can answer. I'm happy to help!
This discussion is closed. You can start a new discussion or contact Articulate Support.