SSE | Sygnal Site Engine
Community ForumSupport Us!Micro-Consulting
  • Sygnal Site Engine ( SSE )
  • The SSE Architecture
  • What's New
  • Feature Roadmap
    • Component Architecture
    • File Copy & Augmented Builds
    • SA5 Integration
  • Installation & Setup
    • Setup Github Repository
    • Setup Netlify
      • jsDelivr
    • Setup Webflow
    • Advanced Install Notes
      • Creating a Persistent Test Env
      • Add SSE to an Existing Repo
  • Usage Notes
    • Developing with SSE
    • Building & Deploying Code
    • Code Structure
    • Page Router
    • Components
      • Components Future Notes
    • Source Structure & Key Files
      • Utilities
      • Route Dispatcher
      • Infrastructure
      • Usage Notes
    • SCSS
    • Useful Library Additions
      • Adding Libraries
      • Luxon
      • Cookies
      • Core Libraries
      • Extending Capabilities
    • Best Practices
    • Unit Testing
      • Using Google Sheets as a Unit Test Data Source
      • Datetime & Timezone Tests
      • Best Practices
      • Page 1
  • Sygnal Devproxy
    • What is Devproxy?
    • Devproxy Setup
    • Cloudflare Setup
    • Webflow Site Configuration
    • Configurations
      • Controlling deployment flow
    • Future
  • Tech Stack
    • Source Code Repository
    • Visual Studio Code
    • Developer IDE
    • Dev Hosting
    • Code CDN
    • Devproxy
  • Further Development
    • Dev Team Notes
      • Engine Mode
    • Reference Project
    • Future
      • Component Development
      • Reactive State Management
      • Expand Script Loading
    • Devmode
    • CI/CD Discussions
      • Page 2
    • SA5
  • Tools
    • Webflow Designer Notation
  • SPECIAL ENHANCEMENTS
    • cookie.js
    • PostHog
Powered by GitBook
On this page
  • Open the Project
  • Build the Project
  • Test your work, in realitime
  1. Usage Notes

Developing with SSE

The basics of developing with Sygnal Site Engine.

PreviousAdd SSE to an Existing RepoNextBuilding & Deploying Code

Last updated 10 months ago

Open the Project

  • Start VS Code

  • Open a GitHub codespace for your project, or check it out locally with GitHub

  • Make whatever changes you like

Build the Project

Open a terminal CTRL+SHIFT+~

Type;

npm run watch

Click the split plane button, top right of the bottom terminal pane.

Type;

npm run serve

Now, any changes you make to the project will be immediately recompiled when you SAVE, and will be available at the URL.

Test your work, in realitime

Typically we test our changes in the webflow.io staging site. To see your code live, you can make a simple, temporary modification to your library include;

<!-- Site Engine (SSE)
     https://engine.sygnal.com
--> 
<script 
  src1="https://mysite.netlify.app/index.js"
  dev- src="http://127.0.0.1:3000/dist/index.js"
  ></script> 

Note how the src attribute has been changed to src1, you can use anything here to suppress it. A space has been added after the dev- as well, so that that src will now be loaded by the browser.

Publish your webflow.io site ONLY.

Now, any code changes you make and save will immediately, and you can view them immediately on your published webflow.io site.

This tag-edit approach is simple, but it is a hack. At Sygnal we use an additional piece of infrastructure we call DevProxy which automatically makes these script changes at a persistent URL, e.g. dev.mysite.com.

Make sure to change the script tag back after your work, most especially before you publish your site to production.

if you'd like this setup for your projects.

http://127.0.0.1:3000/
Talk to us