pureblazor / docs Goto Github PK

Support Spanish, German, Portuguese, and French.

REST API to manage all actions in the CMS using either REST or gRPS.

Automatically and securely backup all your content and data.

Implement a drag-and-drop intuitive interface allowing users to create content in a visual fashion, without having to write code. Users will be able to select components like text, buttons, sliders, etc. in a crude approximation to tools like Retool or Bubble.

Text editor built with Blazor, instead of a wrapper around existing JS implementations.

First-party integration for payments, sms, etc.

• Publish history
• Rollback (undo or rollback to a previous version if needed).
• Git integration for history? e.g., store all articles/blogs/pages in git as plaintext. investigate further.

Fix deficiency with Blazor's refresh to resolve a number of user experience bugs:

• Make Blazor PWA auto-detect a newer version of the app
• Web Assembly is too big and the signalr connection is not smooth
• Failing to reconnect when tabbing away

AI support to generate titles, summaries, references, tags, and more.

First-party e-commerce support and integration capability for your own ecomm solution such as Shopify, Woo, etc.

Functionality to fully utilize PureBlazor CMS for blogs or full sites

• Pages
• Layouts
• Articles

Support the following user requests:

• Be able to format numbers/strings on mobile (not just desktop).
• Detect which device the app is running on (like Bit Platform does).
• Preview in different screen layouts before publishing.
• Extensibility between web and mobile.

Extend the CMS with your own custom plugins with C# and Blazor.

Support Right to Left language styling for CMS.

Support Visual Studio templates

Support automatic Tailwind CSS generation.

Run the app offline for customers in areas with low/unsteady internet connectivity.

Create a full single-page static site with Markdown.

Host static pages on a PureBlazor custom domain (e.g. your-name.wasmhost.dev).

Enable simple fetch and dom manipulation.

Technical Notes

Developers want to be able to easily grab data from the server with minimal overhead. This is easily achievable with Blazor Server. When WASM is introduced, you then must have some kind of API client -- which has varying levels of overhead. This is further complicated when you are using the unified Blazor model where you render both on the server and then again using WASM.

We should investigate ways to improve the experience for this dev flow.

Support for a theme marketplace.

Basic Identity/Login with a Local Account. No external/social login Providers (Auth0, Google, etc.).

Support for workflow integrations (e.g. trigger actions after certain rules are met, approve content for publishing, etc.).

Support bespoke analytics for Blazor instead of solutions like GA/Amplitude.

Host Blazor WASM static sites directly within PureBlazor with your choice of a built-in subdomain (e.g. your-name.wasmhost.dev).

Support Asset Management to streamline the organization, storage, and retrieval of assets such as photos, animations, videos, documents, etc.

Custom form builder for customer content type.

TODO: Determine the best way to represent this to the devs, some ideas:

1. Use JSON
2. Use C# Interfaces
3. Use a UI builder?
4. Use SQL or SQL-ish?

Build Blazor identity, a bespoke openID-complaint identity solution.

• Add a component library to build pages with code (like Radzen or Devexpress).
  • https://github.com/pureblazor/components
• Support reusable blocks of content across different website sections.
• Support Plugins/External Sources (e.g. Nuget feeds) for custom blocks

Larger layout components:

• Headers
• Footers
• Side navigation
• Flyout windows

Share your plugins with others and find others' plugins to add to your CMS.

Use roles and claims to create security boundaries and authotization policies such as administrative access, guest/client login, etc.

One-click landing page and contact forms (e.g. TypeForm).

Support bespoke Application Performance Monitoring (APM) or bring your own APM solution such as New Relic, DataDog, etc.

Convert Figma files to Blazor.

Being able to include the CMS easily in existing B2B applications in the customer's stack.

• Headless CMS API
• Back Office Pages

Enable CMS webhooks to be notified of new content, analytics, comments, etc.

Support experimentation, A/B testing, and feature flags all within the Blazor CMS.

Automatically issue HTTPS certificates on a PureBlazor-custom domain.

Support exporting all data components and pages to use with a different hosting solution without being tied to PureBlazor.

Support background jobs for adhoc and recurring CMS tasks.

Support bespoke logging service for Blazor or bring your own log solution such as Elastic/DataDog/text files.