Skip to content
Open Memside

Create and publish Templates

Template creation has five practical stages:

  1. create the Template details;
  2. add and organize files;
  3. review the complete draft;
  4. run the automated publication review and publish;
  5. maintain the listing, content, versions, and visibility.

New Templates begin as private drafts. Public visibility starts only after a successful review and an explicit publish action.

A Library creator account requires a unique username. The username appears on public Template and creator pages. It must contain 5 to 30 characters and cannot be changed after it is set. The shared Memside account controls the display name and profile picture.

Prepare content that is safe to publish. Remove private information, account credentials, access tokens, confidential material, and content without clear permission for redistribution.

Add the name, description, category, tags, and license. These fields explain what the Template contains and help Library search and discovery.

Create a Template

Write content in the editor, create folders, upload several files, or upload a complete folder structure. Supported Word files are converted into editable content for review.

Manage Template files and folders

Inspect the draft, run the automated publication review, address any findings, and publish the approved version.

Review and publish a Template

Update metadata, publish a new file version, discard private changes, unpublish a listing, or republish eligible content.

Edit, version, and unpublish Templates

Open Settings > Usage & Metrics in Memside to view complete Template downloads, individual file downloads, and the most downloaded owned files.

Usage and metrics

A small weekly-planning Template could contain:

README.md
instructions.md
examples/
simple-week.md

The README explains the purpose, instructions.md defines the process, and the example demonstrates the expected format. Additional folders are useful only when they make the setup easier to understand.

Owned Templates can also be managed through supported MCP tools or the Library REST API. Connected workflows follow the same ownership, review, and publication requirements as the website.