-
Notifications
You must be signed in to change notification settings - Fork 17
Conversation
After (If there was a package.json, this could be |
(Then you need to |
One other thought: if we copy the files to template/app/ rather than moving them there, then we can differentiate between the content of the template and the content of Oghliner's own website. It would also reduce the differences between the template's gulpfile.js and Oghliner's own version of that file, since Oghliner's own version could build from app/ instead of template/app/. |
Note: I made a few updates to the content of app/index.html and updated the file globs in gulpfile.js to offline all the files in app/ (it was missing some of them because I hadn't updated the globs after I used the GitHub Pages Generator to design a nicer layout for the site). |
Missed my package file. The local dependencies should be installed by gulp-install. So now I think we're at:
|
@@ -23,7 +23,7 @@ var oghliner = require('./index.js'); | |||
gulp.task('default', ['build', 'offline']); | |||
|
|||
gulp.task('build', function(callback) { | |||
return gulp.src('app/**').pipe(gulp.dest('dist')); | |||
return gulp.src('templates/app/**').pipe(gulp.dest('dist')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that you're no longer removing the app/ subdirectory, this should continue to build app/ rather than templates/app/.
The output with gulp-conflict is a bit scary, since it puts the word
But it seems like a good idea to use it anyway. |
The other output I noticed are these warnings:
I'm not sure how to pick a license for the user, although perhaps NPM would be satisfied if we added the field and gave it an empty string value. That reminds me that we should probably put the template files into the public domain (except for the ones already copyrighted by GitHub, of course). I'll ping licensing to confirm that. As for description and repository, we should be able to pick sensible values for those. And creating a blank README.md file probably satisfies the README warning. |
My thought too, I'll look into removing it. As for package.json, we could prompt the user during bootstrap for values. |
The other thing to do is commit the newly created files to the master branch, something like:
Which reminds me of two more things:
|
Ah, good idea! |
|
var config = { | ||
name: "oghliner-template-app", | ||
repository: "https://oghliner-template-app.git", | ||
description: "A template app boostrapped with oghliner.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: boostrapped -> bootstrapped.
Looks good! I heard back from licensing and filed #38 to release the template files to the public domain, so we can follow up on that there. |
Starting point for the boostrap command which creates the skeleton template app in any folder. The process for starting from template would now be
Or we could just do
oghliner deploy app
instead of the last two steps.More things we could do: