mojtaba-ja.github.io

My personal academic website. Plain HTML — nothing to install.

Live: https://mojtaba-ja.github.io

---

To change anything

Edit assets/data.js. That is the only file with content in it.

Then:

node build.js
git add -A
git commit -m "what changed" ; git push

Live in about a minute.

---

Add a paper

Paste into the publications list in assets/data.js, at the top of its own group:

{
  group: "peer-reviewed",                // peer-reviewed | working
  title: "Full Paper Title",
  authors: "<strong>M. Jafarian Abyaneh</strong>, J. Jang",
  venues: ["Journal Name — 2026"],
  status: "published",                   // published | review | preprint | prep
  links: [{ label: "DOI", url: "https://doi.org/..." }],
  abstract: `Paste the real published abstract here, or leave it null.`,
},

abstract is kept as a record only — nothing renders it. Readers are sent to the DOI, IEEE Xplore, SSRN or Scholar links instead of a local copy of text the publisher already hosts.

How papers are grouped

The site mirrors the CV's sections instead of showing one flat list. group picks the section; pubSections names them and sets their order:

group	Section on the page
peer-reviewed	Publications — journal articles and the thesis
working	Working Papers & Under Review — under review, preprints, in prep

Entries render in the order you write them, so keep each group reverse-chronological, exactly as the CV lists them. A group with nothing in it prints no heading at all.

Add a research project (the section with figures)

Entries live in research in assets/data.js:

{
  id: "short-name",
  title: "Plain-language title, not the paper title",
  status: "published",                  // published | review | preprint | prep
  hook: "One line that makes a stranger care. This is the sentence that has to land.",
  points: [                             // two to four, one line each
    "A fact with a number in it.",
    "What is actually new about it.",
  ],
  image: {                              // optional — see the rule below
    src: "assets/img/my-figure.jpg", width: 1200, height: 618,
    alt: "What the picture shows, for a screen reader.",
    caption: `Caption, with attribution to the paper it came from.`,
  },
  stats: [{ value: "0.76 m", label: "Average displacement error" }],  // optional
  links: [{ label: "Paper", url: "https://doi.org/..." }],
},

The figure rule: a figure goes on this page only if the paper it comes from is already public — published open access, or posted as a preprint. Nothing from a manuscript under review or in preparation, however good it looks. When one of those becomes public, add its image block and rebuild. Entries with no figure fall back to stats, or to the paragraph alone.

Prepare a figure for the web before adding it (roughly 1200px wide, JPEG):

python -c "from PIL import Image; im=Image.open(rSOURCE.png).convert(RGB); w,h=im.size; im=im.resize((1200,round(h*1200/w))); im.save(assets/img/NAME.jpg,JPEG,quality=86,optimize=True,progressive=True)"

Add a talk or poster

Talks live in their own presentations list, kept out of the paper list:

{
  type: "conference",                    // conference | workshop
  title: "Talk Title",
  authors: "<strong>M. Jafarian Abyaneh</strong>, J. Jang",
  venue: "Meeting Name, City, ST",
  date: "Jan. 2026",
  note: "Poster presentation",
},

talkSections names those two sections the same way pubSections does.

The site is three kinds of page

Page	Answers	Built from
/	"Who is this and is he any good?" — 30 seconds	homeSections()
/cv/	"Give me the complete record."	cvSections()

The homepage is a funnel: masthead → Selected Research (pictures) → Publications → Working Papers → Code → News → Education → Experience (compact) → a link to /cv/. News sits below the papers deliberately — dated one-liners are the weakest content on the page and should not be the first thing a stranger reads. Experience on the homepage shows roles and dates only; the bullets are on /cv/, driven by the same data and the same renderer.

Page order and the jump nav

homeSections() and cvSections() in build.js are the two pages: one line per section, in the order they appear. The row of jump links under the photo is generated from that same list, so a section can never be missing from the nav, and an empty section (no data) prints neither a heading nor a link. To move a section, move its line; to rename it, change the title there; the anchor (#working-papers) follows the short nav label automatically.

Add a news item

{ date: "2026-10-01", text: `Passed my <strong>qualifying exam</strong>.` },

Sorts newest-first on its own.

New CV or resume PDF

Edit the .typ file, then from G:\My Drive\CV and Resume:

bash publish.sh

Or double-click PUBLISH.cmd. It recompiles whatever changed, copies the PDFs into the site, rebuilds, and pushes every repo that changed. Safe to run any time — if nothing changed, it does nothing.

Give it a commit message and every repo it pushes uses that message instead of the dated default:

bash publish.sh "Group papers the way the CV does"

Flag	Effect
"message" or -m "message"	commit message for this run (default: Update site (date))
--dry	show what it would do, change nothing
--check	also test every link (slower, needs network)

The site publishes one document: assets/cv.pdf, built from cv-typst/cv-typst.typ. The resumes in resume-typst/ still compile and still get pushed to their own repo — they are what you attach to an application — but they are not served here. A recruiter offered both reads them as synonyms and has to pick; a resume is tailored per application anyway, so one fixed public copy helps nobody. publish.sh carries the note on how to undo this.

---

Other commands

Command	What it does
python -m http.server 8765	Preview at localhost:8765 before pushing
node check-links.js	Test every link on the site
node submit-indexnow.js	Tell Bing and Yandex about new pages

---

Notes

• Repo is public because GitHub Pages only serves public repos on the free plan.
• index.html, projects/, cv/, sitemap.xml and robots.txt are generated. Don't hand-edit them; node build.js overwrites them.
• Dark mode is the default. The button top-right switches to light.