Ah... I thought you meant a directory wider than DC.
As for security issues in PADkit, that's why I said backend.
It's a good code base to start with.
But as for 2 files? No. That's not the case.
To be honest, PAD is still a good option though. The key is the PAD extensions, where you can define whatever you want in addition to PAD. Pretty much most software developers know PAD to some degree, and there's already PADgen ready to go. All that would be required is adding in an extension, and that can be done in pure HTML. (You need to know PCRE though - Perl Compatible Regular Expressions - but those are pretty easy. No back references or groups or anything like that needed.)
So you'd have an authoring tool already done and ready to go!
(PAD really is much more powerful than most people understand, and it's entirely because it's XML.)
For just DC programs, like coding snacks, PAD could still make things easier with a defined workflow. If you want to come up with some customizations (additions a la PAD extensions), tell me what they are and I'll see if I can come up with a PAD extension that works.
People could then just use PADgen and the DC PAD extension to author the files for you. It's a great way to off-load some work and be productive on other important things.
I have a deep love for XML and PAD. It's just amazing stuff. It would be great fun for me to come up with a DC PAD extension. (I've done a lot of work with data sets, including mucked-up data, and I'm sure I can help out here.)
Basically, don't reinvent the wheel. PAD has the infrastructure already there. Using it will save massive amounts of time.