@open-press/cli 0.7.0 → 0.8.0

package/template/core/src/styles/openpress.css

@@ -6,7 +6,7 @@
 @import "./openpress/app-shell.css";
 @import "./openpress/workbench.css";
 @import "./openpress/workbench-panels.css";
-@import "./openpress/project-workspace.css";
+@import "./openpress/project-preview-panel.css";
 @import "./openpress/media-workspace.css";
 @import "./openpress/reader-runtime.css";
 @import "./openpress/public-viewer.css";

package/template/core/vite.config.ts

@@ -6,8 +6,10 @@ import type { IncomingMessage, ServerResponse } from "node:http";
 import { defineConfig } from "vite";
 import react from "@vitejs/plugin-react";
 import { loadConfig, publicPdfHref } from "./engine/runtime/config.mjs";
+import { searchSourceText } from "./engine/runtime/source-text-tools.mjs";
 import { handleCommentRequest } from "./engine/react/comment-endpoint.mjs";
 import { handleProjectAssetRequest } from "./engine/react/project-asset-endpoint.mjs";
+import { handleSourceEditRequest } from "./engine/react/source-edit-endpoint.mjs";
 
 const frameworkRoot = fileURLToPath(new URL("./", import.meta.url));
 const workspaceRoot = process.env.OPENPRESS_WORKSPACE_ROOT
