Can I change my site's code on GitHub (or in VS Code) and bring it back into Furge?

Yes. Turn on Developer, open Code, and choose Source control beside Files (or press Ctrl+Shift+G). The first Push makes a private repository on your own GitHub with the site's code in a folder called furge: each designed section's HTML and CSS, the shared stylesheet (styles/site.css) and the site's script (scripts/site.js). Change those files anywhere, in VS Code or on GitHub, and push. Back in Furge, Source control shows the commits under Incoming with each file a pull would change; click a file to compare it line by line. Pull brings them into the design as one step, so one Undo takes it back. Untick a file to keep Furge's version. A file changed in both places is asked about: Take GitHub's or Keep mine. A new HTML file in a page's folder becomes a new section at the end of that page, and deleting a section's HTML file removes the section. Changes lists what your next Push sends, with a box for the commit message. Push leaves files Furge didn't write alone, and it's switched off while there's something to pull, so nobody's work is pushed over. Furge cleans HTML from the repository the way it cleans what you type: no scripts or event attributes. The rest of the repository (the app, components and standalone folders) is generated from the design and written again on every push, so change the files in furge instead. Pages are added in Furge, not in the repository. A change made on GitHub shows on the live site once it's pulled into Furge and published.

Steps

  1. Turn on Developer (Shift+D), open Code and choose Source control.
  2. Press Push to send the site's code to GitHub.
  3. After changing files in the furge folder on GitHub, press the refresh button, then Pull.

Also asked as

Related

Still stuck? Ask Furge Help, the round chat button at the bottom right, or contact the Furge team.

← All of Furge's docs