Roadmap & build log
Where Citeable has been, and where it’s going.
Citeable is built in small, frequent steps. The line below traces the key features — what’s shipped to the left, what’s planned to the right, centred on what’s being built right now. A few markers sit past the beta — the directions I expect to take once the first release is out. The full changelog follows.
← ShippedPlanned →
Article & issue data model
Journal presentation & Google Scholar tags
Journal identity & portability
Indexing — OAI-PMH & CrossRef
Editorial workflow
Peer review & reviewer pool
Block-native presentation
Issues & advance access
HTML reader
Author tracking & dashboard
Theme-led block templates
Statistics dashboard
Special issues & guest editors
Editorial board & roles
Archiving — LOCKSS & JASPER
Institution autosuggest
Author accounts & history
Security & data-protection reviewPassed · 0.8
Browse by subjectUp next
Journal data export
Richer HTML — images & equations
0.9 — Public betaFirst public release
Verified ORCIDAfter beta
Revisions & production stages
Customisable review forms
§
Build log
Every release, newest first. Expand any entry for the detail.
0.8.87Issue credits & a faster guest-editor picker Latest›
An issue’s editors are now credited under its volume line — guest editors for a special issue, or the editor-in-chief where a journal chooses to show it — and guest editors are assigned by a type-ahead search with add-and-remove, in place of the old long multi-select.
0.8.82Import a journal’s readership›
Bring an existing journal’s read and download history across from OJS or COUNTER reports, matched onto the right articles by identifier, volume and issue, or title — with a by-hand step for anything that doesn’t line up, which then sticks for next time.
0.8.79The editorial board, arranged your way›
The public editorial board is arranged on a drag-and-drop layout into whatever groupings a journal uses — kept separate from the behind-the-scenes positions that carry permissions — and each member’s ORCID, institution and website now show as small icons.
0.8.78Journal-correct DOIs›
Each article’s DOI is built from the journal’s own prefix and a structured suffix — volume, issue and first page — rather than a generic stem, so the identifier reflects where the article sits.
0.8.77A friendlier submission form›
The author-facing submission form is redrawn: a drag-and-drop manuscript box, clearer required fields, an affiliation suggested from the author’s email, and a keyword minimum — the same details, far easier to complete.
0.8.76A clearer review page›
The reviewer’s page becomes a set of choosable recommendation cards — accept, minor or major revisions, reject — with the manuscript a single download and separate boxes for comments to the author and to the editors.
0.8.71The editor’s lists, as cards›
The submissions inbox and the articles list read as cards rather than dense tables, each with its title, a short meta line, and — for a submission — a workflow indicator showing the stage and how far through it is.
0.8.70The submission editor becomes a workflow›
A submission now opens as a workflow — Submission, Review, Revisions, Decision, Production — under a status header with a clickable stepper, an always-present editorial log, and review tools that appear only once a paper has been sent out.
0.8.65Acceptance letters as PDFs›
Editors can download a formal acceptance letter as a PDF, built from an editable template with the journal’s letterhead and an optional signature, in a choice of layouts — generated without any server tools, so it works on locked-down hosts.
0.8.58A branded sign-in screen›
The WordPress sign-in page now wears the journal’s own identity — its icon or wordmark, its accent colour — instead of the default WordPress branding.
0.8.57Send mail in the journal’s name›
The journal can send its email over authenticated SMTP through its own mailbox, which — with the matching DNS records — is what keeps decision letters and invitations out of spam.
0.8.55Author accounts & history›
Link an author to their WordPress account by email or ORCID — a manager confirms each match — and their work gathers under it, every paper still showing the affiliation it carried at the time. The public author page shows their current affiliation and each article’s as-published one together.
0.8.52Institution autosuggest›
Entering a university email suggests the author’s affiliation, and on profiles their country, filling the field only when it is empty. The list is fetched and cached on the site — never shipped in the plugin — with a manual upload for hosts that block outbound connections.
0.8.50A more Citeable user screen›
Edit a team member straight from their card; the journal profile and editorial permissions become cards lifted to the top of the user screen, each saving on its own without a full page reload.
0.8.49Back-end tidy›
Journal settings are rebalanced so each tab holds one idea, and everything for running the journal sits under a single Citeable-branded Journal menu.
0.8.46How the current issue is chosen›
A setting decides whether the latest issue in a volume is the one with the highest number or the most recent date — with a fix so an issue can no longer be mis-ordered by its WordPress date.
0.8.44Per-person permissions›
A journal manager can grant or deny any single capability for one individual on top of their role, with a line showing what they can do and why.
0.8.43Section-editor decisions›
A section’s editors record their call; an acceptance or rejection is final only once they agree, and a disagreement escalates to the editor-in-chief.
0.8.41Public editorial board›
A front-of-journal block lists the team by role — photos, affiliations and country flags — showing only the positions marked public, and naming the editor-in-chief for DOAJ.
0.8.38The editorial team page›
A visual team screen: drag role chips onto people, reorder by dragging, and invite a new member with a set-your-password email.
0.8.36Configurable roles›
Define the journal’s roles and exactly what each may do; sensible defaults — editor-in-chief, journal manager, editorial board, section editor — ship ready to use.
0.8.34Editor profiles›
Each editor gets a journal profile they fill in themselves — photo, affiliation, country with flag, biography, ORCID and links.
0.8.30Editorial board›
The roster and the journal-wide positions, with each shown-as title kept separate from the powers it carries.
0.8.29Long-term archiving›
An opt-in LOCKSS / CLOCKSS manifest and permission statement so a preservation network can discover and copy the whole journal.
0.8.28Author dashboard›
A signed-in author sees their own submissions and the stage each has reached, shown as a progress line.
0.8.26Announcements›
A portable announcement block that shows the latest notice and hides itself once its time is up.
0.8.24Customisable statistics›
Editors can drag the statistics cards into the order they want and hide the ones they don’t, saved per editor.
0.8.23Readership & reach›
Views and reads over time, the countries readers come from, and a breakdown of reads by access tier — all from the journal’s own data, with no third-party analytics.
0.8.21Statistics dashboard›
A new editor statistics page: submission volume and seasonality, acceptance and desk-reject outcomes, turnaround times and the most-read articles.
0.8.18Theme-led pages›
Journal pages can be rendered by the theme through starter block templates — each works out of the box and stays editable in the Site Editor.
0.8.17Lists & the issue archive›
Clearer admin list columns, an all-issues archive laid out as volume spines, and a guard against two issues sharing a number.
0.8.13Read in the browser›
Articles can carry an HTML reading version — converted from Word, with footnotes shown as sidenotes — alongside the canonical PDF.
0.8.xPrivacy, security & GDPR hardening›
A privacy-by-design pass through the 0.8 line — readership counted without storing personal data, retention applied to stored contacts, and the security and data-protection review carried out ahead of beta.
0.8.8Articles know their issue›
An article’s issue becomes a stored link chosen from a picker rather than fragile text-matching, with inline issue creation and proper cover dates.
0.8.3Author tracking page›
A no-account link lets an author see the stage their submission has reached, without exposing anything they shouldn’t see.
0.7.10Forthcoming issues & advance access›
An issue can be forthcoming; articles go live early as Online First, then the whole issue publishes — and becomes current — in one action.
0.5.0FSE presentation layer›
The block-native presentation foundation — journal pages assembled from blocks the theme can style.
0.4.0Editorial workflow — the spine›
Submissions become their own records, moving through clearly defined editorial stages.
0.3.1Indexing›
An OAI-PMH endpoint and CrossRef DOI deposit — the groundwork that also opens the door to preservation.
0.3.0Journal identity & portability›
Journal title, publisher, ISSNs and accent colour become settings — the point at which the plugin stopped being one journal’s and became any journal’s.
0.1.0The foundation — presentation & Scholar tags›
The very first build: articles and issues as structured records, presented as citable landing pages with metadata, an open abstract, Google Scholar tags, an in-page reader and member-gated PDFs — the core everything else was built on.