Job search
Super Review for a Notion Portfolio: Publishing Controls, Custom Domains, and Content Ownership
Assess Super as a presentation and release layer for existing Notion work, separating public-source permissions and domain control from content ownership and independent preservation.
Super can suit a job seeker who already writes portfolio content in Notion and wants a more configurable public website around it. Its useful increments include themes, custom-domain connection and, on Pro, manual publishing. Keep the source’s public-access rules, content ownership and independent backups separate from those presentation features.
This LandOffer.ai review uses official public documentation inspected October 22, 2026. We did not connect a workspace, publish a portfolio, change permissions or DNS, install an extension, buy a plan or test an export. The two worked records are original fiction. You can browse recent roles on LandOffer.ai, then choose the work samples that explain your contribution before paying for a publishing layer.

Identify the increment over your existing Notion pages
Super’s pricing page distinguishes managing content in Notion from managing the website in Super. That is the right starting point for an existing portfolio: preserve the writing workflow you like, then decide which public presentation or release controls are missing.
Do not assume a separate builder is necessary merely to obtain a public link. Notion’s own publishing help already describes unlimited published pages, a notion.site domain and paid customization or a custom-domain add-on. Compare the exact capability you need, not an outdated claim that Notion cannot publish a portfolio or connect a domain.
A small, clear Notion portfolio may already do the job if readers can find the project, understand your role and access the demonstration. Super becomes more relevant when you want its appearance, navigation or publishing controls while continuing to edit the source in Notion. The controls change how you present and release existing evidence. They do not establish permission to disclose an employer’s work or predict a hiring outcome.
Read the site plan and billing period separately
The inspected monthly comparison displayed Free at $0, Personal at $16 and Pro at $28 per month per site. The annual page displayed Personal at a $12 monthly equivalent billed yearly and Pro at $22 billed yearly. Multiplying the displayed equivalents by twelve gives $144 for Personal and $264 for Pro, paid on the annual billing basis. We did not verify checkout taxes, discounts or an individual renewal quote.
| Site plan | Relevant public inclusions | Portfolio consequence |
|---|---|---|
| Free | super.site address, themes and a Super badge | Evaluate public presentation without assuming a custom domain |
| Personal | Custom-domain connection, password protection, custom code/fonts and badge removal | Useful when those presentation controls are the missing work |
| Pro | Personal features plus manual publishing, redirects/hide controls and additional tools | Consider when release timing or route maintenance justifies the added scope |
The pricing FAQ allows one active free site and says a free site can have as many pages as needed. Paid plans apply to a single site. A portfolio and a separate side-project site do not automatically share one paid subscription.
Analytics and Teams have their own pricing on that page. They are not automatically necessary for a solo portfolio, and the site fee does not by itself establish a domain registration or renewal cost. Check the actual total, billing term and renewal arrangement before paying. The listed monthly Pro increment over Personal is $12, buying additional scope rather than guaranteeing better recruiter attention.
Public-source permissions come before Super passwords
Super’s password-protection feature page says the Notion source page still needs to be public for synchronization. A password on the Super presentation is therefore not a reason to put private source material into that public tree. Treat the original Notion URL as a separate access path that must be appropriate for public exposure.
Notion’s publishing guide warns that subpages are published by default, although their permissions can be restricted. It also explains that visitors can open database pages and switch database views. A tidy portfolio view or a hidden navigation item is not sufficient evidence that underlying material is inaccessible.
The same Notion guide notes that public-page metadata can include contributing users’ names, photos and email addresses. Review collaborators and source material, not only the visible prose. Keep confidential work, private feedback and material you lack permission to disclose outside the public portfolio source rather than relying on styling or an obscure link.
Super documents password inheritance to child pages and says its dashboard preview ignores passwords. This review did not test enforcement. A later visitor-access check should use the actual published route and source permissions; a dashboard preview is not an independent demonstration that a recruiter encounters the intended boundary.
Worked release decision: Ari separates five source items
Ari is a fictional product engineer with an existing Notion collection. The example contains no actual employer documents or private account data. Ari wants a public personal-demo write-up, a custom domain and a deliberate review before changes reach the Super site.
The completed paper inventory is:
| Source item | Fictional content state | Completed release disposition |
|---|---|---|
| Portfolio home | Original introduction and links, reviewed | Include in the proposed public portfolio tree |
| Personal queue demo | Original toy project; contribution and limits explained | Include the reviewed case study |
| Unfinished write-up | Draft reasoning still being checked | Keep outside the proposed public tree |
| Team incident notes | Work-related source material not cleared for disclosure | Exclude; do not treat a Super password as clearance |
| Old resume | Obsolete role description | Exclude; use only an accurate reviewed version later |
Ari’s finished source-tree brief is “Portfolio home → Personal queue demo.” It names the entire proposed public scope. The other three items stay outside it. This is an offline classification of invented material, not a permission change or a decision about real employment confidentiality.
Her complete release memo reads:
Keep the public source limited to my reviewed home page and original toy-project case study. Do not include the unfinished write-up, team notes or old resume. A password or hidden Super link does not turn those items into suitable public sources. I want a custom domain and a review gate for the Super presentation; confirm the Pro requirements before making any account, sharing or domain change.
The manual-publishing documentation specifies both a Pro site and a connected custom domain. Ari’s final plan decision is therefore “Pro is the relevant shortlist for this release-control requirement, conditional on that domain setup; Free and Personal do not satisfy the documented manual-publishing scope.” No subscription or domain is purchased.
Ari now has a two-page public scope and a plan requirement tied to review timing. Neither depends on treating Pro as private storage for her excluded drafts. Notion’s published source still has its own behavior and permissions. Ari first removes unsuitable material from the proposed public scope, then evaluates the website’s release gate.
Plan maintenance across both systems
Super’s current Pages guide describes a Sync setup with the Notion Sync Extension. It says newly discovered pages can be added and published-page updates synchronized; it also says deleted or moved Notion pages are not automatically removed by Sync. We read the public instructions without installing the extension or granting access.
After moving or retiring a case study, compare the Notion source tree, Super page list and exact public URL against the intended inventory. Removing a page in Super does not delete the Notion source, and the guide says an existing source may be discovered again. Conversely, changing the source alone should not be treated as proof that an old Super route has disappeared.
URLs need separate attention. The guide says changing a Notion title does not automatically change its Super URL, while moving a Super page under another parent changes its path. A resume, application form or recruiter email may still contain the previous link. Check the actual destination and any planned redirect before replacing widely shared paths.
Manual publishing adds another state to track. The current documentation describes rebuilding a dashboard preview when relevant pages are visited or refreshed, and publishing either a specific page or the full site. Keep “edited in Notion,” “visible in preview” and “released on the public route” distinct. None of those states was exercised in this review.
Ownership, domain control and backup answer different questions
Some Super domain marketing uses ownership language, but Notion’s privacy-practices help expressly states that customers own their Customer Data, including submitted content. A custom domain changes the address and branding arrangement; it does not create ownership of writing you previously lacked. Nor does it give you rights to someone else’s confidential work or images.
The domain guide describes connecting the domain through the provider and Super. Maintain a record of who controls the registration, renewal and account access, separate from who edits the Notion content. An address you control can be useful for a future hosting change, but the complete site and paths do not migrate themselves.
Notion’s export documentation describes PDF, HTML and Markdown/CSV options with format and permission limits. It explicitly warns that reuploading an exported workspace does not instantly recreate it. Its HTML and data exports are not proof that Super themes, custom code, domain configuration and redirects are preserved.
Owning content, having a live cached website and retaining an independent usable copy are three different things. A preservation record should identify actual source files, assets and configuration, then distinguish what has been retained from what still needs a verified export or reconstruction. This review did not perform a restore or migration.

