6

I'm using git to store my project files including the tex files. Now I'm thinking about starting to write up a first draft.

What's a good project structure for combining latex and the git technology?

For example, if I will have different versions of the draft (say, the first version sent out for conference XYZ, and then newer versions), should I create a folder structure for these? Or should I use git's branching feature? Or something different?

On top of that, should I keep something specific in mind when creating the file structure? Keeping in mind the git versioning, is it more useful to have a file for the head, and files for main parts of the draft? How many of the old "style guides" for tex structures are still valid when using git as a versioning system?

  • 2
    Sorry, but I think this question is off-topic and not TeX specific, but the technique holds for any software or electronic document writing, basically – user31729 Feb 3 '16 at 15:11
  • 4
    It is not off-topic. See this question tex.stackexchange.com/questions/103244/… and this tex.stackexchange.com/questions/75862/… and of course also gitinfo package manual. – percusse Feb 3 '16 at 15:29
  • 3
    I agree that the question is not off-topic, but "What's a good project structure..." is inherently an opinion-based question. There are many such project structures. Some are completely flat, some are excessively hierarchical, some are pure fairy dust. You need to hone your question down to something more specific so it's answerable :-) – Sean Allred Feb 3 '16 at 16:05
  • 2
    @FooBar One of the reasons git has been so successful is its flexibility to a multitude of software engineering paradigms :) There isn't any 'one true flow' for git -- it just doesn't exist. Branches, tags, remotes, versioned folders, etc. are all valid solutions to this. A right answer doesn't exist -- nor does a wrong answer. (In the future, there are usually people in chat with strong opinions that are happy to share them :) – Sean Allred Feb 3 '16 at 16:18
  • 2
    @percusse gitinfo adds the info to the pdf not to the source. – Ulrike Fischer Feb 3 '16 at 19:28
1
Whats about this?

Core
-- animate
------ timeline
------ singlefigures
-- attachments (files to include)
-- audio (for mp3s which can be included in the pdf)
-- bibliography
-- content
------ codelisting
------ glossar
------ hypernation
------ titlepage
------ cites
-- doc
-- figures
------ frontimage
------ symbols
------ tex
------ pdf (pdf created by tex all the time)
------ pdf-export (tikz externalize method or similar)
------ pdf-static (static pdf which wont change)
------ gnuplot
-- performancelog
-- preamble
------ subfolder (for commands and packagesettings)
-- searchstring
-- statistics
-- tables
-- videos
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.