· 2 min read
why i'm building imprint?
i recently started building as a side project, imprint. it's a mix of blog publisher and native ai editor. with the experience of running aligned, i realized that building content and sharing ideas of what we are doing does not work as software. the process for content creation (written at least) is messy, not centralized, it requires a lot of overhead to build process that work and that are data driven.
at the same time, we have now have the best parrots ever - LLMs. they are a great tool to help you express your ideas and reason, but it requires a lot of effort to build good processes and frameworks to take advantage of this. not everyone on the team has the same level of ai expertise and its hard to educate them to be ai native.
so i wanted to build a solution that we can use internally that helps us manage written content as we do with software (sort of PRs and git style management) and at the same time have the ai editor i would love to have in order to have ai help the author express themselves better but not "replace them" creating infinitely ai slop.
so the whole point of imprint is to:
improve written content processes in companies or any organization
help people write better with ai, using the latest tech but expressing themselves better
we believe ai can also help to accelerate the process of making every work follow software practices and at the same time help people leverage ai but without eliminating creativity and clarity.
in a world of abundance of "ideas", we need tools to help us have clear minds and express complex ideas succinctly.
imprint is an internal tool i'm building for myself and our company to express our ideas with more clarity and succinctly.
its one of the first software solution non ethereum related we are putting out-there with the idea of building software that makes things simpler.
the first user of imprint is my personal blog.