1

so I am new to Craft CMS, and would like to understand the Craft developer workflow.

Currently I have been developing on EpiServer using C# in Visual Studio. We have a dev, staging and production environment hosted on Azure.

My current workflow is that when I need new fields or properties, I create them in code. Then I can build html/javascript/etc features that use these fields. And push them through GIT to the development server and from there through Azure deploy the changes to staging and then to production.

Is something similar possible with Craft? I mean is there a "Craft way" of creating fields through code? So that one can push these changes to staging for example and have the fields and html/js/css appear there for testing and then push them on to production?

1 Answer 1

3

Craft gives you the 'best of both worlds' in this regard with the project config. You can just create fields, sections and entry types through the interface. Every change you make is automatically saved to a declarative config in the form of YAML files in your config folder. Then you can commit the project config directory to git, deploy those in your other environments and use console commands to apply the configuration.

You can read more here:

1
  • 1
    Great resources thank you.
    – BrokenCode
    Jan 26 at 11:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.