Acquia Source
Known issues and limitations
Adding or deleting components in and Acquia Source site does not automatically trigger a GitHub sync.
Component deletions: Deleting a component in a site does not remove it from GitHub.
Workaround: You must publish an additional change to trigger the sync. Otherwise, the next GitHub push will recreate the deleted component in the site.
Component additions: Adding a new component does not commit it to GitHub.
Workaround: You must manually click Publish, even if only global CSS is the only pending change, to push it to the repository.
For more details, visit GitHub sync.
Safari is currently not fully supported for editing sites.
Acquia Source is not SOC-2 compliant as of General Availability (GA).
Tailwind Directives can be used in the global CSS. However, it is currently not available in the component-specific CSS.
Using Tailwind's square bracket notation to generate classes on the fly with any arbitrary value is not supported when using the @apply directive for inlining utility classes when adding custom utilities.For example, this following code will not work:
Acquia Source@utility gradient-primary {
@apply from-[#2a7b9b] via-[#57c785] to-[#eddd53] bg-linear-to-br;
}Workaround:
@theme {
--color-gradient-1: #2a7b9b;
--color-gradient-2: #57c785;
--color-gradient-3: #eddd53;
}
@utility gradient-primary {
@apply from-gradient-1 via-gradient-2 to-gradient-3 bg-linear-to-br;
}An error occurs if you try to remove a component through the Component Library.
Workaround: Remove the component through the Code component panel.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.