=== Boosted Front-end Login ===
Contributors:      ProgressionStudios
Tags:              block, forms, login, registration
Requires at least: 6.0
Tested up to:      6.9.1
Stable tag:        1.0.1
Requires PHP:      7.4
License:           GPL-2.0-or-later
License URI:       https://www.gnu.org/licenses/gpl-2.0.html

Boosted Front-end Login

== Description ==

Create Login, Registration, & Lost Password pages using the Block Editor.

[View Demo](https://boosted-login.progressionstudios.com/)

== Features ==
* Add forms to any pages using the block editor
* Login, Registration, & Lost Password pages are created automatically upon plugin activation
* Add custom redirects upon form submissions
* All options are managed within block editor
* Extremely lightweight plugin with no added CSS or JavaScript
* Built-in verification email for registration (New users are placed in "pending" role)

== Contribute ==
Visit the [GitHub repository](https://github.com/ProgressionStudios/boosted-front-end-login) for full source code and to report any bugs.

== Installation ==

1. Install and acivate the "Boosted Front-end Login" plugin.
2. Click to "Add Block" within the block editor to add a new block. 
3. You will find the Login, Lost Password, and User Registration blocks under the heading "Boosted Front-End Login"

== Frequently Asked Questions ==

= How to create custom redirects =

You can adjust the redirects after logging in while editing the Login block. Simply select the block and you will find redirection options on the right editor panel.

= How to change the styling =

This plugin does not include any CSS or JavaScript. All styling is inherited from the theme styling. 

= User Verification pending on Registration =

When registering, users will be placed in a "Pending" role until verified via automated email.

== Screenshots ==

1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`
(or jpg, jpeg, gif).
2. This is the second screen shot

== Changelog ==

= 1.0.01 =
* Tested with WordPress 6.9.1
* Minor maintenance update

= 1.0.0 =
* Initial Release

== Upgrade Notice ==
= 0.1.0 =
* Release