Hello Internet! Meet Redpoint - A New Future for SudoVanilla

Before we get into it, let me introduce myself. I’m Korbs, I also go by SudoVanilla as my developer entity, my work has been guided by a philosophy of open source and digital sovereignty, the belief that we can build software that respects user freedom and privacy without sacrificing functionality. Over the last few years, I’ve moved away from these centralized, corporate platforms to a self-hosted ecosystem, managing my own Mastodon, and to my own Forgejo repositories.

This commitment in my own independence has also led to me down a path to develop an extensive suite of in-house solutions to power my infrastructure and projects. This includes projects around building my own video player, content management system, documentation template, a directory viewer for static assets, and much more.

Redpoint is my most ambitious project yet, to go even further in building my own in-house solutions, my own framework. It’ll represent a shift from simply using open source tools to defining the very architecture they’ll run on. This will guide a new future forward for SudoVanilla projects and its infrastructure, where I now need to build my own foundation that is done my way; up to my standards of performance, privacy, and long-term sustainability.

Meet Redpoint

Say hello to Redpoint, an all-new zero-config, TypeScript-first web framework for developers who value security and performance.

• Server First: Components are rendered on the server, sending lightweight HTML Redpoint boosts site speed by rendering components server-side and delivering lean HTML to the browser, eliminating any unnecessary JavaScript.

• Zero Bloat: Only the code your import reaches the client, so the payload stays tiny and loads instantly. No more worries about node_modules directory or a heavy package manager - Redpoint is built around Deno's secure URL-based imports.

• Layouts and Components: Define reusable layout files and build your own components library with native TypeScript, letting you structure pages consistently while retaining full control over markup and styling.

• Aiming for a Zero-Dependency Core: Aiming to ship with no external dependencies*, keeping the installation footprint minimal and avoiding version-conflict headaches.

Proudly Built on Deno

Thanks to the power of being on top of the Deno runtime, you get TypeScript first-class support with no additional setup needed for your project; security as a standard with a permission-based architecture leaving you with a final say on all network and file system access in a trusted, restricted sandbox; and removing the need of the annoying node_modules directory and package.json file, leaving the legacy overhead behind and no more dependency hell.

With Redpoint being designed around Deno, you also get tons of more features that's provided by Deno: Web Standards, Code Linter, Test Runner, Code Formatter, Standalone Executables, and much more.

Behavior and Structure

As for how I want to design Redpoint as a framework, I'm planning on make it behave and to be structured something similar to the Astro Web Framework, as part of Redpoint is inspired by Astro itself. As I've been using Astro for the past 4 years now and have gotten used to how their structure and ecosystem works, I believe it makes sense to go this direction to have familiarity.

I'm interested in mirroring Astro's component-based architecture and zero-latency overhead. Also by adopting a similar file-based routing system and configuration pattern, I can ensure that Redpoint won't just feel intuitive for me, but to any developer who has worked in environments like this. Part of Astro's mission is to ship less JavaScript to the client, which is something that has become priority in my projects over the past couple of years of development.

Furthermore, I want Redpoint to embrace a highly modular integration system. Just as Astro allows developers to easily plugin and play with their preferred tools - whether it's Tailwind for styling or various UI libraries for specific components.

Future of SudoVanilla

Since this is being developed as an in-house solution for my developer entity, SudoVanilla, this also means all of SudoVanilla projects and it's surrounding ecosystem will all be slated for an overhaul; to be rewritten on top of Redpoint. With that in mind, SudoVanilla will have it's portfolio migrated to use this new framework for all projects moving forward, allowing to battle-test Redpoint in real world scenarios until it is no longer a hobby project, but to become the backbone of SudoVanilla's infrastructure and ecosystem.

Redpoint has been open sourced under the GNU Affero General Public License on SudoVanilla Ark and the documentation are already available to view to get started on using the new framework.

Redpoint is currently only distributed under the sudovanilla.org and redpoint.sh domain name, as part of the SudoVanilla Umbrella Policy. If found else where would be unofficial and not controlled by SudoVanilla.

• Documentation: https://docs.redpoint.sh
• Source Code: https://source.redpoint.sh