Super Sale Limited Time 50% OFF for All-Access Plans
Save 50% Now

Step-by-step guide for updating


Is there any documentation or step-by-step guide for updating a large project that already uses version 9.1.2 of the Metronic Tailwind template?


Text formatting options
Submit
Click any option to insert into your comment. Select text first to wrap it.
  • **text** to make things bold
  • *text* to emphasize
  • ### Heading to make headings
  • [link text](url) for links
  • ![alt text](image-url) to paste in an image
  • - item to make a list
  • 1. item to make an ordered list
  • > quote to quote somebody
  • `code` for single line of code
  • ```js ... ``` for JS code block
  • ```html ... ``` for HTML code block
  • ```scss ... ``` for SCSS code block
  • ```php ... ``` for PHP code block
  • --- for a horizontal rule
  • happy  :)
  • shocked  :|
  • sad  :(

Replies (2)


Hi

We don’t have a single official upgrade step-by-step doc. The approach below outlined is the one we recommend:

Check the Metronic Tailwind changelog for every version.

Download a fresh copy of the latest Metronic Tailwind and compare folder structure, config files (e.g. Tailwind, Vite/build), and dependencies with your project.

You can start by replacing the core assets folder if you not customised it.



I haven’t seen an official step-by-step guide specifically for updating large projects from Metronic Tailwind 9.1.2 to a newer version, but here’s a reliable approach that many developers use:

Check the changelog/release notes for each version between 9.1.2 and your target. This helps you see breaking changes and required steps.

Create a fresh install of the latest Metronic Tailwind and compare folder structure, config files, and dependencies with your project.

Update dependencies gradually (e.g., Tailwind, plugins) rather than all at once to isolate issues.

Run your project after each step to catch errors early.

Migrate custom components or overrides carefully — merge them into the new structure instead of copying everything blindly.


Text formatting options
Submit
Click any option to insert into your comment. Select text first to wrap it.
  • **text** to make things bold
  • *text* to emphasize
  • ### Heading to make headings
  • [link text](url) for links
  • ![alt text](image-url) to paste in an image
  • - item to make a list
  • 1. item to make an ordered list
  • > quote to quote somebody
  • `code` for single line of code
  • ```js ... ``` for JS code block
  • ```html ... ``` for HTML code block
  • ```scss ... ``` for SCSS code block
  • ```php ... ``` for PHP code block
  • --- for a horizontal rule
  • happy  :)
  • shocked  :|
  • sad  :(
Text formatting options
Submit
Click any option to insert into your comment. Select text first to wrap it.
  • **text** to make things bold
  • *text* to emphasize
  • ### Heading to make headings
  • [link text](url) for links
  • ![alt text](image-url) to paste in an image
  • - item to make a list
  • 1. item to make an ordered list
  • > quote to quote somebody
  • `code` for single line of code
  • ```js ... ``` for JS code block
  • ```html ... ``` for HTML code block
  • ```scss ... ``` for SCSS code block
  • ```php ... ``` for PHP code block
  • --- for a horizontal rule
  • happy  :)
  • shocked  :|
  • sad  :(