=== Dulcie ===

Contributors: templatesell
Theme URI: https://www.templatesell.com/item/dulcie/
Author URI: https://www.templatesell.com/
Tags: blog, custom-background, custom-logo, custom-menu, featured-images, threaded-comments, translation-ready
Requires at least: 6.0
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.4
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Free WordPress Blog theme.

== Description ==

Free WordPress Blog theme.

== Installation ==

1. In your admin panel, go to Appearance > Themes and click the Add New button.
2. Click Upload Theme and Choose File, then select the theme's .zip file. Click Install Now.
3. Click Activate to use your new theme right away.

== Frequently Asked Questions ==

= Does this theme support any plugins? =

dulcie includes support for WooCommerce and for Infinite Scroll in Jetpack.

== License ===

License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Dulcie is premium WordPress theme by, Template Sell.
Dulcie Plus is distributed under the terms of the GNU GPL v2 or later.

== Changelog ==
= 1.0.4 - August 24 2026 =

Fixed
* The theme defined and read a constant called LIVELY_S_VERSION - the name belongs to a different theme this one was built from. It is guarded with if ( ! defined() ), so had anything else in the install defined that name first, this theme would silently have versioned its assets from someone else's number. The value was also 1.0.2 while style.css said 1.0.3
* Links measured 2.30:1 against white. style.css sets a readable colour; assets/css/main.css loads afterwards, restates the same bare `a` selector and overrode it with #ababab. Links are #6f6f6f now, 5.03:1
* The comment submit button was white text on #0db3e3, which measures 2.45:1 - and its hover state then halved the whole button's opacity, taking it to roughly 1.5:1. The accent is #0a7fa3 now, 4.59:1 behind white, and hovering darkens the button instead of fading it
* The comment form's name and email fields opened a grid row that the website field closed, and the website field was keyed "website" where WordPress keys it "url". WordPress removes those three fields for a logged-in reader by their standard keys, so it removed the two that opened the row and kept the one that closed it - a logged-in reader got a stray column and an unmatched closing tag
* The comment form dropped the cookie-consent checkbox entirely, and the stylesheet hid the row as well, so "Show comments cookies opt-in checkbox" in Settings > Discussion had no effect and a plugin restoring the field would have found it invisible
* The comment fields had no labels at all - only placeholders, which are not accessible names and disappear as soon as anything is typed
* The site identity was output twice in the same document, once in the mobile bar and once in the sidebar panel, so every front page had two H1 elements with the same text and two copies of the logo
* The comments heading opened <h2> and closed </h3>, and comment counts printed nothing at all when a post had no comments: comments_number() was passed null for the zero case, where the documented "use the default" value is false
* The comment count on every post was wrapped in a link to "#" with an empty title attribute - an anchor that goes nowhere. On an archive listing ten posts that is ten links a keyboard user tabs through for no reason. They point at the post's comments now
* A stray closing </i> after the category icon in the post meta line
* The text domain was loaded without being told where the language files are
* The widget script was registered with true as wp_register_script()'s fourth argument. That argument is the version, not the in-footer flag, so the version became "1" and the script loaded in the header

Accessibility
* Keyboard focus had no styling of its own anywhere in the theme
* The submenu toggle was a <span> with a click handler - not focusable, and deaf to Enter and Space, so submenus could not be opened by keyboard. It is a button now, and reports its state with aria-expanded
* The mobile menu button toggled the panel without ever saying whether it was open, and was unlabelled. Escape closes the panel now
* The menu close control was a <div> inside a javascript:void(0) anchor, and announced as an empty link
* Added prefers-reduced-motion handling

Performance
* Removed 3.4 MB of font files. The theme shipped two complete icon sets in five formats each: SVG (2.3 MB) for iOS Safari 4 and Android 2, TrueType (568 KB) for Android below 4.4, and EOT (492 KB) for Internet Explorer 8 - none of which can run a current WordPress. WOFF2 with WOFF as a fallback covers every browser that can, and nothing renders differently. FontAwesome.otf, a desktop font file referenced by no stylesheet, went with them
* Nunito Sans is served from the theme instead of Google. It was requested on every page view over a protocol-relative URL with no version, in eight faces where the stylesheet uses five
* Removed js/navigation.js. It is the Underscores navigation script; it looks for an element with id="site-navigation", which this theme's markup has never had, so it was downloaded and parsed on every page view and returned on its first statement every time
* Removed a scroll handler that ran an unthrottled jQuery selector for .main-header, a class that appears nowhere in the theme
* Bootstrap was versioned 4.5.0 where it is 4.5.2, Font Awesome 4.5.0 where it is 4.6.3, and main.css was given "4.5.0" as well - the Bootstrap number copied down the list, so main.css never cache-busted when the theme changed it

Editor
* Added editor styles. The theme shipped without any, so writing a post looked nothing like reading one
* Added three block styles - Lead paragraph, Boxed and Plain - and three block patterns
* Dropped add_theme_support() for experimental-link-color and custom-units, both long removed from WordPress

Other
* Two core filters had been renamed with a theme prefix, so no plugin could reach the comment fields or the logout redirect through the documented hooks
* Corrected the readme: the stable tag said 1.0.0 where the theme was on 1.0.3, and the PHP requirement said 5.6
* Added languages/dulcie.pot
* Tested up to WordPress 7.1

= 1.0.3 - April 17 2023 =
* Theme URI added

= 1.0.0 - February 22 2023 =
* Initial release on TemplateSell


== Credits ==

Based on Underscores https://underscores.me/, (C) 2012-2020 Automattic, Inc., [GPLv2 or later](https://www.gnu.org/licenses/gpl-2.0.html)

normalize.css https://necolas.github.io/normalize.css/, (C) 2012-2018 Nicolas Gallagher and Jonathan Neal, [MIT](https://opensource.org/licenses/MIT)

Color pallette is from Twenty Twenty One theme - GPL License

Font-Awesome https://github.com/FortAwesome/Font-Awesome FontAwesome 4.7.0 Copyright 2012 Dave Gandy Font License: SIL OFL 1.1 Code License: MIT License http://fontawesome.io/license/

Line Awesome 1.3.0 by @icons_8 - https://icons8.com/line-awesome License - https://icons8.com/good-boy-license/ (Font: SIL OFL 1.1, CSS: MIT License)

Bootstrap v4.5.2 (https://getbootstrap.com/)
Copyright 2011-2020 The Bootstrap Authors
Copyright 2011-2020 Twitter, Inc.
Licensed under MIT (https://github.com/twbs/bootstrap/blob/main/LICENSE)

Image for theme screenshot, Copyright Hey Beauti Magazine
License: CC0 1.0 Universal (CC0 1.0) 
License Link: https://stocksnap.io/license
Source: https://stocksnap.io/photo/couple-bedroom-WECVMB2SHH
Source: https://stocksnap.io/photo/black-family-HZSUPYGKDJ
Source: https://stocksnap.io/photo/girl-friends-3YF2EP4KOA
Source: https://stocksnap.io/photo/people-back-MFFX4ZPUMM
