diff --git a/README.md b/README.md
index c75c5bb..35c6fa5 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,3 @@
# website
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.com/suyu-emu/website.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.com/suyu-emu/website/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+WIP NOT DONE YET. DO NOT DEPLOY.
diff --git a/TODO.txt b/TODO.txt
new file mode 100644
index 0000000..80e297c
--- /dev/null
+++ b/TODO.txt
@@ -0,0 +1,3 @@
+DONE -Autoclose announcment bar after 7 seconds
+make download page wish uses a yaml file to list builds.
+TODO - ambient background if possible --- do this later tried it was breaking a lot of stuff. need to do this after converting suyu.png and favicon.png to to transparent
\ No newline at end of file
diff --git a/app.js b/app.js
new file mode 100644
index 0000000..cbf519d
--- /dev/null
+++ b/app.js
@@ -0,0 +1,154 @@
+// Smooth Transition For Everything
+const allElements = document.querySelectorAll('*');
+
+allElements.forEach(element => {
+ element.style.transition = 'all 1000ms ease-in-out';
+});
+
+
+// Rgb Effect
+
+// Select Card elements
+const elements = document.querySelectorAll('.card');
+
+// Counter
+let counter = 0;
+
+function changeColors() {
+
+ const color = getRandomColor();
+
+ elements.forEach(element => {
+
+ if(element.classList.contains('card')) {
+ element.style.setProperty('border-color', color, 'important');
+ }
+
+ });
+
+ counter++;
+ counter %= elements.length;
+
+ setTimeout(changeColors, 1000);
+
+}
+
+
+
+// Random color function
+function getRandomColor() {
+ return `rgb(${Math.floor(Math.random() * 256)}, ${Math.floor(Math.random() * 256)}, ${Math.floor(Math.random() * 256)})`;
+}
+
+// Start changing colors
+changeColors();
+
+// Next Section: Make Site Mobile Compatible
+
+
+const sectionOne = document.getElementById('header');
+const sectionOneHead = document.getElementById('headertext')
+const sectionOneSubtext = document.getElementById('headersubtext')
+const sectionOnebutton = document.getElementById('downloadbutton')
+const Sectionthree = document.getElementById('featuresection')
+const cards = document.getElementsByClassName('card');
+let prevMobile = false;
+
+function checkWidth() {
+ const isMobile = window.innerWidth <= 1000;
+
+ if(isMobile !== prevMobile) {
+ if(isMobile) {
+ console.log("Mobile mode on");
+ sectionOne.classList.add('flex-column');
+ sectionOne.style.marginLeft = "0px";
+ sectionOneSubtext.style.marginLeft = "0px"
+ sectionOnebutton.style.marginLeft = "0px"
+ Sectionthree.classList.add('flex-column');
+ for (var i = 0; i < cards.length; i++) {
+ cards[i].classList.add('mt-5');
+ }
+ } else {
+ console.log("Mobile mode off");
+ sectionOne.classList.remove('flex-column');
+ sectionOne.style.marginLeft = "";
+ sectionOneSubtext.style.marginLeft = ""
+ sectionOnebutton.style.marginLeft = ""
+ Sectionthree.classList.remove('flex-column');
+ for (var i = 0; i < cards.length; i++) {
+ cards[i].classList.remove('mt-5');
+ }
+ }
+
+ prevMobile = isMobile;
+ }
+}
+
+// Initial check
+checkWidth();
+
+window.addEventListener('resize', checkWidth);
+
+// Next Section : Button Hyperlinks
+
+const downloadbtn = document.getElementById('downloadbtnone')
+const discordBtn = document.getElementById('discordbtnone');
+const sourceBtn = document.getElementById('sourcebtnone');
+const downloadbtn2 = document.getElementById('downloadbutton')
+const discordBtn2 = document.getElementById('discordbtnthree');
+const sourceBtn2 = document.getElementById('sourcebtntwo');
+const sourceBtn3 = document.getElementById('sourcebtnthree');
+const downloadBtn3 = document.getElementById('downloadbtnthree')
+
+
+discordBtn.addEventListener('click', () => {
+ const url = 'https://discord.gg/2gQRBp44KT';
+ window.open(url, '_blank');
+});
+;
+
+sourceBtn.addEventListener('click', () => {
+ const url = 'https://gitlab.com/suyu2/suyu';
+ window.open(url, '_blank');
+});
+
+downloadbtn.addEventListener('click', () => {
+ const url = "download.html"
+ window.open(url, '_blank')
+})
+
+discordBtn2.addEventListener('click', () => {
+ const url = 'https://discord.gg/2gQRBp44KT';
+ window.open(url, '_blank');
+});
+;
+
+sourceBtn2.addEventListener('click', () => {
+ const url = 'https://gitlab.com/suyu2/suyu';
+ window.open(url, '_blank');
+});
+
+downloadbtn2.addEventListener('click', () => {
+ const url = "download.html"
+ window.open(url, '_blank')
+})
+
+sourceBtn3.addEventListener('click', () => {
+ const url = 'https://gitlab.com/suyu2/suyu';
+ window.open(url, '_blank');
+});
+
+downloadBtn3.addEventListener('click', () => {
+ const url = "download.html"
+ window.open(url, '_blank')
+})
+
+
+
+
+
+// Next Section: Functionality
+
+setTimeout(function(){
+ document.getElementById('announcement').remove()
+}, 7000)
\ No newline at end of file
diff --git a/builds/builds.yaml b/builds/builds.yaml
new file mode 100644
index 0000000..6bbfd94
--- /dev/null
+++ b/builds/builds.yaml
@@ -0,0 +1,11 @@
+builds:
+ - name: Suyu Alpha # Type A Short Name For The Release: Ex: Suyu Alpha, Suyu Beta
+ fullname: Suyu Alpha Build 32doqnks9 # full name
+ id: 1 # Increase This Every Time A Build Get Released. This Id Identifies The Build For The Website To Sort Them By Newest To Oldest.
+ date: 2024-03-06 # date when id get published used to display how long ago was the build releeased
+ description: Added Feature X # description of the build can put changelogs here
+ downloadurlwindows: https://example.com
+ downloadurllinux: https://example.com
+
+ - name: Suyu Beta
+ fullname:
diff --git a/download.css b/download.css
new file mode 100644
index 0000000..29274df
--- /dev/null
+++ b/download.css
@@ -0,0 +1,91 @@
+body {
+ background-color: black !important;
+}
+
+
+/* USE THIS FOR DEBUGGING * {
+ border: 1px solid red;
+ } */
+
+#announcement {
+ background-color: rgb(46, 46, 46) !important;
+}
+
+.navbar, .navbar-brand{
+ background-color: black !important;
+ color: white !important;
+}
+
+.navbar-toggler-icon {
+ background-color: rgb(83, 82, 82) !important;
+}
+
+.nav-link {
+ color: white !important;
+}
+
+.nav-link:hover {
+ color: cyan !important;
+}
+
+
+#suyu-logo {
+ height: 420px;
+}
+
+#headertext {
+ color: white;
+ text-align: top;
+}
+
+#headersubtext {
+ color: white !important;
+ text-align: top;
+ display: flex;
+ align-items: flex-start;
+ margin-left: 20%;
+}
+
+#downloadbutton {
+ margin-left: 20%;
+}
+
+#downloadicon, #sourceicon, #discordicon, #giticon, #windows, #linux-icon {
+ filter: invert(100%);
+}
+
+/* #information {
+ border-top: 2px solid white;
+ border-bottom: 2px solid white;
+} */
+
+#infoheadtext, #infotext {
+ color: white;
+}
+
+#featuresheadertext, .card-title, .card-text, .card-header {
+ color: white;
+}
+
+.card {
+ background-color: rgb(37, 32, 32);
+}
+
+.card {
+ border: 5px solid red;
+}
+
+.btn {
+ color: white;
+}
+
+.btn:hover {
+ transform: scale(1.1);
+}
+
+footer {
+ color: white;
+ text-align: center;
+}
+
+
diff --git a/download.html b/download.html
new file mode 100644
index 0000000..5e57da5
--- /dev/null
+++ b/download.html
@@ -0,0 +1,103 @@
+
+
+
+
+ Suyu Emulator
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/image.webp b/image.webp
new file mode 100644
index 0000000..894ed81
Binary files /dev/null and b/image.webp differ
diff --git a/img/discord.svg b/img/discord.svg
new file mode 100644
index 0000000..024e083
--- /dev/null
+++ b/img/discord.svg
@@ -0,0 +1,4 @@
+
+
\ No newline at end of file
diff --git a/img/download.png b/img/download.png
new file mode 100644
index 0000000..fc86131
Binary files /dev/null and b/img/download.png differ
diff --git a/img/favicon.png b/img/favicon.png
new file mode 100644
index 0000000..f91d482
Binary files /dev/null and b/img/favicon.png differ
diff --git a/img/gitlab.svg b/img/gitlab.svg
new file mode 100644
index 0000000..b2b98b3
--- /dev/null
+++ b/img/gitlab.svg
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/img/linux.svg b/img/linux.svg
new file mode 100644
index 0000000..1d4f353
--- /dev/null
+++ b/img/linux.svg
@@ -0,0 +1,7 @@
+
+
+
+
+
\ No newline at end of file
diff --git a/img/suyu.png b/img/suyu.png
new file mode 100644
index 0000000..9304362
Binary files /dev/null and b/img/suyu.png differ
diff --git a/img/windows.svg b/img/windows.svg
new file mode 100644
index 0000000..81dcb9d
--- /dev/null
+++ b/img/windows.svg
@@ -0,0 +1,19 @@
+
+
+
\ No newline at end of file
diff --git a/index.html b/index.html
new file mode 100644
index 0000000..027008b
--- /dev/null
+++ b/index.html
@@ -0,0 +1,137 @@
+
+
+
+
+ Suyu Emulator
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Loading...
+
+
+
+
+
+
+
+
+
A Open Source Switch Emulator
+
Suyu is an experimental open-source emulator for the Nintendo Switch System. Built with portability in mind, it is coded in C++ and actively maintained for Windows And Linux
+
+
+
+
+
+
+
+
About Suyu
+
Suyu Is A Fork Of Yuzu Made After The Shut Down Of The Yuzu Emulator
+ After A Lawsuit Was Filed On February 26, 2024 And Was Settled On March 4, 2024
+ Causing Yuzu To Stop Distribution Of All There Emulators: Yuzu And Citra
+ Using Archives From The Web The Suyu Team Is Continuing Development Of Yuzu.
Windows
+
+
+ 
Linux
+
+ 
+ 
Source Code
+ 
Download
+ 
Join
+
+