Skip to content

docs: update logo docs and copyright years#652

Open
MortGron wants to merge 1 commit into
mainfrom
docs-logo-and-copyright-year
Open

docs: update logo docs and copyright years#652
MortGron wants to merge 1 commit into
mainfrom
docs-logo-and-copyright-year

Conversation

@MortGron
Copy link
Copy Markdown

@MortGron MortGron commented Jun 5, 2026

Description

Add higher quality Cognite logo and dynamic copyright years in the documentation. This is inspred by the SDK: https://cognite-sdk-python.readthedocs-hosted.com/en/latest/

Motivation and Context

Would make the look of the documentation more aligned with the SDK documentation.

How Has This Been Tested?

Tested locally

Screenshots (if appropriate):

image

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • Refactor (non-breaking change which improves implementation)
  • Performance (non-breaking change which improves performance. Please add associated performance test and results)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Non-functional change (xml comments/documentation/etc)

Contributor Checklist:

  • My code follows the code style of this project.
  • I have added an example of my new feature and included it in the documentation.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My Pull Request name follows the naming convention fix: <description>, feat: <description>, etc.

Reviewer Checklist for Charts compliant functions:

  • The docstrings of the new function follow the contributing guidelines.
  • The new function is professionally documented
  • The new function and associated scripts are covered by one or more unit tests and code coverage did not decrease.
  • The new function is accompanied by an example and it is included in the Gallery of Charts.
  • The new function is reviewed in Chromatic. Access the storybook build results url and comment, approve or deny.
  • All function inputs, arguments, and outputs have a supported data type and have human readable names.
  • No code language is included in the description of the function or parameters (e.g use "polynomial order" instead of "poly_order")

@MortGron MortGron marked this pull request as ready for review June 5, 2026 13:18
@MortGron MortGron requested a review from a team as a code owner June 5, 2026 13:18
@codecov
Copy link
Copy Markdown

codecov Bot commented Jun 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.04%. Comparing base (bbc116a) to head (dc80caa).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #652   +/-   ##
=======================================
  Coverage   91.04%   91.04%           
=======================================
  Files         111      111           
  Lines        4178     4178           
  Branches      552      552           
=======================================
  Hits         3804     3804           
  Misses        231      231           
  Partials      143      143           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 5, 2026

Unit Test Results

    24 files  ±0      24 suites  ±0   35m 22s ⏱️ + 1m 21s
 1 212 tests ±0   1 212 ✅ ±0   0 💤 ±0  0 ❌ ±0 
21 120 runs  ±0  21 108 ✅ ±0  12 💤 ±0  0 ❌ ±0 

Results for commit dc80caa. ± Comparison against base commit bbc116a.

Copy link
Copy Markdown
Contributor

@ebrattli ebrattli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@ebrattli ebrattli added the waiting-for-risk-review Waiting for a member of the risk review team to take an action label Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-for-risk-review Waiting for a member of the risk review team to take an action

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants