I have a couple sites on Google and since they sold to square space I thought I’d try to keep my stuff there. But I can’t figure it out. Square space is a site builder with a GUI and I can’t find anywhere to just deploy my site to them as a react app. I have found a few areas where I can add some code, but they are for specific areas of the provided templates. I’ve even tried to use developer mode, but it looks like you still need to follow their template rules to get anywhere.

It’s been a huge headache, Google made it so easy.

  • ɔiƚoxɘup@beehaw.org
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    They’re supposed to have amazing customer service. Ask them. I bet good money that you can’t do what you’re trying to do though. Best of luck to you.

    • reric88🧩@beehaw.orgOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Thanks! I kind of figured it out after a lot of searching and trial and error.

      I removed all but one page, and removed all content on that page. In website settings, there’s an option for “code injection”. This is where I pasted all my code, but I had to do it in a weird way.

      I built the website with React, and each page was it’s own component. I had to build the project, and then take all of the JS created from the build process and wrap them in script tags, and wrap the CSS in style tags. Then I had to make a div with an id of root within the code injection body. Afterwards, I copied and pasted all the JS and CSS under the root div.

      It’s not perfect and I need to tweak some things, but the site is 90% intact.

  • kambusha@feddit.ch
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    Can’t comment on square space, but you could maybe try firebase (google), github pages, or netlify as alternatives?

    • Gamma@beehaw.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      You can (or at least could ~5 years ago) easily serve a static site through an s3 bucket

        • Gamma@beehaw.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          True, though I think GutHub does need a paid account if you want the repo to be private

          • MJBrune@beehaw.org
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            1 year ago

            Yeah, I mean if it’s a static website unless it’s using a generator, the source is accessible by just visiting the website. So having it public shouldn’t matter too much, right? Even if it’s using a generator, it’s not like what you are writing is secret. That said I use GitLab and Hugo on a private repo. I have no reason to make it public and all the highly experienced web developers told me it simply doesn’t need to be public so why make it public?

            • Gamma@beehaw.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Good point! I rarely use plain static pages, there’s usually some templating involved if I’m going through GH pages.

    • reric88🧩@beehaw.orgOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I actually started looking at firebase today. I’m confused by it, but that’s the case with everything new to me.

      • kambusha@feddit.ch
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        You’ll want to create a new firebase project, install the firebase CLI on your computer and then use the CLI to: login to firebase, select the project you created, and then using the CLI run firebase deploy wherever your code is. That should use firebase “hosting” to serve your static files.

        I find Google Cloud’s documentation extremely confusing (including firebase), so you’re not alone on that front. Took a lot of searching & troubleshooting to finally get my setup working as I intended.