🌊
Urchin Web3 CMS
  • 🌊What is Urchin?
  • 🛠️How it works
  • 🏎️Getting started
  • 🧱API Reference
    • Core
      • urchin()
      • .preflight()
      • .process()
    • Template
      • .template.create()
      • .template.update()
      • .template.get()
      • .template.getAll()
    • Taxonomy
      • .taxonomy.create()
      • .taxonomy.update()
      • .taxonomy.get()
      • .taxonomy.getAll()
    • Asset
      • .asset.create()
      • .asset.update()
      • .asset.get()
      • .asset.getAll()
    • Entry
      • .entry.create()
      • .entry.update()
      • .entry.get()
      • .entry.getAll()
  • 🤔FAQs
Powered by GitBook
On this page

How it works

Unlike cloud-based CMS systems that use databases and teams, Urchin manages data by verifying a single owner via a Solana compatible wallet. That owner can design their CMS system and expand it as necessary and transactions will encur fees from the owners wallet.

In configuring your CMS, Urchin offers a basic set of composable data models to organize your system:

  • templates - blueprints to store you structured data (e.g. what data your cooking blog posts should each include).

  • entries - the data that populates a template (e.g. title: Chicken Noodle Soup, ingredients: ...).

  • taxonomies - tags or categories to help organize all your entries (e.g. soup, winter).

  • assets - file storage that can be referenced within entries (e.g. picture of chicken soup on a table).

In useage, Urchin is first initialized and bound to an owners wallet:

const cms = urchin({payer, cluster});

Next, call methods to create and update what should be included in a transaction payload:

cms.template.create(...);

Finally, execute the transaction:

cms.process();
PreviousWhat is Urchin?NextGetting started

Last updated 1 year ago

🛠️