Design system to provide a consistent identity across Blender projects.
Márton Lente
ca8eb5303b
Fix the JavaScript execution of included HTML components' inner js. This makes it possible to test component parts, like navbar global's testing without copy-pasting code. |
||
---|---|---|
assets | ||
src | ||
.gitignore | ||
LICENSE | ||
package-lock.json | ||
package.json | ||
README.md | ||
site.webmanifest |
Blender Web Assets
Blender Web Assets is a front-end framework which provides design and interactivity components for official blender.org websites.
Install
Requirements
- git to clone and contribute to this repository.
- node.js to install the necessary packages via
npm
. If you need to manage multiple node versions, nvm can be quite handy.
Setup
- Open a terminal.
- Clone repo:
git clone git@projects.blender.org:infrastructure/web-assets.git
. - Enter folder
cd /path/to/web-assets
. npm install
Usage
Standalone
npm start
. This will build the site into/public
, open the site in the browser, and watch for changes in .html and .sass files.
In other projects
The idea behind Web Assets is to be shared between official Blender projects. Using this repository as a git submodule can simplify the process.
Clone, initalize, and update:
git clone git@projects.blender.org:infrastructure/web-assets.git
git submodule init
git submodule update --remote
Then in each project you can just @import
or @use
via Sass the components you need.
Each project must have its own package.json
defining the build pipeline.
Demo
See Web Assets in action:
- blender.org
- Developer Blog (extending the blender.org theme)
- Blender ID
- Blender Conference
- Blender Open Data
Authors
Pablo Vazquez Niklas Ravnsborg-Gjertsen
Copyright and license
This project is licensed under the GPL license copyright © 2023 Blender Foundation.