Hey all.
While Scrivener 3.0 should fix this problem, in the meantime I seem to keep getting hammered by Amazon’s CSS bug. While Amazon are usually good about manually fixing CSS errors at their end, it takes time, often multiple go-arounds, and in situations where they’re getting hammered (like now, with the geofencing problem related to Kindle store searches) your brand new release gets shafted by looking unprofessional.
Is there a mechanism for working around this? Before someone suggests Vellum, that’s too rich for my limited income at the moment, although it looks like a neat solve. I’m curious about whether someone has a process for getting docs into the KDP dash that look and smell legitimate without the roulette experience of seeing which particular CSS file the machine chooses (some of my titles launch fine, others are on fire).
A perfect solution would be the release of Scrivener 3.0, but there appears to be no ETA and hope is not a strategy, so I’m trying to look for a solution for my trilogy releasing in rapid succession.
Thanks 