Blazor Server examples
Reference integration package for teams evaluating RichTextEditor in Blazor Server applications.
dotnet new richtexteditor-blazor -n MyAppChoose a starter, run it locally, and try your real content. Everything you need to begin evaluating RichTextEditor—without a signup.
Choose one path. You do not need to download a ZIP as well as use npm.
Use the React starter below, or choose an Angular, Vue, or other framework example.
Follow its setup commands and open the local URL printed in your terminal. You should see an editor where you can type and format text.
Paste a document and check its formatting. Then connect saving to your application using the content guide.
Start in a new folder with Node.js and npm installed. Run each command in order.
Already have an app? Read the React integration guide →
npm create @richscripts/richtexteditor my-app -- --reactcd my-appnpm installnpm run devOpen the local URL printed in your terminal. You should see an editor where you can type and format text.
Need a hand? Check setup troubleshooting or contact support.
Use the current 2.6.3 packages for new work, keep the 1.015 files for existing deployments that still depend on the older release, and use the upgrade page when you need to move a 1.x license forward.
The current release is the right starting point for teams testing the editor today.
Older builds remain available so existing 1.x applications can stay stable during transition work.
Existing customers can use the upgrade path instead of repurchasing a full new license.
For an existing project, install the npm package and follow your framework’s integration guide. Installing the package alone does not add an editor to your page.
npm install @richscripts/richtexteditornpm create @richscripts/richtexteditor my-app -- --reactPrefer plain HTML? Follow the complete quick-start example, including the stylesheet, editor container, and initialization code. The script below loads the engine only.
<script src="https://cdn.jsdelivr.net/npm/@richscripts/richtexteditor@2.11.0/richtexteditor/rte.js"></script>These packages are useful when you want to evaluate RichTextEditor in a realistic app structure instead of starting from a blank page. .NET teams can scaffold instead of downloading: dotnet new install RichTextEditor.Templates, then run the per-framework command shown on each card.
Reference integration package for teams evaluating RichTextEditor in Blazor Server applications.
dotnet new richtexteditor-blazor -n MyAppSample project showing editor setup inside Razor Pages and common ASP.NET Core page flows.
dotnet new richtexteditor-razor -n MyAppController and view-based sample package for MVC applications built on ASP.NET Core.
dotnet new richtexteditor-mvc -n MyAppClassic ASP.NET MVC sample package for teams working in the .NET Framework stack.
Web Forms sample package for legacy .NET applications that still use the classic page model.
Starter project for evaluating RichTextEditor in PHP applications and admin workflows.
Angular integration package for teams testing component-based setup and editor lifecycle flows.
npm create @richscripts/richtexteditor my-app -- --angularReact sample package for evaluating editor state management, embeds, and application integration.
npm create @richscripts/richtexteditor my-app -- --reactVue sample package for teams exploring RichTextEditor in modern frontend application workflows.
npm create @richscripts/richtexteditor my-app -- --vueMost teams only need the main RichTextEditor package plus one framework example that matches the application they are building. If you are evaluating multiple stacks, download the core package first and then compare framework examples side by side.