OurBigBook logoOurBigBook Docs OurBigBook logoOurBigBook.comSite Source code
If you are making a limited repository that will not have a ton of images, then you can get away with simply git tracking your images in the main repository.
With this setup, no further action is needed. For example, with a file structure of:
./index.bigb
./Tank_man_standing_in_front_of_some_tanks.jpg
just use the image from index.bigb as:
\Image[Tank_man_standing_in_front_of_some_tanks.jpg]
which renders as:
Tank_man_standing_in_front_of_some_tanks.jpg
However, if you are making a huge tutorial, which can have a huge undefined number of images (i.e. any scientific book), then you likely don't want to git track your images in the git repository.
A generally better alternative is to store images in a separate media repository, and especially store images in a separate media repository and track it as a git submodule.

Ancestors (5)

  1. Where to store images
  2. Image
  3. Macro
  4. OurBigBook Markup
  5. Home