Stellar Journal Article LaTeX Template

\documentclass[10pt,a4paper]{article}
\usepackage[margin=1.8cm]{geometry}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{lmodern}
\usepackage{xcolor}
\usepackage{microtype}
\usepackage{titlesec}
\usepackage{abstract}
\usepackage{fancyhdr}
\usepackage{hyperref}
\usepackage{setspace}

\definecolor{ink}{HTML}{1F2937}
\definecolor{muted}{HTML}{6B7280}
\definecolor{accent}{HTML}{0E7490}
\definecolor{rule}{HTML}{CBD5E1}

\hypersetup{colorlinks=true,linkcolor=accent,urlcolor=accent,citecolor=accent}
\setlength{\columnsep}{0.8cm}
\setlength{\parindent}{1em}
\setlength{\parskip}{0.25em}
\renewcommand{\familydefault}{\sfdefault}

\titleformat{\section}
  {\large\bfseries\color{ink}}
  {\thesection}{0.6em}{}
\titleformat{\subsection}
  {\normalsize\bfseries\color{ink}}
  {\thesubsection}{0.6em}{}

\pagestyle{fancy}
\fancyhf{}
\fancyhead[L]{\footnotesize\color{muted}Stellar Journal Article}
\fancyhead[R]{\footnotesize\color{muted}<<doi>>}
\fancyfoot[C]{\footnotesize\thepage}
\renewcommand{\headrulewidth}{0.3pt}
\renewcommand{\headrule}{\hbox to\headwidth{\color{rule}\leaders\hrule height \headrulewidth\hfill}}

\begin{document}

\twocolumn[
\begin{@twocolumnfalse}
  {\LARGE\bfseries\color{ink}<<paper_title>>\par}
  \vspace{3pt}
  {\large\color{muted}<<paper_subtitle>>\par}
  \vspace{8pt}
  {\normalsize\bfseries <<authors>>\par}
  {\small\color{muted}<<affiliation>>\par}
  {\small\color{muted}Correspondence: \href{mailto:<<corresponding_email>>}{<<corresponding_email>>}\par}
  \vspace{4pt}
  {\footnotesize\color{muted}Received: <<received_date>>\quad Accepted: <<accepted_date>>\quad DOI: <<doi>>\par}
  \vspace{10pt}
  \begin{abstract}
  \noindent\textbf{Background.} Programmatic publishing pipelines reduce turnaround and improve consistency in scientific communication.\par
  \noindent\textbf{Aims.} This template demonstrates a submission-style journal layout suitable for automated data injection.\par
  \noindent\textbf{Methods.} We combine strict typographic constraints, two-column flow, and metadata-ready placeholders.\par
  \noindent\textbf{Results.} The output is readable in print and on-screen while remaining easy to populate through APIs.\par
  \noindent\textbf{Conclusions.} Structured LaTeX templates can increase reproducibility and reduce editorial friction.
  \end{abstract}
  \vspace{5pt}
  {\small\textbf{Keywords:} <<keywords>>\par}
  \vspace{8pt}
\end{@twocolumnfalse}
]

\section{Introduction}
Academic teams increasingly publish through software-driven workflows. In this model, manuscript generation, reference updates, and PDF output are orchestrated as part of delivery pipelines instead of manual desktop routines.

\section{Methodology}
\subsection{Template Architecture}
This template uses a strict title block, structured abstract, and publication metadata fields. Placeholder tokens such as <<paper_title>> and <<doi>> are intentionally designed for machine substitution.

\subsection{Quality Constraints}
Microtypography and compact line spacing are applied to preserve readability. The design remains conservative enough for scholarly venues while still feeling contemporary.

\section{Results and Discussion}
In practical usage, this format supports fast draft iteration, easier review packaging, and lower formatting debt across revisions. Teams can keep scientific content as the primary concern while automation handles visual consistency.

\section{Conclusion}
A reproducible manuscript template enables robust publication pipelines. It is especially valuable in organizations that generate frequent technical papers or report-style outputs.

\section*{Data Availability}
Example data and rendering instructions are available in the project repository.

\section*{References}
\begin{enumerate}
  \item A. Rivera and P. Huang, \textit{Automation-First Research Workflows}, Journal of Digital Methods, 12(3), 2025.
  \item N. Patel, \textit{Typography and Readability in Technical PDFs}, Publishing Systems Review, 8(1), 2024.
  \item M. Jensen et al., \textit{Template-Driven Scientific Communication}, Open Tooling Letters, 5(2), 2026.
\end{enumerate}

\end{document}