View Single Post
Old 01-23-2017, 02:30 PM   #45
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,807
Karma: 6000000
Join Date: Nov 2009
Device: many
pps - possible layout of Sigil site:

I was thinking of creating a single Sigil_docs github site that would contain all of the docs in the main Sigil tree to allow easier translation and updates.

Something along the lines of:

Sigil_docs/user_guide_epub/ (with subdirectories by language code each holding the unzipped version of the epub)

Sigil_docs/plugin_framework_epub/ (ditto)

Sigil_docs/building_from_source/ (do we even need this, are translation necessary?)

That said, perhaps it would be better to create 2 different github sites:

Sigil_user_guide
Sigil_plugin_framework

and let the main Sigil github site be the location for building from source instructions since those change by distribution, toolchain, etc.

Using separate sites allows anyone can grab the zip of the master branch quite easily as each would have their own zip archive.

Comments and suggestions for how best to do this and how to handle/store translations welcome!

KevinH
KevinH is offline   Reply With Quote