GitHub issues

100%

✓ Published0🌍 Public

Last edited Sep 12, 2024

Created on Sep 12, 2024

This example converts GitHub issue data into a formatted HTML document and then into a Word file. It shows each issue as a section with its title, labels, body text, and all associated comments, styled with CSS. The code uses the GitHub CLI to export issue JSON, the Showdown library to convert Markdown to HTML, and Pandoc to transform the HTML into a DOCX. The rendering approach is a static document layout rather than an interactive visualization.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 2f2e6351aa30422d52d9

A GitHub Gist documents notes from a front-end development workshop, presenting markdown-formatted text alongside links and embedded images. The page renders the raw markdown content, including headings, hyperlinks, and a Flickr-hosted sketch photo. No interactive visualization or charting library is used; the display relies on standard HTML and markdown rendering through GitHub’s interface. The data source is the gist’s own text file, which is displayed directly as a static document rather than processed through any data-visualization API.

Aalessioalex

66% match

Loading thumbnail…

Gist 9863493

This example assembles a multi-section Markdown document into a unified report and renders it in several output formats. It shows how a single source file can be converted to HTML, PDF, DOC, ODT, and standalone Markdown using the Pandoc document converter. The build script runs `assemble.sh` to concatenate numbered section files into `masters.txt`, then invokes Pandoc with options for section numbering, a table of contents, and custom CSS styling. The PDF output uses XeLaTeX with Georgia and Helvetica fonts, while the HTML version embeds a custom JavaScript template.

Aamundo

64% match

Loading thumbnail…

Gist 95588bd77669e425eaccc173d60db0ea

This example visualizes the concept of turning off GitHub issues, using a force-directed graph rendered with d3.forceSimulation. Nodes represent maintainers, contributors, and pull requests, with links showing the flow of feedback through pull requests instead of issues. The layout is computed dynamically as the simulation runs, with node positions and link paths updated each tick. The data comes from a static JSON array embedded in the code, and the visualization highlights the argument that pull requests, not issues, should be the primary interaction channel.

FFrozenfire92

63% match

Loading thumbnail…

Markdown Demo

This example showcases the rendering of Markdown content in VizHub, demonstrating a wide range of syntax including headings, emphasis, links, tables, code blocks, blockquotes, task lists, and embedded HTML. The README.md file serves as the Markdown source, while the visualization includes an index.html that displays a large "Hello HTML!" message styled with CSS. The example highlights how VizHub processes Markdown and HTML files, using standard Markdown parsing and HTML rendering to present the content in the gallery. It does not use any additional JavaScript libraries for data visualization.

CCurran Kelleher

62% match

Loading thumbnail…

Gist ff898d829474754ee41930e78894fa7e

This example demonstrates a Markdown editor’s multi-format documentation capabilities, showcasing syntax for LaTeX equations, highlighted Python code, flowcharts, sequence diagrams, Gantt charts, and tables. The document mixes inline math with a codecogs image URL for a formula, while leveraging fenced code blocks to invoke specific rendering engines like flow, seq, and gantt. It also includes a Todo list and a Bash command snippet, illustrating how structured text can be transformed into interactive diagrams and formatted output.

AAlsaxian

62% match

Loading thumbnail…

A better markdown cheatsheet.

This markdown cheatsheet visually compares two reference documents side by side, presenting syntax examples and their rendered results for headers, emphasis, lists, links, images, and code blocks. The example uses the GitHub Flavored Markdown parser with custom HTML elements like `<details>` and `<mark>`, and includes TeX mathematical formulae. It demonstrates how a plain-text data format can be organized as a reference visualization through the use of clear section headings, code fences, and live previews.

GGerHobbelt

60% match

Loading thumbnail…

HTML+CSS jotdown notes misc

This example shows a GitHub-style file listing row where not-yet-loaded text is indicated by grey skeleton screen placeholders. Skeleton loading blocks replace commit message and timestamp content using CSS `clip-path` insets and a background gradient with a looping `skeleton-loading` animation. The markup is structured with ARIA roles for grid rows and cells, and an inline SVG octicon folder icon renders the directory indicator. The code demonstrates a pure HTML+CSS technique for improving perceived performance without JavaScript.

GGerHobbelt

60% match

Loading thumbnail…

Latex to md

This example demonstrates the conversion of a LaTeX document into GitHub-flavored Markdown using the command-line tool `pandoc`, with the output being a structured text file containing statistical data and tables. The converted content describes a data visualization application for analyzing census data, including univariate and bivariate statistics, typologies, segregation indices, and trajectories. The document lists data sources from the US Bureau of Census and GeoLytics, and includes tables detailing variables such as ethno-racial composition, age, education, and income, along with tables of variable identifiers and descriptions. The conversion preserves the original document’s headings, tables, and emphasis formatting while adapting it to Markdown syntax.

RRCura

60% match