Fit everything into a common style

[dotSp0T]

This issue acts as a collection and discussion area for styling and design stuff. Identified todos are then extracted into new issues and linked.

• Add DLC Icons to distinguish content #17
• Allow finetuning what is compiled into a PDF #18
• PDF Orientation #19
• Legend/Glossary page #20

[kruzuahz]

Good ideas, you may want to consider latex modes, These seem to work like c-style defines, I'm not sure if they work with pdflatex though.

We could also add DLC icons to the relevant sections

[dotSp0T]

DLC Icons seconded!

Also holy shit the whole document has become barely legible. There's too much going on on the prodchains.

Keeping this issue as a place to discuss and find stuff to do. Creating appropriate sub-issues with single todo tasks

[kruzuahz]

When i first added the extra information for the consnode I wasn't too happy with it either for the same reason, but it grew on me as I was using it. I think the mistake here was adding the lifestyle needs everywhere, this messed up the layout the most. Also while using it the information was generally out of place because you were busy with another region. Therefore I suggest moving the lifestyle needs to its own section.

Alternatively we could easily remove some of the extra information everywhere quickly by changing the template in main.tex

[dotSp0T]

We could do sth similar to the ingame screen, where we got one block per pop-level, icons for all their needs, and 2 numbers next to each icon (how much is consumed per household, and how many more inhabitants will live in the house if fulfilled)

Obviously this will be a rough abbreviation of the whole mechanic. But the whole point of the prodchain document is to give overviews and lookup tables, not exact graphs, etc.

[kruzuahz]

I Agree, we could do this for the lifestyle needs only for now. thats already 13(tiers)x6(needs) items removed from the main chains, and reduces the amount of work.

[kruzuahz]

On a side note would you be OK with creating a release for the document as is? We might be able to get more collaborators if people could use an updated version.

[dotSp0T]

Oh yeah, let's do that. I sorta wanted to get a pipeline going to automatically create releases. But we can do a manual one (though at least have to fix #19 )

[kruzuahz]

great, I will try to look into that this week