layer5io / layer5io/layer5

[Sistent] Add Terminal component to the sistent components page

Open
#7,982 0 comments 0 reactions 1 assignee View on GitHub

@Maanvi212006 is already working on this.

Since Aug 20, 2026.

framework/gatsby language/markdown project/sistent
Dominant language
JavaScript
Stars
1.1k
Forks
1.6k
Avg merge
2d 10h
Merged PRs (30d)
18

Description

Current Behavior

Layer5 and its projects use the Sistent library to enable component reuse across various projects.
The Terminal component is one of the specialized console components available in Sistent, but it is currently not represented in the centralized Sistent component documentation at https://layer5.io/projects/sistent/components.
Adding documentation for Terminal will provide a clear reference for its usage, guidelines, and examples, helping developers understand and reuse the component consistently across Layer5 projects.

Desired Behavior

Add proper documentation for the Terminal component, following the same structure used by other documented Sistent components.
The documentation should follow the new Sistent MDX documentation structure by creating the following files under:
src/collections/sistent/components/terminal/

  • index.mdx: Overview of the Terminal component for interactive CLI execution and live log streaming.
  • guidance.mdx: Output formatting, command history, copy-paste shortcuts, and terminal themes.
  • code.mdx: Code examples demonstrating interactive prompt execution and static/streaming log viewers using <ThemeWrapper> and <CodeBlock>.

The completed documentation should be available on the Sistent components page and provide a centralized reference for developers using Terminal.

Environment:
  • Host OS:
  • Browser:

Contributor Resources and Handbook

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

Join the Layer5 Community by submitting your community member form.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.