Launch

.reuse/dep5

@@ -0,0 +1,18 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: Shader Slang Website
+Upstream-Contact: The Khronos Group, Inc.
+Source: https://github.com/shader-slang/shader-slang.github.io
+
+Files: *
+Copyright: 2024 The Khronos Group, Inc.
+License: CC-BY-4.0
+
+Files: _sass/bootstrap/*
+Copyright: 2011-2024 The Bootstrap Authors
+License: MIT
+
+Files: assets/fonts/*
+Copyright: The Poppins Project Authors
+           The Chivo Project Authors
+License: OFL-1.1
+

CODE_OF_CONDUCT.md

@@ -0,0 +1 @@
+A reminder that this issue tracker is managed by the Khronos Group. Interactions here should follow the Khronos Code of Conduct ([https://www.khronos.org/about/code-of-conduct](https://www.khronos.org/about/code-of-conduct)), which prohibits aggressive or derogatory language. Please keep the discussion friendly and civil.

CONTRIBUTING.md

@@ -0,0 +1,3 @@
+## Contributing
+
+This project welcomes contributions and suggestions. 

LICENSE

@@ -0,0 +1,13 @@
+SPDX-License-Identifier: CC-BY-4.0
+
+Creative Commons Attribution 4.0 International
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an "as-is" basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
+
+Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors : wiki.creativecommons.org/Considerations_for_licensors
+
+Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor's permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public : wiki.creativecommons.org/Considerations_for_licensees

LICENSES/MIT.txt

@@ -0,0 +1,9 @@
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

LICENSES/OFL-1.1.txt

@@ -0,0 +1,43 @@
+SIL OPEN FONT LICENSE
+
+Version 1.1 - 26 February 2007
+
+PREAMBLE
+
+The goals of the Open Font License (OFL) are to stimulate worldwide development of collaborative font projects, to support the font creation efforts of academic and linguistic communities, and to provide a free and open framework in which fonts may be shared and improved in partnership with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. The fonts, including any derivative works, can be bundled, embedded, redistributed and/or sold with any software provided that any reserved names are not used by derivative works. The fonts and derivatives, however, cannot be released under any other type of license. The requirement for fonts to remain under this license does not apply to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+
+"Font Software" refers to the set of files released by the Copyright Holder(s) under this license and clearly marked as such. This may include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting, or substituting — in part or in whole — any of the components of the Original Version, by changing formats or by porting the Font Software to a new environment.
+
+"Author" refers to any designer, engineer, programmer, technical writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of the Font Software, to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled, redistributed and/or sold with any software, provided that each copy contains the above copyright notice and this license. These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission.
+
+5) The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.
+
+TERMINATION
+
+This license becomes null and void if any of the above conditions are not met.
+
+DISCLAIMER
+
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.

README.md

@@ -0,0 +1,38 @@
+# Shader-Slang.com website
+
+This theme is losely based on the Serif theme for Jekyll by [Zerostatic Themes](https://www.zerostatic.io).
+
+## Installation
+
+### Installing Ruby & Jekyll
+
+If this is your first time using Jekyll, please follow the [Jekyll docs](https://jekyllrb.com/docs/installation/) and make sure your local environment (including Ruby) is setup correctly.
+
+### Installing Theme
+
+Download or clone the theme.
+
+To run the theme locally, navigate to the theme directory and run:
+
+```
+bundle install
+```
+
+To start the Jekyll local development server.
+
+```
+bundle exec jekyll serve
+```
+
+To build the theme.
+
+```
+bundle exec jekyll build
+```
+
+### Github Pages
+
+This theme has been tested to work with Github Pages (and Github Project Pages). When using Github Pages you will need to update the `baseurl` in the `_config.yml` otherwise all the css, images and paths will be broken.
+
+For example the site https://shader-slang.com would have `baseurl: "/"`
+

_config.yml

@@ -1,3 +1,48 @@
-theme: jekyll-theme-tactile
-title: The Slang Programming Language
-description: Productivity and performance for real-time graphics developers
+baseurl: '/'
+permalink: pretty
+title: 'Shader Slang'
+
+logo:
+  mobile: "images/logo/slang-logo.svg"
+  mobile_height: "55px"
+  mobile_width: "180px"
+  desktop: "images/logo/slang-logo.svg"
+  desktop_height: "55px"
+  desktop_width: "180px"
+
+
+collections:
+  posts:
+    output: true
+  events:
+    output: true
+
+defaults:
+  - scope:
+      path: ""
+      type: "services"
+    values:
+      layout: "service"
+  - scope:
+      path: ""
+      type: "team"
+    values:
+      layout: "team"
+
+sass:
+  style: compressed
+
+plugins:
+  - jekyll-environment-variables
+
+exclude:
+  - Gemfile
+  - Gemfile.lock
+  - node_modules
+  - vendor/bundle/
+  - vendor/cache/
+  - vendor/gems/
+  - vendor/ruby/
+  - LICENSE.md
+  - LICENSE
+  - README.md

_data/documentation.yaml

@@ -0,0 +1,61 @@
+overview:
+  - title: "User Guide"
+    description: "The guide provides an introduction to the Slang language and its major features, as well as the compilation and reflection API."
+    link_url: "https://shader-slang.com/slang/user-guide/"
+    link_label: "User Guide"
+  - title: "Standard Modules Reference"
+    description: "The reference of the standard modules that comes with the Slang compiler."
+    link_url: "https://shader-slang.com/stdlib-reference/"
+    link_label: "Modules Reference"
+  - title: "Language Specification"
+    description: "The formal specification of the Slang programming language. Work in progress.."
+    link_url: "https://github.com/shader-slang/spec"
+    link_label: "Language Specification"
+  - title: "Feature Matureness"
+    description: "List of Slang Features with their stableness/matureness."
+    link_url: "https://shader-slang.com/docs/feature_matureness"
+    link_label: "Feature matureness"
+  - title: "Command Line Reference"
+    description: "There is the documentation specific to using the slangc command-line tool."
+    link_url: "https://github.com/shader-slang/slang/blob/master/docs/command-line-slangc-reference.md"
+    link_label: "Command Line Reference"
+  - title: "Frequently Asked Questions"
+    description: "Answers to a list of frequently asked questions."
+    link_url: "https://shader-slang.com/docs/faq"
+    link_label: "Slang FAQ"
+
+articles:
+  - title: "SPIR-V  Specific Functionalities"
+    description: "Things to know when using Slang to compile to SPIR-V."
+    link_url: "https://shader-slang.com/slang/user-guide/spirv-target-specific.html"
+    link_label: "SPIR-V Specifics"
+  - title: "Metal Specific Functionalities"
+    description: "Things to know when using Slang to compile to the Metal Shading Language."
+    link_url: "https://shader-slang.com/slang/user-guide/metal-target-specific"
+    link_label: "Metal Functionalities"
+  - title: "WGSL Specific Functionalities"
+    description: "Things to know when using Slang to compile to the WGSL."
+    link_url: "https://shader-slang.com/slang/user-guide/wgsl-target-specific"
+    link_label: "WGSL Functionalities"
+
+tutorials:
+  - title: "Write Your First Slang Shader"
+    description: "See how to write a simple compute shader in Slang and compile it for execution on Vulkan."
+    link_url: "https://shader-slang.com/docs/first-slang-shader"
+    link_label: "My First Shader"
+  - title: "Using the Compilation API"
+    description: "See how to use Slang’s compilation API to integrate the Slang compiler into your application."
+    link_url: "https://shader-slang.com/slang/user-guide/compiling"
+    link_label: "The Complitation API"
+  - title: "Using the Reflection API"
+    description: "See how to use Slang’s reflection API to query for parameter binding info at runtime."
+    link_url: "https://shader-slang.com/slang/user-guide/reflection"
+    link_label: "The Reflection API"
+  - title: "Understanding Slang Generics"
+    description: "Learn how to use Slang’s generics and interfaces to write structured code that can be specialized at compile time."
+    link_url: "/docs/understanding-generics"
+    link_label: "Slang Generics"
+  - title: "Migrating from HLSL to Slang"
+    description: "Main things to know if you are coming to Slang as an HLSL developer."
+    link_url: "/docs/coming-from-hlsl/"
+    link_label: "Coming from HLSL"