# INFEDU LaTeX templates — 2026-10-07 r5

## Choose the right entry file

| File | Output / intended use |
|---|---|
| `main-bibtex.tex` | **Identified Early View example**: authors, correspondence markers, ORCIDs, emails and publication heading. |
| `review.tex` | **Anonymised initial-review PDF**. Use this file for review preparation. |
| `final-preview.tex` | Alias for the identified Early View example; retained for existing preview links. |

**The main-bibtex.tex example is identified.** It must NOT be uploaded as a blinded review PDF. The build helper still defaults to the safe `review` mode when run without an argument.

This is an instructional example, not a published research article. Replace the example title, abstract, contribution statements, body and references. Initial submission remains an anonymised PDF plus a separate confidential Title Page PDF.

## Build

Install a complete TeX distribution with LuaLaTeX and BibTeX, and the packages used by the source. Extract this entire ZIP to its own folder. Do not mix the two bibliography packages: their support files deliberately differ.

```sh
sh build.sh review   # anonymous review.pdf
sh build.sh early    # identified main-bibtex.pdf
sh build.sh final    # identified final-preview.pdf
```

PowerShell equivalents (after local script permissions are configured):

```powershell
./build.ps1 -Mode review
./build.ps1 -Mode early
./build.ps1 -Mode final
```

Manual sequence (replace the job name consistently for another mode):

```sh
lualatex -interaction=nonstopmode -halt-on-error main-bibtex.tex
bibtex main-bibtex
lualatex -interaction=nonstopmode -halt-on-error main-bibtex.tex
lualatex -interaction=nonstopmode -halt-on-error main-bibtex.tex
lualatex -interaction=nonstopmode -halt-on-error main-bibtex.tex
```

Do not enable shell escape. Clear generated auxiliary files when changing a bibliography workflow; keep each workflow in a separate folder. Three post-bibliography LaTeX passes are supplied so front-matter notes, reference links and last-page fields settle.

## Publication heading: edit it in main-bibtex.tex

```latex
\pubyear{2026}
\publicationstage{Early View}
\volume{0}
\issue{0}
\firstpage{1}
\lastpage{\pageref*{LastPage}}
\doi{} % Leave blank until an actual DOI has been assigned.
\copyrightauthors{A. Author, B. Contributor, C. Researcher}
\publishers{Vilnius University and Tallinn University}
```

The heading follows the uploaded INFEDU first-page examples, except that volume and issue are intentionally zero for Early View. The page range is calculated for the current PDF rather than copied from a different article. DOI input is a bare assigned identifier beginning `10.`, not a complete URL. When empty, the preview prints a non-clickable editorial placeholder; it does not invent an assigned DOI. The Editorial Office supplies the actual publication metadata and any genuine history dates. When an article receives issue assignment, change the volume/issue/pagination and clear `\publicationstage{}` as instructed by production.

## Corresponding authors, ORCIDs and emails

The example demonstrates three authors, two affiliations and **two corresponding authors**. Add `\thanksref{cor}` to every corresponding author and define the shared note once:

```latex
\author[a]{\inits{A.}\fnms{Alice}~\snm{Author}%
  \thanksref{cor}\orcid{0000-0000-0000-0000}%
  \ead[label=e1]{alice.author@example.com}}
% Other author blocks follow; use a distinct e1/e2/e3 email label for each.
\thankstext[type=corresp,id=cor]{Corresponding authors: Alice Author and Carol Researcher.}
```

For just one corresponding author, keep the mark on that author only and use “Corresponding author” in the note. Affiliation numbers and the shared asterisk appear before the bracketed ORCID, as in the supplied samples.

The all-zero ORCID is an **unlinked placeholder**, not a real identifier. Replace it with the verified author's ORCID. Non-placeholder values are linked to the ORCID record but are not authenticated by LaTeX. `\orcid{}` omits the displayed field. The original publisher class discards this command; the companion now renders it. All author email links display their own address and point to the matching `mailto:` address.

Update both the visible author list and the plain-text `\INFEDUauthorsmetadata` near the start of the main file. Update `\INFEDUtitlemetadata` when changing the title. The running heads omit ORCIDs and correspondence marks. The review wrapper hides identifying front matter and clears the PDF author field. Review authors must still inspect the body, self-identifying wording, references, acknowledgements, images, file names, attachments and other metadata.

