Git Product home page Git Product logo

packdown's Introduction

Hey, I'm the founder of Metadash.

Previously I was at Better.com and Glean AI.

My interests include design, tech, and startups.

I call New York City home.

packdown's People

Contributors

imsky avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

vitaly-z

packdown's Issues

line parser?

this will make non-file code blocks easy to add and should reduce total LOC. the grammar would still be useful to keep around, but there doesn't seem to be a need for a full parser for Packdown

documentation

  • jsdoc, html output
  • CLI examples for every command
  • library examples for every command
  • how to build, how to test
  • mark lib/ (but not command) functions as private

rework file headings

it's not obvious how to write a structured post with attached files using the current grammar. the H2 is overloaded as the file name so it's difficult to work around. some alternatives:

  • file headings can be of arbitrary level but must be wrapped in </>: # <somedir/somefile.txt>
  • file headings must start with a slash: # /somedir/somefile.txt
  • the file list must be separated from doc info by a rule, i.e. ---

the first approach makes files unambiguous, but doesn't comply with CommonMark's autolink spec. it could comply if the link were using a file:// schema, though that wouldn't look great and would make manual Packdown creation unfriendly.

the second approach introduces a risk where a user who wants to describe a particular file in the document info ends up adding it as a file to the Packdown document itself. this is likely a low risk to begin with, and can be mitigated by escaping the leading slash.

the third approach separates the document and files cleanly (and the grammar is already written for this use case), but it does make mixing files and document sections difficult. if a long tutorial, for example, needs to describe a file and include it immediately, the author is forced to figure out a way to link the user to the "basement" of the document - in effect this problem has to be solved by the implementer.

web demo

demo should include:

  • execute js in code block
  • show a pastebin using html, css, js
  • download all files from a document

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.