The Viking StackKnowledge Base

Organize a project and its assets

Create a project with useful context, group related work, and add assets that another operator can understand.

3 min readbeginnerUpdated September 11, 2026

Projects gives a business a place to organize reusable content, code, and handoff material. Use a project when the work needs context and review before it is copied, shared, or placed into its final destination.

For Northgate ESD Packaging, a “Packaging buyer guide” project could hold a FAQ draft, an email version, and placement notes. Creating those assets does not automatically publish them to the storefront or send them to buyers.

Create a project with context

  1. Select the correct account.
  2. Open Projects.
  3. Open the new-project action.
  4. Enter Project Name.
  5. Review the suggested Slug.
  6. Fill in README / Context.
  7. Choose Create Project.

The form states which account will own the project. Read that line before saving, especially when you manage several businesses. Use a short, recognizable slug and a project name that describes the work rather than an unexplained internal abbreviation.

Useful context tells another operator what the project is for, where the material belongs, which facts are approved, and what still needs review. For Northgate, note that the FAQ will support packaging selection and that technical claims require the product owner's review.

Within a project, use New Subproject when a distinct set of assets needs its own context. Give the subproject a clear name, review its slug, and use Create Subproject.

A parent project might cover the buyer guide, with subprojects for website copy and follow-up email material. Keep the structure shallow enough that a reviewer can find the asset without searching several similarly named containers.

Projects are not automation workspaces. Use Automations for connections and runs; use Projects for assets and their context. A familiar name in both places does not make their records interchangeable.

Add an asset

  1. Open the intended project or subproject.
  2. Choose Add Asset.
  3. Select Kind.
  4. Enter a descriptive Name.
  5. Provide Content for inline material or the appropriate Storage Reference for a binary asset.
  6. Choose Add Asset.
  7. Read the success message and choose Done.

Supported kinds include HTML, Email, CSS, JS, Text, and Image. Choose according to the actual content: plain notes belong in Text; a reusable page fragment belongs in HTML. A storage reference identifies an existing binary asset; the field is not a promise that pasted text uploads a file.

Name a Northgate FAQ asset by purpose and review state, such as “Packaging sizing FAQ — draft.” Put approved source facts and placement instructions in the project context rather than relying on the title to carry every detail.

Find and inspect the result

Use Search assets to narrow by name, kind, or source. Expand the relevant asset row to inspect its preview or content. Copy is available for inline content, while management actions depend on permissions and asset type.

Before handing off, verify that the asset belongs to the intended project and that its contents match the selected kind. A correct file in the wrong client project is still an incorrect handoff.

If an asset appears missing, clear the search and check the parent or subproject. If creation fails, read the form error and check the name, slug, and required content. Do not create several copies while an earlier save is still pending.

Know what done looks like

A project is useful when another operator can locate the material, understand its purpose, and identify the next review or placement step. Publication and external use are separate decisions.