go-schedule

go-schedule brand system

The official go-schedule identity is brand 2.0.0, published with BrandBuilder 2.4.0 on brand.shruggie.tech. Its primary mark is the compact terminal prompt and cursor. The former framed terminal and cron-field artwork is retired. Download the brand guide or the complete pinned kit for full usage guidance.

The current go-schedule mark and wordmark

Choose an asset

ContextUseDownload
Product mark at 24 px or largerFull transparent prompt and cursor markSVG · PNG
Browser and small icons below 32 pxSize-specific favicon or reduced markSVG · PNG
Dark surface or wide headerColor horizontal lockupSVG · PNG
Light surfaceLight-surface horizontal lockupSVG · Black SVG
Single-color productionWhite or black markWhite SVG · Black SVG
Square compositionColor stacked lockupSVG · PNG
Social and link previewsApproved 1280 px imagePNG · SVG

Keep 54 source units of clear space around a lockup. Do not redraw, stretch, rotate, recolor, or retypeset the supplied artwork. The wordmark is outlined in the SVGs and needs no installed font. Use the official platform icons for Windows and macOS packages; the Linux hicolor tree contains size-matched official raster exports.

Color and type

The visual foundation uses Night #071014, Interval Mint #62D9B7, Anchor Blue #58A6FF, Hold Amber #F2B84B, and Stop Red #E05F5F. On light surfaces, use the deeper accessible accent values defined in the official guide and tokens. Pair status colors with text or symbols.

Space Grotesk serves display text, Geist serves body and interface text, and Geist Mono serves commands, schedules, and technical labels. The supplied SVG wordmark is outlined Space Grotesk Bold.

Voice and attribution

Write in short, precise sentences with explicit scheduling policy. Keep cron terminology accurate. When parent attribution is useful, place A ShruggieTech project outside the logo clear space as a subordinate endorsement.

Downloads and provenance

Repository copies are checked against the official archive. Contributors should follow the repository update procedure when adopting a new release.

Edit this page on GitHub

On this page