Add Elevate support to hs project create and helpful info for hs fetch

[joeyblake]

Description and Context

The new HubSpot Elevate theme requires a HubSpot project to run. This feature consists of 3 parts.

1. An update to HubSpot project components for configuration to spin up a new hs project with the Elevate theme as a starting point.

2. An update to hs project create that will create a new HubSpot project with no-template and then hs fetch the Elevate theme into the newly scaffolded project. This also includes a helpful error message in the event that fetching fails to get all of the files the first time.

3. A message and **prompt when attempting to hs fetch @hubspot/elevate to let the user know that Elevate requires a project to work, that allows the user to continue fetching the files if desired,

or abort the fetch, where the cli shows a message to `hs project create` to get started.

** If the fetch destination is already an HS project, this prompt will not show and fetching with proceed as normal.

To test

• Pull this branch
• fetching - from the root of this directory run yarn hs fetch @hubspot/elevate <somedestination that is not a project>
• fetching to a project folder - from the root of this directory run yarn hs fetch @hubspot/elevate <somedestination that is in a project folder> <- nested folders of a project will work too
• create - from the root of this directory run yarn hs project create --templateSource "joeyblake/hubspot-project-components" the templateSource will stub in the elevate option into the project create choices.

TODO

Who to Notify

@TanyaScales @jsines

[jsines]

In the case of hs fetch @hubspot/elevate outside of a project folder - instead of "Would you like to continue fetching without creating a project? [y/N]", would it be feasible to ask "Would you like to create one? [Y/n]", and then "re-route" them to the hs project create flow without making them retype a command?

Otherwise code seems good!

[kemmerle]

You can use the uiAccountDescription util here to format the command.

[kemmerle]

@joeyblake, out of curiosity, why didn't you include the elevate theme template in the hubspot-project-components repo? Do you want to keep the source code off GitHub? Or are you concerned about keeping the theme updated?

[joeyblake]

@joeyblake, out of curiosity, why didn't you include the elevate theme template in the hubspot-project-components repo? Do you want to keep the source code off GitHub? Or are you concerned about keeping the theme updated?

Oh, we're going to, the PR is here 😁 .

[bmatto]

Love it.

[kemmerle]

@joeyblake, I meant that you can move the source code for the Elevate theme directly into the hubspot-project-components repo and download it directly from that repo, as we do with private and public app sample templates. That would save you from having to download a blank template and then downloading the elevate theme separately, unless you don't want to maintain the latest version of the theme in another repo.

EDIT: Nevermind! This comment became moot after the CMS Sync today (10/8). I think the Elevate theme has too many files for the GitHub endpoints to handle reliably.