feat(css): extend hero-overlay effects to banner-overlay.custom-hero #7
No Reviewers
Labels
Clear labels
automation
breaking-change
build
ci-cd
config
css
dependencies
deploy-failure
docker
documentation
dolibarr
generic
good first issue
health-check
health: excellent
health: fair
health: good
health: poor
help wanted
html
javascript
joomla
major-release
minor-release
mokostandards
needs-review
patch-release
php
push-failure
python
release-candidate
security
size/l
size/m
size/s
size/xl
size/xs
size/xxl
standards-drift
standards-update
sync-failure
sync-report
template-validation-failure
tests
type: bug
type: chore
type: enhancement
type: feature
type: refactor
type: version
typescript
version
version-drift
work-in-progress
bug
chore
documentation
enhancement
feature
pending: dependency
pending: deployment
pending: design
pending: documentation
pending: feedback
pending: review
pending: testing
priority: critical
priority: high
priority: low
priority: medium
refactor
roadmap
scope: client
scope: dolibarr
scope: infrastructure
scope: joomla
scope: waas
security
status: blocked
status: duplicate
status: in-progress
status: needs-review
status: wontfix
Automated processes or scripts
Breaking API or functionality change
Build system changes
CI/CD pipeline changes
Configuration file changes
CSS/styling changes
Dependency updates
Automated deploy failure tracking
Docker configuration changes
Documentation changes
Dolibarr module or extension
Generic project or library
Good for newcomers
Repository health check results
Health score 90-100
Health score 50-69
Health score 70-89
Health score below 50
Extra attention needed
HTML template changes
JavaScript code changes
Joomla extension or component
Major version release
Minor version release
MokoStandards compliance
Awaiting code review
Patch version release
PHP code changes
File push failure requiring attention
Python code changes
Release candidate build
Security-related changes
Large change (101-300 lines)
Medium change (31-100 lines)
Small change (11-30 lines)
Extra large change (301-1000 lines)
Extra small change (1-10 lines)
Extremely large change (1000+ lines)
Repository drifted from MokoStandards
MokoStandards sync update
Bulk sync failure requiring attention
Bulk sync run report
Template workflow validation failure
Test suite changes
Something isn't working
Maintenance tasks
Enhancement to existing feature
New feature or request
Code refactoring
Version-related change
TypeScript code changes
Version bump or release
Version mismatch detected
Work in progress, not ready for merge
Something is not working
Maintenance and housekeeping
Documentation improvements
Improvement to existing functionality
New feature or request
Blocked by another issue or external dependency
Tested and approved, awaiting deployment to production
Needs UI/UX or architecture design before implementation
Feature works, needs documentation/wiki update
Awaiting feedback or decision from stakeholder
Implementation complete, awaiting code review
Feature implemented but not yet tested
Must fix immediately
Should fix soon
Nice to have
Fix when convenient
Code restructuring without behavior change
Planned feature or enhancement tracked on the roadmap
Client-specific work
Dolibarr modules and customizations
Server, CI, backups, monitoring
Joomla templates and extensions
MokoWaaS platform
Security vulnerability or hardening
Waiting on external dependency
Duplicate of another issue
Being worked on
Ready for review
Will not be addressed
No labels
Type
—
Status
—
Priority
—
Milestone
No items
No Milestone
Assignees
jmiller (Jonathan Miller)
Clear assignees
jmiller (Jonathan Miller)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: MokoConsulting/MokoOnyx#7
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
.hero-overlaypseudo-element layering (scaled bg image, radial blur softening, glass-effect overlay panel) to.banner-overlay.custom-herohero.phplayout override insidecontainer-bannerto receive the same visual treatment as the standalone hero-overlay systemTest plan
custom-heroclass displays the blur softening and glass overlay.hero-overlayusage is unaffected🤖 Generated with Claude Code
- Add scripts/minify.js using clean-css and terser - Add "Setup Node.js" and "Minify CSS and JS" steps to both .gitea and .github release workflows (runs before packaging) - Add src/media/{css,js}/*.min.{css,js} to .gitignore - Remove tracked .min files from the repo (vendor/ untouched) This eliminates noisy diffs on generated files and ensures the release ZIP always contains freshly minified assets. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>