Get your Foundations and Trends in Programming Languages paper right the first time: a ready-made structure with the right abstract and citations, so editors see your science, not formatting slips.
4.6
Authored by Sumalatha Gangadhar | Published on 11 August, 2026
Submitting to Foundations and Trends in Programming Languages goes smoothly when your draft already matches the journal's own rules. Editors screen new manuscripts against the Foundations and Trends in Programming Languages guide for authors before peer review, so formatting, structure, and required statements should be right on the first draft rather than repaired during upload. This template sets that structure up for you.
It is a manuscript shell aligned to Foundations and Trends in Programming Languages. It covers front matter, the abstract the journal expects, a body organized to the journal's article types, and a reference list in the journal's required style. Confirm current scope and article types on the Foundations and Trends in Programming Languages journal page before you draft.
Prepare the title, authors, affiliations, and ORCID iDs. Write the abstract to the journal's rule and word limit, organize the body to the article type, and apply the required reference style from the first citation. Complete every declaration (ethics, competing interests, funding, data availability) the Foundations and Trends in Programming Languages guide for authors lists, and cite figures and tables in order.
The common failure modes are formatting or reference style that does not match the guide for authors, missing required statements, and an incomplete portal checklist. Clear all three against the Foundations and Trends in Programming Languages guide for authors before you submit.
The shell mirrors what editorial staff check first: article-type fit, the abstract rules, required declarations, and the journal's reference style. For more detail see the author resources. When your draft is ready, upload it through the journal's editorial office.
| Element | Foundations Trends Programming Languages requirement |
|---|---|
| Abstract | Structured abstract required with four essential fields (100 word limit to each field): Purpose, Design/methodology/approach, Findings, Originality. Optional additional headings (also 100 word limit to each field): Research limitations/implications, Practical implications, Social implications |
| Main text | ± 100 pages for review and tutorial papers. No specific word limit stated, only page limit. Original research papers will be rejected - journal publishes exclusively long review and tutorial papers |
| Declarations | Ethics approval/consent as applicable; competing interests; funding; data availability |
| Figures/tables | Publication-ready; cited in order |
| Supplemental | Upload separately when used |
| Keywords | Please feel free to assign any keywords and/or subject-specific keywords such as JEL codes to your article. No specific count or range stated |
| References | Harvard (Emerald's Harvard referencing style). In-text citations: Single author: (Adams, 2006); Two authors: (Adams and Brown, 2006); Three or more authors: (Adams et al., 2006) with 'et al' in italics. Reference list in alphabetical order with DOI included when available |
| Peer review | Full peer review by editorial board member and at least 2 reviewers. The majority of Emerald journals use double-anonymous (double-blind) peer review model, though the specific journal guidelines do not explicitly state whether single-anonymous or double-anonymous is used for this journal |
| Submission | Email: dkielty@emerald.com |
Read the Foundations and Trends in Programming Languages guide for authors once before drafting and once before upload. Draft the abstract after results are stable. Set the reference style before adding citations. Keep a cover letter that states your contribution and fit to Foundations and Trends in Programming Languages in under a page.
Skim two or three recent Foundations Trends Programming Languages papers to calibrate depth and figure style. Make the novelty clear in the first two pages. Deposit data and code when the policy on the Foundations and Trends in Programming Languages journal page requires it. Disclose any preprint or conference version with identifiers in the cover letter.
Do one focused pass against the Foundations and Trends in Programming Languages guide for authors: scope, length, reference style, required declarations, and figure quality. Then submit through the journal's editorial office.