Editing & Iteration Workflow
JET's editing workflow is designed for speed and flexibility. This page covers the full cycle from initial creation through refinement, versioning, collaboration, and publishing.
The Core Iteration Loop
Building in JET follows a simple cycle:
Edit in Chat → Preview Changes → Test Functionality → Save Snapshot → Publish
Unlike traditional development where you write code, refresh, debug, and repeat, JET collapses this into conversational edits with instant visual feedback.
How Editing Works
Stage 1: Initial Creation You start with a seed prompt that generates your first complete version. This is version 1.
Stage 2: Iterative Refinement Now you enter "vibe coding" mode—each message refines the site:
Content changes: "Update the headline"
Design tweaks: "Make buttons more rounded"
Layout shifts: "Move the pricing above testimonials"
Functionality: "Add form validation"
Stage 3: Testing & QA Use device previews and test mode to verify everything works:
Submit forms with test data
Check mobile responsive behavior
Test all navigation links
Verify loading performance
Stage 4: Snapshot & Version Control Save important milestones manually, or rely on JET's automatic snapshots every 10 edits.
Stage 5: Publishing When ready, deploy to staging or production. JET handles hosting, SSL, and CDN automatically.
Versioning System
Automatic Snapshots JET saves your progress automatically:
Every 10 prompts
Before major structural changes
When switching between pages
Every 24 hours (even with no edits)
Manual Save Points Create your own snapshots:
Before experimenting with big changes
When reaching a milestone
Before sharing for feedback
Click "Save Snapshot" and add a label: "Homepage v2", "Before client feedback", "Launch candidate"
Reverting to Previous Versions Access Version History to see:
Timeline of all snapshots
Before/after preview comparisons
Diff view showing exact changes
Click any snapshot to restore it. Your current version moves to a branch so you don't lose work.
Collaboration Features
Shared Projects Invite team members with different roles:
Owner: Full control, can delete project, manage billing Editor: Can make changes, save snapshots, publish to staging Viewer: Can view and comment, but not edit Commenter: Can leave feedback in chat, but not access edit tools
Real-Time Collaboration When multiple editors work simultaneously:
See who's online (avatars in top-right)
Live cursor indicators show where others are working
Chat messages include author names
Conflict resolution prompts appear if editing same element
Commenting System Leave feedback directly in chat:
Tag team members: "@sarah can you review the pricing section?"
Pin comments to specific components
Mark comments as resolved when addressed
Export comment threads for external sharing
Applying Edits Safely
Preview Mode When JET generates a response, you see:
Preview button: See the change without committing
Apply button: Make the change permanent
Modify button: Refine the AI's suggestion before applying
This prevents accidental changes from going live.
Staging vs Production JET supports two environments:
Staging (Default)
Safe testing environment
Unique URL for sharing with team/clients
Not indexed by search engines
Perfect for QA and feedback
Production
Live website on your domain
Indexed by search engines
Only push here when fully tested
Promote staging → production with one click when ready.
Conflict Resolution
When two editors modify the same component simultaneously:
Automatic Merging: If changes don't conflict (e.g., one person edits headline, another edits button), JET merges automatically.
Manual Resolution: If both edit the same property:
JET pauses and shows both versions
You choose: Keep A, Keep B, or Merge manually
Conflict is resolved and work continues
Best Practice: Use comments to coordinate: "Working on hero section now"
Developer Export
Once your site is built, optionally export the code:
What You Get:
Complete source code (HTML/CSS/JS)
Database schema (SQL or NoSQL)
API endpoint documentation
Asset files (images, fonts, etc.)
Deployment instructions
Why Export?
Migrate to your own hosting
Customize beyond JET's capabilities
Integrate with existing systems
Learn from JET's code generation
Format Options:
Standard HTML/CSS/JS
React components
Next.js project
WordPress theme
Raw backend API (Node.js, Python)
Edit Workflow Diagram
Advanced Workflow Tips
Branch Experimentation Want to try a radical redesign without losing current work?
Save a snapshot: "Current stable version"
Make experimental changes
If you don't like them, revert to the snapshot
Your experiment is saved in history if you want to revisit later
Batch Edits Make multiple changes in one prompt for efficiency:
"Make these 5 changes: 1) Update hero headline to 'Welcome', 2) Change button color to blue, 3) Add FAQ section, 4) Move testimonials above pricing, 5) Update footer copyright year"
Template Your Workflow Building similar sites repeatedly? Create a workflow template:
Start with base template
Run standard customization prompts
Save as "Agency Template v3"
Clone for each new client
Publishing Checklist
Before hitting publish, verify:
✓ All content reviewed and finalized ✓ Images optimized and loading properly ✓ Forms tested and connected correctly ✓ Mobile view checked on multiple devices ✓ All links working (internal and external) ✓ SEO meta data added (title, description) ✓ Favicon uploaded ✓ SSL certificate active ✓ Domain connected (if using custom domain) ✓ Analytics installed (if needed)
Deploy with confidence. JET's workflow makes iterating fast and publishing safe.
Last updated