Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create branch for Developer Projects starting point #392

Closed
2 tasks done
TanyaScales opened this issue Nov 19, 2021 · 4 comments · May be fixed by #404
Closed
2 tasks done

Create branch for Developer Projects starting point #392

TanyaScales opened this issue Nov 19, 2021 · 4 comments · May be fixed by #404
Assignees

Comments

@TanyaScales
Copy link
Member

Is your feature request related to a problem? Please describe.

In order to support developers with using the CMS Boilerplate as well as Developer Projects, we want to create a starting point that they can go to and spin it up quickly.

Describe the solution you'd like

We'd like to create a permanent branch in the repo the is specifically for this purpose that houses the correct structure for Developer Projects with the CMS Boilerplate in the theme directory. Suggested branch name: cms-boilerplate-developer-projects

Additional context

For now, the app folder of the project should stay empty

Checklist

@jasonnrosa
Copy link
Member

I tossed up a branch for this. One concern/question I would have is that for this change we move essentially all theme files into a new folder so all files will move. I haven't messed around with branches enough to know if it will continue to pick up sub-sequential updates to say src/fields.json now that the file is moved to src/theme/fields.json in this case. I have a couple updates we can test to verify though.

@jasonnrosa
Copy link
Member

Alright this is pretty much good to go - running into a few issues when testing that I will report but besides that I think the actual work here is done.

@jasonnrosa
Copy link
Member

Just an adjustment here - we will be moving forward without the theme folder and will be omitting hsproject.json. We'll essentially be keeping the same folder structure and just be swapping files with HubL over to .hubl. extensions.

@jasonnrosa
Copy link
Member

Going to close this out given the branch is ready (#404) but it won't be merged so this would be considered done for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants