Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

WordPress How to Make a Website with WordPress Installing WordPress The Famous 5-Minute WordPress Install

shareyourpeace
shareyourpeace
3,244 Points
Posted by shareyourpeace
shareyourpeace
3,244 Points

When we upload for local to Remote, why do we upload directly to public_html rather than a project folder ?

This is a question about Strategy and file organization.

If we are going to create more than one word press site, would it not be best if we created remote sub folders named for the different projects ?

It seems odd to have all of these FILES at the top level.

I just would like some feedback. Thanks

2 Answers

Andrew McCormick
Andrew McCormick
17,730 Points
Andrew McCormick
Andrew McCormick
17,730 Points

If you plan on having multiple installs, then yes they would need to be in your subfolder unless you are doing a multisite.

Typically the tutorial is built so that you are expecting to go to www.mydomain.com and be taken to your site, not www.mydomain.com/project01 . OF course you can do that and have redirects setup, but that's not the point of this tutorial.

The setup you describe is exactly what I have for my staging sites with my clients. I have a dev folder on my webserver, and create a new project folder for each client and direct them to that folder while their site is still in production (i.e. www.mydomain/clients/clientsdomain)