Your comments

Maybe you can just use something like uSteam and place the appropriate code in an HTML block.

I wouldn't directly insert special characters like that in HTML, it's technically not supposed to be inserted that way, just use HTML entities instead. So for ©just use "& copy;" (without the space)


Here's a list of HTML entities on WIkipedia

Assuming you're using Flex (which uses Bootstrap), you can make modals this way:http://getbootstrap.com/javascript/#modals-examples and just place the code in an HTML block, etc.


Some more Bootstrap resources

http://getbootstrap.com/css/

http://getbootstrap.com/components/

http://getbootstrap.com/javascript/

Django? You'd probably like to talk to @A.L. Flanagan

Anywho, you wouldn't gain much dealing with Zen. There didn't seem to be a set methodology in Zen UTL code.

There are a few "apps" which are presumably in the backend that no one can really see on control on our end. Such as:

- Editorial

- Business (business listings, etc.)

- Classifieds

. . . and so on . .

The UTL pieces usually deal with only one of those apps at a time usually, though not always (e.g. a classified listing can be related to a business, etc.)

Components are like models, they do most of the logic on the UTL end. They also have macros that are HTML/UTL

Skins are like themes or templates in other CMSes. "Option macros" are like hooks in WordPress, sort of

Block templates are like atoms or molecules in Atomic Web design. they just really on the components and base system, within the current "skin"

A lot of UTL dev time is just searching through the docs a little but mostly the code, following the references to find the right piece you need to change or hook into.

Hope that helps!

I believe UTL and the basic methodology for underlying Blox system is pretty much the same (someone from TN may correct me if I'm wrong), most of the new stuff in Flex are the skins, components, block templates, etc. that are made in UTL.

I came across this awhile ago and it helps shed light on their methodology, etc for the new UTL stuff in Flex: http://docs.townnews.com/kbpublisher/Flex-Style-guide_9470.html#BLOX_and_Git

Have you tried using article assets and using the audio assets as children of those articles? That'd probably work well for you

I'm not too familiar with Slack integration specifically, but from the Blox side you could probably just use JSON in a search query, searching for the latest article assets.
Something for Zen:
/search/?t=article&s=start_time&sd=desc&d1=1+hour+ago&q=&fmt=json

Or Flex:
/search/?t=article&s=start_time&sd=desc&d1=1+hour+ago&q=&format=json

You can test some changes by saving (but not publishing) them, then using "SIte Preview" in the bottom-right of the Blox admin panel.


It's not perfect, but it works to verify most changes.