Cherry.Portfolio (cherry v0.6.1)

The developer story as typed data: the profile plus every portfolio entry, materialised from a finished build token.

This is the seam the views stand on — timeline, story pages, and the CV all consume %Portfolio{}, never raw documents, so the shape of an entry is a named struct with real fields, not a frontmatter map.

Summary

Types

t()

Functions

entries(portfolio)

Every entry across collections, for taxonomy and freshness scans.

entry_document?(document)

True when the document belongs to a portfolio collection.

filter_by_tag(portfolio, tag)

The portfolio narrowed to entries carrying one tag.

from_build(build)

Builds the typed portfolio from a build token; entries come out newest-first within their collection.

present?(portfolio)

True when the site carries any portfolio content at all.

tags(portfolio)

Every tag used by any portfolio entry, sorted.

Types

t()

@type t() :: %Cherry.Portfolio{
  education: [Cherry.Portfolio.Education.t()],
  oss: [Cherry.Portfolio.OpenSource.t()],
  positions: [Cherry.Portfolio.Position.t()],
  profile: Cherry.Portfolio.Profile.t() | nil,
  projects: [Cherry.Portfolio.Project.t()],
  talks: [Cherry.Portfolio.Talk.t()]
}

Functions

entries(portfolio)

@spec entries(t()) :: [struct()]

Every entry across collections, for taxonomy and freshness scans.

entry_document?(document)

@spec entry_document?(Cherry.Content.Document.t()) :: boolean()

True when the document belongs to a portfolio collection.

filter_by_tag(portfolio, tag)

@spec filter_by_tag(t(), String.t()) :: t()

The portfolio narrowed to entries carrying one tag.

from_build(build)

@spec from_build(Cherry.Build.t()) :: t()

Builds the typed portfolio from a build token; entries come out newest-first within their collection.

present?(portfolio)

@spec present?(t()) :: boolean()

True when the site carries any portfolio content at all.

tags(portfolio)

@spec tags(t()) :: [String.t()]

Every tag used by any portfolio entry, sorted.