cabinjs / cabin Goto Github PK

Currently, we are not validating users interacting with inquirer to select their preprocessor or template engine

Build does not copy fonts directory, Please update the Gruntfile copy task

        'styles/fonts/**',

Thanks for awesome tool.

I've noticed that my content (5000+ words including code examples) fails to render (no errors in the terminal output). The page just stops rendering the content.

It looks like the content is being truncated because there is a set limit maybe?

Not sure what other information I can provide to be honest.

On a Mac with latest OS release and updates.

The layouts folder now has both layout and mixin files in it and needs a new name to describe its current state

expressjs/response-time#15
koajs/response-time#9

As of right now, the site is a really poor experience on mobile. The Cabin website should be responsive just like its themes.

Currently, if a theme cabin.json/package.json is invalid "This theme has an invalid cabin.json" is always printed. A more specific error message would be more helpful.

I think it is important to stay up to date with our dependencies, so that we can utilize new features and allow contributors to use the latest APIs.

Solving this issue will require refactoring affected code to match the new commander API.

The goal of this issue is to normalize naming conventions throughout the codebase. This means changing the cabin.json spec and cli inputs to have a consistent name for a piece of information throughout the site creation process.

cabin.json property renaming

template -> templateEngine
style - > preprocessor

config.js added property naming

preprocessorGruntTask -> used when rendering the _package.json and _Gruntfile.js
templateFileExtension -> used when rendering the cabin.json

Sorry, this may be a philosophical request or I may have missed some documentation. Figured you'd be interested since this is a newer project and the intended audience is likely designery folks (with limited designer JS abilities). Great project though, hope I can submit a theme.

What I tried to do

I wanted to put the about page at /index.html and the paginated blog at /blog.html. So I edited the Gruntfile.

    pages: {
      posts: {
        src: 'posts',
        dest: 'dist',
        layout: 'src/layouts/post.ejs',
        url: 'posts/:title/',
        options: {
          pageSrc: 'src/pages',
          data: {
            baseUrl: '/'
          },
          pagination: {
            postsPerPage: 1,
            listPage: 'src/pages/blog.ejs'
          }
        }
      }
    },

I moved index.ejs to blog.ejs and created a new index.ejs with normal, static content. Unfortunately, after running grunt it still builds the blog (correctly using blog.ejs) at index.html. I expected it to do this at /blog.html (which doesn't render) and for index.ejs to build index.html. Can replicate this using https://github.com/snide/Canvas (note, only set up for EJS).

Playing around I was able to get kind of what I wanted, but only when i specifically set listPage: about.ejs (moving the post forloop there as well) which rendered the blog at about.html and let me render index.html from index.ejs. Unfortunately, then my blog would be labeled /about :)

This could be intended. It's blog software, so you may assume index.html MUST show pagination. From looking at the grunt file output though, I just assumed it was easy to change.

Unfortunately I'm a designer, otherwise I'd look deeper into your JS, but I'm guessing there's some sort of reserved naming that needs to be used?

If I have some XML in a code block and put a comment after the tag, the comment isn't correctly syntax highlighted. Example:

<element attribute="value" /> <!-- attribute = value -->

It seems to correctly color it (light and italics) if I put a // inside the comment:

<element attribute="value" /> <!-- // attribute = value -->

Result:

The screencast on cabinjs.com is outdated and needs to be improved. The video quality is spotty at some parts, and is using an older version of cabin. I plan on making a new one which walks the user through customizing the Candy theme and deploying it.

It might be nice to have some additional prompts when the user runs cabin new to allow for a better initial gruntfile.

Some end users might want a dev and a dist build for their site. This is annoying to do by hand each time but really easy to make a gruntfile template for.

Other things that users might want:

Coffeescript compilation, image optimization

Ran the following command, forgetting to specify the destination folder:

cabin new cabinjs/canvas

The command failed as it tried to mkdir canvas inside of the cabinjs folder that didn't exist.

Do we consider this an error and warn the user that they mistyped the command or actually generate the nested folder?

Cabin fails on windows while trying to delete the .git folder after cloning the theme repo.

I'm looking to use Cabin to render my GitHub pages, but I don't know the best way to do this. I tried initing dist/ as a git repo, and push that, but ever time I run grunt it seems to blow that directory away and thus killing my repo. Do you have a recommendation on a better way to do this?

I think it might be valuable to make themes node modules so that they can keep track of the Cabin and grunt-pages version they are currently supporting using gemnasium so that they can keep up to date with the evolution of the project. Additionally, I think it might be valuable to version themes rather than simply pulling the current master branch from the GitHub repo. Npm would provide a way to version the theme.

Found this script a while ago, seems like a nice alternative to Jekyll (node.js + grunt <3).

Anyway I just tried to create a blog and spelled wrong on the theme name. The script just hang and even ctrl+c didn't work. Had been great if I instead had got an error message like "Theme doesn't exists".

For example:

$_ cabin new blog theme-path-that-doest/exists

