pub.chive.actor.profileConfig

How an author's profile page is arranged: which sections appear, in what order, and which collection is featured. Written by the account holder to their own repository.

Repository @lexicons.governance.chive.pub did:plc:egjghlwgts2hlcer2txilxeh not from the namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authorityactor.chive.pub
Indexed

Record

record · key literal:self

Properties

createdAt

requiredstring · datetime

When this configuration was first created.

featuredCollectionUri

string · at-uri

Collection node pinned to the top of the profile.

Broad kind of profile, used to pick sensible default sections. Open-ended: an unknown value is preserved and falls back to the default layout.

  • maxLength: 64
  • knownValues: researcher | group | institution | project

Ordered display sections. Order in this array is the display order.

  • maxLength: 32
itemsref
Reference

updatedAt

string · datetime

When this configuration was last changed.

#section

object

One section of the profile layout.

Properties

collectionUri

string · at-uri

Collection this section draws from, where the kind supports it.

kind

requiredstring

What the section shows. Open-ended so a section type can be added without invalidating existing records.

  • maxLength: 64
  • knownValues: eprints | collections | reviews | endorsements | fields | affiliations | collaborators

label

string

Heading shown for the section. Defaults to a label derived from `kind` when absent.

  • maxLength: 128

limit

integer

Maximum items to display in this section.

  • minimum: 1
  • maximum: 100

visible

boolean

Whether the section is rendered. A hidden section keeps its configuration.

  • default: true

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Get profile configuration for a user

  • An author's byline.pub profile, signed by and stored in the author's own repository. The repo's DID is the author identity; this record is the byline.pub-specific public profile that extends it, independent of any venue's own profile record. One record per repo (key 'self').