# More focus on local development **URL:** \ **Category:** Feature Requests\ **Created:** [January 29, 2021, 1:59pm UTC](https://community.kinsta.com/t/more-focus-on-local-development/282 "2021-01-29T13:59:47Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![seb](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/seb/32/210_2.png) [@seb](https://community.kinsta.com/u/seb)\ **Post date:** [January 29, 2021, 1:59pm UTC](https://community.kinsta.com/t/more-focus-on-local-development/282/1 "2021-01-29T13:59:47Z")
Hi devKinsta, First nice work! I used to work with Vagrant (resource heavy), Valet+ (can break on 1000 places) or docker (magic for me). But i like the simple app of devKinsta. But what I miss is a nice place to separate the dev files from the generated files, so the SCSS and JS. Normally I use to work in a themesrc folder where alle the php, scss and javascriptfiles are locatied then I use Node (grunt) or webpack to generate the production files and copy the themefiles to a public folder where a wordpress installation is running. Now I build a test with devKinsta where my dev version is in different folder and that works but it is kinda messy ussing refference like “…/…/devKinsta/public/project/wp-content”. But it works! I would be very happy if I could config the structure of project for example: public/wordpress/ public/content/themes/ etc source/ source/assets/scss And from there I can run a complier or whatever in the root. Thanks for reading! ---
**Author:** ![michael](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/michael/32/31_2.png) [@michael](https://community.kinsta.com/u/michael)\ **Post date:** [January 29, 2021, 4:07pm UTC](https://community.kinsta.com/t/more-focus-on-local-development/282/2 "2021-01-29T16:07:38Z")
Thanks for the feedback @seb ! I’m glad you’re liking DevKinsta 🙂