>> Error: the theme "theme-path-that-doest/exists" doesn't exists.

Expected behavior

I should be able to add cluster from my google account

Actual behavior

I was unable to add cluster from my gmail account each time I try to ,the app stops working it force closes

How to reproduce

*Download

*Install

*Launch

*Click on add cluster

*Finally ,if you have a google account on your phone it will automatically want to use any of the google accounts you have ,so just click on the gmail app Logo
and wait for the error..

*Cabin 0.5.0
*Android 7.0 nougat

Recording of the bug

https://youtu.be/joZ2NcztWE4

This will allow for flexible deploys to gh-pages and other non-root locations

We need to validate that the cabin.json files have a valid grunt-pages configuration(required properties and folder structure) since it needs to work with our Gruntfile template. I think if the validation fails, we should have a link to report an issue to GitHub.

Currently the grunt pages version is listed in two places for each theme, it should only have to be listed in package.json and not in the cabin.json

After getting node 0.8 on my system, I can verify that unzip doesn't work properly. After reading some issues, I discovered that a previous patch version works with node 0.8, but the latest patch only works in newer node versions.

I am considering using a different module, but haven't found one that can plug in as a stream.

The gh-pages should help users find themes by allowing them to filter themes by template lang/preprocessor support(jade/less) and theme purpose (blogging/docs).

Users should be able to see screenshots of the filtered themes as mentioned in #3 and copy a shell command that they can then run to scaffold out their project.

Example: If the user filtered by Sass and EJS there is no need to prompt them about preprocessor or template language and we can just use --Sass and --EJS options.

cabin new blog colinwren/Blok --Sass --EJS

It might be cool to have a table that shows what kinds of things a particular theme supports on its gh-page or repo readme. This would give users a quick overview of what they can expect from the theme.

The Cabin repo could have a standard one that would be used across all the themes. It would look something like this:

I think we should have a command to scaffold out a new theme. We could prompt the theme author about what template languages and CSS preprocessors they want to support and then give them everything they need to immediately start working on their templates, styles, and grunt-pages config.

Hi,

I'm generating an RSS feed (you can see my set-up here: https://github.com/Integralist/Website and the distributed version here: https://github.com/Integralist/integralist.github.com) but I'm using Feedburner and it refuses to now update my feed (partly) because the size of the feed is too large...

Your feed filesize is larger than 512K. 
You need to reduce its size in order for FeedBurner to process it.

...this is because the feed.xml being generated includes the entire contents of my articles rather than a short description.

Is there any way to use a short description (I have one defined as meta data in each of my posts).

I have seen multiple tweets from people wanting to convert a Wordpress or Octopress site to Cabin, and I think it would be valuable to have a conversion tool to help users escape from inferior blogging platforms 👅

So I did cabin new newblog and ran grunt.
It failed with this:
Running "pages:posts" (pages) task Fatal error: Cannot call method 'toString' of undefined

It builds ok if there is no code tags like javascript in the .md files.
I downloaded just grunt-page on its own to build the same file, failed again.
Maybe I am doing something wrong here. Can anyone have a look at this please?

Thanks .

The Cabin logo is pretty bland with that black Cabin. @colinwren and I discussed making a cooler logo which would perhaps use the node hexagon and/or more color/imagery surrounding the cabin.

I want to rep a cool smoking cabin logo on my theme, hook it up.

On every new setup cabin new . I'm getting

>> Local Npm module "grunt-pages" not found. Is it installed?
Warning: Task "pages" not found. Use --force to continue.

Adding grunt-pages to the devDependencies fix the issue.

Hi, guys!
I have a problem with building Cabin JS project on my Jenkins. It runs grunt, bet gives out an fatal error:

Running "pages:posts" (pages) task
Fatal error: The metadata for the following post is formatted incorrectly: posts/.svn/all-wcprops

Is there a way to ignore .svn files from Cabin JS?

It seems that dates aren't being processed correctly. See the attached screenshot of my markdown file vs the rendered output.

I install all the dependencies and run grunt which gets up past the generation of posts but then fails on "compass:dist" with a cannot load such file -- sass/script/node (LoadError) error...

