I recently started working on something new under GraceSoft — an experiment around structuring “stories” from actual development activity.
Not content.
Not posts.
Not documentation.
Something closer to a timeline engine.
🧩 The Idea (So Far)
Most of our work already exists in fragments:
- git commits
- project updates
- notes
- milestones
- decisions
But they’re scattered across tools.
What if they could be structured into a single, evolving timeline?
Not manually written after the fact —
but progressively built as the work happens.
⚙️ What’s Been Built (Day 1–?)
Still early, but the current foundation includes:
- timeline creation (MVP structure)
- ownership + access control layer
- integration entry points (starting with GitHub)
- manual sync endpoint
- early-stage pipeline for processing activity into events
No UI direction locked in yet —
focusing purely on data modeling + system design first.
🧱 Current Stack
- Laravel (API + core logic)
- MySQL (structured timeline data)
- GitHub integration (initial source)
- Queue-based processing (for sync pipeline)
Keeping it simple for now —
but designing in a way that won’t break when things scale.
🤔 Open Questions
Still figuring out:
- How much should be automated vs curated?
- What makes a “meaningful” event in a timeline?
- How to avoid turning this into just another activity feed?
- Where does structure end and storytelling begin?
👀 What’s Next
- expanding the sync pipeline
- mapping commits → structured timeline events
- experimenting with milestone detection
- exploring a minimal UI (thinking macOS-inspired)
No roadmap to share yet.
Just building, testing, and seeing where this goes.
If you’ve ever thought about:
- turning work into something more structured
- or making development progress more visible
I’d be curious to hear your thoughts.
Top comments (0)