We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I thought that running peak watch would take the Jade file and compile to an index file with dummy data.
peak watch
// #(IndexPage) .col__4-12 h1.index-page__title Blog .col__8-12.index-page // #(Posts) // #(Text) .text-post .post-title a(href="!(Permalink)").h1 !(Title) .post-date span !(DayOfMonth) !(Month) !(Year) // ## // ## // ##
compiles to:
{block:IndexPage} <div class="col__4-12"> <h1 class="index-page__title">Blog</h1> </div> <div class="col__8-12 index-page"> {block:Posts} {block:Text} <div class="text-post"> <div class="post-title"><a href="{Permalink}" class="h1">{Title}</a></div> <div class="post-date"><span>{DayOfMonth} {Month} {Year}</span></div> </div> {/block:Text} {/block:Posts}
However, when I run it at localhost:1111 all the tags appear in the HTML. Does Peak not support rendering it as Tumblr would, or with dummy data?
localhost:1111
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I thought that running
peak watch
would take the Jade file and compile to an index file with dummy data.Example
compiles to:
However, when I run it at
localhost:1111
all the tags appear in the HTML. Does Peak not support rendering it as Tumblr would, or with dummy data?The text was updated successfully, but these errors were encountered: