100%

Drafting and publishing a blog post (in docpad) using [frontman](https://github.com/Hypercubed/frontman)

✓ Published0🌍 Public

Last edited Sep 21, 2013

Created on Sep 20, 2013

This example demonstrates how to draft and publish a blog post using the frontman command-line tool within a DocPad project. It shows the workflow of creating a new post from a draft template and then publishing it to a dated archive directory. The code uses frontman’s `new` and publish commands, with CSON configuration files (`draft_post.cson` and `publish_post.cson`) that specify metadata like layout, status, and output directories. The publish template dynamically computes the current date to set the post’s `date` field and target folder, while the draft template defaults to a `draft` status and `src/drafts/` output.

AI-generated description

Drafting and publishing a blog post (in docpad) using frontman

Create a new blog post:

$  frontman new.html.md -t src/templates/draft_post.cson -o .
info:    Writing  [...]\src\drafts\new.html.md
It's saved!

Publishing blog post:

$ frontman  src/drafts/new.html.md -t src/templates/publish_post.cson -o .
info:    Writing  [...]\src\documents\archives\2013\09\20\new.html.md
It's saved!

Similar vizzes

Loading thumbnail…

DocPad is great.... but so is Grunt. Use grunt-contrib-connect and grunt-contrib-watch instead of docpad's server and watcher.

This example shows a Grunt-based build workflow that replaces DocPad’s built-in server and watcher with grunt-contrib-connect and grunt-contrib-watch, enabling live-reload during static site generation. The configuration defines a `docpad` task that watches `src/**/*.*` files and triggers a shell command to regenerate output into the `out` directory, while a separate watch task monitors `out/**/*` for live-reload. The `connect` server serves the generated `out` folder on port 9778 with livereload enabled, and tasks like `generate`, `server`, and `run` orchestrate clean builds and continuous development. The code relies on Grunt’s task registry, `grunt-shell`, `grunt-contrib-watch`, `grunt-contrib-connect`, and `grunt-contrib-clean` to handle file watching, HTTP serving, and cleanup.

HHypercubed

57% match

Loading thumbnail…

DocPad: rsync Deploy Script

This example shows a shell script that automates deploying a static website via rsync to a remote server. It defines environment variables for the source directory, destination directory, server, and account, then runs `docpad generate` to build the site before syncing files. The script supports a dry-run mode with the `-n` flag and excludes specified patterns like `.git` and `.svn` using a `.deployignore` file. It relies on the `rsync` command-line tool and the `docpad` static site generator, with the deployment target specified as a user@host:path.

HHypercubed

55% match

Loading thumbnail…

First blog post

This example displays the complete syntax for Markdown formatting, covering headers, emphasis, lists, links, images, blockquotes, code blocks, tables, and task lists. It presents a static text document as a visual reference guide, with the content sourced from an AI-generated assistant reply. The rendering uses standard HTML text formatting to display the Markdown examples and their corresponding visual output. The visual is a plain text layout, with no interactive elements or data-driven graphics.

NNita

52% match

Loading thumbnail…

Pandoc conversation example

This example shows the execution history of a Pandoc command that converts a Markdown syllabus into a standalone DOCX file, visualizing the command’s arguments and file flow as an annotated graph. It uses D3’s `forceSimulation` to lay out nodes representing the input, output, and converter, with `transition.attrTween` animating the edge paths between them. The underlying data comes directly from the gist’s shell command, parsed into JSON, and the view highlights the order of operations—`pandoc.txt`, `syllabus.md`, and the `--from`/`--to` flags—without implying any behavior beyond what the command lists.

CCliffordAnderson

51% match

Loading thumbnail…

This is an example of how to append Pods Templates to content in a custom post type. For an automated version of this see: https://github.com/pods-framework/pods-frontier-auto-template

This example shows how to append Pods Templates to the content of custom post types in WordPress. The plugin registers a `the_content` filter that checks the post type and, for types like `tool`, `campaign`, and `activity-report`, uses the `pods()` API to fetch the current post and render its designated template before the original content. The code relies on the Pods framework to load templates for each post type, returning the template output prepended to the standard content. It modifies display output without altering stored data.

DDerekCaelin

51% 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

49% match

Loading thumbnail…

New Doc

This example presents a minimal, empty HTML page titled “New Doc,” with no visible data or visualization content. The code consists solely of a basic document structure, embedding a YouTube video iframe within the README for reference. Using the standard HTML5 doctype, head, and body elements, the page loads without any JavaScript libraries, datasets, or rendering APIs—offering a blank canvas that demonstrates the raw structure of an HTML document rather than a functional chart or graphic.

Ssamuelsimkai

48% match

Loading thumbnail…

Pandoc to TEI

This example shows a command-line workflow for converting Word documents into TEI Simple XML using Pandoc, with instructions tailored for macOS Terminal. The visualization relies on the Pandoc API to transform `filename.docx` into `filename.xml` with the `-t tei` flag and `-s` for standalone output. It demonstrates the Homebrew package manager’s role in installing Pandoc via `brew install pandoc`. The code highlights the exact Terminal commands—`curl` for Homebrew installation and `pandoc` for conversion—without abstracting the process, making the data source (the Word file) and the output format (TEI) explicit.

CCliffordAnderson

48% match