The Global-Single Saga

[grayghostvisuals]

trafficstars

I am in total agreement Mr. @davatron5000 that the global/single stuff is weird and confusing.

Maybe have it header / footer instead?

[grayghostvisuals]

The problem I'm seeing with this naming convention is that 'header' and 'footer' don't actually coincide with their placement. Global seems to be a more appropriate term because 'footer' doesn't actually have anything placed in the footer. The same goes for header, although that actually does get placed in the head but is not scoped globally.

I also feel it's imperative to explain to users that you must inject the script/style tags in order to see the results ...

"Dear awesome person, before making any script/style adjustments you must inject your script and/or style tags with the buttons provided below into your text edit box of choice. Left box for global page scopes and right box for individual page scopes"

... or something similar but the point is explaining the process thoughtfully

As far as the naming conventions here is what I have at the moment...

• Globally Scoped
• Page Specific

[davatron5000]

For right now, single-code and global-code are already global and page specific (or at least they should be). I'm not sure we want to get agro and break backwards compat at this point (mentioned in #1), any breaking of compatibility should be v2.

For v2, the "global scope" is actually a very small use case to me. Typically people employing Art Direction have a generic index of posts, and then the single post is a complete design. So all Art Direction happens on the Single View.

My current thinking is that maybe a CSS & JS field is worth pursuing. Sorta CodePen.io-style CSS & JS panels but with pre-populated style/script tags - getting rid of all the text/button cruft. CSS would get injected on is_single() with wp_enqueue_styles() and the script block would get injected via wp_enqueue_styles() setting the footer flag to true.

But v2 should probably be built out into a separate branch.

[grayghostvisuals]

@davatron5000

"My current thinking is that maybe a CSS & JS field is worth pursuing. Sorta CodePen.io-style CSS & JS panels. -ZOMG! YES!!!!! Love the idea of a CSS box and a JS box. Way easier to understand for authors

"but with pre-populated style/script tags - getting rid of all the text/button cruf" Yes Please

"CSS would get injected on is_single() with wp_enqueue_styles() and the script block would get injected via wp_enqueue_styles() setting the footer flag to true." I'm no ninja on this one so I'll trust you on that

"But v2 should probably be built out into a separate branch." -Do it Dude! Set up a dev branch on this munky so we can start v2