The idea of a new/expanded Dist::Zilla tutorial has my full support. I have started using dzil some time ago and am pretty happy about that decision. Only I am still struggling with it, especially if a GitHub repository builds its package with plugins I've never heard of before, and which has a bunch of dependencies to modules (or even external tools) I've never heard of before. Quite often I find myself inspecting the plugin code to find out how to get the benefits but disable some unwanted behaviour.

I am sure you are aware of RJBS's tutorial at http://dzil.org/tutorial/start.html which has been written by someone who knows way too much about Dist::Zilla. It is concise, which is a good thing, but it lacks any hints on how to find more details about the plugins: What they actually do, how they can be configured. Often a link to the relevant CPAN would do the trick. I often considered adding stuff, but then doing that in a structured way needs more time than I ever had.

Your article, on the other hand, makes a good introductory chapter in the Comprehensive Book On Dist::Zilla. However, in my opinion it is just too long to be a tutorial. I guess that anyone who considers whether or not to start using Dist::Zilla is aware of software building and packaging. They don't need more motivation, but rather look for hints how to judge cost vs. benefits, or for a guide through the mess of available features. Here are a few questions which I'd like to see answered in an introductory article about Dist::Zilla:

• What's the scope of Dist::Zilla?
• How does it affect the workflow? For example, there are a few articles about how to make dzil distributions palatable for developers who want to contribute on GitHub without using dzil themselves. All of these are blog articles which are not maintained and get difficult to find as years go by.
• How does it compare to other build / install tools?
• What are the resources to learn more? Apart from RJBS's tutorial, the #dzil channel comes into mind, where one can learn a lot by just listening.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.