Hey Boris,
As someone who has worked on a platform that was constantly changing, I can almost guarantee nothing has changed with Aesop Story Engine on the front-end that was not communicated or warned before hand.
We run the latest development version on all theme demos, and live demos, and watch very very carefully for changes. We have not noticed anything, even while testing 1.1. Personally, I’m pretty paranoid about breaking people sites and make every attempt to be weary of this when making changes.
Also, I’d like to just remind you that Aesop Story Engine has little CSS styles, so your theme is responsible for what the components ultimately end up looking like.
With that being said, the last time the character component changed was a month ago, and we only added an ID.
https://github.com/bearded-avenger/aesop-core/commit/ae01c5a18b6d32637fa602166593d0870e9b6248#diff-59e2e5b4374953cdad071ccbadcb3140R41
Prior to this, on July 22 we added a float class to the parent container.
https://github.com/bearded-avenger/aesop-core/commit/b62834d988b33fd7178f3d03bae4d599d4070a7f
This should have had no effect on the positioning as we’ve tested this on our demos (you can even see the character component here https://playground.aesopstories.com/yellow-belly/ and it’s position has not changed with this update) however, if your theme has this setup differently it may require a tweak.
Additionally, this addition was noted in the change-log with a warning that it may affect your theme if you have specific styles.
https://github.com/bearded-avenger/aesop-core/blob/master/README.txt#L153
In the end, we’re doing everything that we could possibly be doing, and more, to prevent any fluctuations within the design of the components on the front end, and I can pretty much guarantee that what you’re seeing is likely a result of your specific theme.
