Do desenvolvimento local ao deploy: o que aprendi criando o Kado
João Ramajo shares his experience developing Kado, a personal finance management platform. The project aimed to address his spending control needs while allowing him to learn new web development concepts. He transitioned from using Filament PHP to a more complex architecture involving Laravel for the backend and React with TypeScript for the frontend.
- ▪Kado is a personal finance management project developed for personal use.
- ▪The project evolved from a simple Filament PHP application to a more complex architecture with Laravel and React.
- ▪Ramajo learned about various web development concepts, including reverse proxy and SSL configuration, while working on Kado.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/joao-ramajo/do-desenvolvimento-local-ao-deploy-o-que-aprendi-criando-o-kado-ipc |
| Publication time | Sat, 30 May 2026 08:00:30 +0000 |
| Retrieval time | 2026-05-30T08:12:08.920Z |
| Last seen | 2026-05-30T08:12:08.920Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | f6loMEu0ESCD |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3340582) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } João Ramajo Posted on May 30 Do desenvolvimento local ao deploy: o que aprendi criando o Kado #webdev #braziliandevs #laravel #php Nos últimos meses, tenho desenvolvido, para uso pessoal, uma plataforma para gerenciar meu dinheiro de uma maneira mais consciente. Não gosto de planilhas e também queria estudar algo novo. Essa união de fatores me levou inicialmente ao Filament PHP e, depois, a uma arquitetura com frontend e backend independentes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).