Worked preservation decision: Ben finds the missing handoff
Ben is a second fictional portfolio owner. In this exercise’s supplied facts, he has local originals for a case study and its two diagrams, plus a text list of his public paths. His displayed portfolio also uses Super styling and a project database. He has not exported that database or saved the styling configuration.
His completed preservation inventory records the difference:
| Component | Evidence available in the fictional case | Completed handoff finding |
|---|---|---|
| Case-study narrative | Local original text | Retain as an independent writing source |
| Two diagrams | Original local image files | Retain originals rather than only embedded URLs |
| Project database | Only the live Notion database | An independent data copy has not been established |
| Super appearance | Theme and custom styling only in the service | No portable design handoff established |
| Public paths | Local text list of three paths | Keep as a route inventory, not a working redirect setup |
| Domain and renewal | Account responsibility not recorded | Document control before planning a hosting change |
His full handoff memo says:
I can reconstruct the case-study text and diagrams from supplied local originals. I cannot yet claim a portable copy of the project database, Super design or domain setup. Keep those gaps explicit. Use the three-path list to plan later verification, and do not describe the live Super site as an independent backup. Do not delete source content or cancel hosting on the assumption that a complete replacement already exists.
Ben’s final decision is “not ready to call this a complete migration package.” The concrete usable output is a limited text-and-diagram handoff plus identified gaps. It avoids the equally misleading conclusions that nothing is portable or that everything shown online is already safely archived.
Super remains a plausible choice when Notion is your preferred source and its added presentation or release controls solve a real need. Keep a simpler existing portfolio when it already communicates the work clearly. Browse recent roles on LandOffer.ai, select one original case study, record what may be public and what you can preserve independently, then choose only the publishing controls you need.
Sources and Further Reading
- Super monthly pricing and annual pricing — plans, per-site billing and expanded free-site FAQ, inspected October 22, 2026.
- Manual publishing — Pro plus connected-domain requirement, preview and release stages.
- Password protection and Pages guide — public Notion source, page tree, synchronization and URL maintenance.
- Notion publishing — native Sites, subpages, database access and metadata boundaries.
- Notion privacy practices — Customer Data ownership statement.
- Notion export — available formats, permissions and reconstruction limits.
- Super domain guide — address configuration; marketing ownership language distinguished from content rights.


