Integrate Assemble - Githubissues

grayghostvisuals commented 10 years ago

@jonschlinkert @doowb

Hey guys long time no chat. I know we've been having back and forths on Effeckt so I thought I would reach out and offer another project to use Assemble on where there are less cooks in the kitchen holding things up.

What I ultimately want to do with the current setup is bottom line…

make it more efficient to create builds.
make it easy as hell for contributors to setup.
Let you both make suggestions to make this project stronger using Assemble.

I've gone ahead and started an Assemble branch for us. Hoping we can work together and have fun while we're doing it. :metal:

doowb commented 10 years ago

I'm glad to help out. I know we've added a lot to assemble since adding it to the Effeckt build, so we probably have more idiomatic ways of using it now.

I see you haven't gotten anything started on the assemble branch yet, so it's a clean start. Is this just to build the http://typeplate.com/ site, for documentation, or something else?

In the meantime, I'll pull down the project and take a look.

jonschlinkert commented 10 years ago

:+1: awesome! yeah this looks interesting, I'd love to help out.

Just a heads up, I'm swamped until the 10th - we might be able to get something up quickly before that, but in the spirit of not over-comitting - my time will free up much more after that.

jonschlinkert commented 10 years ago

lol, that's funny. we seem to do that a lot - always answer at the same time

doowb commented 10 years ago

I know, it's crazy.

grayghostvisuals commented 10 years ago

Love It! You guys are true internet cowboys! @jonschlinkert no worries about time, I understand completely. There's not a ridiculous launch date or anything silly like that. Whatever time/help/advice is donated is appreciated. This is a low and slow cooker sort of deal.

@doowb There are a few things I'm thinking, but like I was saying the sky is the limit here. I'm really wide open to what we can do. Here are a couple things I have listed in my brain dome…

The Sass port I have in the typeplate directory contains a sep. variable file that I usually package as a .zip with the main file once I'm ready to release it which is always a manual process. Something to automate this would be neato.
Making a better build process for the site in general would be wicked (Maybe integrating use-min from Grunt etc.).
@joshnh just gave me a bunch of great feedback I now have in the issue tracker regarding bower and Grunt.
If there is something that can help out with documentation I'm all ears.

grayghostvisuals commented 10 years ago

Also I forgot to say maybe it is voodoo magic you both have going on?

jonschlinkert commented 10 years ago

ha, lol it's some kind of voodoo for sure

jonschlinkert commented 10 years ago

Ok, we're about ready to rock on this. @doowb and I are doing some refactor stuff for Assemble that would be great to finish first, but if you want we can try to tackle this before that. in terms of time, we are working hard to have the refactor done before the end of Dec.

grayghostvisuals commented 10 years ago

@jonschlinkert No worries. Finish what you all need to get done first. This can wait. I may do some stuff like grunt configs, bower updates for the time being. Other than that it's all good. Thanks for keeping me posted :+1:

jonschlinkert commented 10 years ago

:+1:

grayghostvisuals commented 10 years ago

Just updated the master branch with some much needed updates to Grunt. We can still keep out the npm modules dir from the repo but the bower_components dir has to stay unfortunately.

jonschlinkert commented 10 years ago

@grayghostvisuals wow, bro I'm really sorry it's been so long since we got back to you on this! @doowb and I were heads down focused on closing a round of venture funding which pushed out our plans with assemble. but that's done! so we're about to release 0.5.0 of assemble, and I'd love to help out with this if you still want us to.

grayghostvisuals commented 10 years ago

@jonschlinkert Absolutely. That would be great. Whatever approach you all think is the best with this I'm down. :metal:

jonschlinkert commented 10 years ago

:+1: going to work on this over the weekend

jonschlinkert commented 10 years ago

a couple of questions (related to things we might be able to help with):

why is bower_components checked in? if the concern is that you don't want users to have to do both npm install and bower install, we could either tell the user to do npm i && bower install or better, we can just put a scripts property in package.json with the bower install command, and it will happen automatically when npm install is run. If some other reason, umm nevermind... it was @doowb's question.
I can't believe you have typeplate.com. not a question, but still. I can't.
if there are node.js/javascript alternatives for some things you're doing with Ruby, are you open to those? or are there things in the project that need to be Ruby (I haven't looked enough and don't have an opinion either way. just trying to feel out the boundaries here. and I also have some ideas...)
where do you get most of your community? Ruby, node.js, etc. do you have a target audience for this? I ask b/c it might effect decisions on how some of the files are organized etc.

might be good to hop on skype sometime too. it's not a must-have, but I'm down for it (probably @doowb too) if you have the time.

grayghostvisuals commented 10 years ago

I have the bower_components in there only because of the demo page which uses normalize (we toggle it on/off for the demo), but I've always meant to have a grunt-copy task that brings it into the CSS dir. for us instead.

The primary things we're using Ruby for is Compass and Sass so we still need to run and operate with these. As far as alternatives I'm gonna need some more info/details on what you have in mind. We just want an easy documentation system, demo system and ultimately a good build system that can encourage participation. As of now I've moved the project core to the Typeplate bower repo in order to keep this repo for the primary site that provides the examples and docs. The Typeplate bower repo will be primarily for the project core and where the majority of contributors go to contribute to the project core not the site itself.

The majority of people are web developers that use Sass & Compass and appreciate the finer points of typography on the web.

Anytime you wanna hop on Skype/Google Hangout just LMK. :dancer:

PS: name.com = typeplate.com = cname = boomtown

jonschlinkert commented 10 years ago

:+1:thanks for the info!

regarding Ruby/Compass/Sass, cool that makes sense. After scanning quickly that's what it looked like, but I wasn't sure if there was anything else that I missed. I don't want to give (or have) alternatives for those.

We just want an easy documentation system, demo system and ultimately a good build system that can encourage participation.

Agreed, the info about users helps, thanks

jonschlinkert commented 10 years ago

@grayghostvisuals I just noticed an "assemble" branch, should that branch be used for this? It won't effect anything on my part, so either way is fine. Also, that branch has a typeplate directory, but the master branch doesn't. should that be included in this?

grayghostvisuals commented 10 years ago

Yes, the branch for assemble should be used for this work. The “typeplate” directory you're seeing is what I removed in order to bring the project core over to the bower repo. As of now this repo is primarily the demo and the site itself.

jonschlinkert commented 10 years ago

thanks, I'll try to look at it today or tomorrow

grayghostvisuals commented 10 years ago

closing this seeing as we already have this in the works as a PR. Thanks doods!

typeplate / typeplate.github.io

Integrate Assemble #133