Work only in prep_projectx.
Inline images: Readers can adjust font size and line-height. Those adjustments apply only to text, but not to images. Imagine thee resultant visual vomit for a moment, then place the image centered on its own line, where it belongs.
Inline images: Unless custom, risky CSS that is not supported on many e-reader devices and apps is applied to an image, words will not wrap neatly around an image. Rather, words will cut off, and the graphic will render God-knows-where in your paragraph, kicking your reader off the page. #gameover
Images general: I can’t believe I have to add this note in this day and age, but do not use images without the proper licensing. When in doubt, leave it out.
Images general: 72dpi is recommended for EPUB/MOBI. The resolution is more than sufficient, and higher resolutions drastically increase file size with no added benefit.
Images general: Every image must appear on its own line.
Images general: Images must always be styled align center. (This is tackled in Sigil.)
Images general: Recommended max width of images = 350px.
Images general: Be mindful of colored images. Make sure they render well in grayscale because many e-reader devices render only black and white.
Amazon: Images can drastically increase the file size of finished EPUB and MOBI files. Files larger than a certain size may prohibit authors from setting their price the way they’d like, or receiving the 70% royalty rate.
Replace all images in the prep_projectx file with expediently named production slugs.
Ensure every image appears on its own line. Images must never be embedded in-line with text.
If necessary, rename image files to match production slugs. This will make life much easier in the production stage.
Ensure all images used in projectx are saved in the desktop production folder.
Note the position of image production slugs in the key_projectx file.
Plain-old save the prep_projectx file to preserve all changes.