I’d encourage you to try PubKit rather than pkBlog, not just because the latter will only get minimal further development (by me, at any rate), but because PubKit focuses the customizations better without having to hack the core logic. I’d appreciate any feedback on the sticking points during installation so as to improve the guidance that goes with it. And if anyone can point me to a straightforward guide to making an Evo installer package for some of the chunks and snippets, I’d be very grateful for that.
I know there are a lot of bits and pieces to the setup as offered, but it’s important to note that a lot of this is for demo purposes. The main intent is to have a tool for
creating resources and records, for which you only need to install half a dozen files and a few chunks and TVs (OK, the list is growing now...). Other stuff - such as the fancy formatting with PHx extenders for management pages - is just the way I’ve handled the output and management of items once created.
Using PubKit myself, I start with the page I want to publish, creating a few child resources in the Manager for tests; then I create the "post-edit" input page and get it creating new documents properly; then fix up a simple management page to test feeding in "edit" and "delete" commands, or test them by typing them in directly in the URL query string; then I get the Preview working, with the Ditto config file and so on. And then get the management page working with the pretty bits.
KP
☆ A M B ☆
