warlock new...?

[Anthony Kerz]

hey j,

just came across a little spell (pardon the pun) of free time and was able to go over your docs a little more closely, 

and i really like the over-all design and the way on which you convey it in the docs...kudos!

is there a way to create a bare-bones warlock project without starting from an existing project like angular-example?

thinking something roughly equivalent to `rails new <project-name>` (if that is a reference that resonates).

i guess what u have shown here is pretty close, but there is a decent amount of stuff (albeit cool stuff, like social media tags from ngbp) to get rid of for a diff app.

and what i surmise are some important bits like below, i think might benefit from a little mention somewhere in the doc:

```

    <!-- styles -->

    <% webappStyles.forEach( function ( style ) {%>

    <link rel="stylesheet" href="<%= warlock.file.relativePath( warlock.file.dirname(filepath), style ) %>"><%});%>

```

and

```

    <!-- scripts -->

    <% webappScripts.forEach( function ( script ) {%>

    <script type="text/javascript" src="<%= warlock.file.relativePath( warlock.file.dirname(filepath), script ) %>">

    </script><%});%>

```

b.t.w. for someone less familiar with what are probably ubiquitous elements of contemporary web-dev, 

is the `<%` and `%>` notation ejs...?

regards,

tony.

[Josh David Miller]

Hey Tony!

Scaffolding doesn't exist yet, so there's no way to "init" a new project - yet. This is high on the to-do list, but we are first aiming for feature parity with the current Grunt-based ngbp build. However, you have correctly surmised the "important bits" are the script and style includes.

The basic procedure (which probably *should* be added to the docs) is only to init the new NPM project:

$ mkdir new-project && cd new-project

$ npm init

$ npm install --save-dev warlock-spell-angularjs

Technically, Warlock is completely set up - there's just nothing to build. Creating the files as needed (starting with `index.html`, of course) is the next step.

The reason the tutorial follows the ngbp approach is because the vast majority of testers for the alpha will be existing ngbp users and the short-term goal, as I mentioned, is feature parity with that, so it's a reasonable place to start for most.

Oh - and the templates are actually Lo-Dash: http://lodash.com/docs#template

Josh

--
You received this message because you are subscribed to the Google Groups "Warlock Build System" group.
To unsubscribe from this group and stop receiving emails from it, send an email to warlock-engin...@googlegroups.com.
To post to this group, send email to warlock...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/warlock-engine/121a4210-09d2-48a2-9b67-140c138c8a7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.