Every page offers a way onward
- Explain on the changelog what it promises, and how that differs from the roadmap and the pricing page.
- Point the contact and reporting pages at the answers already published on the site.
Building in public
What changed in EmbedFox.
A concise record of reader, publishing and website changes. Product direction belongs on the roadmap; this page records delivered work.
Product updates
Meaningful updates are published in versioned GitHub releases. This page records what they mean for publishers.
The comparison hub reads the same in every language
- Give every published language the same comparison cards, with the entry price and checked date written the way that language writes them.
- List the ten alternatives in Dutch and Romanian, which previously named none.
The embed guide shows the code it describes
- Show the embed snippet itself on the page that explains how to embed a PDF, with its optional attributes.
- Say plainly what a flipbook is and is not in EmbedFox, instead of leaving the word to do the work.
Tool and use-case pages carry their own answers
- Answer what publishers ask on each tool and use-case page, including where the public upload is the wrong choice.
- Say plainly that the four tool pages describe one product under four names.
Every comparison is written the same way
- Give the Issuu comparison the same dated, sourced evidence as the other nine.
- End every comparison with what EmbedFox is and is not, and where to go next.
Documentation answers the next question
- Answer the questions each documentation page raises, from expiry and file replacement to whether an API exists yet.
- Link every documentation page to the pages a publisher usually needs next.
Capability pages answer the question they raise
- Say concretely what each capability does today, down to the snippet attributes and the language order.
- Name what each capability does not do yet, instead of leaving the edge to be discovered.
The comparison hub answers the choice it poses
- Give every alternative its own card with the provider focus, its published entry price and the date that price was checked.
- Open the comparison hub with a plain rule for choosing a hosted platform or a reader on your own page.
The roadmap matches what the product does
- Show documents that stay, team workspaces, file replacement and reader appearance as available, because they are.
- Mark published plan scope that is still being built, so a plan page never reads as a delivery promise.
Clearer plans and a completion page in your language
- Answer the upload completion page in the language the upload started in, and offer the claim step in every published language.
- Show the plan comparison as part of the pricing page, with the price row and one plain line for every capability.
- Keep the billing-period choice, plan cards and capability cards visually consistent.
Render progress shows the work
- Show the number of pages already rendered while a document is being prepared.
- Keep the render phase accessible and stop polling after the bounded preparation window.
Pricing makes the next step clear
- Keep recurring plans and the one-time Lifetime Team offer together in the plan decision before checkout.
- Show the selected plan, billing period, price and workspace as the next explicit step before Stripe.
The public footer names the operator
- Show the verified Sinfin operator identity in the public footer.
- Keep support mailboxes and legal destinations out until they have an accountable owner and legal review.
Comparison pages name the decision
- Give each English comparison detail a clear alternative-to title for the provider it covers.
- Keep the comparison factual: source dates, public boundaries and documented competitor scope remain visible.
Pricing explains the plan choice
- Switch between monthly and yearly EUR list prices without leaving the pricing page.
- Expand a plan comparison and get clear answers about documents after a paid plan ends.
Comparison pages explain the trade-off
- Separate comparable scope, the current public upload boundary and the documented competitor scope on every comparison detail.
- Keep the final choice tied to the document workflow you need instead of claiming one service fits every publisher.
Comparison prices stay source-linked
- Add a current, source-linked Yumpu adFREE price with monthly and annual billing clearly separated.
- Keep comparison prices tied to the provider鈥檚 official pricing page and check date.
Language switching stays in context
- Keep the language switcher on the matching page when a reviewed translation exists.
- Show full language names and flags, with a clear localized home fallback for pages without a translation.
Document links keep their context
- Keep links inside PDF documents and publisher call-to-action layers attributable when readers follow them.
- Preserve existing destination parameters while adding EmbedFox document attribution.
A fox you can recognise
- Introduce the line-origami fox identity: header and footer mark, two-tone lowercase wordmark and favicons.
- Show the fox mark next to the reader鈥檚 Powered by EmbedFox attribution.
- Refresh the social sharing image with the new mark.
A live sample document to try
- Show the FOXFIELD sample magazine as a real embed on the homepage, tool, use-case and feature pages.
- Let an embed open on a chosen page with the data-embedfox-page snippet attribute.
- Offer the sample PDF for download so you can try the upload with a ready-made document.
Replace a file, keep every link
- Let paid publishing workspaces replace a document鈥檚 PDF while its link, deep links and embeds stay stable.
- Add reader and document-library guides plus a full embed attribute reference to the documentation.
Reader appearance that fits
- Match new readers to each visitor鈥檚 light or dark system setting by default.
- Let readers choose automatic, light or dark appearance and remember that choice locally.
- Make the free-reader EmbedFox attribution a direct link to the service.
Clearer upload progress
- Show uploaded and remaining file size while a document is being sent.
- Keep the progress value available to screen readers.
Clearer document search
- Highlight the visible text that matches a PDF search result.
- Keep previous and next search-result controls compact inside embeds.
- Keep the reader stable while changing page or search result.
More room for mobile reading
- Tap a page on a phone to hide reader controls and tap again to bring them back.
- Keep reader controls available on desktop and when reading with a keyboard.
- Leave page links, zoom, search and fullscreen in the same reader instead of opening a separate mobile view.
Clearer public upload scope
- Keep every tool guide, publishing use case and machine-readable summary aligned with the public upload form.
- Describe PDF publishing clearly while public image-set publishing is unavailable.
- Keep the public seven-day reader link and embed scope visible before a document is shared.
More reliable mobile reading
- Keep public reader links, deep page links and embeds at a stable scale on mobile.
- Load PDF bytes in the portions a reader requests, so opening a document does not depend on a full-file transfer.
- Copy the public reader link or embed snippet directly after publishing a document.
- Keep public reader links current when a document is removed, disabled or expires.
More ways to publish
- Publish a PDF in the responsive reader and embed it on your own website.
- Add sourced comparisons, practical publishing tools and use-case guides.
- Keep the public upload boundary and reader links clear before sharing.
Publishing controls take shape
- Add reader presentation, preview and publisher handoff controls for eligible publishing workspaces.
- Add publisher identities and optional logos for a reader that matches the publisher.
- Add a privacy-first aggregate reader interaction view for eligible workspaces.
The first public reader
- Launch the public upload, reader URL, deep links and versioned website embed.
- Add searchable PDF reading, zoom, fullscreen and responsive mobile navigation.
- Make anonymous uploads public for seven days with a clear removal and reporting path.
Where this sits.
Three pages carry three different promises, and it is worth knowing which one you are reading.
- This page
- What has already shipped and what it changes for a publisher. Nothing appears here before it is live.
- The product roadmap
- What is available today and what is being built in public, separated so neither is mistaken for the other.
- The pricing page
- Published plan scope and prices, with anything still in build marked as such rather than sold as delivered.
Follow the releases. The complete version history and release notes are published on GitHub.