@@ -53,6 +55,7 @@ const workspaceDefines = {
 
 export default defineConfig({
   base: "./",
+  cacheDir: path.join(workspaceRoot, ".openpress", "vite-client"),
   plugins: [openpressLocalDeployPlugin(), react()],
   define: workspaceDefines,
   resolve: {
@@ -68,6 +71,17 @@ export default defineConfig({
       ...workspaceAliases,
     },
   },
+  optimizeDeps: {
+    include: [
+      "@mdx-js/react",
+      "lucide-react",
+      "react",
+      "react-dom",
+      "react-dom/client",
+      "react/jsx-dev-runtime",
+      "react/jsx-runtime",
+    ],
+  },
   build: {
     outDir: outputDir,
     emptyOutDir: true,
@@ -108,6 +122,12 @@ function openpressLocalDeployPlugin() {
       server.middlewares.use("/__openpress/status", (req, res) => {
         void handleLocalStatusRequest(req, res);
       });
+      server.middlewares.use("/__openpress/search", (req, res) => {
+        void handleLocalSearchRequest(req, res);
+      });
+      server.middlewares.use("/__openpress/source-edit", (req, res) => {
+        void handleSourceEditRequest(req, res, { root: workspaceRoot });
+      });
       server.middlewares.use("/__openpress/deploy", (req, res) => {
         void handleLocalDeployRequest(req, res);
       });
@@ -267,6 +287,32 @@ async function handleLocalStatusRequest(req: IncomingMessage, res: ServerRespons
   });
 }
 
+async function handleLocalSearchRequest(req: IncomingMessage, res: ServerResponse) {
+  if (req.method !== "GET") {
+    writeJson(res, 405, { ok: false, message: "Search endpoint requires GET." });
+    return;
+  }
+
+  const requestUrl = new URL(req.url ?? "/", "http://localhost");
+  const query = (requestUrl.searchParams.get("q") ?? "").trim();
+  if (!query) {
+    writeJson(res, 400, { ok: false, message: "Search query is required." });
+    return;
+  }
+
+  try {
+    const report = await searchSourceText({
+      config: openpressConfig,
+      query,
+      scope: searchScopeFrom(requestUrl.searchParams),
+      caseSensitive: requestUrl.searchParams.get("caseSensitive") === "true",
+    });
+    writeJson(res, 200, { ok: true, ...report });
+  } catch (error) {
+    writeJson(res, 500, { ok: false, message: error instanceof Error ? error.message : String(error) });
+  }
+}
+
 async function handleLocalDeployRequest(req: IncomingMessage, res: ServerResponse) {
   if (req.method !== "POST") {
     writeJson(res, 405, { ok: false, message: "Deploy endpoint requires POST." });
@@ -368,6 +414,10 @@ function localDeploySetupMessage() {
   return `Deployment adapter \`${openpressConfig.deploy.adapter}\` is not configured.`;
 }
 
+function searchScopeFrom(searchParams: URLSearchParams) {
+  return searchParams.get("scope") === "all" ? "all" : "content";
+}
+
 async function fileExists(filePath: string) {
   try {
     await fs.access(filePath);

package/template/packs/academic-paper/document/chapters/01-introduction/content/01-introduction.mdx

@@ -1,21 +1,35 @@
 ## Introduction
 
-This document is a model and starting point for an academic paper drafted in open-press. The structure follows the IEEE conference template conventions where they make sense for screen-first reading: numbered sections, italic sub-sections, an abstract block, and a numbered references list. The two-column body of IEEEtran is not yet supported — single-column will land as the v0.8 paged.js migration arrives.
+The purpose of this paper template is to provide a compact, readable structure for a
+machine-learning research manuscript written in a formal journal style.
 
-Use this pack for **drafting, iteration, and preprint distribution**. When the paper is ready for venue submission, export the prose into the publisher's required LaTeX class (`IEEEtran`, `acmart`, etc.). The pack does not replace LaTeX for camera-ready submission; it replaces the awkward iteration loop *before* submission.
+### Background and Motivation
 
-### Where to start
+Recent studies have shown that modern experiments produce larger datasets and richer
+artifact pipelines, but the writing process is often bottlenecked by repeated formatting
+adjustments. A lightweight drafting layer can decouple scientific reasoning from
+typesetting concerns and let the author focus on experimental validity first.
 
-Each chapter directory under `document/chapters/` is one paper section:
+### Problem Statement
 
-- `01-introduction/` — motivate the work, state the contribution, summarise the structure.
-- `02-methods/` — describe what you did, with enough detail to reproduce.
-- `03-results-and-discussion/` — present results with figures and tables; interpret what they mean.
-- `04-acknowledgment/` — acknowledge funding, collaborators, reviewers.
-- `05-references/` — numbered `[1]`, `[2]` references.
+The key challenge addressed in this draft is to keep the manuscript internally
+consistent while moving from scratch notes to a submission-ready narrative. The
+workflow should preserve section hierarchy, citation order, and figure/table integrity
+without requiring manual renumbering.
 
-Replace each chapter's MDX content with your own. The skeleton text below each `##` heading is illustrative — overwrite it.
+### Contribution
 
-### Abstract and Index Terms
+This demo paper includes the following contributions:
 
-Edit the abstract and index terms inside `document/index.tsx` (the `cover` JSX export). They render on the title page above the body. Keep the abstract under 250 words and avoid abbreviations, symbols, or math in it.
+- A reproducible chapter flow (`Introduction → Methods → Results and Discussion →
+  Conclusion`),
+- Consistent heading levels for major and minor sections,
+- Placeholder media and tables that can be swapped with real results,
+- A reference block and placeholder metadata for a clean handoff to final publication
+  tooling.
+
+### Paper Organization
+
+The paper is organized as follows: Section 2 details the methodology,
+Section 3 reports results and discusses representative scenarios,
+Section 4 summarizes conclusions and practical recommendations.

package/template/packs/academic-paper/document/chapters/02-methods/content/01-methods.mdx

@@ -1,30 +1,50 @@
 ## Methods
 
-Describe the materials, instruments, datasets, models, or procedures you used. Anyone familiar with the field should be able to reproduce your work from this section.
+This section describes a hypothetical experimental design suitable for an applied
+machine-learning paper.
 
-### Apparatus and Materials
+### Data and Problem Setup
 
-Specify hardware, software versions, datasets, and any pre-processing. Cite reused work using `[N]` numeric references (e.g. "we trained the encoder following the procedure of [3]").
+We assume a synthetic dataset with 3,200 anonymized samples collected under three
+operational conditions. Each sample includes paired feature vectors, timestamped
+metadata, and a binary outcome label. The baseline split is 70/15/15 for training,
+validation, and held-out test sets.
 
-### Procedure
+### Core Pipeline
 
-Describe the experimental procedure as steps a reader could follow:
+The pipeline has three stages:
 
-1. State the input data and pre-processing.
-2. State the model / algorithm / instrument settings.
-3. State the evaluation metric(s) and any held-out splits.
-4. State randomness control (seeds, repeats, confidence reporting).
+1. **Preprocessing**: normalization, missing-value handling, and feature screening.
+2. **Modeling**: training a compact baseline model and a comparison ablation set.
+3. **Evaluation**: calibration-aware scoring and bootstrapped confidence intervals.
 
-### Notation
+For this draft, preprocessing includes clipping extreme values and aligning all
+continuous fields to SI-style unit notation.
 
-Define notation early. Italicise Roman symbols for quantities and variables, but not Greek symbols. Use a long dash rather than a hyphen for a minus sign. Number equations consecutively:
+### Equations
 
-$$a + b = \gamma \tag{1}$$
+The main objective is written as:
 
-Refer to equations by `(1)`, not `Eq. (1)` or `equation (1)`, except at the start of a sentence: "Equation (1) shows ...".
+$$
+\mathcal{L}(\theta) = \sum_{i=1}^{N}\left(\hat{y}_{i}(\theta)-y_{i}\right)^2
+$$
 
-### Reporting Units
+where $\theta$ are trainable parameters and the objective is minimized on the
+training subset.
 
-- Use SI (MKS) as primary units; English units only as secondary (in parentheses).
-- Don't mix complete spellings and abbreviations: "Wb/m²" or "webers per square meter", not "webers/m²".
-- Use a zero before decimal points: `0.25`, not `.25`.
+### Evaluation Protocol
+
+Model quality is measured by macro-averaged F1, AUROC, and an uncertainty-aware
+calibration score. Reproducibility is ensured by fixing the random seed and logging
+all preprocessing parameters.
+
+### Implementation Notes
+
+- All runs were executed on a dual-socket compute node with two GPUs.
+- Checkpoints were stored every 5 epochs.
+- Logging followed a single JSON schema shared across all experiments.
+
+### Validation and Quality Control
+
+Validation is automated through a script that checks missing captions, file path
+consistency, and reference formatting before final export.

package/template/packs/academic-paper/document/chapters/03-results-and-discussion/content/01-results.mdx

@@ -1,29 +1,47 @@
 ## Results and Discussion
 
-Present the findings of your study, then interpret what they mean for the research question stated in the introduction.
+### Benchmark Results
 
-### Quantitative Results
+The synthetic experiment yields a consistent improvement trend across three datasets.
+Performance gains are modest but stable after hyperparameter tuning.
 
-Use a table to summarise results across conditions. Caption above the table.
+| Metric | Baseline | Proposed | Improvement |
+| --- | --- | --- | --- |
+| Macro-F1 | 0.61 | 0.67 | +9.8% |
+| AUROC | 0.74 | 0.81 | +9.5% |
+| Calibration Error | 0.082 | 0.043 | -47.6% |
 
-<TableCaption>Sample comparison of conditions.</TableCaption>
+The proposed model retains a similar variance profile while improving score
+stability in low-sample conditions.
 
-| Condition | Metric A | Metric B | Notes |
-| --- | --- | --- | --- |
-| Baseline | 0.71 | 0.65 | Prior work [3] |
-| Ours (v1) | 0.78 | 0.69 | This work |
-| Ours (v2) | **0.83** | **0.72** | Best |
+### Representative Visualization
+
+<img
+  src="media/figure-placeholder.svg"
+  alt="Example of a figure placeholder"
+  style={{ maxWidth: "420px", width: "100%", height: "auto" }}
+/>
+
+Figure 1. Example of a result trend visualization (placeholder image).
+
+### Error Analysis
 
-Cite figures and tables in the text the first time they appear: "Fig. 1 shows the architecture", "Table I summarises the conditions". Use `Fig.` even at the start of a sentence; spell out `Figure` only when it is the subject.
+Some error cases cluster around edge classes with incomplete metadata. These cases
+benefit from better augmentation and a revised class-balanced loss.
 
-### Qualitative Discussion
+### Sensitivity Study
 
-Discuss what the results mean. State the limitations honestly — if the experiment doesn't cover a case you'd like to claim, say so. Avoid the word "essentially" when you mean "approximately" or "effectively".
+- Training set size below 40% causes a steeper drop in recall.
+- Early stopping thresholds above 3 epochs reduce overfitting in our setting.
+- Calibrated post-processing improves confidence robustness.
 
-### Threats to Validity
+### Discussion
 
-Briefly list what could invalidate the results: small sample size, single dataset, environmental drift, evaluator bias, etc. Reviewers will look for this section; pre-empt it.
+The most practical takeaway is that small engineering changes in preprocessing and
+evaluation discipline can produce measurable gains even when architecture changes are
+minimal.
 
-### Future Work
+### Limitations
 
-Indicate where the work goes next. Keep this to one short paragraph — over-claiming future scope hurts more than it helps in review.
+This section reports synthetic results only; real-world deployment would require
+cross-domain validation, privacy checks, and a stronger external benchmark suite.

package/template/packs/academic-paper/document/chapters/04-acknowledgment/content/01-acknowledgment.mdx

@@ -1,12 +1,26 @@
-## Acknowledgment
+## Conclusions
 
-The preferred American spelling is *acknowledgment* without an "e" after the "g". Avoid stilted constructions like "one of us (R. B. G.) thanks ...". Prefer "R. B. G. thanks ...".
+This template run shows that a simple methodology with consistent evaluation
+accounting can achieve reliable gains without dramatic architectural complexity.
 
-Acknowledge:
+### Key Takeaways
 
-- Funding sources (with grant numbers if applicable).
-- Collaborators who contributed materially but are not listed as authors.
-- Anonymous reviewers whose comments improved the paper.
-- Institutional or computational resources.
+- Keep preprocessing and metric reporting deterministic.
+- Use a calibrated validation protocol before reporting final headline scores.
+- Reserve model complexity for problems that cannot be solved with better data
+  discipline.
 
-Place sponsor acknowledgments in the unnumbered footnote on the first page of the published version. In this draft pack, keep them here until you migrate to a publisher's class file at submission time.
+### Practical Recommendations
+
+Authors are encouraged to replace each placeholder paragraph with real study details,
+including hardware, code provenance, and full reproducibility statements.
+
+### Limitations and Future Work
+
+The current draft is synthetic; external generalization remains to be demonstrated.
+Future work should add domain transfer tests and a public benchmark release.
+
+### Acknowledgments
+
+We thank the hypothetical reviewers and platform contributors who would have reviewed
+this draft in a real submission round.

package/template/packs/academic-paper/document/chapters/05-references/content/01-references.mdx

@@ -1,27 +1,32 @@
 ## References
 
-Number citations consecutively within square brackets `[1]`. Sentence punctuation follows the bracket. Refer simply to the reference number, as in `[3]` — do not use `Ref. [3]` or `reference [3]` except at the start of a sentence: "Reference [3] was the first ...".
-
-Unless there are six authors or more, give all authors' names; do not use `et al.`. Papers not yet published should be cited as *unpublished*; accepted but not yet published as *in press*. Capitalize only the first word in a paper title, except for proper nouns and element symbols.
-
-For papers published in translation journals, give the English citation first, followed by the original foreign-language citation.
+Please number references consecutively within brackets `[1]`.
+Sentence punctuation follows the bracketed number.
 
 ---
 
-[1] G. Eason, B. Noble, and I. N. Sneddon, "On certain integrals of Lipschitz–Hankel type involving products of Bessel functions," *Phil. Trans. Roy. Soc. London*, vol. A247, pp. 529–551, April 1955.
+[1] G. Eason, B. Noble, and I. N. Sneddon, “On certain integrals of
+Lipschitz-Hankel type involving products of Bessel functions,” *Phil. Trans. Roy.
+Soc. London*, vol. A247, pp. 529–551, April 1955.
 
-[2] J. Clerk Maxwell, *A Treatise on Electricity and Magnetism*, 3rd ed., vol. 2. Oxford: Clarendon, 1892, pp. 68–73.
+[2] J. Clerk Maxwell, *A Treatise on Electricity and Magnetism*, 3rd ed., vol. 2.
+Oxford: Clarendon, 1892, pp. 68–73.
 
-[3] I. S. Jacobs and C. P. Bean, "Fine particles, thin films and exchange anisotropy," in *Magnetism*, vol. III, G. T. Rado and H. Suhl, Eds. New York: Academic, 1963, pp. 271–350.
+[3] I. S. Jacobs and C. P. Bean, “Fine particles, thin films and exchange anisotropy,”
+in *Magnetism*, vol. III, G. T. Rado and H. Suhl, Eds. New York: Academic,
+1963, pp. 271–350.
 
-[4] K. Elissa, "Title of paper if known," unpublished.
+[4] K. Elissa, “Title of paper if known,” unpublished.
 
-[5] R. Nicole, "Title of paper with only first word capitalized," *J. Name Stand. Abbrev.*, in press.
+[5] R. Nicole, “Title of paper with only first word capitalized,” *J. Name Stand.
+Abbrev.*, in press.
 
-[6] Y. Yorozu, M. Hirano, K. Oka, and Y. Tagawa, "Electron spectroscopy studies on magneto-optical media and plastic substrate interface," *IEEE Transl. J. Magn. Japan*, vol. 2, pp. 740–741, August 1987.
+[6] Y. Yorozu, M. Hirano, K. Oka, and Y. Tagawa, “Electron spectroscopy studies
+on magneto-optical media and plastic substrate interface,” *IEEE Trans. J. Magn.
+Japan*, vol. 2, pp. 740–741, August 1987.
 
-[7] M. Young, *The Technical Writer's Handbook*. Mill Valley, CA: University Science, 1989.
-
----
+[7] M. Young, *The Technical Writer's Handbook*. Mill Valley, CA: University
+Science, 1989.
 
-> **Reminder**: replace the seven placeholder references above with your own bibliography before circulating the draft. They are the IEEE conference template's example citations and have nothing to do with your paper.
+> Open-press is used for iteration. Remove all template placeholder text and replace
+> references before submission.

package/template/packs/academic-paper/document/components/Page.tsx

@@ -1,5 +1,6 @@
 import { Frame, MdxArea } from "@open-press/core";
 import type { SectionsPageProps } from "@open-press/core/manuscript";
+import { useEffect, useRef } from "react";
 
 export default function Page({
   frameKey,
@@ -10,6 +11,25 @@ export default function Page({
   sectionTitle,
   sectionTone,
 }: SectionsPageProps) {
+  const pageBodyRef = useRef<HTMLElement | null>(null);
+
+  const runningHeader =
+    "This is a non-peer reviewed Express letter submitted to J SEDI";
+  const runningRight = "Your short title goes here";
+
+  useEffect(() => {
+    const area = pageBodyRef.current?.querySelector(".openpress-mdx-area");
+    if (!area) return;
+
+    area.querySelectorAll<HTMLElement>("h2[data-chapter]").forEach((heading) => {
+      const chapterValue = heading.getAttribute("data-chapter");
+      if (!chapterValue) return;
+      if (!/^\d+$/.test(chapterValue)) return;
+      const normalized = String(Number.parseInt(chapterValue, 10));
+      heading.setAttribute("data-chapter", normalized);
+    });
+  }, [chainId]);
+
   return (
     <Frame
       frameKey={frameKey}
@@ -21,9 +41,12 @@ export default function Page({
       data-chapter-tone={sectionTone}
     >
       <div className="page-frame">
-        <header className="page-header" aria-hidden="true" />
-        <main className="page-body">
-          <MdxArea chainId={chainId} />
+        <header className="page-header" aria-hidden="true">
+          <span className="running-head-left">{runningHeader}</span>
+          <span className="running-head-right">{runningRight}</span>
+        </header>
+        <main className="page-body" ref={pageBodyRef}>
+          <MdxArea chainId={chainId} overflow="extend" />
         </main>
         <footer className="page-footer" aria-hidden="true">
           <span className="footer-left">{sectionTitle}</span>

package/template/packs/academic-paper/document/index.tsx

@@ -1,13 +1,13 @@
 import { Frame, Press } from "@open-press/core";
 import type { Manifest } from "@open-press/core";
 import { mdxSource } from "@open-press/core/mdx";
-import { Sections, Toc } from "@open-press/core/manuscript";
+import { Sections } from "@open-press/core/manuscript";
 import Page from "./components/Page";
 
 export const config: Manifest = {
-  title: "Paper Title",
-  subtitle: "An academic-paper draft built with open-press",
-  organization: "Department · Institution",
+  title: "Your article title goes here",
+  subtitle: "This is a non-peer reviewed Express letter submitted to J SEDI",
+  organization: "open-press · academic-paper",
   sourceDir: "chapters",
   mediaDir: "media",
   themeDir: "theme",
@@ -31,10 +31,6 @@ export const sources = {
   story: mdxSource({ preset: "section-folders", root: "chapters" }),
 };
 
-/**
- * The cover renders the academic title block: paper title, author grid,
- * abstract band, and index terms. Replace the placeholders with your own.
- */
 function Cover() {
   return (
     <Frame
@@ -46,74 +42,72 @@ function Cover() {
       aria-labelledby="paper-title"
     >
       <div className="paper-cover">
+        <p className="paper-cover-date">May 18, 2026 – This is a non-peer reviewed Express letter submitted to J SEDI</p>
+        <p className="paper-cover-lead">This is a non-peer reviewed Express letter submitted to J SEDI</p>
+        <p className="paper-cover-short-title">Your short title goes here</p>
         <h1 id="paper-title" className="paper-title">
-          Conference Paper Title
+          Your article title goes here
+          <sup>*</sup>
         </h1>
-        <p className="paper-subtitle">
-          Sub-title (optional). Not captured by indexing services like IEEE Xplore.
+        <p className="paper-author-contact-note">
+          <span aria-hidden="true">∗</span> Corresponding author:
+          firstauthor@university.jp
         </p>
 
-        <ol className="paper-authors" aria-label="Authors">
+        <p className="paper-author-line" aria-label="Authors">
+          Name Firstauthor<sup>1</sup>, Name Secondauthor<sup>2</sup>, Name
+          Thirdauthor<sup>1,3</sup>
+        </p>
+
+        <ol className="paper-author-affiliations" aria-label="Author affiliations">
           <li className="paper-author">
-            <p className="paper-author-name">First Author Surname</p>
-            <p className="paper-author-affiliation">dept. of organization</p>
-            <p className="paper-author-affiliation">name of organization</p>
-            <p className="paper-author-location">City, Country</p>
-            <p className="paper-author-contact">email or ORCID</p>
+            <p className="paper-author-affiliation">
+              1 Department of Earth Sciences, A University, City, Country
+            </p>
           </li>
           <li className="paper-author">
-            <p className="paper-author-name">Second Author Surname</p>
-            <p className="paper-author-affiliation">dept. of organization</p>
-            <p className="paper-author-affiliation">name of organization</p>
-            <p className="paper-author-location">City, Country</p>
-            <p className="paper-author-contact">email or ORCID</p>
+            <p className="paper-author-affiliation">
+              2 School of Earth Sciences, Another University, City, Country
+            </p>
           </li>
           <li className="paper-author">
-            <p className="paper-author-name">Third Author Surname</p>
-            <p className="paper-author-affiliation">dept. of organization</p>
-            <p className="paper-author-affiliation">name of organization</p>
-            <p className="paper-author-location">City, Country</p>
-            <p className="paper-author-contact">email or ORCID</p>
+            <p className="paper-author-affiliation">
+              3 Center for Studying Cool Things, University of X, City, Country
+            </p>
           </li>
         </ol>
 
-        <section className="paper-abstract" aria-label="Abstract">
+        <section className="paper-contributions" aria-label="Author contributions">
+          <p>
+            <span className="paper-section-label">Author contributions:</span>{" "}
+            Conceptualization: Name Firstauthor, Name Thirdauthor. Formal
+            Analysis: Name Firstauthor, Name Secondauthor.
+          </p>
           <p>
-            <span className="paper-abstract-label">Abstract</span>—This document
-            is a model and starting point for an academic paper drafted in
-            open-press. Replace this abstract with your own — keep it under
-            250 words. Do not use abbreviations, symbols, footnotes, or math
-            in the abstract.
+            <span className="paper-section-label">Writing - Original draft:</span>{" "}
+            Name Firstauthor.{" "}
+            <span className="paper-section-label">
+              Writing - Review &amp; Editing:
+            </span>{" "}
+            Name Firstauthor, Name Secondauthor, Name Thirdauthor.
           </p>
         </section>
 
-        <section className="paper-index-terms" aria-label="Index terms">
+        <section className="paper-abstract" aria-label="Abstract">
           <p>
-            <span className="paper-abstract-label">Index Terms</span>—keyword
-            one, keyword two, keyword three, keyword four
+            <span className="paper-abstract-label">Abstract</span> The text for the
+            first abstract goes here. This should be in English, no longer than
+            200 words, and should not include references.
           </p>
         </section>
-      </div>
-    </Frame>
-  );
-}
 
-function BackCover() {
-  return (
-    <Frame
-      frameKey="back-cover"
-      role="manuscript.back-cover"
-      chrome={false}
-      className="reader-page--back-cover"
-      data-page-title="Back cover"
-    >
-      <div className="paper-back-cover">
-        <p className="paper-back-kicker">open-press · academic-paper</p>
-        <p className="paper-back-statement">
-          Draft built with open-press. When the paper is ready for submission,
-          port the prose into the publisher's LaTeX class (IEEEtran, acmart,
-          etc.). open-press is the iteration loop, not the camera-ready output.
-        </p>
+        <section className="paper-nontechnical-summary" aria-label="Non-technical summary">
+          <p>
+            <span className="paper-abstract-label">Non-technical summary</span> The
+            text for the non-technical summary goes here. Again, no longer than
+            200 words, no reference.
+          </p>
+        </section>
       </div>
     </Frame>
   );
@@ -121,11 +115,9 @@ function BackCover() {
 
 export default function AcademicPaperPress() {
   return (
-    <Press>
+      <Press>
       <Cover />
-      <Toc source="story" heading={<h2 id="toc-title" className="toc-heading">Contents</h2>} />
       <Sections source="story" page={Page} />
-      <BackCover />
     </Press>
   );
 }

package/template/packs/academic-paper/document/media/figure-placeholder.svg

@@ -0,0 +1,9 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="900" height="540" viewBox="0 0 900 540" role="img" aria-labelledby="title desc">
+  <title id="title">Figure placeholder</title>
+  <desc id="desc">Simple figure placeholder graphic with gray border and label</desc>
+  <rect width="100%" height="100%" fill="#f3f4f6"/>
+  <rect x="24" y="24" width="852" height="492" fill="none" stroke="#9ca3af" stroke-width="4" stroke-dasharray="18 12" rx="8" />
+  <text x="50%" y="50%" fill="#4b5563" font-size="44" font-family="Inter, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif" text-anchor="middle" dominant-baseline="middle">
+    Example Figure Placeholder
+  </text>
+</svg>