=== Content Vsibility ===
Contributors: iamfriendly
Donate link: https://girlswhocode.com/
Tags: block, content, visibility
Requires at least: 5.0
Tested up to: 5.6
Stable tag: 0.1.2
Requires PHP: 7.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Decide when, where, and to whom your blocks are visible.

== Description ==

Content Visibility provides a set of controls to say whether each discrete piece of content (or 'block' in WordPress parlance) should be shown to users who are signed in to your site or not. Additional add-ons provide controls for [**role-based**](https://github.com/richardtape/content-visibility-user-role) visibility and [**time-based**](https://github.com/richardtape/content-visibility-date-and-time) visibility.

## Individual Block Controls

Every individual block on all posts and pages on your site can have their own controls. Mix and match the visibility of blocks on a single page. Need some blocks to show to everyone and a few to only be available to your site's subscribers? No problem. Only want a message to appear on Christmas Day? You got it. Only want those who are signed in to your site to see certain pieces of content? Easy peasy.

## At a glance

An icon next to each block with active rules allows your content authors to see which blocks may or may not be shown to certain audiences at a glance.

## Reusable blocks

Use Reusable Blocks? No problem, Content Visibility handles those too.

## Columns and Nested Blocks

Do you use columns and put other blocks in them? Content Visibility allows you to control both the 'nested' blocks (such as a paragraph block in a column block) or the 'parent' block themselves (perhaps hide an entire column for users who aren't signed in?). Other examples of nested blocks are the Group Block or if you use an accordion or tabs block; all work!

## Coming Soon

 - [ ] Make content visibility controls available on public Custom Post Types by default
 - [ ] Ensure this works with the new 'widgets' screen (controls appear but functionality is currently blocked by [this gutenberg bug](https://github.com/WordPress/gutenberg/issues/27173))
 - [ ] REST API exploration. Should be fine for non-authenticated requests, but need to dive deeper for auth'd requests
 - [ ] Non-trivial dates. Think things like "Every Wednesday between 3pm and 4pm" or "First two weeks in November"
 - [ ] Geolocation: Show this block only to users whose connection is in France
 - [ ] Specific Users: Only show a block when a specific user is signed in
 - [ ] Do you have any feature requests? [Let me know!](https://github.com/richardtape/content-visibility/issues/new)

## Development

Development is mostly done on [github](https://github.com/richardtape/content-visibility) and releases are made there and here to the WordPress plugins directory.

== Frequently Asked Questions ==

= Got a question? =

Let me know: https://github.com/richardtape/content-visibility/issues/new

== Changelog ==

= 0.1.2 =
* Turns out 0.1.1 wasn't the first public release because I didn't have the deploy script set up. Brilliant work, Rich.
* Added a 'content_visibility_replace_block_content' filter to allow add-ons to filter what a 'removed' block is replaced with.
* Added a 'content_visibility_replace_nested_block_content' filter to allow add-ons to filter what a 'removed' nested block is replaced with.

= 0.1.1 =
* First public release. Check out the Date and Time Add-on and Role Add-on too!

= 0.1.0 =
* Was meant to be the first public release, but caught a few things (most notably that I had been beaten to the punch on the name of the plugin)

== Upgrade Notice ==

None yet.