Job search
Readymag Review for a Portfolio: Published Projects, Responsive Layouts, and Paid Features
Two completed site and layout exercises separate case studies from published projects, preview from live features, and cancellation from taking work offline.
Readymag allows an initial free portfolio with several case studies organized as pages inside one published website. You still need to select each page’s evidence and arrange it for smaller screens. Paid features solve particular publishing and workflow needs; they do not automatically make the portfolio easier for a recruiter to read.
This Readymag review examines published projects, responsive layouts and paid-feature boundaries for tech job seekers. LandOffer publishes this guide and offers job-search tools. We checked public help pages and attempted to read the pricing page on October 21, 2026. We did not create an account, build a project, upload material, purchase a plan or publish anything. Both completed design exercises below use original fictional inputs.

Count published websites separately from case studies
The official plan guide describes Free as one published project with up to ten pages, including Desktop, Mobile and Tablet layouts. A Readymag project can contain the whole portfolio; an engineering case study inside it does not necessarily consume another published-project slot. Count the websites you need to publish and the pages inside each before comparing plans.
The guide describes Personal for one published project and lists domain mapping, private websites and PDF export among paid features. It says Form, Shots and code injection can be tried in Free preview mode but require payment to appear in the published version. Check paid-feature entitlement before relying on something that appears only in the free preview.
Public pricing checks did not yield usable plan prices, and the browser page remained blank after the cookie notice was dismissed. We did not obtain a reliable current numeric price or checkout total. Confirm the applicable plan, billing interval, tax and renewal amount on a working public or purchase page before deciding to pay; no expired promotion is treated as an offer in this review.
Arrange the evidence for the screen the reader uses
The mobile and tablet design guide describes adding separate layouts and rearranging widgets. Its Single column option helps resize and position content, but does not apply to fixed widgets. Desktop Scale Layout does not apply to mobile or tablet layouts. The documented automation is a starting point, not evidence that your particular composition will be usable everywhere.
A desktop portfolio may use a wide image beside a contribution statement. On a phone, the reader needs an intentional sequence: what the project is, what you did, evidence, then the route to more detail. Shrinking both columns into a tiny version of the desktop page can hide the very evidence the site exists to communicate.
The widget-layout guide says content is synchronized between layouts while some attributes can differ. Changing a shared caption can therefore affect other versions. If you need different content, the documentation describes duplicating the widget and hiding the appropriate copy for each layout. That needs careful maintenance so contradictory versions do not remain visible.
We read these controls in documentation, rather than using the editor or measuring a published Readymag page. Review your own text, menus, links and animations on mobile rather than inferring their usability from the available layout controls. Plan time to check the result independently of the editor session.
Completed site plan: three case studies inside one project
Consider Avery, a fictional frontend engineer with three authorized personal projects: an accessible component demo, a data-table interaction and a small WebGL experiment. In this exercise, Avery has permission to show all selected assets. They want one portfolio URL for an invented frontend opening and do not need a custom domain, password or contact form at launch.
Avery's completed architecture uses one published Readymag project with nine pages. It treats case studies as pages within that project, rather than assuming each must be a separately published website.
| Page allocation | Finished content decision | Why it earns the space |
|---|---|---|
| Home: one page | Three case summaries with a clear contribution sentence and links | Reader can choose relevant evidence immediately |
| Component case: two pages | Problem and implementation; interaction and limitations | Separates the artifact from claims about what was tested |
| Data-table case: two pages | State behavior and sample data; design trade-offs | Makes the interaction explainable without a long animation |
| WebGL case: two pages | Visual evidence; own code versus third-party assets | Preserves contribution and attribution boundaries |
| About/contact: one page | Short background and a contact route without an embedded form | Avoids depending on a paid preview-only widget |
| Methods: one page | Shared setup notes and explicit untested claims | Keeps repeated technical context out of every case |
The total is one plus six plus one plus one: nine pages. It fits the documented Free cap with one page remaining. Avery selects Free as the initial plan to evaluate, subject to successfully checking the actual free publication and visitor route later. This is a completed architecture and entitlement decision, not a Readymag build or a claim of verified access.
A planned fourth two-page case would take the total to eleven. Avery decides to replace a weaker existing case before increasing the page count. If both are necessary, paid unlimited pages would address the capacity need; buying another published-project slot would solve a different problem. The title of a plan should not substitute for this arithmetic.
Avery also records what would trigger reconsideration: a custom domain, a genuinely required private site, a needed PDF export or another paid feature. A stronger visual design alone does not establish that one of those entitlements is necessary. The initial decision remains tied to the selected content and audience route.
Completed layout exercise: preserve the contribution at narrow widths
Avery's component case uses an invented disclosure panel example. The stipulated project implements an expandable help section with a labeled control, visible expanded state and keyboard interaction. No execution, accessibility audit or performance test was performed here. The exercise concerns how the explanation should remain readable when the portfolio layout changes.
The proposed desktop page places a contribution paragraph beside a large interaction image, with a short limitations note beneath them. Avery completes a mobile reading-order decision before imagining any editor operations:
| Element | Desktop intention | Completed mobile treatment |
|---|---|---|
| Case title and role | Above the two-column example | Keep first; say the project is personal work |
| Contribution paragraph | Beside the image | Place immediately below the title, before decorative media |
| Interaction evidence | Wide central image | Use a readable crop with a separate explanation of state |
| Limitations | Short note below the main example | Keep in the main flow, not hidden behind an animation |
| Next case link | Visually aligned at the side | Put after the evidence and limitations with a clear text label |
The finished contribution text is: “Personal component demo: I implemented the disclosure control and expanded-state presentation. This portfolio example explains the intended interaction; it does not establish completion of an independent accessibility audit.” The limitation is available before the reader follows another link.
Avery rejects a narrower mockup that puts a decorative video first and reduces the contribution paragraph to a small caption. That arrangement makes the reader wait for motion before learning what Avery did. The replacement sequence is title, contribution, image, limitations and next-case route. The decision is complete even though no page has been built or measured.
There is also a content-maintenance decision. The same contribution wording should remain synchronized across desktop and mobile; Avery does not need a duplicate just to reposition it. If a shorter mobile-only introduction is later necessary, it needs its own explicitly named widget and visibility check. Otherwise, a copied paragraph can become an outdated second account of the same work.
Avery’s final review brief covers portrait and landscape views, any tablet route, text size, overlap, fixed navigation and link reachability. These are proposed checks for a future site, not reported test passes. A mobile layout that looks attractive in an editor still needs the actual published route checked without relying on an owner session.

