Job search
Journo Portfolio Review: Paid Publishing, Work-Sample Backups, and Private Sharing
Distinguish article captures from editable source archives and choose a concrete public/private portfolio route.
Journo Portfolio is useful to assess when your job-search evidence includes published writing, external bylines and work samples that could disappear from their original URLs. Its paid publishing, article backups and privacy options address different needs. Identify which of those needs applies to your portfolio before choosing a plan.
This review checks current pricing and V2 help documentation on October 21, 2026. It includes the domain and cancellation policies, but no account, article import, backup, upload, private page or subscription was tested. LandOffer publishes this review and offers job-search tools. Use recent technical openings to select samples that demonstrate the responsibilities you want to own.

Free editing is different from free publishing
The current V2 billing guide says new accounts can build and edit for free, but the site stays unpublished until upgraded. Plus publishes on a Journo Portfolio address; Pro adds a custom domain, privacy options, article backups and media uploads. Unlimited extends Pro with higher limits and additional features.
The same guide explicitly distinguishes older free accounts, which can remain published under their existing limits. It also says new accounts no longer receive the old seven-day trial. Do not use a legacy V1 page’s free article allowance or trial description as the current offer for a new account.
For a job seeker, free editing can help prepare a draft without committing to publication. It does not provide a public link you can assume a recruiter can view. Conversely, an old published free portfolio does not prove a newly created account has the same entitlement. Verify the actual plan before sending its address.
Current prices separate publishing from backup features
The observed pricing page lists Plus at $7 per month equivalent with annual billing or $9 monthly, Pro at $10 annually equivalent or $12 monthly, and Unlimited at $14 annually equivalent or $18 monthly. The page states that prices include taxes; this is a public pricing statement, not an inspected checkout or currency-conversion result.
Annual baselines at those displayed amounts are $84, $120 and $168. Twelve unchanged monthly payments would be $108, $144 and $216. Pro’s displayed annual difference is $24, equivalent to two $12 monthly payments. Use the displayed arithmetic rather than repeating inconsistent “months free” marketing descriptions.
Plus is the starting publishing candidate when a platform address and ordinary public presentation meet your needs. Pro is relevant when backups, a custom domain or restricted sharing solve a specific requirement. A long article list alone does not establish a need for Unlimited: the V2 guide describes unlimited portfolio items and pages on Pro too.
Media limits remain separate. The current card shows 120 video-equivalent minutes on Pro and 240 on Unlimited; its footnote counts ten audio minutes as one video minute. Those are documented allowances, not storage or playback tests performed here. Multilingual and store features carry beta qualifications on the current page, so do not treat them as tested production workflows.
Article backups preserve a representation of a page
Journo’s current pricing describes article backups as PDFs and screenshots of online work. Its privacy and backup guide describes inspecting an item’s image/PDF backups and changing the item’s destination to a backup when the original disappears. These are documented product capabilities, not evidence that every publication can be captured completely.
A screenshot preserves a visual representation; a PDF may preserve readable text and layout. Neither automatically preserves an editable Markdown source, a Git repository, a runnable code environment, external assets or the rights to republish the original article. Keep those needs separate when your samples include technical tutorials.
After any actual capture, inspect the byline, headings, figures, code blocks and ending. A saved file remains inadequate if the important explanation is clipped or a permission notice is missing. This review did not trigger a capture or verify a resulting file, including any paywalled or dynamically rendered source.
The current item guide distinguishes URL imports, file uploads and blog posts written directly on the site. Importing a URL can create a portfolio item; it does not by itself establish a checked backup or permission to redistribute the publisher’s material. Keep the byline, outlet and original publication context with the sample.
Worked example: finish a three-byline preservation record
Fictional technical writer Tamsin has three writing samples. In this exercise, the stated archive contents and sharing permissions are assumptions, not captured files or inspected contracts. Her goal is to show explanation and documentation work without claiming that a screenshot is a complete technical project.
| Sample and stipulated state | What the available representation preserves | Completed preservation and caption decision |
|---|---|---|
| API pagination explainer, original URL still live | A bylined article and diagrams in an authorized PDF capture | Link the live publication first; retain the permitted capture and editable source separately |
| Migration tutorial, publisher URL removed | A previously checked authorized PDF with byline, date and full ending | Label it an archived publication, name the publisher and original date; do not call the link currently live |
| Interactive code walkthrough, only a screenshot available | A visible portion of the explanation, not the executable notebook or dependencies | Do not present the screenshot as a reproducible code sample; retain source and environment records outside the portfolio |
Tamsin’s first caption reads: “Bylined API pagination explainer; I wrote the explanation and diagrams. Published version linked, with a permitted archived copy retained.” The second reads: “Archived migration tutorial originally published by the named outlet on the stated date; the original URL is no longer available.” Actual users must replace those placeholders with accurate facts.
For the walkthrough, her completed decision is to show only a short authorized writing excerpt until a suitable source package exists. She does not infer that the article-backup feature preserves notebook execution, package versions or repository history. A potential employer looking for code evidence should be told what is and is not available.
Her finished record retains the article title, outlet, original publication date, her role, live-or-archived state, permission scope and the location of independent originals. She keeps a capture’s later date distinct from the original publication date. No article is marked as backed up by Journo in this review.
This separation matters if a publisher closes or reorganizes its archive. A permitted copy can preserve writing evidence, but an unavailable original should remain disclosed. Do not invent a current publication URL or imply that possessing a PDF transfers the publisher’s rights.
Portfolio PDF export is another kind of output
The V2 export guide describes exporting portfolio articles into a PDF with configurable contents. To select particular articles, it directs users to organize them into a block and order them before export.
That PDF provides a documented option for offline review, but it is distinct from each external article’s PDF/screenshot backup. It is also not a complete portable website, source repository or restored external publication. Inspect an actual export for the intended samples and ordering before attaching it to an application; no export was created here.
For technical-writing evidence, keep three independent records: a public portfolio presentation, permitted captures of published work, and editable originals with any relevant code or build files. Maintaining one does not prove the other two are complete.
Private sharing offers specific routes, not anonymity
The V2 privacy guide says Pro is required to change privacy options. It describes Public, Secure link and Password protected routes. Secure-link access depends on possession of the link; the guide warns against publishing it. Password protection depends on a separately chosen password shared with the intended viewer.
The guide also allows restrictions on individual pages and blog posts, with the homepage excluded from that individual-page route. It describes noindex and no-referrer options separately. Noindex asks search engines not to index; it does not require a visitor with the URL to authenticate. No-referrer addresses information sent when a visitor follows an outbound link; it is not an access password.
Neither a shared link nor a shared password proves who is viewing or prevents forwarding and screenshots. Do not repeat a marketing suggestion as a guarantee that a current employer cannot discover the work. Also, a restriction does not authorize disclosure of confidential client material. Use only samples whose permission allows the intended audience.
Worked example: choose a concrete public and private route
Continue Tamsin’s fictional case. She wants a public introduction and two authorized public bylines. A separate documentation sample may be shown only to a specific interview panel. Another client sample has no permission for job-search sharing and stays outside the service.
| Content or reader route | Completed decision | Remaining check before real sharing |
|---|---|---|
| Homepage and two public bylines | Keep public, with accurate attribution and live/archive labels | Open the intended public URL without an editor login |
| Authorized panel-only documentation sample | Consider a password-protected non-homepage on Pro | Confirm that the permission permits this shared-password arrangement and inspect direct-page access |
| Whole-site secure link | Reject for this brief because the introduction is intentionally public | Do not put a whole-site access link into a public resume |
| Client sample without sharing permission | Do not upload | A privacy toggle cannot supply missing permission |
| Noindex on a public page | Do not treat it as the panel-only protection | Verify access controls separately from search visibility |
Her completed route is public introduction plus a separately restricted case page, subject to the actual permission and access checks. She will use a password unrelated to any account password. The password and recipient handling remain future actions; no real secret or private link is created or sent here.
She also removes the restricted sample’s title, thumbnail and detailed excerpt from the public selection in this fictional plan. A public teaser should not expose the same information the private page is intended to restrict. The panel receives only material it is permitted to see, through an arrangement the owner has verified.
Before actual use, Tamsin would check the public homepage, the restricted page without credentials and then the intended authorized route. These are proposed tests, not a security assessment performed on Journo. If the permission requires named-user verification rather than a transferable password, she will need a different sharing arrangement.

Domain inclusion is ongoing within the described Pro service
The pricing FAQ says Pro includes domain registration, renewal and transfer without extra fees; it does not limit that statement to the first year. It also says the user owns the domain and can have it transferred to an account they control without a transfer fee. Changing to a different domain can incur a new registration charge, quoted separately. Pricing and domain FAQ
The V2 domain guide distinguishes keeping an existing domain at an external registrar from transferring its management. With the former, the user continues paying that registrar and handling the relevant configuration. Domain inclusion is not proof that a transfer or setup has happened.
The domain guide discusses ongoing ownership and management, not a universal guarantee that any desired extension is available at any cost. Confirm the exact domain and arrangement before making it the permanent address in applications. No registration, transfer, renewal or DNS change was performed here.
Cancellation preserves the editor, not continued public access
The V2 billing guide says subscriptions charge at the beginning of each monthly or annual period and renew automatically. Canceling leaves paid features through the paid period; when it ends, the content stays in the editor but the public site becomes unpublished. Preserve another sharing plan if submitted applications still point to that address.
The published cancellation policy, dated March 13, 2022, describes refund requests within 14 days of subscribing or seven days of a renewal. It deducts $10 if a domain was registered or renewed on the customer’s behalf. The current pricing FAQ repeats that qualified rule; do not reduce it to an unconditional full refund for every purchase.
Journo Portfolio is worth evaluating when published-writing preservation or controlled sharing justifies Pro beyond basic paid publishing. Keep editable originals independently, inspect any real backup, and choose an access route that matches permission. Continue aligning samples with relevant work through LandOffer without treating a portfolio feature as a hiring-outcome guarantee.


