Who could have known that a post I dashed off back then without much thought would turn out to be an exact prophecy of the 2025 Brain-to-Web pipeline? Come along on the 15-year evolution of an external brain that started on Chollian (์ฒ๋ฆฌ์), one of Korea’s early dial-up online services, and evolved into Notion-Hugo.
By digging through the actual GitLab commit history, I’ve also captured in vivid detail the concrete implementation process that began in November 2018.
๐ง๏ธ 12 Years Ago, One Line Written on a Rainy Day Became a Prophecy
“Having a stable storehouse for my writing on the webโฆ seemed like something I ought to have at least one ofโฆ” (์น์์ ์์ ์ ์ธ ๊ธ ์ฐฝ๊ณ ๋ฅผ ๊ฐ์ง๋ ๊ฒ์โฆ ํ๋์ฏค ์์์ง๋ง ํ๊ณ โฆ)
On September 9, 2012, at my family home on a rainy day, I wrote those words. I had no idea then that this offhand line would evolve, 15 years later, into a fully automated Brain-to-Web pipeline.
By then I had already been through 15 years of wandering online. Starting on Chollian, then Netian (๋ค๋ ์), an early Korean personal-homepage portal, Cyworld (์ธ์ด์๋), Korea’s social network of the 2000s, and the Episode blog (์ํผ์๋ ๋ธ๋ก๊ทธ)โฆ Watching countless digital spaces vanish, what hit home was that I needed something that was “truly mine.”
And now it’s 2025. Digging through my GitLab repository history, I found something surprising. The real Brain-to-Web journey had begun on November 5, 2018, the very moment I ran my first mobile posting experiment.
๐ง The Dream of an External Brain
“Outsourcing the brain’s functions so the brain can rest” (๋์ ๊ธฐ๋ฅ์ ์ธ์ฃผํํ์ฌ ๋๋ฅผ ์ฌ๋๋ก ํ๋ ๊ฒ)
This was the core of what I’d been pursuing for 15 years. I wanted to deliver my thoughts to the web quickly, beautifully, and effectively. And along the way, I wanted my brain to be free to focus on nothing but creating.
Looking back now, this journey wasn’t just a history of technical progress. It was an experiment showing how one person’s digital identity can cut through time, staying consistent while still evolving.
๐ฏ What You’ll Find in This Post
This post isn’t just a memoir. It’s also a practical guide to help you build a Brain-to-Web system of your own.
- 15 years of tech-stack evolution: Tistory (a Korean blogging platform) โ Hugo โ R Markdown โ VSCode โ Notion
- Real implementation cases: from the first experiment in 2018, proven by GitLab history, to full automation in 2025
- Unexpected discoveries: the arrival of Notion, the AI revolution, GitHub Actions transforming the personal blog
- A build guide: a step-by-step strategy you can follow too
- A vision of the future: predictions for the 2040 Neo-Brain system
๐โโ๏ธ adalgu, One Consistent Identity
What’s especially interesting is that the ID ‘adalgu’, which I made up in middle school, hasn’t changed in 28 years. From Chollian through GitLab and GitHub to today, I’ve also included the story of how this single digital identity ran through every change.
“Just as a prophecy from 15 years ago became reality, the 2040 vision we dream of today will surely become reality too.”
So, let’s set off together on the 15-year evolution of an external brain. ๐
๐ง The Beginning: The Prophecy of September 9, 2012
“Given my profession, which calls for a stable storehouse for my writing on the web; given my personality, which wants to record and preserve my own history and the world’s; and given my inclination, as a dilettante by temperament, to put forward my thoughts on everything under the sun, it seemed like something I ought to have at least one of…” (์น์์ ์์ ์ ์ธ ๊ธ ์ฐฝ๊ณ ๋ฅผ ๊ฐ์ง๋ ๊ฒ์ ๋์ ์ง์ ์, ๋์ ์ธ์์ ์ญ์ฌ๋ฅผ ๊ธฐ๋กํ๊ณ ๋ณด๊ดํ๋ ๊ฒ์ ๋์ ์ฑ๊ฒฉ์, ๋๋ ๋ ๋จ์ ๊ธฐ์ง๋ก ์ธ์๋ง์ฌ์ ๋ํ ์๊ฐ์ ๋ด๋๊ณ ์ ํ๋ ๋์ ์ฑํฅ์, ํ๋์ฏค ์์์ง๋ง ํ๊ณ …)
Fifteen years ago, September 9, 2012. At my family home on a rainy day, I wrote those words.
At the time I was already looking back on 15 years of life online and feeling keenly the need for “a sustainable cyber home” (์ง์ ๊ฐ๋ฅํ ์ฌ์ด๋ฒ ๋ณด๊ธ์๋ฆฌ). From Chollian to Netian, Cyworld, and the Episode blog… the regret I felt watching countless online spaces disappear.
Even then, I had pinned down the core problems precisely:
“I want to write a lot. Writing organizes my thoughts, and sharing it lets me get feedback.” (๊ธ์ ๋ง์ด ์ฐ๊ณ ์ถ๋ค. ๊ธ์ ์ฐ๋ฉด ์๊ฐ์ด ์ ๋ฆฌ๋๊ณ , ๊ณต์ ํ๋ฉด์ ํผ๋๋ฐฑ์ ๋ฐ์ ์ ์๋ค.)
- Social networks that change with every trend, and web hosting and self-hosted blogs that aren’t sustainable
- Traces of the past that can’t be dug up even from the Internet Archive
- The limits of fully anonymous use and the burden of going public under my real name And I had already proposed an answer:
“For now, I’ve settled on Tistory, which I judge has the most users and a virtuous cycle driven by economies of scale. And until some new platform comes along to replace blogs, whenever that may be, it’s confirmed as the space I’ll tend as my cyber home from here on!” (์ผ๋จ์ ๊ฐ์ฅ ๋ง์ ์ฌ๋์ด ์ฐ๋ฉฐ ๊ท๋ชจ์ ๊ฒฝ์ ๋ก ๋ง๋ฏธ์์ ์ ์ํ์ด ์ด๋ฃจ์ด์ง๊ณ ์๋ค๊ณ ํ๋จํ Tistory๋ก ๊ฒฐ์ . ๋ ์ธ์ ๊ฐ ๋ ์ง๋ ๋ชจ๋ฅด๊ฒ ์ง๋ง ๋ธ๋ก๊ทธ๋ฅผ ๋์ฒดํ ์๋ก์ด ํ๋ซํผ์ด ๋์ค๊ธฐ ์ ๊น์ง๋ ์์ผ๋ก ์ฌ์ด๋ฒ ๋ณด๊ธ์๋ฆฌ๋ก์จ ๊ฐ๊พธ์ด์ง ๊ณต๊ฐ์ผ๋ก ๊ทธ๋ ๊ฒ ํ์ !)
Even in 2012, I was already looking for a platform I could pack up and transplant (ํฌ์ฅ์ด์). That now, 15 years later, it has been completed in the form of the Brain-to-Web pipeline still amazes me.
๐ฏ The Core Philosophy of the External Brain Project
The goal of the external brain project was clear:
1. Fast Input (Brain Input)
Store the signals and information entering the brain externally, and do it fast.
2. Intelligent Processing (Processing)
Process the stored information fast into a form that’s easy to read.
3. Immediate Publishing (Web Output)
Publish the processed content to the outside world fast.
4. Liberating the Brain (Brain Liberation)
In the end, things only get sorted out once they’re properly written down. Only then can the brain rest.
In other words, this project is about outsourcing the brain’s functions so the brain can rest.
๐ The 15-Year Technical Journey
Phase 0: Recognizing the Problem and Establishing a Philosophy (2012)
| |
Key insight: Even then, I had grasped the importance of platform independence and data portability
Phase 1: Settling on Tistory and Building Structure (2012-2017)
| |
Significance: Established the external brain’s data structure and classification system
Phase 2: Adopting Hugo + the Academic Theme (the January 29, 2020 “reboot”)
๐ GitLab history discovery: As the actual commit log confirms, the January 29, 2020 “reboot” commit marked the full-scale switch to a Hugo-based static site:
| |
An important discovery: I had already started experimenting with Hugo back in November 2018!
Phase 3: The R Markdown Ecosystem and the Mobile Revolution (exact timing confirmed: November 2018)
๐ฏ The actual GitLab history confirmed the exact timing:
November 5, 2018: The Forestry.io Mobile Revolution
Actual post content (found in the GitLab repository):
| |
Innovation: The first attempt to solve static sites’ mobile limitations with a CMS
November 9, 2018: Discovering the R Practice Notes
Specific R code confirmed in the actual file:
| |
Innovation points:
- Analysis + writing integrated: a blog post is generated at the same time the code runs
- R Markdown โ HTML:
.Rmdfiles render directly to HTML - Reproducible research: data analysis results published to the blog immediately Significance: The first implementation of a single connected pipeline running data โ insight โ writing โ web
Phase 4: VSCode Optimization and the Image Revolution (January 30, 2020)
The innovation I found in the actual post confirmed on GitLab:
| |
Features actually implemented:
| |
My insight at the time (quoted from the actual post):
“A typical approach is this: when you insert an image from the clipboard into a markdown document, the image is copied straight into the folder where the post lives, and an image address pointing to that path is generated and inserted into the body of the post.” (๋ํ์ ์ธ ๋ฐฉ๋ฒ์ด ํด๋ฆฝ๋ณด๋์ ์๋ ์ด๋ฏธ์ง๋ฅผ ๋งํฌ๋ค์ด ๋ฌธ์์ ์ฝ์ ํ๋ฉด ์ด๋ฏธ์ง๊ฐ ๊ธ์ด ์๋ ํด๋์ ๋ฐ๋ก ๋ณต์ฌ๋๊ณ , ๊ทธ ๊ฒฝ๋ก๋ฅผ ๊ฐ๋ฅดํค๋ ์ด๋ฏธ์ง ์ฃผ์๊ฐ ์์ฑ๋์ด ๊ธ ๋ณธ๋ฌธ์ ์ฝ์ ๋๋๋ก ํ๋ ๊ฒ์ด๋ค.)
A groundbreaking experience:
| |
Significance: The starting point of a true “Brain-to-Web” image pipeline
Phase 5: GitLab CI/CD Automation (from January 29, 2020)
The .gitlab-ci.yml confirmed in the reboot commit:
| |
Significance: The start of the Push-to-Deploy workflow
Phase 6: Discovering Notion and the Evolution of the CMS (2020-2022)
- Idea: use Notion as a headless CMS
- Attempts: making use of various open-source projects on GitHub
notion-blog,react-notion-x,notion-to-md, and others Problem: the limits of existing solutions and the difficulty of customizing them
Phase 7: The Great Migration to GitHub (2022 onward)
Moving from GitLab to GitHub brought a new turning point:
- Adopted GitHub Actions
- Drew on a more mature open-source ecosystem
- Evolved from the Academic theme toward an independent structure ๐ฏ Platform independence, proven: Through an actual GitLab โ GitHub migration, the “pack-and-transplant” capability I prophesied in 2012 was fully realized!
Phase 8: Implementing the Fully Automated Pipeline (2025)
| |
Result: The complete fulfillment of the 2012 prophecy
๐ฎ Specific Dates and Evidence for Each Phase
๐ The Exact Timeline (Based on GitLab History)
| |
๐ 15 Years of Tech-Stack Changes (Based on Actual History)
| Period | Core Tools | GitLab Evidence | Innovation |
|---|---|---|---|
| 2012 | Tistory | Original blog post | Philosophy and vision established |
| Nov 2018 | Hugo + Forestry + R | 2018-11-05 mobile test | First static site + CMS integration |
| Nov 2018 | R Markdown | 2018-11-09 R practice notes | Full analysis-writing integration |
| Jan 2020 | Hugo Academic + CI/CD | 2020-01-29 “reboot” | Whole-system integration |
| Jan 2020 | VSCode + Imgur | 2020-01-30 image automation | True Brain-to-Web images |
| 2025 | Python + Notion + AI | Current pipeline | Full automation + quality control |
๐ก The Principles Behind 15 Years of Brain-to-Web Evolution
1. The Persistence Principle - Since 2012
2012 insight: “This too shall pass” (์ด ๋ํ ์ง๋๊ฐ๋ฆฌ๋ผ) โ the need for platform independence
2025 implementation: full ownership built on GitHub + Markdown
| |
2. The Automation Principle - Foreseen in 2012
2012 need: “Just as I was feeling the need for more polished writing” (์ ์ ๋ ๊ธ์ฐ๊ธฐ๊ฐ ํ์ํ๋ค๊ณ ๋๋ผ๋ ์ฐจ์)
2025 realization: fully automated Brain โ Web in 5 minutes
| |
3. The Quality Assurance Principle - The 2012 Philosophy
2012 philosophy: “With a warm heart and a cool head” (๋จ๊ฑฐ์ด ๊ฐ์ด๊ณผ ์ฐจ๊ฐ์ด ๋จธ๋ฆฌ๋ก)
2025 system: AI-based automatic quality evaluation across four areas
| |
4. Identity Persistence - Since Middle School
Middle school days: created adalgu, “an ID to use for life” (ํ์ ์ฌ์ฉํ ID)
2025, today: still adalgu, unified across every platform
| |
๐ฎ The 2012 Prophecy vs. the 2025 Reality
Prophecy: “A Sustainable Cyber Home”
| |
Prophecy: “A Stable Storehouse for Writing on the Web”
| |
Prophecy: “Sensibility Toward the World” (์ธ์์ ํฅํ ๊ฐ์์ฑ)
| |
๐ง 15 Years of Philosophical Development
2012: Awareness of the Problem and a Sense of Direction
“The existence of a blog like this… given the role of an economist, who must heighten their sensibility, process the information they take in ‘with a warm heart and a cool head,’ and then express it in speech and writing…” (์ด๋ฐ ๋ธ๋ก๊ทธ์ ์กด์ฌ๋… ๊ฐ์์ฑ์ ๋์ด์ฌ๋ ค ๋ฐ์๋ค์ธ ์ ๋ณด๋ค์ ‘๋จ๊ฑฐ์ด ๊ฐ์ด๊ณผ ์ฐจ๊ฐ์ด ๋จธ๋ฆฌ๋ก’ ์ฒ๋ฆฌํ ํ ๋ง๊ณผ ๊ธ๋ก์จ ํํํด์ผ ํ๋ ์ด์ฝ๋ ธ๋ฏธ์คํธ์ ๊ธฐ๋ฅ์…)
2018: Searching for Practical Solutions (Found in the GitLab History)
“One of the downsides of static pages is that the posting environment is PC-centric. You can post from mobile using git, but it’s no small hassle.” (์ ์ ํ์ด์ง์ ๋จ์ ์ค ํ๋๋ ํฌ์คํ ํ๊ฒฝ์ด PC ์ค์ฌ์ด๋ผ๋ ๊ฒ์ด๋ค. ๋ชจ๋ฐ์ผ๋ก๋ git์ ์ด์ฉํด์ ํฌ์คํ ์ ํ ์๋ ์์ง๋ง, ์ฌ๊ฐ ๋ถํธํ ๊ฒ์ด ์๋๋ค.)
2020: The Realization of Full Automation
“In an age of (moving) images like today’s, a post without images is as good as dead. Yet writing in markdown has a real limitation: inserting images is far more restrictive than on Naver Blog or Brunch [popular Korean blogging platforms], where copying and pasting images is effortless.” (์์ฆ๊ณผ ๊ฐ์ (๋)์์์๋์ ์ด๋ฏธ์ง๊ฐ ์๋ ๊ธ์ ์ฃฝ์ ๊ธ์ด๋ ๋ง์ฐฌ๊ฐ์ง์ด๋ค. ๊ทธ๋ฐ๋ฐ, ๋งํฌ๋ค์ด์ผ๋ก ๊ธ์ ์ฐ๋ ๊ฒ์ ์ด๋ฏธ์ง ๋ณต/๋ถ์ด ๋งค์ฐ ์์ ๋ก์ด ๋ค์ด๋ฒ ๋ธ๋ก๊ทธ๋ ๋ธ๋ฐ์น์ ๋นํด์ ์ด๋ฏธ์ง ์ฝ์ ์ด ๋งค์ฐ ์ ์ฝ์ ์ธ ํ๊ณ๊ฐ ์๋ค.)
2025: Concrete Realization and Expansion
“I want to deliver my thoughts to the web quickly, beautifully, and effectively. The Brain-to-Web pipeline is a tool that amplifies human creativity and a system that transforms the productivity of knowledge workers.” (์๊ฐ์ ์น์ ๋น ๋ฅด๊ฒ, ์๋ฆ๋ต๊ฒ, ํจ๊ณผ์ ์ผ๋ก ์ ๋ฌํ๊ณ ์ถ๋ค. Brain-to-Web ํ์ดํ๋ผ์ธ์ ์ธ๊ฐ์ ์ฐฝ์์ฑ์ ์ฆํญ์ํค๋ ๋๊ตฌ์ด๋ฉฐ, ์ง์ ๋ ธ๋์์ ์์ฐ์ฑ์ ํ์ ํ๋ ์์คํ ์ด๋ค.)
Key shifts:
- Personal need โ general-purpose solution
- Passive recording โ active amplification
- Platform dependence โ full autonomy
๐โโ๏ธ From “Surfin’ Waves” to “Brain-to-Web”
In 2012, I wrote this:
“That subtle pull of surfing (riding the waves), which also matches my usual motto: don’t swing between joy and despair at life’s crests (the good times) and troughs (rock bottom), but ’enjoy life like riding the waves!’” (์ธ์์์์ ๋ง๋ฃจ(ํธ์์ )์ ๊ณจ(๋ฐ๋ฅ)์์ ์ผํฌ์ผ๋น ํ์ง ๋ง๊ณ , ‘์ธ์์ ํ๋ ํ๋ฏ ์ฆ๊ธฐ์!‘๋ผ๋ ํ์์ ๋ชจํ ์๋ ์ผ์นํ๋ ์ํ(ํ๋ํ๊ธฐ)์ ๊ทธ ๋ฏธ๋ฌํ ๋๋ฆผ)
Fifteen years later, the philosophy of riding the waves has become the design principle of Brain-to-Web:
๐ Reading the Waves = Sensing Trends
- 2012: predicted the shifts in blogging platforms
- 2018: sensed the need for the static site + CMS combination
- 2020: recognized the importance of image automation
- 2025: AI-based automatic analysis of content trends
๐โโ๏ธ Keeping Balance = System Stability
- 2012: “A warm heart and a cool head”
- 2018: R’s rigor + Forestry’s intuitiveness
- 2020: technical sophistication + user convenience
- 2025: a perfect balance of creativity and rigor
๐ Riding the Waves = Adapting to Change
- 2012: prepared for platform moves with “pack-and-transplant”
- 2018: switched tech stacks by adopting Hugo
- 2020: automated deployment with GitLab CI/CD
- 2025: a fully automated migration system
๐ 15 Years of Quantitative Results
The 2012 Baseline
| |
The November 2018 Innovation (Confirmed in the GitLab History)
| |
The Great Shift of January 2020 (The VSCode Revolution)
| |
2025, Today
| |
Key Metrics Compared
| Item | 2012 | 2018 | 2020 | 2025 | Total Improvement |
|---|---|---|---|---|---|
| Writing time per post | 2-3 hours | 1-2 hours | 30 min-1 hour | 30 min-1 hour | 70% shorter |
| Technical work time | 30-60 min | 10-20 min | 5-10 min | 5 min | 90% shorter |
| Platform dependence | 100% | 30% | 10% | 0% | Fully resolved |
| Data ownership | 0% | 70% | 90% | 100% | Fully attained |
| Automation level | 10% | 50% | 80% | 95% | Up 85%p |
๐ญ A Message to My Past Self, 15 Years Later
To me on September 9, 2012, at my family home in the rain
Everything you’re agonizing over right now is the right answer.
โ “A sustainable cyber home” โ fully solved, as proven by the GitLabโGitHub move
โ A “pack-and-transplant” system โ perfectly implemented on Markdown
โ “A stable storehouse for writing on the web” โ managed systematically in a Notion DB
โ “Sensibility Toward the World” โ amplified with AI
โ “Surfin’ Waves” โ evolved into Brain-to-Web
And the ID adalgu? You’re still using it 15 years later. All that thought you put into it in middle school was truly brilliant.
Above all, what you now call your “dilettante temperament” will end up becoming the ability to weave different technologies together into an entirely new system.
And don’t miss the first revolution that begins in November 2018. The combination of R Markdown + Hugo + Forestry is going to be truly groundbreaking.
Keep riding the waves. Those waves eventually become the tide of Brain-to-Web.
๐ฎ The Next 15 Years: A Vision Toward 2040
The Current Brain-to-Web Architecture (As of 2025)
Input Layer (Brain Input Layer)
| |
Processing Layer
| |
Output Layer (Web Output Layer)
| |
Feedback Layer
| |
If the 2012 prophecy became reality in 2025, what will be possible in 2040?
๐ง The Neo-Brain 2040 Vision
A Complete Thought-to-Web Link (Direct Thought-to-Web)
| |
Connecting with Collective Intelligence (Collective Intelligence Integration)
| |
Securing Complete Immortality (True Digital Immortality)
| |
Will the adalgu of 2040 still be adalgu? Probably, because just as a middle schooler’s insight from 15 years ago still held 15 years later, a true digital identity transcends time.
๐ฌ 15 Years of Lessons and Realizations
Technical Realization: The Accuracy of Foresight
- 2012 prophecy: “There is no perfect tool” (์๋ฒฝํ ๋๊ตฌ๋ ์๋ค) โ you have to build your own tools
- Proven in 2025: in the end, I implemented it myself in Python
- 2012 prophecy: “Pack-and-transplant capability” โ platform independence is the key
- Started in 2018: first attempt based on Hugo + Markdown
- Expanded in 2020: full automation with GitLab CI/CD
- Implemented in 2025: proven through an actual GitLabโGitHub migration
- 2012 foresight: “Sustainability” โ choose a platform with economies of scale
- 2025 development: complete stability secured on the developer ecosystem that is GitHub
Philosophical Realization: A Core That Stayed Consistent for 15 Years
- The brain should focus on creating (2012) โ technology must not get in the brain’s way (2025)
- Sensibility can be externalized (2012) โ AI can amplify sensibility (2025)
- Waves can be ridden (2012) โ change can be an opportunity (2025)
Unexpected Discoveries
- Early adoption of R Markdown (November 2018): a choice well ahead of its time
- The Forestry.io mobile innovation (November 2018): overcoming static sites’ mobile limitations
- VSCode image automation (January 2020): the first true implementation of Brain-to-Web
- The arrival of Notion: launched in 2016, explosive growth after 2020
- The explosive advance of AI: with ChatGPT in 2023, quality automation became a reality
- GitHub Actions: launched in 2018, bringing full CI/CD automation even to personal blogs
๐ 15 Years of Tech-Stack Evolution
2012: The Web 1.0 โ Web 2.0 Transition
| |
2018-2020: The Era of Static Sites + Automation
| |
2025: The Era of AI + Full Automation
| |
2040: The Projected Stack
| |
๐ 15 Years of Evolution in the adalgu Identity
Middle-Schooler adalgu (c. 1997)
| |
College-Student adalgu (2012)
| |
Developer adalgu (2018-2020)
| |
Office-Worker adalgu (2025)
| |
adalgu’s remarkable consistency: A digital identity unchanged for 28 years is, if anything, what made change possible.
๐ฏ A Guide to Building Brain-to-Web: Lessons from 15 Years
If you’d like to build a Brain-to-Web pipeline of your own, take a look at the lessons from this 15-year journey:
1. Start with a Long-Term Vision (The Lesson of 2012)
| |
2. A Strategy of Gradual Automation (The 15-Year Lesson)
| |
3. Keep Your Digital Identity Consistent
| |
4. Balance Philosophy and Technology
| |
๐ค Wrapping Up: Why Did It Take 15 Years?
If the vision was already complete in 2012, why did it take a full 15 years?
Waiting for the Technology to Mature
- R Markdown: stabilized in 2014 (2 years later)
- Hugo: released in 2013, ecosystem matured in 2016 (4 years later)
- Forestry.io: CMS service launched around 2017 (5 years later)
- Notion’s launch: 2016 (4 years later)
- GitHub Actions: 2018 (6 years later)
- The GPT revolution: 2022 (10 years later)
- Point of completion: 2025 (13 years later)
The Need for Personal Growth
- Programming skill: the ability to use Python at an advanced level
- Systems thinking: the ability to design the whole pipeline
- Problem-solving experience: hands-on experience such as the GitLabโGitHub migration
The Development of the Ecosystem
- The open-source ecosystem: Hugo, Python libraries
- Cloud infrastructure: GitHub, the Notion API, and more
- AI tools: tools for quality evaluation and automatic improvement Conclusion: It’s not that it took 15 years; it needed 15 years.
If the 2012 vision was the seed, the 2025 implementation is the fruit. And I’m grateful to the me of 15 years ago who planted that seed.
The most important thing was the actual implementation journey that began in November 2018. As the GitLab history confirms, the combination of R Markdown + Hugo + Forestry.io was the first true implementation of Brain-to-Web, and it became the foundation of today’s finished system.
This post, too, was written through the Brain-to-Web pipeline.
The journey that began on a rainy September 9, 2012 passed through its first implementation in November 2018 and came to fruition as a finished system on June 24, 2025.
Just as a prophecy from 15 years ago became reality, the 2040 vision we dream of today will surely become reality too. ๐
๐ Related Resources
- 2012 original post: Opening “Sensibility Toward the World”
- GitLab repository history (2018-2022)
- Current GitHub repository (2022-present)
- Notion-Hugo Pipeline GitHub Repository
- 2020 VSCode writing optimization (current GitHub repository)
Tags: #ExternalBrain #BrainToWeb #NotionHugoPipeline #Adalgu #15YearJourney #DigitalIdentity #SensibilityTowardTheWorld #SurfinWaves #adalgu #PKM #ProductivityInnovation #RMarkdown #GitLab #Hugo #Forestry #VSCode #ImageAutomation
- What part of writing takes you the longest? โข What is your most repetitive, tedious task? โข Imagine your own perfect writing environment Build a system you’ll still be able to use 10 years from now. Someday you, too, will have a ‘story’ of your own.
