Skip to content

Conversation

@thusc
Copy link
Contributor

@thusc thusc commented Nov 29, 2021

Hi Johan, this is the third step. As a reminder, the branches are multiple-basedirs, then cli, then this one.

thusc added 17 commits November 27, 2021 18:04
This will make it possible to cleanly separate Bedrock's templates from
the user project templates.
This calls the Gulpfile main task, 'build'.
This allows to run `bedrock build` from a directory that contains
content/ but not core/.
The goal is to allow to do something like

  npm install git+https://github.com/thusc/bedrock.git#cli

and have a working Bedrock program.
This supposes that the current directory doesn't have a core Bedrock
install, but instead used a standalone Bedrock program.
This is supposed to contribute to
usebedrock#391.
This one is equivalent to `npm start` in a regular Bedrock install.
@vercel
Copy link

vercel bot commented Nov 29, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/monocompany/bedrock/9VoG32xzv1xVMeVkruW6NcZtWiTN
✅ Preview: https://bedrock-git-fork-thusc-additional-subcommands-monocompany.vercel.app

This commit changes where Bedrock development server is looking for
templates. Instead of using the local core/ directoy, it directs Bedrock
to its own core/ directory.

In addition, to allow styleguide templates to live in the local project,
this commit adds an underscore prefix to the _styleguide/ directory.

(The underscore is used to make sure those .pug files are not part of
the main content processed by the static build.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant