[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"profile-en":3,"$f2px89nnpqt89g":74},{"fullName":4,"role":5,"headline":6,"intro":7,"about":8,"essay":9,"location":10,"currentPosition":11,"availability":12,"email":13,"phone":14,"whatsappUrl":15,"linkedinUrl":16,"githubUsername":17,"cvUrl":18,"photoUrl":19,"domains":20,"experiences":37,"testimonials":63,"updatedAt":72,"translations":73},"Marc Ariel Oka","Senior Software Engineer · Fullstack","I design and build software products, *from the system to the experience.*","Senior fullstack software engineer based in Abidjan. I design and build complete web and mobile applications, with a frontend specialisation and projects in artificial intelligence, automation and machine learning. Founder of FACTio, an invoicing SaaS in production.","I am a fullstack software engineer. I design and build complete applications, web and mobile: architecture, business logic, APIs, databases and interfaces.\n\n## How I approach a problem\n\nBefore writing code, I try to understand the business: who uses the tool, what constraints they work under, what absolutely has to work. A good part of my work is turning scattered processes — spreadsheets, WhatsApp threads, manual data entry — into reliable, clear applications.\n\n## What I do\n\nI work on the backend as much as on the frontend, mainly with Laravel, Vue.js, Nuxt and Flutter. I am currently a senior fullstack developer at Flot, with solid frontend experience. Outside that role, I work on artificial intelligence, automation and machine learning projects in Python, sometimes with models running locally through Ollama.\n\n## FACTio, my product\n\nI designed, built and shipped FACTio, my own SaaS for invoicing and payment tracking, aimed at freelancers and small businesses. I keep evolving it based on what its users need.\n\n## What I want to go deeper into\n\nAI engineering and machine learning applied to real products, the architecture of applications that need to last, and the quality of interfaces on complex user journeys.","I work across the whole of an application, web or mobile: its architecture, business logic, APIs, data and interfaces. I am currently a senior fullstack developer at Flot.\n\nWhat I am most passionate about is applied research in artificial intelligence: understanding how models work, putting them to the test on real problems and seeing what holds up in production. I explore agents, automation and machine learning, often with models running locally.\n\nI am also building [FACTio](\u002Fprojets\u002Ffactio), my own invoicing SaaS, now in production. Along the way, I have designed platforms such as [Perafind](\u002Fprojets\u002Fperafind), [DS-Accessories](\u002Fprojets\u002Fds-accessories) and [Digifop](\u002Fprojets\u002Fdigifop) for AGEFOP.","Abidjan, Côte d’Ivoire","Senior Fullstack Developer at Flot","Available for projects, locally and internationally","okaamarc@gmail.com","+225 05 76 10 52 39","https:\u002F\u002Fwa.me\u002F2250576105239","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmarc-ariel-oka\u002F","Marc-Ariel-Oka","\u002Fcv\u002Fmarc-ariel-oka-cv.pdf","\u002Fimages\u002Fmarc-ariel-oka.webp",[21,25,29,33],{"title":22,"tools":23,"problem":24},"Fullstack Software Engineering","Laravel · PHP · PostgreSQL · MySQL · Docker","Designing a complete application — architecture, business logic, API, database, interface — and evolving it in production.",{"title":26,"tools":27,"problem":28},"Advanced Frontend","Vue.js · Nuxt · TypeScript · Tailwind CSS · Flutter","Fast, readable interfaces, including on complex journeys, on the web as well as on mobile.",{"title":30,"tools":31,"problem":32},"AI Engineering & Automation","Python · Ollama · Agents IA","Automating repetitive tasks and connecting language models to your data — locally when confidentiality requires it.",{"title":34,"tools":35,"problem":36},"Machine Learning","Python","Designing and integrating models when hand-written rules are no longer enough.",[38,44,49,54,59],{"title":39,"period":40,"company":41,"current":42,"description":43},"Senior Fullstack Developer","2025 — present","Flot",true,"Implementing designs and building high-performance interfaces, creating APIs and integrating third-party services. Leading integrations and the production releases of the web and mobile applications.",{"title":45,"period":46,"company":47,"description":48},"Fullstack Developer","2025","Emeryte","Building internal software: a money transfer application and a sports betting management platform.",{"title":50,"period":51,"company":52,"description":53},"Fullstack & IoT Developer","2024 — 2025","Orange Digital Center","Selected for the Orange Digital Academy programme to design an innovative project combining IoT and artificial intelligence.",{"title":55,"period":56,"company":57,"description":58},"Web Developer","2022 — 2024","In-novation","Building a platform to manage paid assignments for influencers and content creators.",{"title":60,"period":61,"company":57,"description":62},"Web Developer Intern","2022","Contributed to building an e-commerce template generator for small retailers.",[64,68],{"role":65,"quote":66,"author":67},"Project Manager — Perafind","Marc Ariel Oka est un travailleur vraiment sérieux. En travaillant avec lui sur Perafind, j'ai apprécié son dévouement et sa passion pour son métier de développeur. Dynamique et ouvert d'esprit, il sait piloter un projet et aime le travail bien fait. Je suis très satisfait de collaborer avec lui.","Franck Joris Anael Ahoussi",{"role":69,"quote":70,"author":71},"CEO — DS-Accessories","Un travail vraiment impeccable, rien à redire.","Michèle Samuela Koumi Ntakpe","2026-11-05T20:00:57.915801+00:00",{},{"project":75,"sections":147,"introHtml":148,"bodyHtml":149,"toc":150,"highlights":176,"previous":187,"next":188},{"id":76,"slug":77,"title":78,"summary":79,"excerpt":80,"intro":81,"body":82,"highlights":83,"seoTitle":99,"seoDescription":100,"kind":101,"origin":102,"period":103,"role":104,"coverUrl":105,"coverAlt":106,"status":107,"featured":42,"sortOrder":108,"lang":109,"translated":42,"technologies":110,"context":139,"responsibilities":140,"decisions":141,"challenges":141,"solutions":141,"results":142,"liveUrl":143,"demoUrl":141,"repoUrl":141,"translations":144,"publishedAt":145,"updatedAt":146},"85d6d21f-bbc9-4df1-ae3b-eecf9a9e7f4d","factio","FACTio","My own SaaS for invoicing and payment tracking, aimed at freelancers and small businesses.","Invoices and quotes, expense tracking, automatic OHADA accounting, FNE certification and e-mail and WhatsApp payment reminders. I designed, built and shipped it to production.","Small businesses can't afford an accountant day to day. Invoices are issued as they go, scattered, with whatever knowledge is at hand. And at year end, when financial statements have to go to the State, everyone is overwhelmed.\n\nFACTio started from that observation. I built it to issue invoices and quotes, track expenses and give a view of the books without the user having to enter anything. With the arrival of the FNE in Côte d'Ivoire, it also simplifies an integration that is difficult.\n\nIt is my own SaaS, from the first commit in January 2026 to automated deployment in production. This case study covers the decisions that shaped its architecture, what I chose to postpone, and what is still to do.","## Where it started\n\nI wanted to answer that observation with a simple tool: you issue your invoices and quotes, you track your expenses, and all of it gives a view of the books without the user having to enter anything. The intended effect is twofold. Entrepreneurs pick up accounting notions by seeing what their own day-to-day operations produce; and since everything is centralised, the accountant can build a high-quality financial statement at year end, with confidence.\n\nA second trigger was the arrival of the FNE in Côte d'Ivoire. Integrating it into a system is difficult; FACTio simplifies it, and it is my way of encouraging companies to stay compliant.\n\nI don't publish adoption numbers here: they are not the point of this case study.\n\n## The first building blocks\n\nThe repository was created on 3 January 2026 with a Laravel API and a Vue app in a single monorepo. In the first days I wrote the authentication screens and the deployment configuration. Then the project went quiet until late March.\n\nIn March the real problem became going live. For a week the commits read like any first deployment: ports, nginx, environment variables, CORS, timeouts. In the end, a GitHub Actions pipeline deployed to a VPS. April brought subscriptions, permissions, support channels and error tracking with Sentry. In September I added the affiliate programme and my first complete test suite with CI.\n\n## A deliberately simple architecture\n\nThe backend is a **Laravel** API authenticated with Sanctum, with three separate spaces: user, admin and affiliate. The frontend is a **Vue** application in TypeScript (Vite, Pinia, Tailwind) that can be installed as a web app.\n\nIn production, Docker Compose runs five services: the API on php-fpm, a queue worker for outgoing messages, a scheduler for recurring tasks, and two nginx instances. Data lives in **PostgreSQL**; tests run on SQLite. External services are few: Lemon Squeezy for subscriptions, the FNE platform for certification, Google for sign-in, Sentry for errors, and **Wasly**, the WhatsApp messaging SaaS I am building in parallel, with FACTio as its first customer.\n\n[![Simplified FACTio architecture: Vue application, two nginx instances, Laravel API, queue worker, scheduler, PostgreSQL and external services](\u002Fimages\u002Fprojects\u002Ffactio-architecture.svg)](\u002Fimages\u002Fprojects\u002Ffactio-architecture.svg)\n\n*Simplified diagram, based on the project's Docker Compose configuration.*\n\nI did not try to build a \"scalable\" architecture before having users: one monorepo, one database, clearly separated services.\n\n## October: from a product to a roadmap\n\nIn October 2026 I changed how I worked. I wrote a roadmap from the actual state of the code (routes, models, migrations, services) and then executed it in **batches**: foundations, audit log, PDF, invoicing, customers, reminders, expenses and cash management, accounting, authentication and subscription, observability, customer portal and PWA. Each batch was merged before the next one.\n\nI got help from a coding assistant (Claude): to debug certain errors, to challenge my proposals against my original ideas and to implement several batches. The scope, the trade-offs and the validation (tests, CI, production release) stayed mine.\n\nOn 6 October a set of decisions fixed the direction: card subscription with automatic billing (no Mobile Money), uncapped WhatsApp outside the trial to attract the first users, and online payment by the end customer postponed.\n\n## The decisions that shaped the product\n\n**WhatsApp: separating the engine from the product.** The first version embedded a WhatsApp engine in the repository. I moved it out of FACTio to rely on Wasly, the other SaaS I am building and for which FACTio is the first customer: one session per company, queued sending, signed webhooks. Each product keeps its own responsibilities.\n\n**Numbering: a locked counter.** An invoice must carry a unique number even when two users create a document at the same instant. Each company has one series per document type and per year, incremented inside a locked transaction. A number already taken is skipped, never reused. The format is configurable.\n\n**Accounting: we never rewrite history.** OHADA entries are generated automatically, corrections go through reversing entries, and closing a fiscal year locks the period. Tests check that entries balance. One bug reminded me why: third-party accounts shared between customers had to be repaired with a dedicated command.\n\n**FNE: each company keeps its own link.** I decided that each company enters its own FNE production link. That choice needed guardrails: the address is validated before any call, and the same certification cannot run twice in parallel. The PDF carries the DGI sticker with its number and QR code.\n\n**Deployment: never without green CI.** Production deployment only runs when CI is green on the main branch, without stopping containers, and pulls fresh base images.\n\n## Quality, and its pitfalls\n\nCI runs linting, dependency audits, backend tests, frontend tests, the build and an end-to-end Playwright journey against a production build. It also taught me concrete lessons: an intermittent failure caused by OPcache's JIT on the runners, an unstable E2E journey fixed by switching SQLite to WAL mode, security advisories with no available fix that I documented instead of breaking the lint setup.\n\nReviewing the code also surfaced several security flaws, which I fixed.\n\n## What I left out\n\nNo Mobile Money subscription, no online payment for the end customer, no bank reconciliation, no stock management, no multi-currency. These absences are decisions or deferrals, not oversights. FACTio ships no artificial-intelligence feature: AI helped build the product, it does not run it.\n\n## Where FACTio stands\n\nThe product is in production, deployed automatically after every green CI run. The latest versioned work covers dependency and base-image security. Around the code, the project comes with a landing page, a demo playbook and presentation videos.\n\nStill to do: quote reminders, history import, bank reconciliation and, depending on adoption, online payment by the end customer.",[84,87,90,93,96],{"body":85,"title":86},"*Problem*: an engine inside the repository ties the product to an unstable component. *Decision*: FACTio becomes a client of Wasly, my other SaaS (WhatsApp), with one session per company and HMAC-SHA256 signed webhooks. *Consequence*: messaging becomes a service of its own, which FACTio uses like any other customer.","WhatsApp: from embedded to a dedicated service",{"body":88,"title":89},"One counter per company, type and year, incremented under `SELECT … FOR UPDATE`. A taken number is skipped, never reused; format (prefix, separator, padding) is configurable.","Numbering without duplicates",{"body":91,"title":92},"Automatic OHADA entries, corrections by reversal, a year-end closing that locks the period, FEC export, balance tests.","Accounting you don't rewrite",{"body":94,"title":95},"Each company enters its production URL, validated before any call; the same certification cannot run twice in parallel.","FNE: one link per company, with guardrails",{"body":97,"title":98},"Production deployment only runs after green CI on the main branch, without downtime, on up-to-date base images.","Deploy without breaking things","FACTio — case study: building and shipping an invoicing SaaS for Côte d'Ivoire","FACTio case study: my invoicing SaaS for Ivorian small businesses — Laravel, Vue, OHADA accounting, FNE certification, WhatsApp reminders, CI\u002FCD.","SaaS in production","product","2026 — ongoing","Founder & Software Engineer","\u002Fimages\u002Fprojects\u002Ffactio.webp","FACTio home page","published",1,"en",[111,115,119,123,127,131,135],{"id":112,"name":113,"slug":114},"dced59f3-5c3b-4ee1-b03a-1356b04de744","Docker","docker",{"id":116,"name":117,"slug":118},"34a7d189-accd-4ddb-87c2-5cdd682ca55f","Laravel","laravel",{"id":120,"name":121,"slug":122},"44512b60-1094-4481-9c0a-86e7e76264b2","PHP","php",{"id":124,"name":125,"slug":126},"e3844443-49eb-4785-8b4f-6fd30b006e0c","PostgreSQL","postgresql",{"id":128,"name":129,"slug":130},"5befc380-4994-4031-bbeb-d16941dfba02","Tailwind CSS","tailwind-css",{"id":132,"name":133,"slug":134},"d9ef12c1-f397-4295-b284-3e79981dd835","TypeScript","typescript",{"id":136,"name":137,"slug":138},"673fa695-c2f1-4af8-bd06-4ce8872fdf4f","Vue.js","vue-js","FACTio is my own product: a SaaS for invoicing and payment tracking, aimed at freelancers and small businesses.","I designed, built and shipped FACTio. From product design to technical architecture, through fullstack development and deployment, I led the whole of its delivery.","","The product is in production. I keep evolving it based on what its users need.","https:\u002F\u002Fwww.getfactio.com\u002F",{},"2026-11-05T10:43:49.536997+00:00","2026-11-05T10:47:29.359266+00:00",[],"\u003Cp>Small businesses can’t afford an accountant day to day. Invoices are issued as they go, scattered, with whatever knowledge is at hand. And at year end, when financial statements have to go to the State, everyone is overwhelmed.\u003C\u002Fp>\n\u003Cp>FACTio started from that observation. I built it to issue invoices and quotes, track expenses and give a view of the books without the user having to enter anything. With the arrival of the FNE in Côte d’Ivoire, it also simplifies an integration that is difficult.\u003C\u002Fp>\n\u003Cp>It is my own SaaS, from the first commit in January 2026 to automated deployment in production. This case study covers the decisions that shaped its architecture, what I chose to postpone, and what is still to do.\u003C\u002Fp>\n","\u003Ch2 id=\"where-it-started\">Where it started\u003C\u002Fh2>\n\u003Cp>I wanted to answer that observation with a simple tool: you issue your invoices and quotes, you track your expenses, and all of it gives a view of the books without the user having to enter anything. The intended effect is twofold. Entrepreneurs pick up accounting notions by seeing what their own day-to-day operations produce; and since everything is centralised, the accountant can build a high-quality financial statement at year end, with confidence.\u003C\u002Fp>\n\u003Cp>A second trigger was the arrival of the FNE in Côte d’Ivoire. Integrating it into a system is difficult; FACTio simplifies it, and it is my way of encouraging companies to stay compliant.\u003C\u002Fp>\n\u003Cp>I don’t publish adoption numbers here: they are not the point of this case study.\u003C\u002Fp>\n\u003Ch2 id=\"the-first-building-blocks\">The first building blocks\u003C\u002Fh2>\n\u003Cp>The repository was created on 3 January 2026 with a Laravel API and a Vue app in a single monorepo. In the first days I wrote the authentication screens and the deployment configuration. Then the project went quiet until late March.\u003C\u002Fp>\n\u003Cp>In March the real problem became going live. For a week the commits read like any first deployment: ports, nginx, environment variables, CORS, timeouts. In the end, a GitHub Actions pipeline deployed to a VPS. April brought subscriptions, permissions, support channels and error tracking with Sentry. In September I added the affiliate programme and my first complete test suite with CI.\u003C\u002Fp>\n\u003Ch2 id=\"a-deliberately-simple-architecture\">A deliberately simple architecture\u003C\u002Fh2>\n\u003Cp>The backend is a \u003Cstrong>Laravel\u003C\u002Fstrong> API authenticated with Sanctum, with three separate spaces: user, admin and affiliate. The frontend is a \u003Cstrong>Vue\u003C\u002Fstrong> application in TypeScript (Vite, Pinia, Tailwind) that can be installed as a web app.\u003C\u002Fp>\n\u003Cp>In production, Docker Compose runs five services: the API on php-fpm, a queue worker for outgoing messages, a scheduler for recurring tasks, and two nginx instances. Data lives in \u003Cstrong>PostgreSQL\u003C\u002Fstrong>; tests run on SQLite. External services are few: Lemon Squeezy for subscriptions, the FNE platform for certification, Google for sign-in, Sentry for errors, and \u003Cstrong>Wasly\u003C\u002Fstrong>, the WhatsApp messaging SaaS I am building in parallel, with FACTio as its first customer.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Fimages\u002Fprojects\u002Ffactio-architecture.svg\">\u003Cimg src=\"\u002Fimages\u002Fprojects\u002Ffactio-architecture.svg\" alt=\"Simplified FACTio architecture: Vue application, two nginx instances, Laravel API, queue worker, scheduler, PostgreSQL and external services\" loading=\"lazy\" decoding=\"async\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>Simplified diagram, based on the project’s Docker Compose configuration.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>I did not try to build a « scalable » architecture before having users: one monorepo, one database, clearly separated services.\u003C\u002Fp>\n\u003Ch2 id=\"october-from-a-product-to-a-roadmap\">October: from a product to a roadmap\u003C\u002Fh2>\n\u003Cp>In October 2026 I changed how I worked. I wrote a roadmap from the actual state of the code (routes, models, migrations, services) and then executed it in \u003Cstrong>batches\u003C\u002Fstrong>: foundations, audit log, PDF, invoicing, customers, reminders, expenses and cash management, accounting, authentication and subscription, observability, customer portal and PWA. Each batch was merged before the next one.\u003C\u002Fp>\n\u003Cp>I got help from a coding assistant (Claude): to debug certain errors, to challenge my proposals against my original ideas and to implement several batches. The scope, the trade-offs and the validation (tests, CI, production release) stayed mine.\u003C\u002Fp>\n\u003Cp>On 6 October a set of decisions fixed the direction: card subscription with automatic billing (no Mobile Money), uncapped WhatsApp outside the trial to attract the first users, and online payment by the end customer postponed.\u003C\u002Fp>\n\u003Ch2 id=\"the-decisions-that-shaped-the-product\">The decisions that shaped the product\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>WhatsApp: separating the engine from the product.\u003C\u002Fstrong> The first version embedded a WhatsApp engine in the repository. I moved it out of FACTio to rely on Wasly, the other SaaS I am building and for which FACTio is the first customer: one session per company, queued sending, signed webhooks. Each product keeps its own responsibilities.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Numbering: a locked counter.\u003C\u002Fstrong> An invoice must carry a unique number even when two users create a document at the same instant. Each company has one series per document type and per year, incremented inside a locked transaction. A number already taken is skipped, never reused. The format is configurable.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Accounting: we never rewrite history.\u003C\u002Fstrong> OHADA entries are generated automatically, corrections go through reversing entries, and closing a fiscal year locks the period. Tests check that entries balance. One bug reminded me why: third-party accounts shared between customers had to be repaired with a dedicated command.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>FNE: each company keeps its own link.\u003C\u002Fstrong> I decided that each company enters its own FNE production link. That choice needed guardrails: the address is validated before any call, and the same certification cannot run twice in parallel. The PDF carries the DGI sticker with its number and QR code.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Deployment: never without green CI.\u003C\u002Fstrong> Production deployment only runs when CI is green on the main branch, without stopping containers, and pulls fresh base images.\u003C\u002Fp>\n\u003Ch2 id=\"quality-and-its-pitfalls\">Quality, and its pitfalls\u003C\u002Fh2>\n\u003Cp>CI runs linting, dependency audits, backend tests, frontend tests, the build and an end-to-end Playwright journey against a production build. It also taught me concrete lessons: an intermittent failure caused by OPcache’s JIT on the runners, an unstable E2E journey fixed by switching SQLite to WAL mode, security advisories with no available fix that I documented instead of breaking the lint setup.\u003C\u002Fp>\n\u003Cp>Reviewing the code also surfaced several security flaws, which I fixed.\u003C\u002Fp>\n\u003Ch2 id=\"what-i-left-out\">What I left out\u003C\u002Fh2>\n\u003Cp>No Mobile Money subscription, no online payment for the end customer, no bank reconciliation, no stock management, no multi-currency. These absences are decisions or deferrals, not oversights. FACTio ships no artificial-intelligence feature: AI helped build the product, it does not run it.\u003C\u002Fp>\n\u003Ch2 id=\"where-factio-stands\">Where FACTio stands\u003C\u002Fh2>\n\u003Cp>The product is in production, deployed automatically after every green CI run. The latest versioned work covers dependency and base-image security. Around the code, the project comes with a landing page, a demo playbook and presentation videos.\u003C\u002Fp>\n\u003Cp>Still to do: quote reminders, history import, bank reconciliation and, depending on adoption, online payment by the end customer.\u003C\u002Fp>\n",[151,155,158,161,164,167,170,173],{"id":152,"text":153,"level":154},"where-it-started","Where it started",2,{"id":156,"text":157,"level":154},"the-first-building-blocks","The first building blocks",{"id":159,"text":160,"level":154},"a-deliberately-simple-architecture","A deliberately simple architecture",{"id":162,"text":163,"level":154},"october-from-a-product-to-a-roadmap","October: from a product to a roadmap",{"id":165,"text":166,"level":154},"the-decisions-that-shaped-the-product","The decisions that shaped the product",{"id":168,"text":169,"level":154},"quality-and-its-pitfalls","Quality, and its pitfalls",{"id":171,"text":172,"level":154},"what-i-left-out","What I left out",{"id":174,"text":175,"level":154},"where-factio-stands","Where FACTio stands",[177,179,181,183,185],{"title":86,"html":178},"\u003Cp>\u003Cem>Problem\u003C\u002Fem>: an engine inside the repository ties the product to an unstable component. \u003Cem>Decision\u003C\u002Fem>: FACTio becomes a client of Wasly, my other SaaS (WhatsApp), with one session per company and HMAC-SHA256 signed webhooks. \u003Cem>Consequence\u003C\u002Fem>: messaging becomes a service of its own, which FACTio uses like any other customer.\u003C\u002Fp>\n",{"title":89,"html":180},"\u003Cp>One counter per company, type and year, incremented under \u003Ccode>SELECT … FOR UPDATE\u003C\u002Fcode>. A taken number is skipped, never reused; format (prefix, separator, padding) is configurable.\u003C\u002Fp>\n",{"title":92,"html":182},"\u003Cp>Automatic OHADA entries, corrections by reversal, a year-end closing that locks the period, FEC export, balance tests.\u003C\u002Fp>\n",{"title":95,"html":184},"\u003Cp>Each company enters its production URL, validated before any call; the same certification cannot run twice in parallel.\u003C\u002Fp>\n",{"title":98,"html":186},"\u003Cp>Production deployment only runs after green CI on the main branch, without downtime, on up-to-date base images.\u003C\u002Fp>\n",null,{"slug":189,"title":190},"perafind","Perafind"]