After publishing XT Tailwind for Joomla (anibalsanchez/XT-Tailwind-for-Joomla, XTTJ for short), I have been receiving questions about Tailwind CSS and how to implement it on Joomla. I have summarized them here for future reference. These are the frequently answered questions:
If I build a site with XTTJ, are the other extensions compatible?
No. Most Joomla extensions are currently built based on Bootstrap 2 and jQuery. XT-Tailwind-for-Joomla does not load Bootstrap and jQuery (or any other library or third-party script) to keep the template minimal in the implementation of the original Tailwind CSS distribution.
Are you building a "generic template" with Tailwind?
No. At this point, we are developing several sites using this project (anibalsanchez/XT-Tailwind-for-Joomla) and adapting it to our requirements. Since the toolchain has node, PostCSS, Webpack, and other tools not meant for live sites, then porting XT Tailwind for Joomla to a LAMP site is not possible.
On February 01, 2019, the Lando team released a major update, Lando Is Ready For The Masses With RC2 Release. The article describes how Lando has been growing exponentially and the need for an architecture reorganization to reduce the technical debt and prepare Lando for the future.
A month ago, on May 13, 2019, Tailwind team released 1.0.0, the first stable release of the project. Tailwind has been growing exponentially, and the step of defining a stable API is the most important milestone achieved so far.
At its core, Tailwind offers:
- A clean and simple Utility-first set of tools and syntax to express any design
- A modern toolbox to quickly manage templates
- A consistent approach to achieve the objectives with a lean methodology
I have created a template for Joomla that implements Tailwind CSS. Now, it is the right time to publish the third version of the template that empowers this blog: anibalsanchez/XT-Tailwind-for-Joomla v2.0.3. The template comes with the latest Tailwind CSS version (1.0.3) that has been released after the v1 mark. It is powered by Tailwind, Webpack, PostCSS, PurgeCSS, and CSSNano. The final size of the stylesheet is minimal, 3KB.
In general, Akeeba backups are infallible. I'm used to moving backups between servers blindly, with the kickstart restore or the Unite command line. However, MySQL GEOMETRY fields are a hard case. It seems that MySQL 5.6 - MySQL 5.7 transitions are rough.
Restoring a backup on a MySQL failed due to a POINT field. After searching, it seems that there's no solution, and a POINT field can't be exported and imported between MySQL versions.
# Failed with error: 1416 -- Cannot get geometry object from data you send to the GEOMETRY field
In this particular case, I'm lucky. The extension (JCalPro) that uses the POINT field also stores the original Latitude and Longitude. So, the POINT field "latlng" can be reconstructed with:
- Extly Tech
- Team Leader / Senior Developer
- Empower your project with our web solutions
- Today, working on Laravel, Amazon AWS, and Ionic/ Angular
- A Joomla Volunteer