Hey there! AmzroSevca typing! This repo is for the Quick Deployment (QD) version of Asveora which is NOT the full Asveora project. It is meant for those who want to deploy an Asveora profile space as quick as possible. It does not require node, express, terminals, git, or any kind of dedicated development environment. Just grab a basic text editor such as Window 11's Notepad or an Integrated Development Environment (IDE) such as VS Code that can read and edit files. Please make sure you download a TEXT EDITOR (Notepad, Notepad++, etc.) or an IDE (VS Code, Eclipse, etc.) and not a WORD PROCESSOR (Microsoft Word, LibreOffice, OpenOffice, WordPad, Appple Pages, etc.) since people often confuse word processors with text editors. Word processors are for writing papers. Not coding websites. Also, if you are new to coding and not very confident with technology, the recommendation is just to stick to text editors and avoid IDEs altogether for the time being. They are simple, lightweight, and straightforward.

This repository only contains the necessary parts to deploy a single-page lite version Asveora profile space (which we hope you will build into a full profile space as time goes on 😊). The HTML page stores all of the HTML code of your profile page, the styles folder holds all of your CSS style sheets, and the media folder holds all of the images and other media filetypes that you have placed on your profile page. Replace the "username" word in the name of the HTML file with your Asveora username. Therefore instead of "username.html" it will look something like "johndoe.html" which will help your wheelcore administrator keep track of your files. Once you have made the changes you want to your username.html file, make a copy of it, delete index.html, and rename the copy you just made of username.html to index.html. This will overwrite the old index.html file.

This repository is dual-licensed under the GNU General Public License v3.0 (GPLv3) and the Asveora Commercial License Agreement (ACLA).

You may use, modify, and distribute this project under the terms of the GPLv3, or, if you are using this software in a commercial, closed-source, or non-GPL-compatible context, you may instead operate under the terms of the ACLA, subject to its separate conditions.

By using this software, you agree that your usage must comply with at least one of the applicable licenses, depending on how the software is used or distributed.

For full details, please refer to the LICENSE-GPLv3 and ACLA license files included in this repository.

"LICENSE-code" governs all of the code within this repository. "LICENSE-assets" governs all of Asveora's branded and copyrighted assets. These licenses exist to ensure that Asveora remains an open source project that people can freely use the code from while avoiding any legal problems surrounding Asveora's IP.

Head over to https://www.asveora.social/p/join.html and start having fun! It is expected that most users of Asveora will become contributors at some point in due time. Why so? Because Asveora is a self-deployable project. The more you do yourself, the more options, customization, and freedom you gain. However if you are just starting out with Asveora it is understandable if you do not want to immediately jump into deploying the RD version of Asveora. It is recommended that you go find an existing wheelcore to join, have the wheelcore admin get you set up with Quick Deployment (QD) and then slowly start taking control of your Asveora presence as you become more familiar with computers, networking, and web development. Yes, even smarpthones are computers!

This is one of the easiest life-long ways to break away from centralized social media platforms and ecosystems such as FaceBook, X, Instagram, Reddit, Pinterest, Flickr, etc. Everything you build with Asveora is yours to keep, move, delete, etc. No one controls your presence, data, and where they belong but you. Not only will it greatly improve your tech literacy, but it will also enable you to build your own online digital networks, storefronts, portfolios, blogs, news feeds, fan pages, etc. You get to decide what domain registrars, protocols, email services, file hosting services, content management systems, etc. you use. All of your code, assets, and projects stay with you locally and you decide where you display them on the internet. Asveora was built to give people more freedom with how they exist online and highlight just how incredibly crucial tech literacy is. Many people are not tech literate in an age where many parts of their lives are directly reliant upon digital technology. This is dangerous and needs to change. Why? Because situations like the following are all too common:

• Discord IDs Leaked (2025): https://www.bbc.com/news/articles/c8jmzd972leo
• Meta & YouTube Lawsuit (2025): https://www.yahoo.com/news/articles/meta-youtube-lose-social-media-175400791.html
• Meta Scam Ads Lawsuit (2026): https://mashable.com/article/meta-accused-of-profiting-from-scam-ads-in-class-action-lawsuit
• Reddit API Protests (2023): https://apnews.com/article/reddit-blackout-api-91f60aaec2eaf7cd0e3751e2fb3dd653

Always wanted to know how to code your own websites, web apps, local software apps, or even video games? Web development is a great way to get familiar with the general philosophy of programming! It is what I started out with before branching out into languages such as Python and C#. HTML (Hypertext Markup Language) is incredibly simple once you get the hang of just a few basic tags. I would argue that anyone could learn the basics of HTML and CSS (Cascading Style Sheets) is an afternoon or a day. JS (Javascript) might take a little longer though since its a lot more involved with logic and math haha.

