Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 1
    This structure looks fine to me, provided it compiles this way: you didn't explicitly show your directory structure. // I'd like to draw your attention to package `subfiles', which allows you to compile any included file separately, e.g. for checking purposes ... if you can live with an "incorrect" numbering. Find an example here: tex.stackexchange.com/a/688740/245790 , and the package here: ctan.org/pkg/subfiles . Commented 19 hours ago
  • 1
    As an alternative approach you can apply the Refactoring approach to your (main) document: 1) Just start. 2) Review and spot parts, which you now can outsource (via include). 3) Check via compile(s). 4) Repeat. // This way your structure evolves as needed over time. You can start with a predefined structure, but you don't need to: it will kind of "come up by itself", with you as the driving force. // Here I outlined the process a bit more tex.stackexchange.com/a/725090/245790 , though it will look a bit different when splitting documents continuously. Commented 19 hours ago
  • 2
    I think your structure is right; there’s no problem with it at first glance. Commented 18 hours ago
  • 2
    It's not clear if this is your actual naming scheme, but try to avoid numbering your filenames. If you decide to swap introductionChap.tex with preliminariesChap.tex, that's not bad. If you decide to swap file1.a with file2.b, your main file will forever have things out of order. Commented 15 hours ago
  • 1
    @Teepeemm Yes. In retrospect, I agree. Commands within the main \input file that reference sibling files will have to be handled as well. I've offered an answer that should circumvent the problem. Commented 4 hours ago