Home
<aside>
🛠️
This is a manual test of the restart-ramp workflow for the syntax-dx project, using:
Restart-ramp post (draft)
What I was building
- A custom Node.js webhook receiver deployed on Railway.
- Goal: handle incoming events and generate clean, specific HTML reports on the backend.
Why this design
- Needed stricter, programmatic control over LLM prompt injection and output quality.
- Wanted to avoid the limitations of a pure WordPress/PHP chatbot style plugin.
Current state
- Gemini API is returning HTML wrapped in markdown code fences (`html), so it is not yet ready to send directly.
Friction and open decision
- Output must be sanitized (strip code fences and validate it) before cloud deployment.
- Need to choose the email delivery routing:
- Send directly from Railway using Resend.
- Or pass the result back to WordPress for FluentSMTP.
Next steps (on restart)
- [ ] Implement HTML sanitization and stripping of code fences.
- [ ] Decide email delivery route (Resend vs FluentSMTP path).
- [ ] Push repo and run live webhook tests on Railway.
Notes
- If we like this structure, the next automation step could be: generate this page automatically whenever 2+ logs exist for the same Project on the same day.