Job search
Typedream Review for a Job-Search Portfolio: Page Limits, CMS Cases, and Paid Publishing
Organize three cases into a readable portfolio, distinguish pages from CMS collections, and choose paid publishing only for a defined requirement.
Typedream is worth investigating for a portfolio built around a few clear cases and an update routine you can maintain. Its free plan publishes one page, which can be enough for three concise project summaries. A paid plan becomes relevant when you need separate case pages, the documented CMS workflow or a custom domain. Three case studies do not automatically require three CMS collections or the highest plan.
This review checked official public pages on October 22, 2026. We read pricing and documentation without creating an account, connecting a database, building or publishing a site, changing domain records or uploading private work. The examples are fictional planning records, not hosted portfolios or measured recruiter outcomes. LandOffer publishes this guide and offers recent technology roles; use the responsibilities in relevant postings to choose which work your portfolio should explain.

Start with three cases and a reading path
A portfolio should make it easy to identify the work, your contribution and the evidence available. For each case, prepare a short problem statement, your role, one important decision, an artifact you may share and any limitation on the result. A builder can arrange that material; it cannot establish ownership or create missing project evidence.
Put the project, your role and the available evidence where a reader can find them quickly. A compact page can introduce all three projects, with clearly separated sections and links to permitted supporting material. Separate case pages allow longer explanations and a direct URL for the project most relevant to an application. Neither structure is inherently stronger; choose the one that makes your evidence easiest to inspect.
For technical work, a useful artifact might be a public repository, an architecture explanation or a small demonstration using invented data. Label prototypes and personal exercises accurately. Avoid turning a local example into a deployed production system, or a team outcome into a claim that you personally implemented every component.
Your portfolio link is a supplement to the employer’s application requirements. Preserve a suitable resume attachment and any requested work sample. A polished website does not establish that an application portal accepts a link in place of a file.
What the current plans actually include
The pricing page displayed these individual-site options:
| Plan | Displayed monthly billing | Displayed rate on annual plan | Relevant portfolio boundary |
|---|---|---|---|
| Free | $0 | $0 | Publish one page, Typedream.app domain, Typedream badge and one seat |
| Launch | $20 per month | $15 per month | Unlimited pages, custom domain and one blog/CMS collection |
| Grow | $49 per month | $42 per month | Unlimited CMS collections and password protection, among other additions |
The paid plans are per site. Annual rates are presented as monthly equivalents, so compare the complete commitment with your expected use. Multiplying the listed rates by 12 gives $180 for Launch and $504 for Grow; those are arithmetic comparisons, not checkout totals including taxes, domain costs or future changes. We did not purchase either plan.
Both paid tiers advertise a free first year of a .xyz domain. That is narrower than every custom domain being free indefinitely. If you already own a domain, investigate connection requirements and its separate renewal. You do not need sales, email-marketing or large form allowances simply to present three projects.
The pricing FAQ describes automatic monthly or annual renewal and cancellation taking effect at the end of the billing period. The period you choose matters if the portfolio must remain available during an extended search. Keep an independent copy of the underlying text, images and links rather than assuming continued hosting without an active arrangement.
Understand a CMS collection versus a case item
Typedream’s current CMS index links guides for collection setup, editing items and changing collection and item-page layouts. The model is useful for a recurring set of cases: a collection organizes items, while an item page presents an individual case using a shared structure.
There is a documentation-age limitation. The linked setup guide, dated May 31, 2022, describes a Notion connection and refers to a Pro plan. Current pricing instead uses Free, Launch and Grow. Use the current pricing page for plan entitlement. The 2022 Pro reference and Notion steps describe that guide’s context, not a verified walkthrough of today’s editor.
The guide describes mapping database fields into collection and item templates, then previewing and publishing. For planning, the useful distinction is between the index, the repeated case structure and each case’s content. We did not connect Notion, inspect database permissions or test synchronization. Confirm the current supported data route and item allowance before committing your portfolio to it.
Three projects with the same fields can be planned as three items in one Cases collection. That is different from three independent collections with unrelated structures. Launch’s one-collection entry may therefore be the relevant tier to investigate; the public pricing description does not establish every item limit, media allowance or integration constraint.
Worked example: fit three projects into one portfolio structure
Ivo is a fictional developer planning a portfolio around three personal exercises. The project descriptions below are stipulated teaching examples, not work performed by this review or links to real repositories. He completes this structure record before choosing an editor or paying for hosting.
| Case | Evidence he would explain | Truthful scope in this fictional record | Placement decision |
|---|---|---|---|
| Inventory API exercise | Request validation, error handling and a short repository walkthrough | A personal example, with no production usage claim | One summary section; a separate case page if the explanation grows |
| Pipeline-observation exercise | A diagram and sample log interpretation using invented data | A demonstration, without a measured incident-reduction result | A second section using the same role/decision/evidence fields |
| Scheduling tradeoff write-up | A comparison of two approaches and the reason for a small design choice | A design explanation, not a tested performance benchmark | A third section with its own limitation statement |
His completed page brief reads: “Introduce my focus, then show three clearly separated cases. Each case explains what I did, one decision, a permitted artifact and what the example does not establish. Keep the resume and contact route easy to find. Do not add a shop, subscriber list or lead-capture funnel to solve a portfolio problem.”
His free-plan option is one public page with three concise sections. His paid option is a main page plus three longer case pages; if their repeated structure needs CMS, plan one Cases collection containing three items. The paid outline could have a homepage, an about/resume page and three case pages, while still planning only one Cases collection; confirm the current item allowance before adopting it.
His decision is to draft the one-page version first and investigate Launch only if separate URLs, repeated-content management or his own domain become necessary. Grow is not justified merely by the number three. This is an information-architecture decision, not a claim that either version has been built, published or tested with recruiters.