Views and add-ons need a current entitlement check
The project-views guide says paid plans have monthly limits and count repeat visits, the owner's visits and preview views. A visit covers the whole project rather than every page switch within the session. It lists unlimited project views for Free. A view counter is not a count of unique recruiters, applications or hiring decisions.
That matters when comparing an initially free portfolio with a paid upgrade. A development session or repeat review can contribute to usage. Do not take a published-project allowance as proof that viewing capacity is also unrestricted, and do not interpret an analytics increase as evidence an employer read a particular case study.
The general plan guide mentions adding extra views to any plan, but the focused Add-ons guide says add-ons are Advanced-only and require an upgrade from Free, Personal or Freelancer. These descriptions are not aligned. Confirm current eligibility and the actual price breakdown instead of assuming a small view purchase is available on a lower tier.
For Avery, no paid view purchase is part of the initial decision. If a later upgrade changes that, the review needs a new usage and cost check. This article does not establish the account's available capacity, an overage price or the behavior of a real usage counter.
Cancellation does not necessarily take a portfolio offline
The cancellation guide says ordinary cancellation stops renewal after the current paid period; it describes refund availability within 24 hours of purchase. After expiry, published projects remain online on the Free account. Editing and republishing can require unpublishing other projects, and the free ten-page limit affects future page additions.
The same guide says password-protected projects remain private, while custom-domain routes need attention: it instructs users to unmap those domains before expiry to avoid an offline message. Published projects can use the Readymag domain on Free. Cancellation, unpublishing, changing a domain and deleting content are therefore separate decisions. We did not perform any of them or verify a refund.
If you want a portfolio removed from public view, do not use cancellation alone as proof it is gone. Conversely, if a resume already links to a custom domain, do not assume visitors will automatically reach the retained Readymag version after a downgrade. Review the actual link you distributed and the intended ongoing destination before changing a subscription.
Avery's initial Free site has no paid cancellation step, but the future maintenance record preserves this distinction. An eventual custom-domain upgrade would require a separate continuity decision before expiry. The subscription's status is not enough evidence to declare either public removal or continued recruiter access.
PDF export and external hosting are different outputs
The plan guide lists PDF export among paid features, while the code-export guide restricts source export to Business/Advanced and Extra. A PDF can provide a readable document; it is not an interactive self-hosted website. The code workflow requires publishing, exporting and server configuration, rather than simply saving a local page.
The export guide also documents limitations for form destinations, page metadata and later changes. Edits require returning to the project, republishing and exporting again. We did not export a file, configure a server or validate an external deployment. Keep original text and media independently even if a paid export route may become available later.
Readymag fits a job seeker willing to design an intentional portfolio and maintain its alternate layouts. Use LandOffer job-search tools to find relevant openings, then organize evidence around what the reader needs to understand. Match paid features to a specific requirement, confirm the current offer and check the visitor route before including the link in an application.
Sources and Further Reading
- Understanding plans — published-project/page limits and paid features.
- Mobile and tablet layouts — rearrangement and automation limits.
- Widgets in different layouts — synchronized content and visibility.
- Project views — counted visits and limits.
- Add-ons — Advanced-only eligibility statement.
- Cancellation — retained projects and downgrade consequences.
- Code export — paid eligibility and configuration requirements.


