diff --git a/.github/ISSUE_TEMPLATE/sistent_feature.md b/.github/ISSUE_TEMPLATE/sistent_feature.md new file mode 100644 index 000000000000..52444c480226 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/sistent_feature.md @@ -0,0 +1,29 @@ +--- +name: πŸš€ Enhancement in Sistent Project +about: Propose a new feature, suggest a component, or report an issue for Sistent. +title: '[Sistent]' +labels: 'project/sistent, kind/enhancement' +assignees: '' +--- +### Current Behavior + + +### Desired Behavior + + +### Screenshots / Mockups + + +### Implementation + + +--- +

Contributor Resources and Handbook

+ +The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the [`master` branch](https://github.com/layer5io/layer5/tree/master). +- 🎨 See [Sistent Repository](https://github.com/layer5io/sistent). +- πŸ“š See [contributing instructions](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md). +- 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9) +- πŸ™‹πŸΎπŸ™‹πŸΌ Questions: [Discussion Forum](https://discuss.layer5.io) and [Community Slack](https://slack.layer5.io). + +Join the Layer5 Community by submitting your [community member form](https://layer5.io/newcomer). diff --git a/.github/workflows/meshmap.yml b/.github/workflows/meshmap.yml index 9117e7ded4d4..753268b2c1a3 100644 --- a/.github/workflows/meshmap.yml +++ b/.github/workflows/meshmap.yml @@ -38,7 +38,7 @@ jobs: path: action repository: layer5labs/kanvas-snapshot - id: test_result - uses: layer5labs/Kanvas-Snapshot@v0.2.11 + uses: layer5labs/Kanvas-Snapshot@v0.2.12 with: githubToken: ${{ secrets.GITHUB_TOKEN }} mesheryToken: ${{ secrets.MESHERY_TOKEN }} diff --git a/src/collections/integrations/meshery-core/icons/components/pen-terminal/icons/color/pen-terminal-color.svg b/src/collections/integrations/meshery-core/icons/components/pen-terminal/icons/color/pen-terminal-color.svg new file mode 100644 index 000000000000..05bc4b31a3a9 --- /dev/null +++ b/src/collections/integrations/meshery-core/icons/components/pen-terminal/icons/color/pen-terminal-color.svg @@ -0,0 +1,3 @@ + + + diff --git a/src/collections/integrations/meshery-core/icons/components/pen-terminal/icons/white/pen-terminal-white.svg b/src/collections/integrations/meshery-core/icons/components/pen-terminal/icons/white/pen-terminal-white.svg new file mode 100644 index 000000000000..b29670dc82e6 --- /dev/null +++ b/src/collections/integrations/meshery-core/icons/components/pen-terminal/icons/white/pen-terminal-white.svg @@ -0,0 +1,3 @@ + + + diff --git a/src/collections/integrations/meshery-core/icons/components/picture/icons/color/picture-color.svg b/src/collections/integrations/meshery-core/icons/components/picture/icons/color/picture-color.svg new file mode 100644 index 000000000000..05bc4b31a3a9 --- /dev/null +++ b/src/collections/integrations/meshery-core/icons/components/picture/icons/color/picture-color.svg @@ -0,0 +1,3 @@ + + + diff --git a/src/collections/integrations/meshery-core/icons/components/picture/icons/white/picture-white.svg b/src/collections/integrations/meshery-core/icons/components/picture/icons/white/picture-white.svg new file mode 100644 index 000000000000..b29670dc82e6 --- /dev/null +++ b/src/collections/integrations/meshery-core/icons/components/picture/icons/white/picture-white.svg @@ -0,0 +1,3 @@ + + + diff --git a/src/collections/integrations/meshery-core/index.mdx b/src/collections/integrations/meshery-core/index.mdx index 6689ea13fe90..9c38483e89f8 100644 --- a/src/collections/integrations/meshery-core/index.mdx +++ b/src/collections/integrations/meshery-core/index.mdx @@ -64,9 +64,15 @@ components: [ "description": "", }, { -"name": "pen-connector-node", -"colorIcon": "icons/components/pen-connector-node/icons/color/pen-connector-node-color.svg", -"whiteIcon": "icons/components/pen-connector-node/icons/white/pen-connector-node-white.svg", +"name": "picture", +"colorIcon": "icons/components/picture/icons/color/picture-color.svg", +"whiteIcon": "icons/components/picture/icons/white/picture-white.svg", +"description": "", +}, +{ +"name": "pen-terminal", +"colorIcon": "icons/components/pen-terminal/icons/color/pen-terminal-color.svg", +"whiteIcon": "icons/components/pen-terminal/icons/white/pen-terminal-white.svg", "description": "", }, { diff --git a/src/collections/integrations/ps-db/index.mdx b/src/collections/integrations/ps-db/index.mdx index d5a2bceeb55b..604584cd0f33 100644 --- a/src/collections/integrations/ps-db/index.mdx +++ b/src/collections/integrations/ps-db/index.mdx @@ -1,6 +1,6 @@ --- title: Percona Server for MySQL -subtitle: Meshery provides performance reports, including performance test results, node resource metrics etc. so that operators may easily understand the overhead of their service mesh’s control plane and data plane in context of the overhead incurred on nodes running within the cluster. In order to generate performance test reports of service meshes and their workloads, Meshery uses Grafana and/or Prometheus as visualization and metrics systems, respectively. This guide outlines the requirements necessary for Meshery to connect to these systems. The steps may vary depending upon the service mesh and its configuration. +subtitle: Collaborative and visual infrastructure as design for Percona Server for MySQL integrationIcon: icons/color/ps-db-color.svg darkModeIntegrationIcon: icons/white/ps-db-white.svg docURL: https://docs.meshery.io/extensibility/integrations/ps-db @@ -28,20 +28,20 @@ components: [ "description": "", }] featureList: [ - "Native support for PromQL", - "Create custom charts with your own Prometheus queries", + "A fully compatible, enhanced, and open source drop-in replacement for any MySQL database.", + "Percona Operators include backup/restore, high availability, replication, sharding, logging features and more.", "Keep charts in-sync with Mesherys panel viewer" ] workingSlides: [ ../_images/kanvas-visualizer.png, ../_images/kanvas-designer.png ] -howItWorks: "Meshery provides performance reports, including performance test results, node resource metrics etc. so that operators may easily understand the overhead of their service mesh’s control plane and data plane in context of the overhead incurred on nodes running within the cluster. In order to generate performance test reports of service meshes and their workloads, Meshery uses Grafana and/or Prometheus as visualization and metrics systems, respectively. This guide outlines the requirements necessary for Meshery to connect to these systems. The steps may vary depending upon the service mesh and its configuration." +howItWorks: "Percona Operators eliminate the complexities of Day 1 and Day 2 database operations and seamlessly integrate with Meshery and Kanvas." howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." published: TRUE ---

-The Prometheus monitoring system and time series database. +Percona Server for MySQL is a fully compatible, enhanced, and open source drop-in replacement for any MySQL database.

Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology. diff --git a/src/collections/integrations/ps-operator/index.mdx b/src/collections/integrations/ps-operator/index.mdx index 43c4045f5bd7..5018bacad00f 100644 --- a/src/collections/integrations/ps-operator/index.mdx +++ b/src/collections/integrations/ps-operator/index.mdx @@ -28,7 +28,7 @@ components: [ "description": "", }] featureList: [ - "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", + "High-performance MySQL database", "Manages backups, restores, and upgrades", "Provides high availability and failover" ] diff --git a/src/components/Features/TwoColLayout.js b/src/components/Features/TwoColLayout.js index 29e18c823e03..bc0eaf7f3c9f 100644 --- a/src/components/Features/TwoColLayout.js +++ b/src/components/Features/TwoColLayout.js @@ -92,7 +92,7 @@ const TwoColLayout = ({ containerRefs, contentRefs }) => { (contentRefs.current[1] = el)}> -

