From bc0411c3d6b86f2ce6a7bdb9c50b9f07ce8e409b Mon Sep 17 00:00:00 2001 From: nikhilchauhangithub Date: Mon, 7 Aug 2023 00:40:26 +0530 Subject: [PATCH 1/3] responsiveness of the Why KubeEdge section Signed-off-by: nikhilchauhangithub --- src/components/why/styles.module.css | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/src/components/why/styles.module.css b/src/components/why/styles.module.css index 0f1e2dd367..b6940ab6f9 100644 --- a/src/components/why/styles.module.css +++ b/src/components/why/styles.module.css @@ -1,3 +1,4 @@ +/* Default styles */ .whyContainer { display: flex; flex-direction: column; @@ -18,4 +19,17 @@ .reasonContent { font-size: 0.9rem; white-space: pre-wrap; -} \ No newline at end of file +} + +/* Responsive styles */ +@media screen and (max-width: 768px) { + .reasonBox { + flex-basis: 50%; /* Show two reasons per row on screens up to 768px */ + } +} + +@media screen and (max-width: 480px) { + .reasonBox { + flex-basis: 100%; /* Show one reason per row on screens up to 480px */ + } +} From c70ebaf0efd6261a30c17c08a063e80aa8e12520 Mon Sep 17 00:00:00 2001 From: nikhilchauhangithub Date: Mon, 7 Aug 2023 01:15:37 +0530 Subject: [PATCH 2/3] Responsiveness of Recent News section Signed-off-by: nikhilchauhangithub --- src/components/blogPost/index.scss | 153 +++++++++++++---------------- 1 file changed, 70 insertions(+), 83 deletions(-) diff --git a/src/components/blogPost/index.scss b/src/components/blogPost/index.scss index 835c743066..a60d113455 100644 --- a/src/components/blogPost/index.scss +++ b/src/components/blogPost/index.scss @@ -1,114 +1,101 @@ .blogPostContainer { - @media screen { - @media (max-width: 992px) { - .sectionContainerInner { - .row { - .left { - flex: 0 0 100%; - max-width: 100%; - } - } - } - } - @media (max-width: 768px) { - .sectionContainerInner { - .row { - .left { - flex: 0 0 100%; - max-width: 100%; - } - } - } - } - } + padding: 20px; /* Add padding to the blogPostContainer */ .row { - display: -ms-flexbox; display: flex; - -ms-flex-wrap: wrap; flex-wrap: wrap; margin-right: -15px; margin-left: -15px; + } - .left { - flex: 0 0 33.333333%; - max-width: 33.333333%; + .left { + flex: 0 0 100%; + max-width: 100%; + text-align: left; + position: relative; + margin-bottom: 1rem; + padding: 10px; /* Add padding to the left container */ + } + + .right { + flex: 0 0 100%; + max-width: 100%; + font-size: 1.2rem; + display: flex; + flex-direction: column; + gap: 20px; + padding: 10px; /* Add padding to the right container */ + } + + .viewBlogContainer { + h3 { text-align: left; - position: relative; - margin-bottom: 1rem; + cursor: pointer; - h1 { - text-align: left; - margin-bottom: 0.5rem; + &:hover { + color: #3578e5; } + } - a { - cursor: pointer; - } + p { + margin-bottom: 10px; + opacity: 0.9; + font-size: 0.8rem; + overflow: hidden; + text-overflow: ellipsis; + display: -webkit-box; + -webkit-line-clamp: 2; + -webkit-box-orient: vertical; } - .right { - flex: 0 0 66.666667%; - max-width: 66.666667%; - font-size: 1.2rem; + .info { display: flex; flex-direction: column; - gap: 20px; + justify-content: center; + font-size: 0.8rem; - .viewBlogContainer { - h3 { - text-align: left; - cursor: pointer; - - &:hover { - color: #3578e5; - } - } + .author { + font-size: 0.8rem; - p { - margin-bottom: 10px; - opacity: 0.9; - font-size: 0.8rem; - overflow: hidden; - text-overflow: ellipsis; - display: -webkit-box; - -webkit-line-clamp: 2; - -webkit-box-orient: vertical; + a { + color: rgba(0, 0, 0, 0.54); } + } - .info { - display: flex; - flex-direction: column; - justify-content: center; - font-size: 0.8rem; - - .author { - font-size: 0.8rem; + .update-time { + font-size: 0.8rem; + color: rgba(0, 0, 0, 0.54); + } + } + } +} - a { - color: rgba(0, 0, 0, 0.54); - } - } +/* Responsive Styles */ +@media screen and (max-width: 992px) { + .blogPostContainer { + .left { + flex: 0 0 100%; + max-width: 100%; + } + .right { + flex: 0 0 100%; + max-width: 100%; + } + } +} - .update-time { - font-size: 0.8rem; - color: rgba(0, 0, 0, 0.54); - } - } - } +@media screen and (max-width: 768px) { + .blogPostContainer { + .row { + flex-direction: column; } } } -html[data-theme="dark"] { +html[data-theme='dark'] { .blogPostContainer { .viewBlogContainer { - .author { - a { - color: rgb(255, 255, 255, 0.6) !important; - } - } - + .author a, .update-time { color: rgb(255, 255, 255, 0.6) !important; } From 76dd12e822bda740a30802802945b7658a7487c3 Mon Sep 17 00:00:00 2001 From: nikhilchauhangithub Date: Mon, 7 Aug 2023 01:34:46 +0530 Subject: [PATCH 3/3] fixed broken linkfix Signed-off-by: nikhilchauhangithub --- blog/cncf-sandbox-announcement/index.mdx | 48 ++++++++++++------------ 1 file changed, 25 insertions(+), 23 deletions(-) diff --git a/blog/cncf-sandbox-announcement/index.mdx b/blog/cncf-sandbox-announcement/index.mdx index 7cea91ee78..c9dbfb7146 100644 --- a/blog/cncf-sandbox-announcement/index.mdx +++ b/blog/cncf-sandbox-announcement/index.mdx @@ -1,29 +1,31 @@ --- authors: -- Sanil Kumar -- Jun Du + - Sanil Kumar + - Jun Du categories: -- General -- Announcements + - General + - Announcements date: 2019-03-19 draft: false lastmod: 2019-03-19 subtitle: KubeEdge was accepted into the CNCF sandbox in March 2019 -summary: KubeEdge is a Kubernetes Native Edge Computing Framework. KubeEdge was accepted +summary: + KubeEdge is a Kubernetes Native Edge Computing Framework. KubeEdge was accepted into the CNCF sandbox in March 2019 tags: -- KubeEdge -- kubeedge -- edge computing -- kubernetes edge computing -- K8S edge orchestration -- edge computing platform -- cncf sandbox -- cloud native + - KubeEdge + - kubeedge + - edge computing + - kubernetes edge computing + - K8S edge orchestration + - edge computing platform + - cncf sandbox + - cloud native title: 'From the K8S blog: KubeEdge - a Kubernetes Native Edge Computing Framework' --- -The **KubeEdge** team presented their case for sandboxing at the CNCF TOC meeting on 12th March 2019. - + +The **KubeEdge** team presented their case for sandboxing at the CNCF TOC meeting on 12th March 2019. + ## **Today we announce the acceptance of KubeEdge under the CNCF sandbox.** @@ -36,23 +38,24 @@ Original Article: [Source](https://kubernetes.io/blog/2019/03/19/kubeedge-k8s-ba :::info -CNCF Sandbox page: [CNCF Sandbox Projects](https://www.cncf.io/sandbox-projects/) +CNCF Sandbox page: [CNCF Sandbox Projects](https://www.cncf.io/sandbox-projects/) ::: :::info -[KubeEdge Repository](https://github.com/kubeedge/kubeedge) | [KubeEdge Documentation](https://docs.kubeedge.io) | [Setup KubeEdge](https://docs.kubeedge.io/en/latest/setup/setup.html) +[KubeEdge Repository](https://github.com/kubeedge/kubeedge) | [KubeEdge Documentation](https://kubeedge.io/docs) | [Setup KubeEdge](https://kubeedge.io/docs/category/setup) -::: +::: -## **KubeEdge becomes the first Kubernetes Native Edge Computing Platform with both Edge and Cloud components open sourced!** +## **KubeEdge becomes the first Kubernetes Native Edge Computing Platform with both Edge and Cloud components open sourced!** Open source edge computing is going through its most dynamic phase of development in the industry. So many open source platforms, so many consolidations and so many initiatives for standardization! This shows the strong drive to build better platforms to bring cloud computing to the edges to meet ever increasing demand. KubeEdge, which was announced last year, now brings great news for cloud native computing! It provides a complete edge computing solution based on Kubernetes with separate cloud and edge core modules. Currently, both the cloud and edge modules are open sourced. Unlike certain light weight kubernetes platforms available around, KubeEdge is made to build edge computing solutions extending the cloud. The control plane resides in cloud, though scalable and extendable. At the same time, the edge can work in offline mode. Also it is lightweight and containerized, and can support heterogeneous hardware at the edge. With the optimization in edge resource utlization, KubeEdge positions to save significant setup and operation cost for edge solutions. This makes it the most compelling edge computing platform in the world currently, based on Kubernetes! ### **_Kube(rnetes)Edge_!** - Opening up a new Kubernetes-based ecosystem for Edge Computing + The key goal for KubeEdge is extending Kubernetes ecosystem from cloud to edge. From the time it was announced to the public at KubeCon in Shanghai in November 2018, the architecture direction for KubeEdge was aligned to Kubernetes, as its name! It started with its v0.1 providing the basic edge computing features. Now, with its latest release v0.2, it brings the cloud components to connect and complete the loop. With consistent and scalable Kubernetes-based interfaces, KubeEdge enables the orchestration and management of edge clusters similar to how Kubernetes manages in the cloud. This opens up seamless possibilities of bringing cloud computing capabilities to the edge, quickly and efficiently. @@ -61,7 +64,6 @@ Based on its roadmap and architecture, KubeEdge tries to support all edge nodes, KubeEdge provides a containerized edge computing platform, which is inherently scalable. As it’s modular and optimized, it is lightweight (66MB foot print and ~30MB running memory) and could be deployed on low resource devices. Similarly, the edge node can be of different hardware architecture and with different hardware configurations. For the device connectivity, it can support multiple protocols and it uses a standard MQTT-based communication. This helps in scaling the edge clusters with new nodes and devices efficiently. - ## **You heard it right!** > **KubeEdge Cloud Core modules are open sourced!** @@ -91,16 +93,14 @@ Even if you want to add more control plane modules based on the architecture ref - KubeEdge provides scalable lightweight Kubernetes Native Edge Computing Platform which can work in offline mode. - - It helps simplify edge application development and deployment. - - Cloud vendor agnostic and can run the cloud core modules on any compute node. ::: - ## **Release 0.1 to 0.2 – game changer!** + KubeEdge v0.1 was released at the end of December 2018 with very basic edge features to manage edge applications along with Kubernetes API primitives for node, pod, config etc. In ~2 months, KubeEdge v0.2 was release on March 5th, 2019. This release provides the cloud core modules and enables the end to end open source edge computing solution. The cloud core modules can be deployed to any compute node from any cloud vendors or on-prem. Now, the complete edge solution can be installed and tested very easily, also with a laptop. @@ -117,6 +117,7 @@ The installation is simple and can be done in few steps: - The detailed steps for each are available at [KubeEdge Setup](https://docs.kubeedge.io/en/latest/setup/setup.html) ## **Future: Taking off with competent features and community collaboration** + KubeEdge has been developed by members from the community who are active contributors to Kubernetes/CNCF and doing research in edge computing. The KubeEdge team is also actively collaborating with Kubernetes IOT/EDGE WORKING GROUP. Within a few months of the KubeEdge announcement it has attracted members from different organizations including JingDong, Zhejiang University, SEL Lab, Eclipse, China Mobile, ARM, Intel to collaborate in building the platform and ecosystem. KubeEdge has a clear [roadmap](https://docs.kubeedge.io/en/latest/getting-started/roadmap.html) for its upcoming major releases in 2019. v1.0 targets to provide a complete edge cluster and device management solution with standard edge to edge communication, while v2.0 targets to have advanced features like service mesh, function service , data analytics etc at edge. Also, for all the features, KubeEdge architecture would attempt to utilize the existing CNCF projects/software. @@ -124,6 +125,7 @@ KubeEdge has a clear [roadmap](https://docs.kubeedge.io/en/latest/getting-starte The KubeEdge community needs varied organizations, their requirements, use cases and support to build it. Please join to make a kubernetes native edge computing platform which can extend the cloud native computing paradigm to edge cloud. ## **How to Get Involved?** + We welcome more collaboration to build the Kubernetes native edge computing ecosystem. Please join us! :::info