CMS Development

silvacarl
Member

Using the CLI to download existing web site and its assets?

SOLVE

Is there a simple way to use the CLI to download existing web site and its assets?

 

So they can be worked on locally, then re-uploaded?

0 Upvotes
1 Accepted solution
Anton
Solution
Key Advisor | Diamond Partner
Key Advisor | Diamond Partner

Using the CLI to download existing web site and its assets?

SOLVE

Hi @silvacarl

to get things right. HubSpot got templates/layouts and websites/landing-pages/thank-you-pages which are based on those templates/layouts. 

 

You can download/upload

  • templates/layouts
  • assets from the file-manager
  • HubDB tables(if you got them)

via CLI.

 

You can't download/upload pages that are build with the templates/layouts. 

But you can export all websites/landing-pages/thank-you-pages but unfortunately not reupload them back to HubSpot. 

 

Additional information:

You could build yourself an "overengineered" API solution for page editing but this is an overkill imo. ( still in beta right now) 

 

 

To sum up things:

The best-pracitse workflow is:

  • Create templates that you'd like to use mutliple times in CLI/locally and upload them to HubSpot - not every single page needs its own template
  • Build your pages directly in HubSpot - you don't have an easy solution to do this locally

 

 

hope this helps, 

 

best, 

Anton




check
Did my post help answer your query? Help the Community by marking it as a solution



View solution in original post

5 Replies 5
Anton
Solution
Key Advisor | Diamond Partner
Key Advisor | Diamond Partner

Using the CLI to download existing web site and its assets?

SOLVE

Hi @silvacarl

to get things right. HubSpot got templates/layouts and websites/landing-pages/thank-you-pages which are based on those templates/layouts. 

 

You can download/upload

  • templates/layouts
  • assets from the file-manager
  • HubDB tables(if you got them)

via CLI.

 

You can't download/upload pages that are build with the templates/layouts. 

But you can export all websites/landing-pages/thank-you-pages but unfortunately not reupload them back to HubSpot. 

 

Additional information:

You could build yourself an "overengineered" API solution for page editing but this is an overkill imo. ( still in beta right now) 

 

 

To sum up things:

The best-pracitse workflow is:

  • Create templates that you'd like to use mutliple times in CLI/locally and upload them to HubSpot - not every single page needs its own template
  • Build your pages directly in HubSpot - you don't have an easy solution to do this locally

 

 

hope this helps, 

 

best, 

Anton




check
Did my post help answer your query? Help the Community by marking it as a solution



silvacarl
Member

Using the CLI to download existing web site and its assets?

SOLVE

also, what you poinetd to is EXACTLY what we wanted to find!  LOL!  even if it is in beta, we can try it out.

silvacarl
Member

Using the CLI to download existing web site and its assets?

SOLVE

thank you!  i will check out those beta APIs.

 

being able to use all of our production tools, testing locally, and then uploading is what we need to do.  The drag and drop is nice, but we want to create a large site with many custom features, so doing it on a local dev machine is easier, then uploading.

silvacarl
Member

Using the CLI to download existing web site and its assets?

SOLVE

I guess in addition to that, can i develop a site locally and then when its ready upload it?

0 Upvotes
Anton
Key Advisor | Diamond Partner
Key Advisor | Diamond Partner

Using the CLI to download existing web site and its assets?

SOLVE

I wouldn't recomend this. The CLI/local environment shouldn't be used for this.

 

The optimal workflow should - as already mentioned - be:

  1. create a developer account(it's free)
  2. set up a local dev environment
  3. connect the live and dev environment to the local one
  4. develop(and test) a so called theme for your company/project locally 
  5. push it to the dev environment
  6. test it (build some pages with lorem ipsum/try your custom modules...)
  7. optimize the code after the test
  8. return to step6 as long as you want
  9. when finished push the latest state to the live environtment
  10. build pages in the live environment
  11. publish the pages
  12. done

 

hope this helps

 

best, 

Anton




check
Did my post help answer your query? Help the Community by marking it as a solution



0 Upvotes