social.plus UIKit ships production‑ready building blocks covering social feeds, communities, chat, realtime engagement, moderation, and media workflows. This page orients you to the component families, helps you choose the right starting layer, and links to deeper implementation docs.
If you are still validating product fit, start with out‑of‑the‑box components first. Defer heavy styling or forking until core UX assumptions are proven.

When to Use Pre‑built Components

Use UIKit components when you need to: Consider building custom (or moving to Fork & Extend) when you:
  • Need radical UX divergence not achievable via theming/styling/dynamic config
  • Must embed experimental interaction paradigms (novel canvas, 3D, AR)
  • Have compliance constraints requiring full source review & diff control

Quick Navigation

Media & Ephemeral

Chat Components

For advanced dynamic layout adaptation, combine components with Dynamic UI to conditionally show/hide or rearrange modules without forking.

Customization Path (Decision Snapshot)

GoalStart HereEscalate ToWhen to Escalate
Brand colors & typographyCutomizationComponent StylingNeed granular token overrides beyond palette
Adjust spacing / hide elementsComponent StylingDynamic UIMultiple layouts per context (role, A/B test)
Conditional layouts & feature gatingDynamic UIFork & ExtendNeed structural changes not expressible in config
Experimental UX / deep logic changesFork & ExtendFull control & long‑term ownership required

Troubleshooting

Next Steps

Keep feedback flowing: note gaps or advanced scenarios and feed them back before committing to a fork—often a lighter abstraction exists.