diff --git a/.github/workflows/ccc-build-and-deploy.yml b/.github/workflows/ccc-build-and-deploy.yml new file mode 100644 index 0000000..9d43bce --- /dev/null +++ b/.github/workflows/ccc-build-and-deploy.yml @@ -0,0 +1,14 @@ +name: CCC build and deploy + +on: + schedule: + - cron: "0 1 * * *" + workflow_dispatch: + +jobs: + build-landscape: + uses: cncf/landscape2-sites/.github/workflows/build-and-deploy.yml@main + with: + foundation: ccc + repository: confidential-computing/landscape + secrets: inherit diff --git a/.github/workflows/ccc-validate-settings.yml b/.github/workflows/ccc-validate-settings.yml new file mode 100644 index 0000000..229069d --- /dev/null +++ b/.github/workflows/ccc-validate-settings.yml @@ -0,0 +1,18 @@ +name: CCC validate settings + +on: + pull_request: + branches: + - main + paths: + - ccc/settings.yml + +jobs: + validate-landscape-settings: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - uses: cncf/landscape2-validate-action@v2 + with: + target_kind: settings + target_path: ccc/settings.yml diff --git a/README.md b/README.md index 07be3b4..7dff12b 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,7 @@ This repository contains the settings and deployment workflows of some foundatio | [![AOUSD build and deploy](https://github.com/cncf/landscape2-sites/actions/workflows/aousd-build-and-deploy.yml/badge.svg?branch=main)](https://github.com/cncf/landscape2-sites/actions/workflows/aousd-build-and-deploy.yml) | | | [![ASWF build and deploy](https://github.com/cncf/landscape2-sites/actions/workflows/aswf-build-and-deploy.yml/badge.svg?branch=main)](https://github.com/cncf/landscape2-sites/actions/workflows/aswf-build-and-deploy.yml) | | | [![CAMARA build and deploy](https://github.com/cncf/landscape2-sites/actions/workflows/camara-build-and-deploy.yml/badge.svg?branch=main)](https://github.com/cncf/landscape2-sites/actions/workflows/camara-build-and-deploy.yml) | | +| [![CCC build and deploy](https://github.com/cncf/landscape2-sites/actions/workflows/ccc-build-and-deploy.yml/badge.svg?branch=main)](https://github.com/cncf/landscape2-sites/actions/workflows/ccc-build-and-deploy.yml) | | | [![CDF build and deploy](https://github.com/cncf/landscape2-sites/actions/workflows/cdf-build-and-deploy.yml/badge.svg?branch=main)](https://github.com/cncf/landscape2-sites/actions/workflows/cdf-build-and-deploy.yml) | | | [![CNCF build and deploy](https://github.com/cncf/landscape2-sites/actions/workflows/cncf-build-and-deploy.yml/badge.svg?branch=main)](https://github.com/cncf/landscape2-sites/actions/workflows/cncf-build-and-deploy.yml) | | | [![DLT build and deploy](https://github.com/cncf/landscape2-sites/actions/workflows/dlt-build-and-deploy.yml/badge.svg?branch=main)](https://github.com/cncf/landscape2-sites/actions/workflows/dlt-build-and-deploy.yml) | | diff --git a/ccc/settings.yml b/ccc/settings.yml new file mode 100644 index 0000000..7aa726a --- /dev/null +++ b/ccc/settings.yml @@ -0,0 +1,321 @@ +# Landscape2 settings +# +# This settings file allows customizing some aspects of the landscape. + +# Foundation (required) +# +# Name of the foundation. This value is used in some labels, so we recommended +# to keep it as short as possible. +# +# foundation: +# +foundation: CCC + +# Url (required) +# +# Url where the landscape will be hosted. +# +# url: +# +url: https://ccc.landscape2.io/ + +# Analytics (optional) +# +# Analytics providers configuration. When an analytics provider is set up, some +# additional code from the provider will be injected into the web application. +# +# analytics: +# gtm: # Google Tag Manager configuration +# container_id: # Landscape web application container ID +# + +# Base path (optional) +# +# Base path where the landscape will be hosted. By default the generated +# landscape is prepared to be hosted at the root of the domain. However, if the +# landscape will be hosted in a subpath, this value must be set accordingly. +# +# base_path: / +# + +# Categories (optional) +# +# Categories information is read from the `landscape.yml` data file. The way +# categories are displayed in the web application is computed dynamically based +# on the number of categories and subcategories, as well as the number of items +# on each. Sometimes, however, we may want subcategories to be displayed in a +# specific order within a category (this happens often in the Members category). +# In those cases, it is possible to define that order by overriding a category. +# +# This option can also be used to not display one or more subcategories in some +# sections of the landscape [*]. To achieve that, we only need to exclude the +# subcategory from the subcategories list when overriding a category. +# +# [*] +# - Grid mode: excluded subcategories won't be displayed +# - Card mode: items in excluded subcategories won't be displayed when +# filtering by group or classifying by category +# +# categories: +# - name: +# subcategories: +# - +# - +# +categories: + - name: Confidential Computing Consortium Member Company + subcategories: + - Premier + - General + - Associate + - Startup + + +# Colors (optional) +# +# Colors used across the landscape UI. The colors section is optional but, when +# provided, *all colors must be provided*. Colors must be specified using the +# following format: "rgba(, , , )". +# +# colors: +# color1: # Buttons, groups, links +# color2: # Some highlighted items like filters button, search icon +# color3: # Participation stats bars, spinners, modal titles +# color4: # Categories titles in filters, fieldset in filters modal +# color5: # Categories and subcategories frames (odd) +# color6: # Categories and subcategories frames (even) +# color7: # Borders, shadows and options boxes in games +# +colors: + color1: "rgba(0, 118, 187, 1)" + color2: "rgba(235, 0, 69, 1)" + color3: "rgba(0, 118, 187, 1)" + color4: "rgba(0, 118, 187, 1)" + color5: "rgba(82, 44, 192, 1)" + color6: "rgba(0, 118, 187, 1)" + color7: "rgba(243, 240, 251, 1)" + +# End user (optional) +# +# This section allows defining what items should be marked as `end user` based +# on the category and subcategory they belong to. If the `enduser` field has +# been set on a given item, that value will take precedence. +# +# enduser: +# - category: (required) +# subcategories: (optional) +# - +# - category: +# + +# Featured items (optional) +# +# This section allows highlighting items that match certain criteria. You can +# define a list of rules and the matching items will be featured in a special +# way in the landscape. +# +# Each rule must define a field for the check as well as the values that will +# trigger a match. At the moment the fields supported are: +# +# - maturity +# - subcategory +# +# When a given item's field matches any of the values provided, it will be +# considered a featured item. For each option, it is possible to also define an +# order (which item would be displayed first) and a label for the item. +# +# featured_items: +# - field: subcategory +# options: +# - value: +# - value: +# +featured_items: + - field: subcategory + options: + - value: "Premier" + +# Footer (optional) +# +# This section allows customizing some aspects of the footer. +# +# footer: +# links: +# facebook: +# flickr: +# github: +# homepage: +# instagram: +# linkedin: +# slack: +# twitch: +# twitter: +# wechat: +# youtube: +# logo: # Foundation logo featured on the footer +# text: # Copyright notice, for example +# +footer: + links: + github: https://github.com/confidential-computing + homepage: https://confidentialcomputing.io + linkedin: https://www.linkedin.com/company/confidential-computing/ + slack: http://slack.confidentialcomputing.io + twitter: https://twitter.com/confidentialc2 + youtube: https://www.youtube.com/@confidentialcomputingconso5871 + logo: "http://confidentialcomputing.io/wp-content/uploads/sites/10/2022/07/Logo_White.svg" + +# Grid items size (optional) +# +# Defines the preferred size of the landscape items in the grid mode. When the +# landscape contains many items, it is recommended to use the `small` size. +# However, if there aren't many items, choosing `medium` or `large` may make +# the landscape look nicer. Users will still be able to adjust the items size +# from the UI using the zoom controls. +# +# grid_items_size: +# +grid_items_size: large + +# Groups (optional) +# +# In some cases, specially when a landscape contains lots of items, it may be +# interesting to organize them in groups. Each group will be displayed on a +# different tab in the landscape web application. Each entry must contain the +# name of the group (it will be displayed as is) and a list with the categories +# (as defined in the landscape.yml data file) that will be part of this group. +# +# When groups are used, categories not listed in any group won't be displayed +# in the grid mode. +# +# groups: +# - name: +# categories: +# - +# - +# + +# Header (optional) +# +# This section allows customizing some aspects of the header. +# +# header: +# links: +# github: +# logo: # Foundation logo featured on the header +# +header: + links: + github: "https://github.com/confidential-computing/landscape" + logo: "https://confidentialcomputing.io/wp-content/uploads/sites/10/2022/07/cc_consortium-color.svg" + +# Images (optional) +# +# Urls of some images used in the landscape UI. +# +# images: +# favicon: +# open_graph: +# + +# Logos viewbox (optional) +# +# In order to display the logos as large as possible in the landscape, during +# the build process we try to update their viewbox if `adjust` is set to true +# (by default it is when this setting is not provided). However, sometimes this +# does not help and logos may not be displayed correctly. In those cases, it is +# possible to exclude some of them from being adjusted by adding the logo(s) +# file name to the `exclude` list. +# +# logos_viewbox: +# adjust: true +# exclude: +# - logo1.svg +# - logo2.svg +# + +# Name of the members category (optional) +# +# Landscapes usually have a special category dedicated to the members of the +# corresponding foundation. It is possible to use any name for that category, +# but it is important that we define it here as there are some special +# operations that depend on it. +# +# members_category: +# +members_category: Confidential Computing Consortium Member Company + +# Osano (optional) +# +# Osano cookies consent form configuration. When the Osano configuration is +# provided, some additional code will be injected into the web application. +# +# The `customer_id` and `customer_configuration_id` fields values can be +# obtained from the url in the configuration script code available on the Osano +# site: +# +# https://cmp.osano.com///osano.js +# +# osano: +# customer_id: +# customer_configuration_id: +# + +# Screenshot width (optional) +# +# Width of the landscape screenshots automatically generated (in pixels). +# Screenshots won't be taken if this value is not provided. +# +# screenshot_width: +# +screenshot_width: 1500 + +# TAGs (optional) +# +# Projects items can specify which TAG owns them in the `landscape.yml` file +# (by using the `tag` field in the `extra` item's section). However, sometimes +# this information is not available at the item level. This configuration +# section provides a mechanism to automatically asign a TAG to projects items +# based on the categories and subcategories they belong to. +# +# For example, we can define that all projects in the category are +# owned by . When the items are processed, the corresponding TAG will be +# set in the items that match the rule defined. The TAG defined at the item +# level always takes precedence, so when it's present it won't be replaced. +# +# NOTE: TAGs names should only use lowercase case letters and hyphens (no +# spaces or other characters), and should not be prefixed with "tag". The +# subcategories field is optional and, when omitted, all of them will be +# included. +# +# tags: +# : +# - category: +# subcategories: +# - +# - +# : +# - category: +# + +# Upcoming event (optional) +# +# This section allows configuring an upcoming event that will be featured on +# the landscape web application. Expired events won't be displayed. +# +# upcoming_event: +# name: # Event name (required) +# start: # Start date: (required, format: YYYY-MM-DD) +# end: # End date: (required, format: YYYY-MM-DD) +# banner_url: # Event banner image url (required, recommended dimensions: 2400x300) +# details_url: # Event details URL (required) +# + +# View mode (optional) +# +# This section allows customizing the default view mode of the landscape web +# application. The view mode can be set to either `grid` or `card`. When +# omitted, the default view mode is `grid`. +# +# view_mode: +#