Merge marketing showcase into main

feat(marketing): add showcase, comparison, v4 preview, and X thread

Author: Thomas Gorisse

.editorconfig

@@ -0,0 +1,30 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.{kt,kts,java}]
+indent_style = space
+indent_size = 4
+
+[*.xml]
+indent_style = space
+indent_size = 4
+
+[*.{gradle,gradle.kts}]
+indent_style = space
+indent_size = 4
+
+[*.{yml,yaml}]
+indent_style = space
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.json]
+indent_style = space
+indent_size = 2

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -0,0 +1,39 @@
+title: "[Idea] "
+labels: ["enhancement", "idea"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Suggest a new feature or improvement. We love hearing what the community needs.
+
+  - type: textarea
+    id: idea
+    attributes:
+      label: Describe the idea
+      description: What should SceneView be able to do?
+    validations:
+      required: true
+
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use case
+      description: What problem does this solve? What are you building?
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Other approaches or workarounds you've considered.
+
+  - type: dropdown
+    id: module
+    attributes:
+      label: Module
+      options:
+        - sceneview (3D)
+        - arsceneview (AR)
+        - New module
+        - Not sure

.github/DISCUSSION_TEMPLATE/q-a.yml

@@ -0,0 +1,41 @@
+title: "[Q&A] "
+labels: ["question"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Ask a question about SceneView. Please search existing discussions first.
+
+  - type: textarea
+    id: question
+    attributes:
+      label: Question
+      description: What do you need help with?
+      placeholder: "How do I load a model from a URL instead of assets?"
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: What I've tried
+      description: Code you've tried, error messages, or approaches that didn't work.
+      render: kotlin
+
+  - type: dropdown
+    id: module
+    attributes:
+      label: Module
+      options:
+        - sceneview (3D)
+        - arsceneview (AR)
+        - Both
+        - Not sure
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: SceneView version
+      placeholder: "3.2.0"

.github/DISCUSSION_TEMPLATE/show-and-tell.yml

@@ -0,0 +1,34 @@
+title: "[Show & Tell] "
+labels: ["showcase"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Share what you've built with SceneView! Screenshots, videos, and links welcome.
+
+  - type: textarea
+    id: project
+    attributes:
+      label: What did you build?
+      description: Describe your project and how SceneView is used.
+    validations:
+      required: true
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots or video
+      description: Drag and drop images or paste links to videos.
+
+  - type: textarea
+    id: code
+    attributes:
+      label: Interesting code snippets (optional)
+      description: Any SceneView patterns you're proud of or found useful.
+      render: kotlin
+
+  - type: input
+    id: link
+    attributes:
+      label: Play Store / GitHub link (optional)
+      placeholder: "https://play.google.com/store/apps/details?id=..."

.github/workflows/docs-on-release.yml

@@ -0,0 +1,33 @@
+name: Update docs on release
+
+# Automatically rebuilds and deploys the docs site when a new release is published
+# or when key API/marketing files change. This ensures the website always reflects
+# the latest state of the SDK.
+
+on:
+  release:
+    types: [published]
+  push:
+    branches: [main]
+    paths:
+      - 'llms.txt'
+      - 'sceneview/Module.md'
+      - 'arsceneview/Module.md'
+      - 'ROADMAP.md'
+
+jobs:
+  trigger-docs-deploy:
+    name: Trigger docs rebuild
+    runs-on: ubuntu-latest
+    steps:
+      - name: Trigger docs workflow
+        uses: actions/github-script@v7
+        with:
+          script: |
+            await github.rest.actions.createWorkflowDispatch({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              workflow_id: 'docs.yml',
+              ref: 'main'
+            });
+            console.log('Triggered docs rebuild');

.github/workflows/docs.yml

@@ -5,9 +5,12 @@ on:
     branches: [main]
     paths:
       - 'docs/**'
-      - 'marketing/codelabs/**'
+      - 'marketing/**'
       - 'CHANGELOG.md'
       - 'MIGRATION.md'
+      - 'CONTRIBUTING.md'
+      - 'ROADMAP.md'
+      - 'llms.txt'
   workflow_dispatch:
 
 jobs:
@@ -25,10 +28,14 @@ jobs:
 
       - name: Sync content into docs
         run: |
+          # Codelabs from marketing
           cp marketing/codelabs/codelab-3d-compose.md docs/docs/codelabs/codelab-3d-compose.md
           cp marketing/codelabs/codelab-ar-compose.md docs/docs/codelabs/codelab-ar-compose.md
+
+          # Root docs
           cp MIGRATION.md docs/docs/migration.md
           cp CHANGELOG.md docs/docs/changelog.md
+          cp CONTRIBUTING.md docs/docs/contributing.md
 
       - name: Build site
         run: mkdocs build --config-file docs/mkdocs.yml --site-dir site

CODE_OF_CONDUCT.md

@@ -0,0 +1,62 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in the
+SceneView community a harassment-free experience for everyone, regardless of
+age, body size, visible or invisible disability, ethnicity, sex characteristics,
+gender identity and expression, level of experience, education, socio-economic
+status, nationality, personal appearance, race, caste, color, religion, or
+sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior:
+
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**thomas@sceneview.com**.
+
+All complaints will be reviewed and investigated promptly and fairly. All
+community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

SECURITY.md

@@ -0,0 +1,33 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Support Level          |
+| ------- | ---------------------- |
+| 3.2.x   | Fully supported        |
+| 3.1.x   | Security fixes only    |
+| < 3.1   | Not supported          |
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in SceneView, please report it responsibly by emailing **security@sceneview.com**. Do not open a public GitHub issue for security vulnerabilities.
+
+When reporting, please include:
+
+- A description of the vulnerability and its potential impact
+- Steps to reproduce the issue
+- Affected version(s)
+- Any suggested mitigation or fix, if available
+
+You can expect an initial response within **48 hours** of your report. We will work with you to understand and validate the issue, and will provide updates on our progress toward a fix.
+
+## Disclosure Policy
+
+SceneView follows a **90-day coordinated disclosure** policy. After a vulnerability is reported:
+
+1. We will confirm receipt within 48 hours.
+2. We will investigate and work on a fix within the 90-day disclosure window.
+3. Once a fix is available, we will release a patched version and publish a security advisory.
+4. The reporter may publicly disclose the vulnerability after the fix has been released or after the 90-day window has elapsed, whichever comes first.
+
+We appreciate the efforts of security researchers and community members who help keep SceneView and its users safe.