Roots Discourse

Best practices for exporting/importing reusable site blueprint

sage9
#1

Just getting started here and happy to be around great company!

I’m creating a “site blueprint” of sorts for giving to team members to start from. It will be a living blueprint as it’ll be constantly maintained so that when a team member starts a new project they can begin from the newest version of the blueprint.

Working with Trellis/Bedrock/Sage.

What would you guys think is the best way to export and import (both relevant blade/scss/css files &
database) into fresh sage installations?

Hope this makes sense. Let me know if you have any questions!

Thanks,

Brendan

0 Likes

#2

There’s a few different ways you could approach this so I’ll share a few:

  • copy the previous project files and modify to suit the new project
  • maintain your own forks of Trellis, Bedrock and Sage
  • create WP plugins and composer packages for things you want to reuse (e.g. Filters and actions for a plugin that you use on every project)

I use both the last 2 of that list and find it quite useful.

0 Likes

#3

This is great help, thanks!

I began considering yesterday the option of forking & maintaining the root-example-project repo. Seems like the most straightforward way to go for team members since they can simply clone, run composer & yarn, and boot the vm.

I very much needed that confirmation, so thanks again. This community is simply the best.

0 Likes

closed #4

This topic was automatically closed after 42 days. New replies are no longer allowed.

0 Likes