The New Way to Build with AI! Introducing ReUI — the developer platform for agentic UI with shadcn/ui
Browse ReUI Pro

How should I organize static files and external resources?


I’m working with Metronic 9 and Tailwind and I’m trying to keep the project structure clean as the number of static resources increases.

I understand the basic Metronic structure, but I’m not completely sure about the best way to organize additional files that are not directly part of the UI components. For example, if a project contains documentation, configuration references, downloadable resources, and other static files, should these remain inside the main assets structure or should they be kept separately?

I’m mainly concerned about avoiding unnecessary duplication and making sure that future updates to Metronic don’t make the custom resource structure difficult to maintain.

Is there a recommended folder structure or best practice for handling these kinds of external/static resources in Metronic 9 with Tailwind?

I’ve also been comparing different approaches to organizing PS2 emulator-related documentation and system-file references, and this resource helped me understand how those files can be categorized separately:

I’d appreciate any recommendations from developers who have maintained a Metronic project with a large number of custom static resources.


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 (0)