Easing your Workflow Burden Collaboratively

+

Cognitive overload is real

Empower DevOps, platform, and site reliability engineers with our orchestration management solution. Achieve seamless collaboration and operational harmony for enhanced productivity.

Learn more → diff --git a/src/components/Features/images/22.svg b/src/components/Features/images/22.svg new file mode 100644 index 000000000000..f789f4ea28d8 --- /dev/null +++ b/src/components/Features/images/22.svg @@ -0,0 +1,17 @@ + + + + + + + + + + + + + + + + + diff --git a/src/components/Features/images/cursor-2.svg b/src/components/Features/images/cursor-2.svg index a29c0544418d..88834405d80d 100644 --- a/src/components/Features/images/cursor-2.svg +++ b/src/components/Features/images/cursor-2.svg @@ -1,12 +1,5 @@ - - - - - - - - - - - + + + + diff --git a/src/components/Features/images/cursor-21.svg b/src/components/Features/images/cursor-21.svg new file mode 100644 index 000000000000..aa37f667fedd --- /dev/null +++ b/src/components/Features/images/cursor-21.svg @@ -0,0 +1,42 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/src/pages/cloud-native-management/generate-gcp-architecture-diagram.js b/src/pages/cloud-native-management/generate-gcp-architecture-diagram.js index 67b1dfbc656b..45c28526af7a 100644 --- a/src/pages/cloud-native-management/generate-gcp-architecture-diagram.js +++ b/src/pages/cloud-native-management/generate-gcp-architecture-diagram.js @@ -12,7 +12,7 @@ const Gcp = () => { }; export default Gcp; export const Head = () => { - return ; }; \ No newline at end of file diff --git a/src/sections/ArchitectureDiagram/index.js b/src/sections/ArchitectureDiagram/index.js index e65560b67022..f8ffb3a6b01c 100644 --- a/src/sections/ArchitectureDiagram/index.js +++ b/src/sections/ArchitectureDiagram/index.js @@ -12,7 +12,7 @@ import customizationGIF from "./images/customization.gif"; import shapesAndTemplatesGIF from "./images/shapes-and-templates.gif"; import RelatedPicks from "../../components/RelatedPicks"; let data = { - heading: "Design Architecture Diagram Online", + heading: "Design Architecture Diagrams Online", sub_heading: "Effortlessly create software architectures, application architectures and system architectures in minutes.", image: whiteboard_svg }; @@ -50,13 +50,13 @@ const ArchitectureDiagram = () => {

Why use an architecture diagramming software?

-

Following all the elements within your cloud environment can be challenging, but a visual diagram of your cloud architecture will help you stay up to date with its status, understand the relationship between components, identify and solve problems. This complexity adds up when multiple team members are working on the same project. A collaborative cloud diagramming sofware could help to pinpoint information and ensure that everybody is on the same page.

+

Cognitive overload is real. Trying to hold all elements of your environment in your mind can be challenging, but a visual diagram of your cloud architecture will help you stay up to date with its status, understand the relationship between components, identify and solve problems. This complexity adds up when multiple team members are working on the same project. A collaborative cloud diagramming sofware could help to pinpoint information and ensure that everybody is on the same page.

-

Visual Tool That Get Things Done

+

Visual Tool That Gets Things Done

Not just pretty pictures. Data-linked visual apps to streamline all your efforts.

diff --git a/src/sections/Community/Handbook/community-roles.js b/src/sections/Community/Handbook/community-roles.js index b3c2d7cf5262..e5e5fb69c54d 100644 --- a/src/sections/Community/Handbook/community-roles.js +++ b/src/sections/Community/Handbook/community-roles.js @@ -223,6 +223,54 @@ const CommunityGuide = () => { + +

Release Manager Role

+ + +

+ The role of release manager for a release lasts a total of about 6 months. This is divided up among activities before the initial release comes out and activities after the initial release while the release is within active maintenance. The majority of the time is spent in the month before the first release. After that, there is 6 months of time during which point releases come out on approximately a 3 week cycle. During three of these months, the release manager is working on the latest release. This 6 month time period is divided into two sections. In the first three months, this is the primary release and all fixes get cherry-picked from master here. After 3 months, the next release of the Meshery project comes out and there are three more months of support before this release goes to the end of life. +

+ +

Responsibilities

+ +

Before Release

+
    +
  • Cutting branches -- 8 to 16 hours divided between all release managers. Working on automating. Will still take a while with automation, probably around half a day. With automation, a lot of the time will be waiting for automated steps to complete as opposed to being directly involved.
    • +
  • Testing days -- 8 to 16 hours divided between all release managers spread over two weeks in order to orchestrate the testing events. This does not include any time that the release managers additionally devote to picking up and testing individual tests.
    • +
  • Spreadsheets
    • +
  • Prioritization
    • +
  • Chasing people to get things done
    • +
  • Prioritization of issues in step with workgroups
    • +
  • Release management meetings -- 45 minutes to 1 hour every week for each release manager. Increases as the release gets closer.
    • +
  • Release notes/upgrade notes for point release -- 1 week for of the release managers as well as reviewing from other release managers
    • +
  • Code reviews from docs team as well as workgroup leads
    • +
  • Generation of release notes using automated tooling
    • +
  • Updating release notes to make them more readable
    • +
  • Announcement of release on Twitter/Discuss/Slack -- 5 minutes for one release manager for Discuss/Slack. For Twitter, reach out to someone with access.
    • +
+ +

Ongoing for all releases

+
    +
  • Watching for release blockers - part of the code review process. Wouldn't say it needs additional time
    • +
  • Code reviews/deciding whether to accept cherry picks -- about an hour per day for each release manager. Ramps up just before the initial release. Ramps down to an hour per week towards the EOL for a release
    • +
  • Minor release every 3 weeks.
    • +
  • Release notes - 1 hour for a single release manager
    • +
  • Creating releases - 8 hours spread across all release managers. Most of this is automated (i.e. update proxy and then wait for tests to complete, trigger a build and wait for tests to complete)
    • +
  • 48 hour testing -- this involves requesting those who run the tests to trigger the tests and waiting for 48 hours. There is very little needed from a release manager other than checking in to make sure everything is working well
    • +
  • Handle vulnerability fix integration in step with product security workgroup -- approximately 3 patch releases -- for private security releases, release managers are responsible for coordinating a flush release to get all fixes before the security fix out as well as ensuring they don't accept patches until the release is out. Most of the additional release related work is taken care of by the security fix lead although the release managers are expected to review release notes, build PRs, and other related content. The flush release takes about the same amount of time as a regular release.
    • +
  • Meshery build and release meetings -- one hour per release manager per week
    • +
  • End Of Life for release -- 8 hours
    • +
+ +

Qualifications for Release Manager

+
    +
  • A member of the Layer5 community and active for the last 3 months
    • +
  • Approved by a majority vote of current maintainers.
    • +
  • At least one release manager for each version needs to meet requirements for access info in case of vulnerabilities
    • +
+ +

Process for volunteering for release management

+

Contact a current maintainer to volunteer or nominate yourself.

diff --git a/src/sections/Docker-Meshery/index.js b/src/sections/Docker-Meshery/index.js index 8e999159f26b..25a2e33b22c1 100644 --- a/src/sections/Docker-Meshery/index.js +++ b/src/sections/Docker-Meshery/index.js @@ -4,7 +4,7 @@ import { Row, Col } from "../../reusecore/Layout"; import docker from "../../assets/images/socialIcons/docker_white.svg"; import meshery from "../../assets/images/meshery/icon-only/meshery-logo-white.svg"; import DockerExtensionMeshery from "./docker-extension-meshery"; -import KanvasCTA from "../kanvas-cta"; +import KanvasCTA from "../Kanvas/kanvas-cta"; const MesheryDockerPage = () => { return ( diff --git a/src/sections/Home/FeaturesContainer/index.js b/src/sections/Home/FeaturesContainer/index.js index 8bbedfbb1948..fc1d5a9e9b44 100644 --- a/src/sections/Home/FeaturesContainer/index.js +++ b/src/sections/Home/FeaturesContainer/index.js @@ -26,26 +26,17 @@ const FeaturesContainer = () => { const layoutRef = useRef(null); const featuresInfo = [ { - title: "Collaborate with Precision", + title: "Build Systems Faster, Together", show_custom_cursor: true, animationOne: true, redirectLink: "/cloud-native-management/kanvas/collaborate/peer-reviews", - desc: "Real-time collaboration for cloud and cloud native designs with live-editing, instant feedback, deploy dry runs, and secure access controls.", + desc: "Real-time collaboration for cloud native and Kubernetes designs with live-editing, instant feedback, deploy dry runs, and secure access controls.", imgLink: isDark ? CommentingImageDark : CommentingImageLight, cursor: false, }, - { - title: "Generate stunning diagrams", - show_custom_cursor: false, - animationOne: false, - redirectLink: "/whiteboard", - desc: "Crafting cloud-native symphonies: Our engineering diagramming tool is your conductor's baton, turning Kubernetes infrastructure into a canvas for freestyle orchestration.", - imgLink: isDark ? WhiteboardingImage : WhiteboardingImageLight, - cursor: true, - }, { title: "Multi-Cloud by Design", - show_custom_cursor: false, + show_custom_cursor: true, animationOne: true, redirectLink: "", desc: ( @@ -72,6 +63,15 @@ const FeaturesContainer = () => { }, ], }, + { + title: "Be on the same page, literally", + show_custom_cursor: true, + animationOne: false, + redirectLink: "/whiteboard", + desc: "Crafting cloud-native symphonies: Our engineering diagramming tool is your conductor's baton, turning Kubernetes infrastructure into a canvas for freestyle orchestration.", + imgLink: isDark ? WhiteboardingImage : WhiteboardingImageLight, + cursor: true, + } ]; useEffect(() => { diff --git a/src/sections/Kanvas/kanvas-cta/index.js b/src/sections/Kanvas/kanvas-cta/index.js new file mode 100644 index 000000000000..3512ea7b1c1b --- /dev/null +++ b/src/sections/Kanvas/kanvas-cta/index.js @@ -0,0 +1,118 @@ +import React from "react"; +import styled from "styled-components"; + +import { Container } from "../../../reusecore/Layout"; +import Locator from "./locator.svg"; +import MesherySurface from "./meshery-surface.svg"; +import Button from "../../../reusecore/Button"; + +const KanvasCTAWrapper = styled.div` +.CTAbody { + background: + linear-gradient(180deg, rgba(71,126,150,1) 0%, rgba(0,179,159,1) 100%); + border-radius: 2rem; + display: flex; + padding: 2rem; + text-align: center; + margin: 2rem auto; + align-items: center; + + .surface { + width: 60%; + min-width: 160px; + } + .rotate{ + animation: coin-rotate 4s ease-in-out infinite alternate; + /* animation-fill-mode: both; */ + transition: all .3s; + display: block; + margin: 1rem auto; + height: 15rem; + } + @keyframes coin-rotate { + from { + transform: translateY(5%); + } + to { + transform: translateY(-5%); } + } + .button { + margin: 1rem auto; + } + .text{ + display: block; + margin: auto; + } + .subtext { + color: ${props => props.theme.white}; + font-size: 1.5rem; + font-weight: 300; + margin: 1rem 0rem; + } + h2 { + padding: 0; + color: ${props => props.theme.white}; + span { + font-size: 6rem; + } + } + + @media screen and (max-width:767px) { + display: block; + .surface { + width: 30%; + } + .rotate { + margin: 0 auto 0.25rem; + height: 12rem; + } + h2 { + margin: 1rem 0rem; + span{ + font-size: 3rem; + + } + } + .subtext{ + font-size: 1rem; + } + .button-text{ + display: none;; + } + } + @media screen and (max-width:340px) { + h2{ + span{ + font-size: 2rem; + } + } + } +} +`; + +const KanvasCTA = () => { + return ( + + +
+
+ + +
+
+

Kanvas is here!

+

Discover a catalog of best practice cloud native patterns.

+ + +
+
+ + + + ); +}; + +export default KanvasCTA; + diff --git a/src/sections/Kanvas/kanvas-cta/kanvas-icon-white.svg b/src/sections/Kanvas/kanvas-cta/kanvas-icon-white.svg new file mode 100644 index 000000000000..40abcebcab48 --- /dev/null +++ b/src/sections/Kanvas/kanvas-cta/kanvas-icon-white.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/src/sections/Kanvas/kanvas-cta/locator.svg b/src/sections/Kanvas/kanvas-cta/locator.svg new file mode 100644 index 000000000000..b45cef0f2caf --- /dev/null +++ b/src/sections/Kanvas/kanvas-cta/locator.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/src/sections/Kanvas/kanvas-cta/meshery-surface.svg b/src/sections/Kanvas/kanvas-cta/meshery-surface.svg new file mode 100644 index 000000000000..9cfd19adbcad --- /dev/null +++ b/src/sections/Kanvas/kanvas-cta/meshery-surface.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/src/sections/Kubernetes-Diagram/diagram.js b/src/sections/Kubernetes-Diagram/diagram.js index 5811f418cc1f..df0cb432e941 100644 --- a/src/sections/Kubernetes-Diagram/diagram.js +++ b/src/sections/Kubernetes-Diagram/diagram.js @@ -150,17 +150,17 @@ const Kubernetes = () => {
-

Diagram + Config = Awesome!

-

- Stop wrestling with code templates! Our visual configuration interface gives you the precision of code with the ease of a diagram. +

Kubernetes made simple.

+ {/*

Visualize, configure, deploy.

*/} +

Ditch the code complexity. Design your Kubernetes clusters visually, then deploy with confidence.

-

Deploy with No Code Kubernetes

+

No Code Kubernetes Deployments

- Our visual Kubernetes interface enables anyone to deploy production-grade software with no code. Whether you're new to Kubernetes and are looking for the best way to learn or a seasoned pro, Kanvas has all the features you need to be successful in deploying and configuring your software using the industry-leading container orchestrator, all with no code.

+ Kanvas for Kubernetes empowers anyone to deploy production-ready infrastructure effortlessly. No coding experience? No problem! Kanvas offers all the tools you need to deploy and configure your software on Kubernetes, the top container orchestrator, without writing a single line of code. Perfect for beginners learning the ropes or seasoned professionals seeking streamlined workflows, Kanvas ensures success in deploying and managing your applications on Kubernetes.

@@ -175,18 +175,18 @@ const Kubernetes = () => {
-

Visual drag & drop

+

From Idea to Infrastructure in Seconds

- Instantly search for and find any integration that CNCF supports and drop on the canvas to create your cloud native infrastructure. Kanvas allow you to drag, drop and connect all your cloud components together simply and easily - no-code required! + Unlock the power of cloud-native computing without the coding complexity. Kanvas' drag-and-drop interface lets you visualize and build your cloud infrastructure effortlessly.

Learn more → -

Extensive Kubernetes Icon Library

+

Comprehensive Kubernetes Toolkit for Platform Engineers

- Utilize a vast and continually expanding collection of Kubernetes icons designed for both diagramming and orchestration scenarios. Craft globally comprehensible diagrams that are not only authentic but also aligned with the latest industry standards. + Leverage an extensive and continuously updated library of Kubernetes components, meticulously designed for both diagramming and orchestration. Create accurate, industry-standard diagrams that communicate your infrastructure designs effectively across teams. Click "dry run" before deploying to ensure your configurations are error-free.

@@ -202,11 +202,11 @@ const Kubernetes = () => { -

Kickstart with Ready-to-Use Templates

+

From Zero to Kubernetes in Minutes

- Jumpstart your projects with our quick-start templates designed for both Kubernetes diagramming and orchestration management. Access a range of professionally crafted templates that are fully customizable, ensuring you can tailor them to your specific needs. + Fast-track your Kubernetes projects with our curated collection of quick-start templates for both diagramming and orchestration. These professional-grade blueprints are fully customizable, giving you the flexibility to adapt them to your unique requirements.

- Learn more → + Explore Kubernetes templates → diff --git a/src/sections/Projects/Project-grid/index.js b/src/sections/Projects/Project-grid/index.js index e4b8634c55d5..3759ed57bef3 100644 --- a/src/sections/Projects/Project-grid/index.js +++ b/src/sections/Projects/Project-grid/index.js @@ -5,7 +5,7 @@ import PageHeader from "../../../reusecore/PageHeader"; // import ProudMaintainers from "../../../sections/Home/Proud-maintainers"; import { ThemeManagerContext } from "../../../theme/app/ThemeManager"; import { ProjectWrapper } from "./projectGrid.style"; -import KanvasCTA from "../../kanvas-cta"; +import KanvasCTA from "../../Kanvas/kanvas-cta"; import extension from "../../../assets/images/docker-extension/docker-extension-meshery-logo.svg"; import meshery from "../../../assets/images/meshery/icon-only/meshery-logo-light.svg"; diff --git a/src/sections/Projects/SMI/index.js b/src/sections/Projects/SMI/index.js index 6679337fca85..7cb10cb79926 100644 --- a/src/sections/Projects/SMI/index.js +++ b/src/sections/Projects/SMI/index.js @@ -5,7 +5,7 @@ import React from "react"; import SMIWrapper from "./smi.style"; import { Row, Col, Container } from "../../../reusecore/Layout"; import Button from "../../../reusecore/Button"; -import KanvasTA from "../../kanvas-cta"; +import KanvasCTA from "../../Kanvas/kanvas-cta"; import data from "./data"; import c_icon from "./c-icon.svg"; @@ -111,7 +111,7 @@ const SMIPage = () => { - + ); }; diff --git a/src/sections/Projects/SMP/index.js b/src/sections/Projects/SMP/index.js index 582f255a3c05..eb747593182d 100644 --- a/src/sections/Projects/SMP/index.js +++ b/src/sections/Projects/SMP/index.js @@ -8,7 +8,7 @@ import { BgImage } from "gbimage-bridge"; import SMPWrapper from "./smp.style"; import { Row, Col, Container } from "../../../reusecore/Layout"; import Button from "../../../reusecore/Button"; -import KanvasCTA from "../../kanvas-cta"; +import KanvasCTA from "../../Kanvas/kanvas-cta"; import example from "../../../assets/images/smp-page/service-mesh-performance-specification-example.gif"; import smp from "../../../assets/images/smp-page/smp-white.svg";