Update website
All checks were successful
Gitea Actions Demo / publish (push) Successful in 22s

This commit is contained in:
david-swift 2024-10-14 21:34:21 +02:00
parent c06e2e8bad
commit c5468eec91
14 changed files with 82 additions and 45 deletions

View File

@ -42,7 +42,6 @@ links = [
{ name = "Guides" , menu = [
{ url = "@/backends/_index.md", name = "Backends" },
{ url = "/tutorials", name = "Tutorials" },
{ url = "/hig", name = "Human Interface Guidelines" },
{ url = "/docs", name = "Documentation" },
]},
{ url = "https://forums.aparoksha.dev/", name = "Community" },

View File

@ -80,11 +80,17 @@ struct SearchView: View {
## Supported Platforms
<div style="margin-bottom: 2em;">
Aparoksha's goal is to enable you to bring your app to as many users as possible on completely different platforms.
Therefore, it is built in an open and extensible way.
Creating a backend for a new platform is almost as simple as creating an app!
</div>
<a class="inline-button" href="https://meta.aparoksha.dev/documentation/meta/createbackend">Create a Backend</a>
<br>
A list of some backends is available [here](@/backends/_index.md). They can be combined with Aparoksha in a simple way.
Aparoksha itself currently supports the three major desktop platforms [GNOME](@/backends/Adwaita/index.md), [Windows](@/backends/WinUI/index.md), and [macOS](@/backends/AppKit/index.md).
Aparoksha itself currently supports [GNOME](@/backends/Adwaita/index.md) and [Windows](@/backends/WinUI/index.md).
What makes the Aparoksha project unique is that each backend is a fully independent project, optimized for its platform.
In a cross-platform app, you can leverage the full potential of the individual backends by writing platform-specific bits of code.

View File

@ -1,7 +1,7 @@
+++
title = "Adwaita"
description = "Develop beautiful apps following the design guidelines of the GNOME desktop."
date = 2023-09-12
date = 2024-10-07
[taxonomies]
tags = ["Linux", "Aparoksha"]
[extra]
@ -11,7 +11,7 @@ banner = "Adwaita.png"
Develop beautiful apps following the design guidelines of the GNOME desktop.
Read the <a class="external" href="https://aparokshaui.github.io/adwaita-swift">documentation</a> to get started or <a class="external" href="https://github.com/AparokshaUI/adwaita-swift">browse the code</a> on GitHub.
Read the <a class="external" href="https://adwaita-swift.aparoksha.dev">documentation</a> to get started or <a class="external" href="https://git.aparoksha.dev/aparoksha/adwaita-swift">browse the code</a>.
## The Backend
@ -30,10 +30,10 @@ Now, install <a class="external" href="https://apps.gnome.org/en/Builder/">GNOME
<a class="external" href="https://flatpak.org/">Flatpak</a> facilitates the distribution of apps on Linux.
If you decide to use Flatpak already when developing the app, you do not have to install any dependencies on your system.
Simply clone the <a class="external" href="https://github.com/AparokshaUI/AdwaitaTemplate">template repository</a>, open in GNOME Builder, and run the template app.
Simply clone the <a class="external" href="https://git.aparoksha.dev/aparoksha/adwaita-template">template repository</a>, open in GNOME Builder, and run the template app.
Follow the instructions in the readme file to create your own app.
{{ image(url="Environment.png", alt="A native GNOME app called Tuba") }}
{{ image(url="Environment.png", alt="GNOME Builder and a todo app") }}
## The Design
@ -45,7 +45,7 @@ The following screenshot serves as an example for GNOME's design language.
## Distribution
The apps can be distributed using Flatpak. The most popular app store is <a class="external" href="https://flathub.org">Flathub</a>.
Read the <a class="external" href="https://aparokshaui.github.io/adwaita-swift/documentation/adwaita/publishingapps">instructions in the official docs</a>.
Read the <a class="external" href="https://adwaita-swift.aparoksha.dev/documentation/adwaita/publishingapps">instructions in the official docs</a>.
## Aparoksha Interoperability
This backend is part of the Aparoksha package. If you use default Aparoksha elements, they will render correctly on GNOME.

View File

@ -1,11 +0,0 @@
+++
title = "AppKit"
description = "Build fully native macOS apps."
date = 2024-09-13
[taxonomies]
tags = ["macOS", "Aparoksha"]
[extra]
featured = true
+++
Hello

Binary file not shown.

After

Width:  |  Height:  |  Size: 94 KiB

View File

@ -1,12 +1,28 @@
+++
title = "TermKit"
description = "Create simple user interfaces for terminal applications."
date = 2024-07-10
date = 2024-10-13
authors = ["david-swift"]
[taxonomies]
tags = ["Linux", "macOS"]
[extra]
hot = false
+++
Hello
Create simple user interfaces for terminal applications.
Read the <a class="external" href="https://term-kit-backend.aparoksha.dev/documentation/termkitbackend">documentation</a> or browse the code <a class="external" href="https://git.aparoksha.dev/david-swift/term-kit-backend">here</a>.
## The Backend
This backend is based on a <a class="external" href="https://github.com/david-swift/TermKit">fork of TermKit for Swift</a> which is built on top of <a class="external" href="https://invisible-island.net/ncurses/">ncurses</a>.
## The Development Environment
It is possible to develop and run TermKit applications on Linux and macOS.
The integrated terminals of GNOME Builder and VS Code are particularly helpful for quickly previewing the apps.
{{ image(url="Environment.png", alt="GNOME Builder and a demo app", transparent=true) }}
## Aparoksha Interoperability
You can combine this backend with the Aparoksha umbrella backend.
As it is not part of the Aparoksha framework, you have to implement shared widgets yourself.

BIN
content/backends/WinUI/App.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 442 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 665 KiB

BIN
content/backends/WinUI/WinUI.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 206 KiB

View File

@ -1,11 +1,42 @@
+++
title = "WinUI"
description = "Create apps for Microsoft Windows."
date = 2024-09-13
date = 2024-10-14
[taxonomies]
tags = ["Windows", "Aparoksha"]
[extra]
featured = true
banner = "WinUI.png"
+++
Hello
Create modern apps for Microsoft Windows.
Start in the <a class="external" href="https://git.aparoksha.dev/aparoksha/winui-swift">repository</a> or browse the <a class="external" href="https://winui-swift.aparoksha.dev/documentation/winui_swift/">reference documentation</a>.
## The Backend
The WinUI backend is based on the <a class="external" href="https://github.com/thebrowsercompany/swift-winui">swift-winui bindings</a> for <a class="external" href="https://learn.microsoft.com/en-us/windows/apps/winui/">WinUI</a>.
## The Development Environment
You need a Windows installation to develop WinUI apps.
<a class="external" href="https://code.visualstudio.com/">VS Code</a> is a great editor for working with WinUI for Swift.
Follow the <a class="external" href="https://www.swift.org/documentation/articles/getting-started-with-vscode-swift.html">instructions on the Swift website</a>.
{{ image(url="Environment.png", alt="VS Code and a simple demo app") }}
## The Design
Follow the <a class="external" href="https://learn.microsoft.com/en-us/windows/apps/design/">official design guidelines</a> when developing apps.
The following screenshot shows the WinUI 3 Gallery, showcasing WinUI's features.
{{ image(url="App.png", alt="The WinUI Gallery app" transparent=true) }}
## Distribution
Create an installer via <a class="external" href="https://nsis.sourceforge.io/Download">NSIS</a> or another application.
## Aparoksha Interoperability
This backend is part of the Aparoksha package. If you use default Aparoksha elements, they will render correctly on Windows.
You can call platform-specific widgets for Windows as well.

View File

@ -5,7 +5,7 @@ template = "article_list.html"
page_template = "article.html"
+++
The backends listed here are based on the <a class="external" href="https://github.com/AparokshaUI/Meta">Meta package</a>.
The backends listed here are based on the <a class="external" href="https://git.aparoksha.dev/aparoksha/meta">Meta package</a>.
They can be used in combination with the Aparoksha package.
The backends marked with a star are part of the Aparoksha package.

View File

@ -1,13 +0,0 @@
+++
title = "Hi!"
+++
I'm David, the maintainer of the Aparoksha project.
You can find me on <a class="external" href="https://mastodon.de/@david_swift">Mastodon</a>,
<a class="external" href="https://git.aparoksha.dev/david-swift/">this project's Gitea instance</a>,
and on <a class="external" href="https://github.com/david-swift">GitHub</a>.
If you benefit from this project and have enough money, <a class="external" href="https://ko-fi.com/david_swift">donations</a> are appreciated to compensate the server costs.
Thank you!
Don't forget to share your projects on the Fediverse and in the <a class="external" href="https://forums.aparoksha.dev/t/projects">Aparoksha forums</a> :)

View File

@ -1,6 +1,21 @@
+++
title = "Documentation"
featured = true
description = "A collection of links to the documentation of the components of Aparoksha."
[taxonomies]
tags = ["Linux", "macOS", "Windows", "Aparoksha"]
+++
The following links lead to the API documentation of individual parts of the Aparoksha framework.
## Foundation
- [Meta](https://meta.aparoksha.dev/) includes guides about the fundamental principles of the Aparoksha project and guides on how to create backends and apps
- [Levenshtein Transformations](https://levenshtein-transformations.aparoksha.dev)
- [Localized](https://localized.aparoksha.dev)
- [SQLite for Meta](https://meta-sqlite.aparoksha.dev)
## Aparoksha Backends
- [Adwaita for Swift](https://adwaita-swift.aparoksha.dev/documentation/adwaita/) contains multiple articles and a detailed tutorial
- [WinUI for Swift](https://winui-swift.aparoksha.dev/documentation/winui_swift/)

View File

@ -1,6 +0,0 @@
+++
title = "Human Interface Guidelines"
featured = true
[taxonomies]
tags = ["Linux", "macOS", "Windows", "Aparoksha"]
+++