Problems, not a portfolio
Projects
A documented selection from more than 100 websites built over thirty years. Each one began because something in life needed a better answer.
The foundationLiveLearnBuildlivelearnbuild.com
- What problem did I experience?
- The websites, books, systems, relationships, lessons, and questions made sense individually, but the philosophy connecting them was difficult to see.
- Why did I build this?
- To build the digital foundation from which every other website grows and give one life a place where its parts can be understood together.
- What did I learn?
- A life's work becomes coherent when what was lived, learned, and built can remain connected.
Private documentationPink Journalnotes.crowncrew.dev
- What problem did I experience?
- I needed a small, private place to write without first deciding what the writing would become.
- Why did I build this?
- To give raw thoughts a quiet room before they became plans, products, or public writing.
- What did I learn?
- Private writing does not need an outcome. Sometimes its purpose is simply to let life speak honestly.
Life documentationPink JourNotespinkjournotes.com
- What problem did I experience?
- Journals, recipes, reminders, recordings, and everyday thoughts were living in separate places.
- Why did I build this?
- To bring private life documentation together in one place that remains separate from public writing.
- What did I learn?
- Private documentation and public documentation can support the same life without needing an automated bridge between them.
Family documentationMy Family Threadmyfamilythread.space · parked
- What problem did I experience?
- Family stories, photos, dates, and small updates were disappearing into group chats and old phones.
- Why did I build this?
- To create a family-only space for posts, chat, books, photos, dates, and memories.
- What did I learn?
- A family archive is built from ordinary days, not only milestones.
LearningEverlight Virtual Academyeverlightvirtualacademy.online
Open everlightvirtualacademy.online
- What problem did I experience?
- Homeschool families needed lessons, progress records, and proof of learning without losing the parent-led nature of home education.
- Why did I build this?
- To build structured K–12 homeschool support for Filipino families in one continuing system.
- What did I learn?
- Education is not only content. It is continuity, support, documentation, and the confidence to keep going.
Learning intelligenceEverlight OMG AIai.everlightvirtualacademy.online · private
- What problem did I experience?
- Everlight had its own curriculum, families, records, and rules, but a general AI assistant could not understand that context by default.
- Why did I build this?
- To give the academy a private AI workspace for research, support, and operations within Everlight's own boundaries.
- What did I learn?
- AI becomes more useful when it is grounded in one system's real knowledge and responsibilities.
LearningEverlight Globalglobal.everlightvirtualacademy.online
Open global.everlightvirtualacademy.online
- What problem did I experience?
- Everlight's Philippine home could not fully express the needs of independent homeschool families living in other countries.
- Why did I build this?
- To create the first global doorway into Everlight's structured lessons, records, and homeschool support.
- What did I learn?
- Everlight Global evolved into EVA Homeschool.
LearningEVA Homeschoolevahomeschool.com
- What problem did I experience?
- The same need for structured homeschool support existed beyond one country, but the system had to travel across different family realities.
- Why did I build this?
- To give global independent homeschool families lessons, worksheets, quizzes, records, and portfolio support.
- What did I learn?
- The need to understand a child's learning is universal, even when the rules and context around it change.
PublishingOpenLeafopenleafbooks.com
- What problem did I experience?
- The books were written, but they still depended on other people's shelves and systems.
- Why did I build this?
- To give the books a direct digital home where the catalog, delivery, and relationship with readers could remain connected.
- What did I learn?
- Writing becomes more durable when the writer also understands the shelf it lives on.
Family creativityLRGSMlrgsm.ph
- What problem did I experience?
- The stories, characters, comics, and games Lyle and I made together needed one shared home.
- Why did I build this?
- To preserve the creative world we were building as a family instead of leaving it scattered across files and feeds.
- What did I learn?
- Making things together is also a way of documenting a family's imagination.
Small curiositiesLil Quackylilquacky.lrgsm.ph
- What problem did I experience?
- A small character and a collection of duck facts were too playful to need a large product, but too delightful to leave as a loose idea.
- Why did I build this?
- To give curiosity a tiny home inside the LRGSM world.
- What did I learn?
- Not every build needs to become large. Some things are complete because they make learning feel light.
ComicsSuper Tatangsupertatang.com
- What problem did I experience?
- A continuing Filipino comic needed an archive where complete stories could live beyond a social feed.
- Why did I build this?
- To give Super Tatang its own reading room and preserve the director's-cut versions of the work.
- What did I learn?
- An archive gives a story continuity. A feed only gives it a moment.
Comics · 18+PanelXXpanelxx.com
- What problem did I experience?
- Adult comics needed a deliberate 18+ home with clear boundaries instead of being mixed into general creative spaces.
- Why did I build this?
- To create a controlled subscription library for mature work and the audience it was made for.
- What did I learn?
- Responsible publishing includes knowing the audience and designing the right access boundaries.
Creative toolsComic Animatoranimate.crowncrew.dev
- What problem did I experience?
- The comics began as still panels, while the places where stories were shared increasingly expected motion and video.
- Why did I build this?
- To turn existing artwork into animated scenes and exportable videos without rebuilding every story in a full animation suite.
- What did I learn?
- A good tool extends the artist's work. It does not need to replace the artist.
Personal documentationPlukRubyplukruby.com
- What problem did I experience?
- My work, learning, books, and systems existed, but the person connecting them was hard to see.
- Why did I build this?
- To give my professional work and the ideas behind it one personal home.
- What did I learn?
- A person is understood more clearly through a connected body of work than through a résumé alone.
Earlier business homeRubyLen IT Solutionsrubylenitsolutions.online · archive
- What problem did I experience?
- The technical work I was doing for other people needed a name and a place of its own.
- Why did I build this?
- To give that work an early business identity before the larger ecosystem had taken shape.
- What did I learn?
- A first home does not need to be the final home. It can still document where the work began.
Marketing intelligencePlukRuby AIai.plukruby.com
- What problem did I experience?
- Client ad accounts, strategy, copy, creative, lead forms, audits, and launches were spread across separate tools and repeated steps.
- Why did I build this?
- To connect Meta advertising work inside one AI-assisted operating system.
- What did I learn?
- AI helps marketing most when it is embedded in a real workflow and accountable to real campaign data.
Creative toolsImage Gen Assistantgen.plukruby.com
- What problem did I experience?
- Creating useful marketing images required repeated prompting, formatting, and coordination across disconnected tools.
- Why did I build this?
- To make image generation a repeatable working process instead of a one-off experiment.
- What did I learn?
- Generation becomes useful when the purpose, constraints, and destination of the image are clear.
WorkGet Solid Marketinggetsolidmarketing.com
- What problem did I experience?
- Ads, funnels, tracking, leads, and follow-up were too often treated as separate tasks.
- Why did I build this?
- To bring Meta advertising and the systems around it into one accountable way of working.
- What did I learn?
- An ad does not create a result by itself. The surrounding system must make sense too.
Marketing operationsGetSolid SMMsmm.getsolidmarketing.com · private
- What problem did I experience?
- Social media services, pricing, orders, providers, and delivery needed to be tracked as one operation.
- Why did I build this?
- To give Get Solid Marketing a controlled workspace for managing repeatable social media fulfillment.
- What did I learn?
- Automation is only useful when the service around it remains visible and accountable.
Local servicesWashNearcarwash.crowncrew.dev
- What problem did I experience?
- Drivers needed an easier way to find and book a nearby carwash, while local shops needed a clearer path to available customers.
- Why did I build this?
- To test whether local discovery and booking could make one everyday service easier for both sides.
- What did I learn?
- The problem was larger than carwash. What WashNear taught me about local discovery, trust, and service information became the foundation of LokalShops.
Local trustLokalShopslokalshops.com
- What problem did I experience?
- Good local shops were hard to discover and trust beyond the businesses people already knew.
- Why did I build this?
- To expand what began with WashNear into a Philippine directory and map for many kinds of local businesses.
- What did I learn?
- WashNear showed me that local commerce is not only about being listed. It is about becoming known, useful, and trusted over time.
Local servicesPinoy Carwashpinoycarwash.com · parked
- What problem did I experience?
- Carwash discovery still needed a Philippines-specific home focused on shops rather than the WashNear booking experiment.
- Why did I build this?
- To explore a separate national directory identity for carwash owners and customers.
- What did I learn?
- Two projects can begin in the same industry and still be built to answer different questions.
Local servicesPinay Laundrypinaylaundry.com · not published
- What problem did I experience?
- Neighborhood laundry services were useful but difficult to compare when pricing, pickup details, and availability lived in posts and private messages.
- Why did I build this?
- To imagine a clearer local home where laundry services could be discovered and understood before a customer reached out.
- What did I learn?
- Everyday services earn trust through simple information: what they do, where they serve, what it costs, and what happens next.
Circular economyJunkShopPinasjunkshoppinas.com · not published
- What problem did I experience?
- Recyclable materials and usable scrap were difficult to route to the right nearby junk shop because local knowledge was scattered.
- Why did I build this?
- To create a Philippine home for finding junk shops, understanding what they accept, and keeping useful materials in circulation.
- What did I learn?
- What looks like waste is often undocumented value waiting for the right local connection.
Proof of workProofolyoproofolyo.work
- What problem did I experience?
- Remote workers were being asked to prove themselves with résumés that could only describe their work.
- Why did I build this?
- To help people turn experience, samples, and capability into a portfolio link they own.
- What did I learn?
- Capability becomes credible when it is documented with evidence.
Operating ecosystemCrownCrewcrowncrew.dev
- What problem did I experience?
- People, clients, tools, and operating knowledge were growing across separate systems without a shared technical home.
- Why did I build this?
- To create an ecosystem where the team and the internal tools supporting the work could develop together.
- What did I learn?
- A crew becomes stronger when its knowledge and systems are shared instead of living with one person.
Business operationsCrownPOSpos.crowncrew.dev
- What problem did I experience?
- A small shop can sell all day and still lose understanding of inventory, cash, products, and what actually moved.
- Why did I build this?
- To create a practical point-of-sale system where daily transactions and inventory could remain connected.
- What did I learn?
- A transaction becomes useful knowledge when it is documented as part of the whole operation.
Artificial intelligenceOMG AIomg.crowncrew.dev
- What problem did I experience?
- Useful AI was scattered across models, tools, and command lines, making it difficult to use as one dependable working partner.
- Why did I build this?
- To create a controlled agent workspace with managed access, multiple model providers, tools, files, and visible work logs.
- What did I learn?
- An agent becomes useful when access, tools, fallbacks, and accountability are designed together.
InfrastructureMothermother.crowncrew.dev · private
- What problem did I experience?
- The systems I built lived on one server, but their health, domains, and failures were invisible unless I checked them one by one.
- Why did I build this?
- To give the entire living system one place where I could see what was online, what was changing, and what needed care.
- What did I learn?
- Infrastructure is not beneath the work. It is the quiet work that allows everything else to remain alive.
Life togetherLyle & Rubylyleruby.us · awaiting DNS
- What problem did I experience?
- More than thirty years of family, work, creativity, learning, and building existed as separate chapters.
- Why did I build this?
- To give the shared story of Lyle and Ruby one place across time.
- What did I learn?
- A life's work is not a collection of products. It is one story told through what we lived, learned, and built.