Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: change website twitter and linkedin URLs #456

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

MdechampG
Copy link
Member

@MdechampG MdechampG commented Mar 11, 2024

All in the title

Summary by CodeRabbit

  • Documentation
    • Updated URLs and references across the documentation and configuration files from okp4.network to axone.xyz.
    • Renamed all instances of OKP4 to Axone for brand consistency.
    • Updated protocol references within Governance Text Credentials documentation to align with the new terminology.

@MdechampG MdechampG requested a review from ccamel March 11, 2024 13:01
Copy link
Contributor

coderabbitai bot commented Mar 11, 2024

Walkthrough

The recent updates involve a comprehensive rebranding from OKP4 to Axone, affecting URLs, references, and terminology across various documents and schemas. This transition aims to ensure consistency with the new protocol name, enhancing clarity and cohesion throughout the documentation and ontology schemas.

Changes

Files Change Summary
docs/index.mdx, docusaurus.config.js Updated URLs and references from okp4.network to axone.xyz and renamed OKP4 to Axone.
docs/.../ontology/the-power-of-ontologies.md Updated references from OKP4 to Axone in the document.
ontology/schemas/credential-governance-text.md, ontology_versioned_docs/version-v3.0.0/schemas/credential-governance-text.md Updated protocol reference from "OKP4" to "Axone" for Governance Text Credentials.

🌟🐇🌟
In the world of code, where changes abound,
A rabbit hopped in, with a joyful bound.
"From OKP4 to Axone," it cheerily said,
With every document and schema ahead.
Let's hop to the future, with names anew,
Together, there's nothing we can't do!
🚀📜🎉

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 8

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 5552d4f and 25e9a00.
Files selected for processing (5)
  • docs/index.mdx (4 hunks)
  • docs/technical-documentation/ontology/the-power-of-ontologies.md (2 hunks)
  • docusaurus.config.js (3 hunks)
  • ontology/schemas/credential-governance-text.md (1 hunks)
  • ontology_versioned_docs/version-v3.0.0/schemas/credential-governance-text.md (1 hunks)
Additional comments: 8
docs/technical-documentation/ontology/the-power-of-ontologies.md (1)
  • 37-37: The update from [OKP4](https://github.com/okp4/okp4d) to [Axone](https://github.com/okp4/okp4d) correctly reflects the rebranding. However, consider adding a comma after "protocol" for better readability in the sentence: "The Ontology is at the heart of the Axone protocol, as much of the information is encoded and stored as an ontology on-chain in the blockchain transactions."
docs/index.mdx (4)
  • 182-182: The URL update to https://axone.xyz is correct and aligns with the rebranding efforts. This change ensures that users are directed to the updated website.
  • 203-203: The update to the website URL in the social media section is correct. However, using the IconOKP4 for the Axone website link might be misleading. Consider updating the icon to match the Axone branding if such an icon is available.
  • 226-226: The LinkedIn URL has been correctly updated to https://www.linkedin.com/company/axone-protocol. This change ensures that users are directed to the correct LinkedIn page for Axone.
  • 253-253: The Twitter URL update to https://twitter.com/axonexyz is correct and aligns with the rebranding efforts. This ensures users are directed to the correct Twitter page for Axone.
docusaurus.config.js (3)
  • 229-229: The update of the footer logo href to https://axone.xyz is correct and aligns with the rebranding efforts. This ensures that the footer logo links to the updated website.
  • 267-267: The Twitter URL has been correctly updated to https://twitter.com/axonexyz in the footer links. This change ensures that users are directed to the correct Twitter page for Axone.
  • 291-292: The label and URL update to Axone.xyz and https://axone.xyz respectively, in the "More" section of the footer, is correct and aligns with the rebranding efforts. This ensures that users are directed to the updated website and recognizes the new branding.

Copy link
Member

@bot-anik bot-anik left a comment

Choose a reason for hiding this comment

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

Device URL
desktop http://localhost:3000/

Device URL
mobile http://localhost:3000/

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

Copy link
Member

@ccamel ccamel left a comment

Choose a reason for hiding this comment

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

LGTM!

@MdechampG MdechampG merged commit 7540a41 into main Mar 11, 2024
12 checks passed
@MdechampG MdechampG deleted the feat/social-media-update branch March 11, 2024 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants