The resource library provides downloadable assets, design files, documentation materials, and software packages to the Alius community. It serves developers, designers, contributors, and vendors who need official assets for their work.

Resource Types

Design Assets

  • Brand guidelines document (PDF)
  • Logo files (SVG, PNG in multiple sizes, with and without wordmark)
  • Color palette files (ASE, CLR, Sketch palette)
  • Icon library (SVG set, icon font)
  • UI kit / component library (Figma, Sketch)
  • Template files (presentation, document, social media)

Software Downloads

  • CLI installers (macOS, Linux, Windows)
  • SDK packages (Python, JavaScript, ROS)
  • Firmware files (for hardware products)
  • Configuration templates
  • Example projects and starter kits

Hardware Resources

  • 3D printable files (STL, OBJ)
  • CAD models (STEP, Fusion 360)
  • Schematics (PDF, KiCad)
  • Bill of materials (BOM)
  • Assembly instructions (PDF, interactive)
  • Dimension drawings

Documentation Resources

  • API reference (offline PDF)
  • Getting started guides (PDF)
  • Datasheets
  • Whitepapers and technical reports
  • Changelog and release notes

Download Page Structure

The resource download page should follow a consistent structure:

Category Navigation

  • Group resources by type (Design, Software, Hardware, Documentation)
  • Allow filtering by product, version, and format
  • Show the total count of resources in each category

Resource Card

Each resource item should display:

  • Resource name
  • Brief description
  • File format(s) available
  • File size
  • Version number
  • Last updated date
  • Download button
  • Preview option (when applicable — images, PDFs)

Version Display

  • Show the current/latest version prominently
  • Indicate beta or pre-release versions with a tag
  • Allow access to previous versions through a version history list
  • Mark deprecated versions with a warning

Version Management

Version Naming

  • Follow semantic versioning (MAJOR.MINOR.PATCH)
  • Pre-release versions use suffixes: -alpha.1, -beta.2, -rc.1
  • Display version numbers consistently across all resources

Release Process

  • Each release should have a changelog entry
  • Resources are tagged with the release version
  • Users can subscribe to release notifications
  • Older versions remain accessible but are clearly marked as non-current

Compatibility Tracking

  • Resources that depend on specific software or hardware versions must declare compatibility
  • Use a compatibility matrix to show which resource versions work with which product versions
  • Provide upgrade guides when major version changes introduce breaking changes

Access Control

  • Most resources are publicly accessible to support the open-source mission
  • Some resources (vendor materials, internal templates) may require authentication
  • Clearly communicate license terms for each resource (MIT, CC-BY, proprietary)