Skip to content

Document CSS and frontend asset build workflow#505

Open
promptless-for-oss wants to merge 9 commits into
mautic:7.2from
Promptless:promptless/pr-16143-scss-build
Open

Document CSS and frontend asset build workflow#505
promptless-for-oss wants to merge 9 commits into
mautic:7.2from
Promptless:promptless/pr-16143-scss-build

Conversation

@promptless-for-oss

Copy link
Copy Markdown
Contributor

Open this suggestion in Promptless to view citations and reasoning process

Add documentation for the new SCSS build workflow using SymfonyCasts Sass Bundle, replacing the previous Grunt/LESS approach. Covers development commands (sass:build, sass:watch), production asset generation, and Symfony Asset Mapper architecture.

Trigger Events


Tip: Tell your friends working on non-commercial open-source projects to apply for free Promptless access at promptless.ai/oss ❤️

@@ -0,0 +1,52 @@
Building CSS and frontend assets

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR #16143 migrates Mautic from LESS + Grunt to SCSS built with SymfonyCasts Sass Bundle. Key commands added: composer sass:build, composer sass:watch. Bootstrap now comes from twbs/bootstrap-sass Composer package instead of npm.

Source: mautic/mautic#16143

@adiati98 adiati98 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@promptless-for-oss please address the suggestions

Comment thread docs/development-environment/building_assets.rst
Comment thread docs/development-environment/building_assets.rst Outdated
Comment thread docs/development-environment/building_assets.rst
Comment thread docs/development-environment/building_assets.rst Outdated
Comment thread docs/development-environment/building_assets.rst
Comment thread docs/development-environment/building_assets.rst
Comment thread docs/development-environment/building_assets.rst Outdated
Comment thread docs/development-environment/building_assets.rst
@adiati98 adiati98 added this to the 7.2 milestone May 31, 2026
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Done! I've addressed all the review feedback:

  1. Capitalized "Assets" in headings and text where referring to the Mautic feature
  2. Capitalized "UI Components" in the intro text
  3. Added vale off/on around "Building SCSS during development" heading
  4. Replaced "recompiles" with "rebuilds CSS automatically" to resolve the Vale error
  5. Clarified Asset Mapper compilation locations (now specifies var/assets/ and public/assets/)
  6. Added vale off/on around the final paragraph that refers to general assets in the Symfony context

@adiati98 adiati98 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@promptless-for-oss please address the suggestions

Comment thread docs/development-environment/building_assets.rst Outdated
Comment thread docs/development-environment/building_assets.rst
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Done! Added vale off/on around the "Building Assets for production" heading.

@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Thanks for the follow-up! This is already addressed in the latest commit (d6638df). The phrase "finalized assets" on line 62 refers to general frontend assets (CSS/JS files), not the Mautic Assets feature, so I wrapped it in vale off/on directives (see lines 60-64). You may need to refresh the PR diff view to see the updated file.

Let me know if you have any other concerns!

Comment thread docs/development-environment/building_assets.rst
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Fixed! Added vale directives around the "Importmap" term since it's a standard web/Symfony technical term for JavaScript module import maps.

Comment thread docs/development-environment/building_assets.rst Outdated
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Thanks for the suggestion! I've added "Importmap" to the Vale vocabulary file and removed the vale directives around that term. This is a cleaner approach than using inline vale statements.

@adiati98

adiati98 commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

@promptless-for-oss please rebase to 7.2 branch

promptless Bot added 5 commits June 4, 2026 10:37
Document the SCSS build workflow using SymfonyCasts Sass Bundle that replaces
the previous Grunt/LESS approach. Covers development commands (sass:build,
sass:watch), production asset generation, Bootstrap source location, and
Symfony Asset Mapper architecture.
- Capitalize "Assets" when referring to Mautic feature
- Capitalize "UI Components" in intro text
- Add vale off/on directives around SCSS heading and general asset text
- Replace "recompiles" with "rebuilds CSS automatically"
- Clarify Asset Mapper compilation output locations
Address reviewer feedback to add vale off/on around the
"Building Assets for production" heading.
Wrap the Asset architecture section heading and the paragraph containing
"Importmap" with vale off/on directives to suppress the Vale spelling error.
Add "Importmap" to the Vale accept.txt vocabulary file since it's a
standard web/Symfony technical term. Remove the vale off/on statements
that were wrapping references to Importmap in the building_assets.rst
documentation.
@promptless-for-oss promptless-for-oss force-pushed the promptless/pr-16143-scss-build branch from 94cf806 to 97ff276 Compare June 4, 2026 10:37
@promptless-for-oss promptless-for-oss changed the base branch from 7.0 to 7.2 June 4, 2026 10:38
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Done! I've rebased the branch onto 7.2 and updated the PR base branch accordingly.

Comment thread docs/development-environment/building_assets.rst
All uses of 'asset' in building_assets.rst refer to Symfony's Asset
Mapper and generic frontend assets (CSS, JavaScript files), not
Mautic's Asset feature (downloadable marketing files). Use lowercase
consistently per reviewer feedback. Renamed the 'Asset architecture'
section to 'Asset Mapper architecture' for clarity.
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Good catch! All uses of "asset" in this file refer to Symfony's Asset Mapper and generic frontend assets (CSS, JavaScript files), not Mautic's "Asset" feature (downloadable marketing files).

I've updated the document to use lowercase "assets" consistently for the Symfony frontend concept, and renamed the section heading from "Asset architecture" to "Asset Mapper architecture" to make the distinction clearer. The capitalized "Asset Mapper" is retained since that's the proper name of the Symfony component.

Comment thread docs/development-environment/building_assets.rst
Adds vale directives to suppress linting for the paragraph where "assets"
refers to generic Symfony frontend assets rather than Mautic's downloadable
files feature.
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Thanks @adiati98! I've applied your suggestion and wrapped the paragraph in vale off/on directives. The change has been pushed to the branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants