linemanjs / lineman-docs Goto Github PK

not-full-width, black bar isn't really utilized (just there to show the logo). do we need a menu? just axe it and add the icon?

It would be awesome to have answers on the "design of lineman" relating to some of the opinions that Lineman has as an addendum to the Questions & Answers section following the Lineman vs Yeoman feature grid.

@searls probably has the best insight into answer these, here's a few of the common questions I get regarding this stuff:

• Why doesn't Lineman have sub-generators for its project templates? (ie: yo angular generate controller:food)
• Why does Lineman wrap grunt, testem and other tools instead of letting users reference them directly?
• Why does Lineman use Testem as its default test runner?
• Why doesn't Lineman use Bower or any other Package Management tools?

Clicking the sidebar links makes it to disappears sometimes. I know that is not final but maybe you didn't notice it yet (or is just my lovely browser (chrome)).

It is a rendering issue but not sure what causes it.

Need to make it clear those big cute icons to our template projects are calls to actions. Currently there's not even a cursor icon

When I tried to deploy an example (using your angular template) to heroku. Heroku told me to push to a branch like master

so instead of:

git push heroku

I had to do:

git push heroku master

Cheers :)

see this gist here. we can probaby pull it in mostly as-is

We are offering ourselves to do a redesign of the web page. (Free, of course) If you want. This is one proposal, we can talk if you want something different

Hey @jasonkarns -- I'm not sure why I never got around to this, but we should rely on the lineman-blog plugin instead of grunt-markdown-blog directly. It takes a lot of the default config out of the userspace project's hands.

I wonder if it would be beneficial to include (MIT vs BSD) in the comparison table as well.

Add the following plugins to the Linemanjs.com documentation, as per @searls request.

https://github.com/Psiablo/lineman-autoprefixer
https://github.com/Psiablo/lineman-imagemin
https://github.com/Psiablo/lineman-svgmin

i think the lineman vs. yeoman table should be an html table. the ascii art is cute but when you're editing the file directly it's a lot of work to keep it formatted. Also I feel like it's not super readable. @davemo -- I guess this means we need to style tables?

Should have a section describing lineman plugins, explaining the loading scheme, and listing the known current plugins

There are a few wiki pages that were extracted from the original readme. How many of these deserve to be added to the docs?

1. Lineman's Tests: explaining how to hack on and run the rspec suite on lineman itself
2. Sass: explaining the special enabling of sass (the enabled flag and ruby)
3. Test Frameworks: quick tutorial of configuring testem for various frameworks (jasmine/mocha/qunit)
4. Troubleshooting: which only had 1 item (the old too-many-open-files -- still a problem??)

Votes on which should be moved to the docs?

ability to override lineman core deps (or lineman plugin deps)