Here are two propositions of messages to display when the phylomemy crashes.

1) If the export of the .dot file crashes in backend or if the front end crashes when loading the .json

"Oops something went wrong ! Your corpus and map list may not be ready for building a phylomemy. Have you annotated the entire time period of your corpus ? Have you a good ratio between specific and generic terms in your map list ?"

2) When the frontend is loading the .json file

"Your phylomemy is on its way but it might take some time to display it. Take a coffee or a tea in the meantime."