Your login page is the first screen many people see of your site, and by default it is the same grey box as everyone else's. Latchkey lets you design it \u2014 colours, background, card, fields, button, typography, logo \u2014 and see the result on the real page while you work.<\/p>\n\n
The preview is the real page.<\/strong> The panel loads your actual It never touches how logging in works.<\/strong> Every form stays the form WordPress rendered, posting where WordPress told it to post. No custom sign-in handling, no password processing, no session code. That is why Latchkey keeps working next to your two-factor and security plugins instead of fighting them \u2014 and why it cannot lock you out.<\/p>\n\n There is no licence key, no trial and no setting that stops halfway. Every template, every colour, every control in this plugin works on every install.<\/p>\n\n The meter is drawn by this plugin but scored by WordPress core, using the zxcvbn library that already ships with WordPress. The calculation happens entirely in the browser. This plugin reads the resulting rating, not the password: it watches the class name core writes and mirrors it onto a segmented bar. No password value is read, stored, logged or transmitted by Latchkey.<\/p>\n\n The meter appears where WordPress creates a password \u2014 the \"set a new password\" screen. It never appears on the sign-in form, where showing an assessment of an existing password would tell you nothing useful.<\/p>\n\n\n No. The plugin never touches authentication. It styles the page around the native forms.<\/p><\/dd>\n It should not. Because the native markup is preserved, plugins that add fields, checks or messages to the login form continue to work; their additions simply inherit the design.<\/p><\/dd>\n The login screen returns to the WordPress default immediately. Nothing is left behind in your theme or in wp-login.php.<\/p><\/dd>\n Yes, inside the admin preview. That preview is restricted to administrators and cannot create accounts.<\/p><\/dd>\n Yes. Plugins that move The stylesheet is a single cached file and the per-site part is about a kilobyte written inline. Nothing is fetched from anywhere else.<\/p><\/dd>\n Yes. Export writes a JSON file of every setting and import reads it back. Uploaded images live in each site's own media library, so pick those again on the new site.<\/p><\/dd>\n\n<\/dl>\n\n\nwp-login.php<\/code> in a frame and updates it as you drag a slider. There is no second rendering path that can drift from what visitors get, so what you approve is what ships.<\/p>\n\nNothing is held back<\/h4>\n\n
What you can change<\/h4>\n\n
\n
Built to behave<\/h4>\n\n
\n
prefers-reduced-motion<\/code>, and offers its own switch for people who want animation off regardless.<\/li>\nAbout the password strength meter<\/h4>\n\n
\n
\/wp-content\/plugins\/<\/code>, or install it through Plugins \u2192 Add New.<\/li>\n\n
Does this change how logging in works?<\/h3><\/dt>\n
Will it conflict with my security or two-factor plugin?<\/h3><\/dt>\n
What happens to my design if I deactivate the plugin?<\/h3><\/dt>\n
Can I preview the registration screen even though registration is closed?<\/h3><\/dt>\n
Does it work with a renamed login URL?<\/h3><\/dt>\n
wp-login.php<\/code> to an address of your choosing still render the same page underneath, so the design applies there too.<\/p><\/dd>\nWill it slow my login page down?<\/h3><\/dt>\n
Can I move my design to another site?<\/h3><\/dt>\n
1.0.1<\/h4>\n\n
\n