About Kecare: Start Here Meow

Writing documentation is really a bit difficult for me...
If you find anything hard to understand, please don't scold me first (whispering). You can submit an Issue / PR to help me improve it, and I'll be super grateful! Sorry, sorry, sorry (bow.gif)

Kecare is a generator framework for modern static blogs and note sites. Its primary goal is not to "create another Hexo," but to separate the content system from the theme/framework, turning your blogging capabilities into "pluggable modules" meow~

What Makes Kecare More "Advanced" Than Hexo: Non-Invasive Meow!

Many traditional blogging solutions (like Hexo) will lock you into a fixed ecosystem:
themes, builds, plugins, directory structures—many things are tightly coupled with it. If you want to switch tech stacks, you have to start over from scratch.

The core advantage of Kecare lies in its Non-intrusive nature.

In one sentence, it means:

If you are a front-end developer, you can directly "install" a blog system onto your existing application with almost no concern for the technology stack used by the original project.
You just need to create a .kecare/ directory in your old project, write the content and rules according to the convention, and Kecare will generate the blog-related pages/data for you based on the rules you define, meow~

Your original project could be:

• Vue / Nuxt
• React / Next
• Svelte / SvelteKit
• Traditional Server-Side Rendering Frameworks (SSR)
• Even just an old project (as long as you can integrate the generated results, it's fine)

Kecare doesn't force you to migrate, change your architecture, or rewrite your pages.
It's like an "external content production line," attaching the blog system in the lightest way possible meow~

Two Ways of Usage: Default Theme vs Custom Theme

Kecare offers two "user-friendly starting paths" for external users, and you can choose according to your needs~

1) Default Theme (Works Out of the Box Meow)

If you just want to have a blog that works, looks good, and is ready for writing right away—you can directly use the default theme I provide.

• Tech Stack: Nuxt + Vue3
• Target Audience: You who want to start writing quickly and get the blog up and running first, meow~
• Features: You almost don't need to understand the internal details of Kecare. Just place the .kecare/ content as per the documentation and run the commands.

2) Custom Themes (The True "Non-Invasive" Capability Meow)

If you value the freedom of being "technology stack agnostic," then Kecare's custom theme path is just for you~

You can:

• Add a .kecare/ directory in any tech stack/framework (Vue/React/Svelte/SSR/legacy projects)
• Define generation rules in your preferred way (e.g., how articles are converted to HTML, how routing data is generated, how menu data is generated, etc.)
• Let Kecare output consumable content artifacts for your project (such as structured data, static page fragments, resource indexes, etc.)

Then your project only needs to do one thing:

By integrating Kecare's output for rendering (or directly publishing it), you complete a "plugin-style blog system."

This is the ideal state of Kecare: Blogging capabilities are additional, portable, and not bound to themes, meow~