logicalparadox / codex Goto Github PK

Embedded HTML tokens get tagged with the language 'html' by marked, but highlight.js uses 'xml' for highlighting HTML. One-line fix coming...

Dave

If you re-export the configuration options for highlight.js then clients of codex can customize their syntax highlighting. Pull request coming...

Dave

The assets directory generates a 'public' directory. It would be great if that could be configured with a custom name, or even configured just to go to the root directory.

Dave

Hi there,
Thanks for the great project.
Your Link to your github is wrong:
http://alogicalparadox.com/codex/

Other than that:
works like a charm!

When emacs creates auto-save files like .#index.md, the watcher picks them up immediately and "build" tries to convert them. It would be useful to allow an ignore option to specify globs or regexps for filename patterns to ignore.

Thanks,
Dave

The fact that codex lets me have nested directories is the killer feature I need for the TC39 wiki, which many other static site generators (like Jekyll) don't seem to support. But it would be great if nested directories could default to their parents' layouts, instead of having to create new layout files for every child.

Dave

Use connect to serve static. Add cli option. Uses same defaults/options as build.

It would be good to support the ability to deploy assets to the root of the output directory. For example, favicon.ico or gh-pages CNAME files.

Dave

...

Submit to codexjs.com

It'd be so sweet to automatically infer smart quotes and turn them into curly quotes in the generated HTML.

Dave

If a code snippet chooses a language highlight.js doesn't know about, highlight.js just explodes. Codex should test for unknown languages and default to text.

Patch coming in a sec.

Dave

When an .md file has improperly indented headers it seems to crash the JS code and report an internal error. For example, running codex on a project with a file containing the following:

---
title: Home

---

Hello, world.

produces the error:

/Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/node_modules/yaml/lib/yaml.js:179
  throw new Error(msg + ', ' + context(this.peek()[1].input))
        ^
Error: document not properly dedented, near "\n---"
    at Parser.expect (/Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/node_modules/yaml/lib/yaml.js:179:9)
    at Parser.parseDoc (/Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/node_modules/yaml/lib/yaml.js:266:8)
    at Parser.parse (/Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/node_modules/yaml/lib/yaml.js:232:19)
    at Object.eval (/Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/node_modules/yaml/lib/yaml.js:384:46)
    at /Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/lib/codex/plugins/pages.js:33:26
    at Array.forEach (native)
    at /Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/lib/codex/plugins/pages.js:16:13
    at /Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/lib/codex/plugins/pages.js:79:29
    at /Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/lib/codex/plugins/pages.js:79:29
    at Object.oncomplete (/Users/dherman/Sources/tc39-codex-wiki/node_modules/codex/lib/codex/plugins/pages.js:85:27)

Dave

I've been poking around at the default templates and using introspection like #{Object.keys(file)} to find out what built-in template variables are available for the layout files, but it'd be great to get a list of these in the README. So far I see:

file.{title,template,render-file,inPath,inFile,outPath,href,prepared,project}
files.{root,pages,posts}

Any others? I'm happy to file a pull request with a patch to the README.

Thanks,
Dave

A user should be able to sort the output of data nodes by including yaml attributes.

Supported attributes

• date
• weight