Lineage as of now is build within each indicator. You have to select for each indicator what are the main sources for it (either indicator or whole node). Did you struggle in terms of interface, lineage computation (server side), or any other topic ?
I think I should rework the way table node are made, and how users can define proper lineages within their canvas. If you have any suggestion :)
I'll also work to provide user a way to go back to the home page. If you have any feedback on how I could improve the marketing, I would welcome them with gratitude.
Ah, thanks for flagging this. I’ve actually seen that 404 myself a couple of times, but it’s pretty rare and usually goes away on retry. Looks like something flaky in the GitHub OAuth flow. I need to dig in and investigate properly
Appreciate that
Right now it’s proprietary and free, there’s no ongoing cost. I don’t have a pricing model locked in yet. The rough idea is to eventually go freemium (keep the core stuff free, add a paid tier for heavier/advanced use). Still figuring out what makes sense, and I’ll be upfront if/when that changes.
The main motivation really was what you mentioned: so many “best practices” live in blog posts or scattered docs, but almost no one actually packages them into something usable. I’m just trying to pull those ideas together in a way that saves people from reinventing the wheel. Still early days, so I’m curious to see if it resonates beyond my own itch.
Lineage as of now is build within each indicator. You have to select for each indicator what are the main sources for it (either indicator or whole node). Did you struggle in terms of interface, lineage computation (server side), or any other topic ? I think I should rework the way table node are made, and how users can define proper lineages within their canvas. If you have any suggestion :)
I'll also work to provide user a way to go back to the home page. If you have any feedback on how I could improve the marketing, I would welcome them with gratitude.