Finalize list of chapters for V1

[addyosmani]

Currently in the index we have:

• Introduction
  • Why automate?
  • Command-line
  • Node and npm
• Build systems
  • Modern tools vs. shell scripts
  • Grunt
  • Brunch
  • Gulp
• Scaffolding
  • Yeoman
  • Loom
• Dependency Management
  • Bower
  • npm + Browserify
  • ComponentJS

We'll want to revise this with the structure we've been discussing over in #9 so that it's clear to contributors what we'd love to have covered.

[michealbenedict]

I am curious to understand what content the topic Command-line would contain.

Would it be helpful to start adding brief descriptions/outline to each of these topics For example, As a developer, I would love if the topic Why Automate could talk about the following sub-topics.

• Problem statement (Developer Pain, list scenarios if possible so developers can relate)
• Briefly talk about changing trends i.e increase in frontend application complexity and the need to save developer time
• Proposed solution/s (such as build systems, scaffolding, dependency management), how these are helpful and set the context for the book.

Not sure whether this is the best approach.

[travm]

I believe the command-line content would aim to ease worries of front-end developers who might be intimidated by command-line interfaces. I think that is probably the biggest opponent for these tools - just educating and building developers confidence so that they can comfortably use CLIs and not rely on a GUI for everything.

[jrcryer]

:+1: Think this looks good for V1. Also think @travm is spot on with his comments.

[addyosmani]

Exactly what @travm said. Fear of the command-line is a big barrier to newcomers getting started with these tools. We need a strong intro that walks them through how straight-forward it can be and summarises the many advantages it offers.

[michealbenedict]

Sounds perfect, thanks for the clarification.

[addyosmani]

I've been revising the list of chapters in our readme to include a few additions that were requested. I think we should now have a solid final list that we can tackle.

Also happy to share that we've got confirmed authors for most sections now too. Exciting times :)

[zenorocha]

What do you think about having a section in "Scaffolding" and "Dependency Management" explaining why those things are important?

Or questions like

"Why should I use Yeoman or any other tool to scaffold my projects? Why not forking a repository instead?"

and

"Why should I use a dependency management tool instead of including third-party projects manually?"

are going to be answered in "Why automate?"?

[jhnns]

Why are CommonJS-bundlers like browserify and webpack under "Dependency Management"? Imho this chapter should just include package managers and link to those bundlers.

[jhnns]

@zenorocha these are important questions! Should definitely be answered somewhere.

[mischah]

Hi @addyosmani, the »Dependency Management« ist missing a chapter about SystemJS :kissing_heart:

… Don’t you think so?

P.S. and what about jspm?

[addyosmani]

More than welcome PRs to include them :)

On Wed, Aug 26, 2015, 11:05 PM Michael Kühnel notifications@github.com wrote:

Hi @addyosmani https://github.com/addyosmani, the »Dependency Management« ist missing a chapter about SystemJS https://github.com/systemjs/systemjs [image: :kissing_heart:]

… Don’t you think so?

P.S. and what about jspm http://jspm.io/?

— Reply to this email directly or view it on GitHub https://github.com/tooling/book-of-modern-frontend-tooling/issues/15#issuecomment-135188155 .