_config.yml can have

defaults:
  -
    values:
      layout: "default"

This way, there's no need to specify in every html

---
layout: default
---

This works in jekyll, but not darko.

att

and i want to create new blog site by your darko, can you help me Mr chen ?

I am attempting to serve a site locally using darko for the first time. I've installed darko using npm, and the command darko --help returns the correct information. However, any of the other commands such as serve or build return darko-serve(1) does not exist, try --help.

I attempted this in both git bash and from windows command line with same results. Any help is appreciated!

OS: Windows 7

Darko uses highlight.js for syntax highlighting currently. The generated result is not compatible with the result of pygments though. Therefore those styles written for pygments won't be usable if some one is switching from Jekyll to Darko.

There are pygments compatible Node modules available, such as peacock. But it only highlights syntax of JavaScript.

Any thoughts?

When resolving url path, query strings shall be omitted.

Reported by @nickli

There shall be page.previous & page.next variables, which point to the corresponding post in site.posts.

Darko returns something like [object Object] currently. This can't be right.

References:

• http://jekyllrb.com/docs/variables/

https://jekyllrb.com/news/2018/01/02/jekyll-3-7-0-released/

LiveReload is available as an option during development: with jekyll serve --livereload no more manual page refresh.

Reported by @nickli

The static method Liquid.Templet.registerTag might be removed...

Node.js has limits on opening file descriptors, see nodejs/node-v0.x-archive#5401

I've got two options, 1) use graceful-fs as a drop in replacement of built-in fs module; 2) access files in batch, keep the total opened file descriptors below the red line.

Guess I'll give the second option a try.

I receive the following error when using darko-serve -w in Cygwin in Windows 7

path.js:204
        throw new TypeError('Arguments to path.join must be strings');
              ^
TypeError: Arguments to path.join must be strings
    at f (path.js:204:15)
    at Object.filter (native)
    at Object.exports.join (path.js:209:40)
    at FSWatcher.<anonymous> (D:\Workspaces\node_modules\darko\bin\darko-serve:191:22)
    at FSWatcher.emit (events.js:98:17)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1044:12)

The issue seems to be that the filename argument for watch is not supported on every platform.
See: http://nodejs.org/docs/latest/api/fs.html#fs_filename_argument

It would be great if darko could provide support for custom tags and generators located in _plugins directory

Currently I'm able to use "custom tags/generators" but it is very ugly way :)

What do you think about this feature ? It is possible?

Fatal error in ../deps/v8/src/api.cc, line 1248

Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().

For some reason, Darko inserts comma in every URL. I've tried changing baseUrl and url yml properties with no luck. There might be a bug somewhere in the code. I am trying to find the place where you parse URLs, but don't know where it is located.

<link rel="canonical" href="http://yoursite.com,/,/">

<link rel="stylesheet" href="/,/css/main.css">