/Users/markmcdonnell/.rbfu/rubies/1.9.3-p385/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `require': cannot load such file -- sass/script/node (LoadError)

...so I can't get any further with this at the moment :-(

My Ruby dependencies are...

Using chunky_png (1.2.8) 
Using fssm (0.2.10) 
Using sass (3.2.12) 
Using compass (0.12.2) 
Using bundler (1.3.5) 

Hey,

This isn't a direct issue with CabinJS but I'm putting this issue here in case any one can help clarify how to resolve it.

I recently downgraded my Ruby version: https://github.com/Integralist/Website/commit/016ac98319ed41da86299dfb0321ae12a4225e2c and it seems that one of the required gems (specifically compass) is unable to be located...

Running "compass:dist" (compass) task
Verifying property compass.dist exists in config...OK
File: [no files]
Options: sassDir="src/styles", cssDir="dist/styles"
/Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:118:in `require': cannot load such file -- sass/script/node (LoadError)
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:118:in `rescue in require'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:124:in `require'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches/browser_support.rb:1:in `<top (required)>'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:2:in `block in <top (required)>'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `each'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `<top (required)>'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions.rb:9:in `<top (required)>'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass.rb:5:in `block in <top (required)>'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass.rb:4:in `each'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/lib/compass.rb:4:in `<top (required)>'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:66:in `require'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/bin/compass:20:in `block in <top (required)>'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/bin/compass:8:in `fallback_load_path'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/gems/compass-0.12.2/bin/compass:19:in `<top (required)>'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/bin/compass:23:in `load'
    from /Users/markmcdonnell/.gem/ruby/2.0.0/bin/compass:23:in `<main>'
Warning: Task "compass:dist" failed. Use --force to continue.
Error: Task "compass:dist" failed.
    at Task.<anonymous> (/Users/markmcdonnell/Google Drive/Dropbox/Library/Github/integralist (CabinJS)/Website/node_modules/grunt/lib/util/task.js:197:15)
    at null._onTimeout (/Users/markmcdonnell/Google Drive/Dropbox/Library/Github/integralist (CabinJS)/Website/node_modules/grunt/lib/util/task.js:225:33)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

Aborted due to warnings.

I've checked the paths to where the gems are installed...

❯ gem env                                                                 
RubyGems Environment:
  - RUBYGEMS VERSION: 2.0.14
  - RUBY VERSION: 2.0.0 (2013-11-22 patchlevel 353) [x86_64-darwin13.0.0]
  - INSTALLATION DIRECTORY: /Users/markmcdonnell/.gem/ruby/2.0.0
  - RUBY EXECUTABLE: /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/markmcdonnell/.gem/ruby/2.0.0/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-13
  - GEM PATHS:
     - /Users/markmcdonnell/.gem/ruby/2.0.0
     - /Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/gems/2.0.0
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - https://rubygems.org/

...and it seems that they are being installed to the first path and not the second (e.g. when I ls the files I can find them in the first path and not the second).

But, the stack trace seems to suggest that it has correctly found compass when trying the first path so I'm not sure why it then tries the fallback gem path.

I've also tried installing directly to that secondary path: bundle install --path=/Users/markmcdonnell/.rubies/ruby-2.0.0-p353/lib/ruby/gems/2.0.0/gems but when I check the gems directory it doesn't show any gems installed?

Not sure what else to try

It would be nice to see some screenshots of themes to entice users to check them out. Maybe an image slider?

Right now the cabin new command accetps user/repo as an optional parameter like so:

cabin new colinwren/Blok

It is often really convenient to just copy the enitre github url like this:

cabin new https://github.com/colinwren/Blok

Cabin should accept both formats

Hi,

I've just discovered that running grunt I get the following error...

Running "default" task

Running "server" task
Warning: Task "connect" not found. Use --force to continue.
Error: Task "connect" not found.
    at Task.run (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:171:28)
    at Object.thisTask.fn (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/grunt/task.js:78:16)
    at Object.<anonymous> (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:282:30)
    at Task.runTaskFn (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:235:24)
    at Task.<anonymous> (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:281:12)
    at Task.<anonymous> (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:215:7)
    at Task.runTaskFn (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:238:9)
    at Task.<anonymous> (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:281:12)
    at Task.start (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/util/task.js:290:5)
    at Object.grunt.tasks (/Users/markmcdonnell/Box Sync/Library/Github/integralist/Website/node_modules/grunt/lib/grunt.js:155:8)

Aborted due to warnings.

You can see my code here: https://github.com/Integralist/Website

I've already run npm install.

Modules...

❯ npm list | grep connect
├─┬ [email protected]
│ └─┬ [email protected]

Gems...

❯ gem list

*** LOCAL GEMS ***

bigdecimal (1.2.0)
bundler (1.5.2)
chunky_png (1.2.9)
compass (0.12.2)
fssm (0.2.10)
io-console (0.4.2)
json (1.7.7)
minitest (4.3.2)
psych (2.0.0)
rake (0.9.6)
rdoc (4.0.0)
sass (3.2.12)
test-unit (2.0.0.0)

The integration tests are not in good shape right now 😦 We need to have discrete integration tests for different types of user input and situations.

Right now we are simply checking for the existence of files instead of validating the file content so we have no idea if someone breaks the templates or not when contributing.

I am planning on tackling this in the next few days, I hope to have a PR ready sometime this weekend.

Similar to cabinjs/parse-request#1 we need to remove this once unshiftio/url-parse#145 is resolved.

Have you consider to integrate grunt-usemin into the build flow?

https://github.com/CabinJS/Cabin/blob/master/lib/new.js#L175-L224

I think generate is valuable for timestamping and pre-filling the required metadata properties for a post.