Install the Markshare CLI

Before you start

Use this guide when your source content is already markdown and you want a terminal-first path toward a shareable webpage. Markshare is a fit for reports, launch notes, customer research summaries, technical notes, and other documents where opening a full CMS would be heavier than the job requires.

You need:

• a terminal
• a shell that can run a standard install script command
• network access to markshare.to
• permission to run remote install scripts on the machine
• markdown content you want to publish or test after installation

This page only documents the install command listed in ReScience Lab product facts. It does not invent additional flags, account flows, hosting limits, privacy guarantees, or publish commands.

Steps

1. Open a terminal on the machine where you want to use Markshare.

2. If your security policy requires review, inspect the remote script before running it. Remote shell scripts should be treated like any other executable dependency.

3. Run the install command:

   curl -sSL markshare.to/install.sh | bash

4. Open a new terminal session if the installer updates your shell path.

5. Use the installed Markshare CLI, built-in help, or current Markshare product documentation for the latest publishing command and available options.

Verify it worked

A successful installation should make the Markshare command available in your shell. If the command is not found, restart the terminal, check your PATH, and review any messages printed by the installer.

Before publishing important content, test with a small markdown file. Confirm that headings, links, lists, code blocks, and emphasis render the way you expect.

When to use Markshare instead of a site page

Use Markshare when the artifact should be quick to publish and easy to share as its own page. Examples include research summaries, draft notes, internal updates, launch memos, lightweight docs, and AI-generated reports that need a readable link.

Use a pages-as-code workflow instead when the page should become part of your main website. Durable SEO pages usually need canonical URLs, schema, navigation, internal links, sitemap inclusion, and ongoing content QA. Markshare is the lighter path for standalone markdown publishing; Pagewell is the stronger path for repo-native site pages. If you are unsure, start by asking whether the document needs to rank, convert, and live in navigation. If yes, use the main site. If no, publish the standalone artifact.

Common issues

• If the install command fails, confirm the terminal has network access.
• If your shell blocks remote scripts, review the script source before running it.
• If the CLI is not available after installation, restart the terminal or check your shell PATH.
• If markdown output looks wrong, preview the file first with the markdown preview tool.
• If the document should become a durable website page with metadata, schema, and internal links, use a pages-as-code workflow instead of a standalone publish flow.

Related pages

• Markshare product page
• Markdown publishing definition
• Publish markdown from terminal
• Free markdown preview tool

Sources

• Markshare
• Markdown Guide: Basic syntax
• Last checked: 2026-05-09