Check the GET-HELP.txt file or the GET-HELP.md file! Whichever one suits your taste! :)

Even if you are on a mobile device, you can still make use of Asveora! Yes, there ARE ways to code on your smartphone or tablet and manage files in the same way you would within the desktop environment of any other operating system. Below are a couple of options for both Android and iOS (we got everyone covered here)! Please keep in mind that any information or data presented here is based on available information from online sources. Please double check ALL details with OFFICIAL sources as Asveora will not be liable if you make a purchase and there is a mismatch in expectations based on what is listed here and what you get. Asveora is not sponsored by nor affiliated with any of these products.

• For Editing Code – QuickEdit Text Editor (Free / Contains Ads) – https://play.google.com/store/apps/details?id=com.rhmsoft.edit&hl=en-US
• For Editing Code – QuickEdit Text Editor Pro (Paid / Pay Once / No Ads) – https://play.google.com/store/apps/details?id=com.rhmsoft.edit.pro&hl=en
• For Managing Files – Material Files (Free / Open Source / No Ads) – https://play.google.com/store/apps/details?id=me.zhanghai.android.files&hl=en-US

• For Editing Code – Koder Code Editor (May or may not be paid???) – https://apps.apple.com/us/app/koder-code-editor/id1447489375
• For Managing Files – FileBrowser Professional (Paid / Pay Once / No Ads) – https://apps.apple.com/us/app/filebrowser-professional/id854618029

Contribution guidelines will be coming at some point!

First, you will want to install the following on your system:

• git
• node.js
• express.js
• An Integrated Development Environment (IDE) such as:
  • Notepad++ (Windows) – https://notepad-plus-plus.org/downloads/
  • Visual Studio Code (Linux, MacOS, Windows) – https://code.visualstudio.com/download
  • Eclipse (Linux, MacOS, Windows) – https://www.eclipse.org/downloads/
  • Jetbrains' WebStorm (Linux, MacOS, Windows) – https://www.jetbrains.com/webstorm/

Keep in mind that you install express once you have node.js with the npm install express command in terminal. If you do not know how to use git or node.js then please refer to the following guides:

• git: https://github.com/git-guides
• node: https://nodejs.org/learn/getting-started/introduction-to-nodejs

I would highly recommend first familiarizing yourself with how system environment variables are handled on whatever operating system you are using. This will help you understand how environment variables are stored, how they are accessed, and how your system manages tools on the Command Line Interface (CLI). Unfortunately a lot of people assume that those using GitHub, GitLab, or Codeberg understand how desktop environments and file systems work. If you do not understand your own desktop environment or desktop filesystem, I would recommend starting with one of these guides depending on your operating system.

• Linux: https://ubuntu.com/tutorials/command-line-for-beginners#1-overview
• MacOS: https://developer.apple.com/documentation/foundation/file-system
• Windows: https://learn.microsoft.com/en-us/windows/win32/fileio/file-systems

With that out of the way, go on ahead and run the following command in a directory where you want to store your repo pull. To directly run the CLI in a specific folder in Windows you can just type cmd into the address bar of file explorer while in the directory you want to use. Otherwise you will need to do the cd ../somefilepath/theDirectoryYouWantToCloneTheFilesInto command. I highly recommend YYYY-MM-DD/files for a reason I will mention here in a minute.

# clone the repository
cd ../somefilepath/theDirectoryYouWantToCloneTheFilesInto
git clone https://github.com/Asveora/rich-deployment

You can opt to label the directory as YYYY-MM-DD so you remember when you pulled the main branch and make a new YYYY-MM-DD directory for every pull. But this is a bit obtuse to some people and they will most likely just use the git pull command to update the build with committed changes in one directory. But I like having backups of the repo that I can reference while working on the project.

Once you have pulled the repo go on ahead and create a server.js file in the directory above the one that you cloned the project files into. Said directory should be your YYYY-MM-DD one from the YYYY-MM-DD/files I mentioned earlier. This will allow you to start up a node.js server on localhost for development. Create a new server.js file with your IDE. Then copy and paste the below code into it before saving it:

const express = require('express');
const path = require('path');

const app = express();

// This line is the key:
app.use(express.static(path.join(__dirname, 'files')));

app.listen(3000, () => {
  console.log('Server running at http://localhost:3000');
});

Now open your terminal in the YYYY-MM-DD directory via cding to it or doing the file explorer cmd trick I mentioned above for Windows users. Then simply run node server.js and you should be good. If you get an error or have any missing dependencies then make sure you have installed express with npm install express or do a quick internet search for the error you get. If that does not work, then reach out in the Asveora Network Plaza community at: https://stt.gg/5wB2Zzb0