balajicm24/latex_project_guide

Purpose and Runtime

This is a Django project that presents operational guides/checklists for LaTeX-related publishing workflows. It is server-rendered rather than a separate frontend application. Django is launched through manage.py, with production entry points in latex_guide/wsgi.py and latex_guide/asgi.py.

Project Composition and Routing

The latex_guide package owns Django project configuration and top-level URL dispatch:

• latex_guide/settings.py

• latex_guide/urls.py

• latex_guide/wsgi.py

The core app is the functional application boundary. Its routes are defined in core/urls.py and are expected to be included by the project URL configuration.

Guide/Checklist Request Handling

core/views.py is the primary controller layer. It receives requests for individual workflow pages, selects the appropriate template, and renders server-side HTML. The app is oriented around distinct document-processing procedures rather than persisted business entities.

Relevant paths:

• core/views.py

• core/urls.py

• core/templates/core/base.html

Workflow Page Families

The central product surface is a set of dedicated guide pages for different LaTeX conversion or typesetting processes:

• LaTeX-to-DOCX: core/templates/core/latex2docx.html

• LaTeX-to-XML: core/templates/core/latextoxml.html

• OLH typesetting: core/templates/core/olhtypeset.html

• UP pre-editing/typesetting: core/templates/core/uppreedit.html, core/templates/core/uptypeset.html

These templates form the main presentation boundary: workflow instructions are embedded/rendered as HTML pages, with shared layout inherited from the base template.

Source Material and Checklist Generation

The notes/ directory contains workflow-specific source notes, including notes/LaTeX2Docx_Note.txt, notes/LaTeXML_Note.txt, and notes/UP_Note.txt. generate_checklists.py is an offline generation/maintenance script, likely connecting these textual instructions to the checklist-oriented web content. It is separate from the request-serving path.

Presentation Assets

Shared browser assets are served from the repository’s static tree:

• static/css/style.css

• static/js/main.js

• static/images/

Templates use core/templates/core/base.html as the current common shell. core/templates/core/bak/ preserves older versions of those workflow templates and is not part of the primary rendering surface unless explicitly routed.

Persistence and Admin Boundary

Django model and administration extension points exist in:

• core/models.py

• core/admin.py

• core/migrations/

However, the repository structure indicates the architectural focus is content-driven guide rendering; no external APIs, queues, databases beyond Django’s configured persistence layer, or document-conversion services are represented in the supplied tree.