Repository navigation
Replies: 2 comments
|
🦗🦗 |
0 replies
|
For coming back to a client website a month later, we built WorkLedger to keep the delivery history with the work instead of the old agent chat. You can organize the website under a project and keep its specification, recorded decisions, change references and verification evidence together. When a delivery continues in a new supported coding session, its handover brings the recorded decisions, open questions and next action forward. That gives the next session a starting point for following the earlier architecture and understanding what still needs your input. We build WorkLedger at Digital Disruptors. If you want to try it with one client repository, our guided 30-day pilot is free: https://workledger-ai.com/early-access |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
One of the paperclip companies that I've built is creating client websites.
My question is: down the road, when I need to modify that website or add more pages or content and I wanted to follow my paperclip agents' architecture and SEO strategy, what is the best way to update these past 'Issues' (ie, website "A") that was done in paperclip so that it takes it through each of my agents' processes?
I was thinking organizing as a 'project' would fully silo the builds, but am unsure.
Anybody else have experience with creating new iterations on past creates inside of one company?
The other alternative was to clone and create a company for each client. That seems like overkill. 🤯
All reactions