[royale-docs] branch master updated: added why royale

[ha...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

harbs pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new 7f9dca8  added why royale
7f9dca8 is described below

commit 7f9dca87dd4bb94fc902644c07708ec99f9c7ef1
Author: Harbs <ha...@in-tools.com>
AuthorDate: Mon Jan 3 17:57:16 2022 +0200

    added why royale
---
 _data/toc.json        |  3 +++
 welcome/why-royale.md | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 64 insertions(+)

diff --git a/_data/toc.json b/_data/toc.json
index e864c34..137a40b 100644
--- a/_data/toc.json
+++ b/_data/toc.json
@@ -8,6 +8,9 @@
                     "path": "welcome/what-is-royale.md"
                 },
                 {
+                    "path": "welcome/why-royale.md"
+                },
+                {
                     "path": "welcome/high-level-view.md"
                 },
                 {
diff --git a/welcome/why-royale.md b/welcome/why-royale.md
new file mode 100644
index 0000000..254ba93
--- /dev/null
+++ b/welcome/why-royale.md
@@ -0,0 +1,61 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+# 
+# http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+layout: docpage
+title: Why Royale?
+description: The advantages of using Royale
+permalink: /welcome/why-royale
+---
+# Why Royale?
+
+The advantages of using Royale
+
+Let's face it. There are lots of frameworks out there and each one claims to be the best. What does Royale give you that you don't get with other frameworks?
+
+## Time Proven
+Royale takes the best parts of Flex which was the first major web application framework. Flex was developed by the best in the field and Royale was designed by one of the lead architects of Flex.
+
+## Battle Tested
+Flex has run huge enterprise applications and Royale sits on the experience of that. Royale is being used to continue to run these applications which were originally developed in Flex.
+
+## Safe
+Royale is backed by Apache and offers the peace of mind knowing that Apache processes govern Royale's releases.
+
+## Unopinionated
+If you are using a framework, chances are you have been fighting with the framework to do what you want. You searched Stack Overflow to be told "you're doing it wrong". You need to use Framework "x" exactly like so!
+
+In Royale, we don't tell you how to build your applications. You like OOP? Great! You like FP? Great! How to manage your state? However you like! You don't like dealing with async rendering loops? Great. Royale doesn't have them. You want to control exactly how and when something is rendered? You are in the driver seat.
+
+You want to use dependency injection? Check. Don't like it? You don't need to use it.
+
+In short, Royale gives you the tools you need and doesn't tell you have to use them.
+
+## Fast!
+Most frameworks try to get as close to vanilla javascript as they can. In Royale we try to be _faster_ than vanilla javascript. In most cases Royale will _beat_ the best performance you can squeeze out of native HTML and Javascript. That's because the DOM is only used when necessary and we never do any kind of DOM syncing or traversal.
+
+## Zero configuration necessary
+Out of the box, Royale will build both debug and release builds of your application. You don't need any external tools to package "tree shake" or what-have-you.
+
+## Small and speedy deployments
+Royale compiles your entire application into a single JS file, a single minified CSS file and a tiny HTML file. Your _entire deployment_ can often be smaller than 100KB. Because Royale knows a lot about your application, it can be very smart about what's included and what can be minified.
+
+With Royale, the need for breaking your app into pieces and doing server side rendering to improve performance can be a thing of the past. You can get better performance out of Royale without any of those steps.
+
+## The kitchen sink
+Royale has a lot of functionality built in that you might otherwise look for elsewhere.
+
+## Open
+The Royale community is truly open. We're not run by some big company with an agenda. We don't care about politics. We're just little folk like you trying to build great software. We're waiting for you to join and help us build upon the best framework on earth!
\ No newline at end of file