## Required opening

Informative title -> English structured abstract -> 4–6 keywords -> labelled Contribution and implications for informatics education -> article body.

The title should identify the recognisable educational subject and specific focus. About 12–20 words is guidance only; there is no title-word eligibility cutoff.

Use ONE abstract environment with four short labelled paragraphs: **Problem and aim; Approach; Findings; Conclusions**. **Main argument** may replace Findings for conceptual/theoretical papers; **Synthesis** may replace it for review/synthesis papers. Use exactly one third label. The complete abstract is **150–250 words excluding the Abstract heading and four labels**. It must independently state the main contribution, educational significance and principal warranted implication. Keep the remaining abstract text intact when exporting plain text.

After 4–6 keyword phrases, provide **3–5 full-sentence bullets, <=150 words including their labels**, excluding the section heading and markers. Lead-in labels must be visible: **Knowledge contribution; Educational and community value; Implications for CS education**, introduced in that order. Additional substantive points may repeat a required label. **Conditions and limits** is optional as a separate final bullet. There is no compulsory fourth bullet or minimum of 100 words. Labels identify functions, not three independent discoveries. Keep necessary qualifications in the relevant claim.

Use the separate bullets to clarify significance and use. Necessary conceptual overlap is permitted; repeated study summaries are not helpful. Keep the contribution section outside the abstract and keyword environments. The abstract must not depend on those bullets for its only account of the contribution.

These presentation requirements do not prescribe research philosophy, empirical data, a particular main-text structure, or demonstrated societal benefit. Preserve the package’s existing initial-submission versus final-publication article-length guidance and anonymous-review workflow.

The instructional worked abstract contains 182 whitespace-delimited words excluding labels. Its five keyword phrases are separate; the three contribution bullets contain 74 words including labels. The example reports no empirical study or citation benefit.

## Length

INFEDU does not impose a formal word limit at initial submission. For the final publication version, most full-length articles should aim for 6,000–8,000 words and should generally not exceed 10,000 words. This is guidance, not an absolute ceiling; longer articles may be appropriate when the evidence, scope, contextual detail, synthesis or argument requires additional space. Shorter articles are welcome when adequately reported. Exceeding 10,000 words at initial submission does not require advance permission or a separate length justification. Remove avoidable repetition, but retain information essential to evaluating the work.

Count the article body from the introduction through the conclusion, including headings, in-text citations, quotations, footnotes/endnotes, text in tables, and table and figure captions. Also count appendices retained within the article, regardless of position. Exclude the title page, abstract, keywords, contribution-and-implications section, references, acknowledgements, declarations and separate online supplementary files. Report this count on the separate Title Page and update it for the final publication version.


## Class, references and provenance

`infedu.cls` is byte-for-byte unchanged from the uploaded original. Its notice is retained. All local front-matter, PDF-metadata and display fixes are in `infedu-authoring.sty`. No font files are included. The original 170 × 240 mm page geometry is retained.

This is the BibTeX/natbib compatibility workflow. Its local `vtexnatbib.sty` loads real natbib, and `infedu-apa.bst` supplies the repaired reference style. It is not a complete APA 7 engine: specialised reference types, long author lists, and some same-author/year disambiguation cases require manual checking. Use the separately supplied biblatex/Biber package when more complete automated APA 7 handling is needed. Do not substitute the old `apa.bst`.

The two supplied published PDFs were used as first-page style references (author marks, bracketed ORCIDs, emails, copyright/publishers). Their article content, identifiers and references are not copied into the template. This is a front-matter correction, not a substantive revision of those articles or a new reference-style policy.

## Release checks

This r5 release implements the approved title, structured-abstract, keyword and
labelled-contribution rules using the supplied r4 distribution as the baseline.
The class, companion and bibliography support files, reference database, wrappers
and build helpers are retained. Sources, previews and download archives form one
matched release. The release report records the actual checks completed.

Different TeX versions can change pagination. Rebuild and inspect the PDF after
replacing the instructional example. Keep the two bibliography workflows separate.

Current author instructions: https://infedu.vu.lt/journal/INFEDU/information/instructions-for-authors