webdevstudios / wds-hero-widget Goto Github PK

Throughout we use code in __ and _e, etc. These need to be processed through sprintf.

If there is a hook to add a part dynamically, we could make this droppable into an area.

Right now we have primary, secondary, and parallaxes. Our main types should be created based on a filter, which also let's user's add other types.

Doesn't look like it always centers (using twentyfifteen here)

• Bump versions: changelog, plugin header, & in class versions

If this thing is not a platform (and it really is), and it's useful to a user, maybe get into wp.org.

Feels out of place in the root.

The idea here is that the overlay should be part of ::before or ::after.

I shouldn't be able to just enter anything there.

For 1.0 we'll set it to the URL they place there, but we can maybe use CMB2 to make these use files from the media library.

[hero ....]Custom Content[/hero]

I'm not seeing the Custom Content in the heros.

I noticed on some themes that I, at times, couldn't override the CSS in place for headings, causing some things to not be centered. There will, at times, require some additional CSS to ensure things center.

Right now it's a bit cluttered and I need to check to ensure these are correct.

I have an issue hen trying to install the plugin. I turns out my site uses a plugin (required by the theme) which already includes CMB2. CMB2 is bootstrapped within the theme's plugin as is, I mean (it seems it comes from the Github master repo), so what changes would I have to make in order to use WDS-Hero-Widget?

Thanks in advance.

The Gruntfile right now is very basic. I was able to get it to compile a .css file in /assets but it seems to be doing a lot more than that.

I'd be awesome if I could get a Grunt master to come in and clean things up. Just want Grunt to generate the .pot files, compile our SASS files into CSS (maybe even minify them), for production.

Just want to get the code up to par.

@gregrickaby made me aware of some standard markup/SCSS that is being used at WDS and we may need to make the markup comply with the changes.

The markup of the old version shouldn't just be junked, maybe there is a way to have multiple versions of markup that we can declare in arguments or something? People have probably already written styles for the markup as it was, so we don't want to bork those if they want the new features of 1.1.

See http://codepen.io/webdevstudios/pen/JGmXwm

Right now they are direct <img> tags, and should be div elements with backgrounds so they can be background-size: cover.