Wenodify
This platform — the visual studio and public site (wenodify.peacae.com). Idea Map, Idea Pad, and Family Tree live here.
About Wenodify
Create content visually — built for relationships, not documents.
Wenodify runs in your browser with two canvases in Studio. Idea Map is where you create maps, conversations, and quizzes visually. Family Tree is for genealogy, language lineage, and org charts. Add nodes, connect branches, fill in labels and notes, then export JSON or SQL when you are ready.
A Wekify product on Peacae.com, created to author Kifuliiru conversations, questions, and maps — and to support other places the same way.
How to read the name
Brand · verb · workspace
Wenodify is the brand · nodify is the act · Studio is where you work.
nodify
To nodify is to work on the canvas — add nodes, branch, relate, label, note, and lay out a map or tree.
Studio
The in-browser workspace at /app where you create content visually: Idea Map for maps and conversations, Idea Pad for freeform whiteboards, Family Tree for genealogy and lineage, plus export and local-first editing.
Where it came from
We needed a place to think before the database.
Wenodify is part of the Peacae.com family — Peacae is the home for Wekify products that are not language products. The company is Wekify LLC. Wekify's current language work is Kifuliiru: conversations, questions, lesson paths, and family trees that need a dedicated studio before they belong in a dictionary or learning app. We kept authoring that content inside the same platforms meant to preserve and deliver it. Those surfaces became crowded: mapping, editing, storing, and running experiences all fought for the same UI.
Wenodify started as a deliberate split. A dedicated studio for mind maps, concept maps, whiteboards, and family trees — authoring first, export as the handoff. Platforms stay specialized for preservation and delivery. We are not trying to replace a genealogy subscription. We are building the toolchain we will use ourselves.
We from Wekify, nodify from nodes. The brand is Wenodify; the verb is nodify — add nodes, branch, relate, and shape a map or tree on the canvas. Studio is the workspace; nodify is what you do in it.
Family
Wenodify, Peacae, Wekify, and Kifuliiru
These names are related. They are not four names for the same product.
Wenodify
The visual studio you are on. Idea Map, Idea Pad, and Family Tree live here so you can create content visually, then export it.
Peacae
Peacae.com is the home for Wekify products that are not language products. Wenodify is one of them.
Wekify
Wekify LLC builds Wenodify, Peacae, and the Kifuliiru language platforms.
Kifuliiru
The language Wekify is currently working with. Wenodify was created so teams can author Kifuliiru conversations, questions, and lesson paths — and support other places the same way.
How it fits together
What Studio does
Map, edit, and export — a mind map, a whiteboard, or a family tree, all in the browser. No account required; your work stays local until you choose to download it.
Map on the canvas
Start with a root node and create content visually. Add children, partners, and branches — Idea Map for maps and conversations, Idea Pad for loose sketches, Family Tree for genealogy and lineage.
Edit and organize
Labels and notes on every node. Collapse branches, search the map, auto-layout, undo — stay in flow while the structure grows.
Export your work
Download JSON to keep editing later, or SQL with an export profile. Import a file back anytime to pick up where you left off.
Idea Map · mind maps and seven export shapes
Same tree. Different meaning at export.
Idea Map is the mind map canvas. Seven types on one tree — pick the shape that matches how your content will be delivered: a classic concept map, a conversation, a quiz, and more.
Ideas
Concept maps and outlines. Label = topic; body = notes.
Conversation
Scripted dialog and guided scenes. Label = spoken line; body = delivery notes.
Chatbot
Interactive bots with reply options. Label = prompt or option; body = bot response.
Quiz
Branching assessments. Label = question; body = choices and feedback.
Steps
Procedures and lesson paths. Sibling order matters.
Explorer
Browse-by-topic trees. Label = entry; body = summary or reference.
Chain of Thought
Reasoning from problem to answer. Label = beat; body = full thought. Sibling order matters.
Idea Pad · freeform whiteboard
Sketch first. Structure later.
Idea Pad is the infinite board — sticky cards, ink, and arrows with no graph type to pick. Export JSON when you want a backup; use Idea Map when the sketch is ready to become a tree.
Sticky cards
Handwritten notes on colored cards you can drag anywhere on the board.
Ink
Freehand strokes in five colors for sketches, arrows, and marks that are not a card yet.
Connections
Arrow links between cards when two thoughts belong together.
Focus hops
Dim everything beyond N hops from a card so one branch stays readable.
Family Tree · genealogy, org charts, eight templates
One family tree maker. Eight ways to start.
Family Tree is a genealogy and family tree maker that also covers language families, clan lineage, noun classes, etymology, dialect maps, org charts, and knowledge domains. Pick a template when you start — exports include treeType so loaders know how to read your labels. Read the tree types guide
Family Genealogy
Household genealogy and family tree maker — the default template for people, partners, and generations.
Language Family Tree
Linguistic descent — how a proto-language splits into branches and regional forms.
Clan & Lineage Tree
Clan structure and living descent from a shared ancestor.
Noun Class Tree
Grammatical noun-class systems — classes, subclasses, and exemplar vocabulary.
Word Etymology Tree
Lexical history — how a root form develops across time and usage.
Dialect Map
Regional variation — how a standard or parent lect splits into dialect geography.
Org Chart
Org chart maker — teams, departments, and reporting lines on the family tree canvas.
Knowledge Domain Tree
Taxonomic knowledge maps — subjects broken into topics and subtopics.
Product principles
Built for the canvas
Every control should help you map, edit, or export — not compete with the work.
Momentum first
Creation should feel immediate. The tool should never become the work.
Clarity over clutter
Controls stay close enough to help and quiet enough to let the canvas lead.
See it in motion