Good practice for packaging / folder management with Sigil

[wdaly]

Coming from a print background, I’m used to a routine of packaging final artwork files in InDesign for archiving, so that all links and fonts are self-contained in a 'Final' folder. As far as I can see there is not a similar function in Sigil. I'm new to making ebooks, so I'm feeling my way through at the moment, building and modifying folder structures as I learn. I've renamed and moved folders around, though so far there don’t appear to be any links lost in doing this, but I wanted to put the question out there and find out people’s preferred ways to archive a finished ebook generated in Sigil.

[DiapDealer]

Originally Posted by wdaly

but I wanted to put the question out there and find out people’s preferred ways to archive a finished ebook generated in Sigil.

A finished ebook generated in Sigil IS an archive. As to folder structure... Sigil has it's own required structure and will automatically adjust/modify links to make sure the ePub complies with its requirements. There is no real wiggle-room concerning the structure of a Sigil created ePub: you either accept the structure it requires or you don't use it (to put it bluntly).

[wdaly]

Thanks DiapDealer, that in fact seems to make life quite easy. To clarify, by folder structure, I meant my own project folders for saving the epub files and image files.

[mrmikel]

It is an archive, but it is not normally an archive of all the changes and the stages of all the images used to reach the final product. For that sort of thing I just save all the versions with a different alpha or numeric ending, so I can backtrack if I need to. And if you do search and replace with regex you will need to!

[DiapDealer]

Originally Posted by wdaly

Thanks DiapDealer, that in fact seems to make life quite easy. To clarify, by folder structure, I meant my own project folders for saving the epub files and image files.

Sorry. My bad. I assumed you were talking about internal structure. I don't really save anything ouside the epub's archive. But like mrmikel said, I often save several versions of the epub along the way. Once it's finalized, however... I consider the epub itself to be the "project files."