What does it do?

I started Juniper in 2004 to replace Dreamweaver's templating feature while building a small- to medium-size website. Essentially, I wanted to never have to copy-and-paste markup, or make changes to code in more than one place. And I didn't want to use Dreamweaver.

What's wrong with Dreamweaver?

At the time, Dreamweaver had only recently been ported to OS X. The UI had some usability issues. Editing markup in Dreamweaver's built-in editor was nightmarish. I wasn't a fan of Dreamweaver's templating implementation, which seemed fragile and too dependent on Dreamweaver itself. I didn't want to be tied to it.

These are all my personal opinions of course, and I'm sure it's been improved upon since then. The answer is that nothing is wrong with Dreamweaver, but just in case you don't want to use it ...

So Juniper is a Yet Another WYSIWYG HTML editor? (aka, YAWYSIWYGHTMLE)

No. Building a YAWY — one of those — sounds like a lot of very painful work. (And kudos to Dreamweaver's team or anyone who takes it on.)

To use Junpier, you have to be able to (and want to) code your markup by hand. This will be true even when your use of Juniper is mediated by the GUI application.

To use the stand-alone PHP/XML engine means knowing HTML at least and, at best, some PHP.

Oh, so it's Yet Another PHP Templating Engine? (ie, a YAPHPTE)

Well ... yes. But also oh so much more!

Okay, how do I get it?

You can't yet. Not officially. As of now (December 2006) it is not quite ready for general consumption. This here software company's a back-burner operation, see? If you're curious about Juniper or want to find out when it's released, please get in touch!