MokoConsulting/MokoOnyx
1
0
Fork 0
Code Issues 10 Pull Requests 1 Releases 3 Wiki Activity

Release: dev ? main � metadata footer, auto-minify, print view, CI overhaul #24

Merged
jmiller merged 2 commits from dev into main 2026-05-16 01:09:32 +00:00
Conversation 0 Commits 2 Files Changed 2
+11 -14
jmiller commented 2026-05-16 01:09:17 +00:00
Owner
Copy Link
Copy Source

Summary

  • Article metadata footer � Renders Joomla custom fields as a styled footer on article layouts, grouped by field group
  • Auto-minification � user.css, user.js, and custom theme files auto-minified via MokoMinifyHelper
  • Component/print-view overhaul � Dedicated component.css, GA4 print tracking, custom light theme support, footer removed
  • User override files � user.css/user.js replace custom_head_start/custom_head_end params (loaded via Web Asset Manager)
  • Media folder cleanup � Install/update script removes stale .min files, deprecated assets, unminified vendor CSS
  • Asset registry simplified � Duplicate .min entries removed from joomla.asset.json; Joomla auto-resolves .min when debug is off
  • Font Awesome vendor trimmed � Removed 21k+ lines of unminified CSS; assets point to .min.css only
  • Migration cleanup � Removed migration tab, description callout, and custom code fieldset from template config
  • CI additions � PHPStan static analysis, Gitleaks secret scanning, CSS sync workflow
  • Workflows migrated � All CI/CD moved from .gitea/ to .mokogitea/ with template sync + issue templates

Test plan

  • Install/update template on Joomla 5.x � verify media cleanup runs
  • Verify component.php print view renders without footer, with component.css
  • Confirm article metadata footer appears when custom fields are set
  • Check user.css/user.js load after all other assets
  • Verify auto-minification generates .min files on first page load

?? Generated with Claude Code

## Summary - **Article metadata footer** � Renders Joomla custom fields as a styled footer on article layouts, grouped by field group - **Auto-minification** � `user.css`, `user.js`, and custom theme files auto-minified via MokoMinifyHelper - **Component/print-view overhaul** � Dedicated `component.css`, GA4 print tracking, custom light theme support, footer removed - **User override files** � `user.css`/`user.js` replace `custom_head_start`/`custom_head_end` params (loaded via Web Asset Manager) - **Media folder cleanup** � Install/update script removes stale `.min` files, deprecated assets, unminified vendor CSS - **Asset registry simplified** � Duplicate `.min` entries removed from `joomla.asset.json`; Joomla auto-resolves `.min` when debug is off - **Font Awesome vendor trimmed** � Removed 21k+ lines of unminified CSS; assets point to `.min.css` only - **Migration cleanup** � Removed migration tab, description callout, and custom code fieldset from template config - **CI additions** � PHPStan static analysis, Gitleaks secret scanning, CSS sync workflow - **Workflows migrated** � All CI/CD moved from `.gitea/` to `.mokogitea/` with template sync + issue templates ## Test plan - [ ] Install/update template on Joomla 5.x � verify media cleanup runs - [ ] Verify `component.php` print view renders without footer, with component.css - [ ] Confirm article metadata footer appears when custom fields are set - [ ] Check user.css/user.js load after all other assets - [ ] Verify auto-minification generates .min files on first page load ?? Generated with [Claude Code](https://claude.com/claude-code)
jmiller added 2 commits 2026-05-16 01:09:17 +00:00
Removed footer position from component.php d2e27f1735
docs: update CHANGELOG with complete unreleased changes 58960fd17d 
Add missing entries for article metadata footer, auto-minification,
media folder cleanup, FA vendor simplification, asset registry cleanup,
CI additions, and workflow migration to .mokogitea/.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit 78993efd9b into main 2026-05-16 01:09:32 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 patch-release
Patch version release
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 release-candidate
Release candidate build
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Type —
Status —
Priority —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoOnyx#24
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?