2 points | by np123greatest a day ago
3 comments
Hi HN, I’m the author.
This started as an engineering experiment around whether video creation can be made reproducible and pipeline-driven, rather than manually edited.
Wiki2Video is a CLI-first, end-to-end system: Wikipedia → script → narration → visuals → subtitles → final video.
I also tested it by running a small YouTube channel to uncover real-world bottlenecks, not just demo outputs.
Would love feedback from people who have built automation or content pipelines.
This reminds me of https://wiki.devilfruit.com
Cool project!
Thanks! That’s a good comparison.
My focus here is less on building a curated wiki experience, and more on making the entire transformation reproducible as a pipeline .
I’m especially curious how far this kind of automation can go before manual curation becomes unavoidable.
Hi HN, I’m the author.
This started as an engineering experiment around whether video creation can be made reproducible and pipeline-driven, rather than manually edited.
Wiki2Video is a CLI-first, end-to-end system: Wikipedia → script → narration → visuals → subtitles → final video.
I also tested it by running a small YouTube channel to uncover real-world bottlenecks, not just demo outputs.
Would love feedback from people who have built automation or content pipelines.
This reminds me of https://wiki.devilfruit.com
Cool project!
Thanks! That’s a good comparison.
My focus here is less on building a curated wiki experience, and more on making the entire transformation reproducible as a pipeline .
I’m especially curious how far this kind of automation can go before manual curation becomes unavoidable.