# How to organize your files on your Meteor projects

DevFeed: [How to organize your files on your Meteor projects](<https://devfeed.tech/articles/how-to-organize-your-files-on-your-meteor-projects-34697.md>)

Original publisher: [Read original article](<https://medium.com/unexpected-token/how-to-organize-your-files-on-your-meteor-projects-ef7f34373ed?source=rss----2d2624499d2---4>)

Author: Vianney Lecroart

Published: 2015-05-07T15:13:56Z

Content type: tutorial

Language: en

Sources: [eFounders](<https://devfeed.tech/sources/efounders.md>)

Topics: [Meteor](<https://devfeed.tech/topics/meteor.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>)

Tags: [developer](<https://devfeed.tech/tags/developer.md>), [files](<https://devfeed.tech/tags/files.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [meteor](<https://devfeed.tech/tags/meteor.md>), [meteorjs](<https://devfeed.tech/tags/meteorjs.md>), [structure](<https://devfeed.tech/tags/structure.md>)

## AI overview

The article discusses how to organize files in Meteor projects. It explains Meteor's file-loading priorities and alphabetical ordering, then shares the author's experience and reasons for preferring task-oriented file grouping over a Ruby on Rails-style structure.

## Source excerpt

illustration by Adrien Griveau I have been working on Meteor projects for more than 2 years now. I already shared the reasons of this choice in a previous post. Today I want to address the question of file structure. Unlike frameworks such as Ruby on Rails, which has clear instructions on how files should be organized, Meteor lets you decide how you want to structure them. It only sets a handful of rules on files priorities. For instance, files inside a directory called lib are always added above all other files. Also, Meteor sorts all files in alphabetic order. But this autonomy leaves first-time users with a lot of questions, as you can see on StackOverflow or on Meteor's forum. Obviously, the topic is hot. Abigail Watson, a well-known developer in the Meteor family, wrote an article about it. In her awesome Meteor cookbook, she dedicated a section to describe the different file structures, depending on your project. As you can see, there's more than one solution. So, how do you set up the right structure for your project? Here are my thoughts and return on experience based on the different projects I run at eFounders. Why I decided not to follow the Ruby on Rails file structure Meteor evangelist Josh Owens (if you don't know him, he's the guy behind Meteor news site crater.io, The Meteor podcast, and The Meteor club) reuses part of the directory structure used in Ruby on Rails. But as he explained in this article, his main reason for doing so being "having spent 9+ years working with that framework", it didn't convince me (no offense Josh). Going a step further, here are my reasons not to use the Ruby on Rails file structures. First, it generates too many small files and directories. You end up with tenths of open tabs, and switching between tabs can very quickly become annoying. Second, I almost always work on a specific task on a specific part of the app (let say the comment system of a blog). Therefore, I like to have all files related to this task close to ea