[Feedback Wanted] Directory structure question

[thefrosty]

Just curious why your /functions/ are located in your /assets/ directory? Shouldn't they be in an /includes/ directory?

Edit from @JeremyEnglert - should the functions be moved from assets/functions to an includes/ directory? This seems to be how many themes have it setup.

[JeremyEnglert]

Some themes use /includes/ others use /assets/, some even use /library/. Unless there is some kind of standard I missed? (Which is likely).

To me, "assets" makes the most sense as they are pieces of code that belong to the theme.

[thefrosty]

Thanks.

To me assets is more CSS, JS, Images. But just wanted to ask the question.

[JeremyEnglert]

That's actually a great point. Definitely something to think about - especially since many themes seem to take that route.

[thefrosty]

Just dropping my 2 cents for what it's worth.

[JeremyEnglert]

I'd love for WP to have some kind of standards/best practices when it came to file structure.

[JeremyEnglert]

Made some changes to the original post to get feedback from more users. 👍

[mrscharf]

I've always thought of includes to indicate server side and assets to indicate front end. Since the functions file uses include() to call up the functions files, it would probably make more sense for them to be in an includes directory.

[anyway]

I'm also slightly irritated that the functions folder is located under assets. I would leave the name "functions", because of the relationship to functions.php, and would place the folder directly into the theme root.

[iamchaka]

I'm still a pup learning WP, but when I worked with another CMS and it was set up just as @mrscharf stated. Is there any other files that would benefit from this? Also are you thinking having the includes folder on the same directory level as parts, assets, etc?

[JeremyEnglert]

@iamchaka - correct! If this change were to happen, the includes directory would be in the root of the theme.

[JeremyEnglert]

This change will happen in the next update.

#185