Custom front page theme example?

[imagingbook]

@hochleitner Should we add a sample document demonstrating the creation/use of a custom theme?

[hochleitner]

I think that might be a good topic for the wiki. It could contain a guide on how to create a custom theme together with a sample document on Overleaf.

[imagingbook]

Good idea, but shouldn't we still keep the sample document somewhere inside the repo? I am mainly thinking of future updates (of the themes scheme) and associated build checks ...

[imagingbook]

Just thinking ... Perhaps we should consider breaking up this repo into user and dev repos and keep things together in a super repo? Of course, the current repo would continue as the user repo in this case.

[hochleitner]

The question ist, where would the style and class files be? Right now, they're in the dev directory and the build process copies them over to the document directory, includes them in the zip files and removes them again from the documents.

If these files are strictly in a separate repo, how do we inject them into the the release zip files (I'd avoid things like submodules if possible).

What we could try is setting up a CI/CD process in the repository, thus building things on the server side upon push and providing the zip files and PDFs under "releases". This would make the repo effectivly a source/dev-driven repo with the user-things moved to the releases. I'm not sure though if it is feasible with consistent Overleaf links.

[imagingbook]

Yes, the idea was to use submodules that would map to the existing directory structure (or similar). The make process would work as before. I've used this extensively in other projects, but it does have its quirks.
Alltogether I think it is not needed here and would only complicate things unnecessarily - I suggest to simply forget it. Let's keep things simple ...