Plan updates before treating CMS as a convenience
The item-editing guide, also dated May 31, 2022, describes editing a collection item, previewing and publishing. It does not establish that every database change automatically appears in the live site without review. Keep the editing source, preview and public result separate in your maintenance plan.
A repeated layout can keep role, evidence and limitation fields consistent across cases. Review shared changes carefully because one template edit can affect several pages. Before changing a field or template, identify which case pages depend on it. Check that titles, role statements, images, links and limitation notes still appear correctly in representative items after the change.
Use the actual target URL in your application record. Recheck links when you change a slug or reorganize a case. A custom domain can make the address easier to maintain, but it does not fix a broken case link or guarantee uninterrupted hosting. Typedream’s domain documentation describes the connection separately from page content; no domain configuration was performed here.
We did not verify a portable site-code export or migration workflow. Keep original case text, image files, captions and a simple list of page addresses outside the builder. That is a practical maintenance record, not a claim that Typedream exports a complete independently hostable site.
Worked example: prepare a case-update record
Selene is a fictional portfolio owner considering the same three-item Cases structure. She wants to add a small follow-up to one case while keeping the other two unchanged. This is a completed offline update plan, not an editor session, synchronized database or successful publication.
| Change item | Completed scope choice | Review before considering the update done |
|---|---|---|
| Updated case content | Add a paragraph explaining a revised validation decision in the Inventory API exercise | Preserve the original problem and identify exactly which decision changed |
| Evidence label | Keep “personal exercise” and “no production usage claim” | Do not promote the revision into a customer deployment or measured result |
| Shared fields | Use title, my role, decision, artifact, limitations and review date for every item | Confirm all three cases retain the required fields after any schema change |
| Template | Leave the common layout unchanged for this content-only revision | If a layout change becomes necessary, review more than the edited case |
| Application link | Keep the intended case address in her own link record | Inspect the public destination after an authorized future publication |
Her prepared update paragraph reads: “This follow-up explains why I changed the example’s validation boundary. It adds reasoning to the original exercise. It does not introduce a production deployment, customer adoption or measured performance result.” The wording is fictional case copy, not a report of an experiment conducted for this article.
Her completed maintenance note is: “Update the individual item’s explanation, retain the scope labels and inspect the preview. If a shared field or template changes, check all three items before publication. After any authorized publication, verify the exact link used in applications. Keep the previous text and original artifact separately.”
Her decision is to evaluate whether one collection provides that repeatable structure without adding unnecessary collections. The plan leaves the actual current editor, data integration and publication behavior untested. It defines the evidence needed to judge the update rather than assuming a sync completed.
Keep permission and access control separate
Treat published portfolio material as material a reader may copy or forward. Use work you have permission to show, and replace sensitive examples with clearly labeled synthetic material where appropriate. A password does not grant permission to disclose employer or client information.
Grow’s current pricing lists password protection. The Locks documentation describes page protection using a password or token. We did not test either, and token gating is unnecessary for a straightforward recruiter reading path. Before relying on protection, inspect exactly which pages and media are covered and how a recipient will obtain access.
The unpublishing guide describes disabling Share to web for selected pages and avoiding an option that makes all pages public. Read the actual current controls carefully. Removing a navigation link is not the same action as withdrawing a page, and withdrawing material cannot retrieve copies already made by readers.
For an employer-restricted case, the useful first question is what you may share at all. Confirm the permitted material and sharing route before choosing a hosting tier for an employer-restricted case.
Choose the smallest workable publishing arrangement
Free is worth investigating for one compact public page. Launch becomes relevant for separate pages, one repeated CMS structure or a custom domain. Grow needs a specific extra requirement, such as multiple distinct collections or verified password protection. Marketing capacity is not automatically portfolio value.
Save a three-case outline, a permission/evidence note and a maintenance record before buying. For each application, find relevant roles on LandOffer and select the case that best explains the requested work. Record the selected case URL, underlying artifact and last review date with the application. Choose a publishing arrangement that supports that reading path and maintenance routine.
Sources and Further Reading
- Typedream pricing — current page, collection, domain, protection and billing entries.
- CMS documentation index — routes to setup and item-layout guides.
- CMS setup guide and item editing — dated May 31, 2022; current editor not tested.
- Domain documentation — domain connection is separate from case content.
- Page locks and unpublishing — documented protection and withdrawal routes, not tested security guarantees. Sources checked October 22, 2026.


