Skip to content
Ithaca, New York · Research-publisher discussion widgets

Research Publisher Discussion Widget Development for Ithaca

A reader may have a question about one panel of a published figure rather than the article as a whole. The conversation needs to show exactly what the question refers to, especially when the publisher replaces an image or removes a panel. We help Ithaca, New York research publishers design embedded discussion products around explicit figure references and editorial ownership.

Our Poppin case, recorded in Türkiye, documents in-page software, realtime discussion and a publisher dashboard for an embeddable widget. Its delivered product concerns prediction markets. Figure anchors, research-publisher roles and reference repair would be new requirements. Curiosive uses AI to accelerate implementation with engineer-reviewed quality and stays involved as a long-term product partner.

Fictional research article with a selected figure panel connected to a question card and a separate revised figure
AI-generated research discussion concept; not a Poppin screenshot, actual research figure or scholarly review result.
5+
years building for production
12
countries the work runs in
100%
of code read by a senior engineer
1 day
to hear back, from the engineer
Browse industry workflows →

Give each reader question a precise publication reference

Begin with authorized article templates and the figure identifiers the content system can provide. Decide whether a question refers to the article, a complete figure or a selected panel. A nearby caption should not become the only reference when the layout changes. Identify what the publisher can represent consistently in HTML and what needs a different treatment for PDFs or third-party embeds. The product should expose supported reference types clearly to the reader.

Relevant work: Poppin in-page discussion and publisher embeds

The published Poppin case describes a browser extension inside a shadow root, a background service worker, a popup and a side panel. Page-level posts, comments, chat and follows use a realtime connection. Its Next.js publisher dashboard installs a widget through a script and manages style, settings and announcements. NestJS, TypeORM, RabbitMQ, WebSockets and Firebase support the stack. This Türkiye-recorded prediction-market product provides embedded-software evidence; figure discussions and research editorial workflows would receive a separate Ithaca project scope.

Keep changed figures from silently changing a question

Agree how a figure replacement affects existing questions. Retaining a historical reference, marking an anchor unresolved and asking an editor to review a suggested reattachment are different behaviors. The software should follow the chosen rule instead of assuming that the second panel in a new image means the same thing as the second panel in the old one. A removed panel needs a visible destination and explanation. Publishers supply the reference mapping and authorize editorial changes.

Define reader discussion separately from editorial decisions

Specify who can ask a question, reply, report content and act on a reference repair. A reader conversation does not itself establish an editorial decision or a research finding. Review how the widget behaves in the supported article layouts, including a narrow screen and an unavailable figure. AI accelerates familiar interface and record-handling work; engineers review anchor identity, host-page styling and reconnect behavior. Optional author tools or automated classification need their own scope and evaluation.

Review a figure question after its referenced panel changes

For a new engagement, bring authorized article pages, figure and panel identifiers and publisher-owned discussion rules. Proposed acceptance examples: a question opens beside the selected panel; a whole-article comment remains a separate reference; a replaced figure leaves an earlier question with an explicit unresolved or historical anchor; and an authorized editor can review a proposed reattachment. Include a removed panel and an unsupported embedded figure. These are proposed research-publisher checks, not claims about historical Poppin figure annotations, scholarly publishing or peer-review workflows.

A product partner for the publishing workflow

New article templates, figure formats and reader questions create continuing product work. We keep a shared backlog with written acceptance examples and engineer-reviewed releases. Monthly AI-accelerated development starts from $2,000, with scope, capacity and operating responsibilities agreed in writing. Curiosive LLC works remotely with Ithaca teams through agreed Eastern-time review windows, with engineering led from Ankara. The relationship continues as the publication refines its discussion experience and editorial tools.

Questions

The things people ask before starting.

Can you build figure discussion widgets for an Ithaca research publisher?

Yes. Bring authorized article templates, figure identifiers and discussion rules so we can scope the embed and publisher tools around the supported reference types.

Does Poppin include scholarly figure annotations?

Its Türkiye-recorded case documents a prediction-market product with page-level discussion and publisher embeds. Research figure anchors and editorial repair workflows would be new work.

What happens to a question when a figure is replaced?

We agree that behavior during discovery. Options include retaining a historical anchor, marking it unresolved or having an authorized editor review a proposed reattachment.

Can you maintain the widget as article templates change?

Yes. Continuing work can cover template compatibility, new reference types and publisher feedback through a shared backlog.

How it starts

What happens after you write to us.

  1. 01

    You describe the product

    One paragraph on what you are building, roughly when you need it, and who it is for. No brief, no form with fifteen fields.

  2. 02

    You get a reply within a day

    From the engineer who would do the work, not a sales team. If we are not the right fit we say so, and where possible we point you somewhere better.

  3. 03

    You get a scoped plan

    Scope, price and timeline in writing before anything is committed. You decide with the numbers in front of you.

No long contract to begin, no lock-in to our tooling, and the code is yours from the first commit.

Start a conversation
Contact

Looking for an engineering partner for the long haul?

A short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.

Ankara / Türkiye · Working across European and US time zones