Merge branch 'master' into playgroundPage

CONTRIBUTING.md

@@ -414,7 +414,7 @@ Follow the following instructions to start contributing.
 **2.** Clone your forked copy of the project.
 
 ```
-git clone --depth=1 https://github.com/layer5io/layer5.git
+git clone --depth=1 https://github.com/<your-username>/layer5.git
 ```
 
 **3.** Navigate to the project directory.

README.md

@@ -135,7 +135,7 @@ alt="Nighthawk" align="left" />
 
 <p style="clear:both;">
 <h1><a name="contributing"></a><a name="community"></a> <a href="https://layer5.io/community">Community</a> and <a href="https://layer5.io/community/handbook">Contributions</a></h1>
-<p> We would love to accept your contributions! This project is community-built and welcomes collaboration. Contributions, updates, <a href="/../../issues">discrepancy reports</a> and <a href="/../../pulls">pull requests</a> are all appreciated. Contributors are expected to adhere to the <a href="https://github.com/cncf/foundation/blob/master/code-of-conduct.md">CNCF Code of Conduct</a>.
+<p> We warmly welcome all contributors! Our projects are community-built and each welcomes open collaboration. As you get started, please review this project's <a href="https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md">contributing guidelines</a>. Whether you are a user or code contributor and whether your opening an <a href="/../../issues">issue</a> or a <a href="/../../pulls">pull requests</a>, know that any form of your engagement is considered contribution and is appreciated. Contributors are expected to adhere to the <a href="https://github.com/cncf/foundation/blob/master/code-of-conduct.md">CNCF Code of Conduct</a>.
 </p>
 <p>
   Join us in the <a href="https://discuss.layer5.io">discussion forum</a> and on <a href="https://slack.layer5.io"><img src=".github/assets/images/slack.png" height="16px" align="bottom" /> Slack</a> to learn more about Layer5 and its community! Make sure you see the <a href="https://layer5.io/community/newcomers">newcomer's guide</a> for a tour of resources available to you.

src/collections/programs/lfx-2023/lfx-2023.mdx

@@ -113,21 +113,96 @@ A use-case that fits very well is be the ability to use it to run performance te
 #### Representing Kubernetes ontology in MeshModel
 
 **Description**: Network topologies and graph databases go hand-in-hand. The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph. Deliverables (among other items):
-- MeshModel capabilities browser
-- Import/export of MeshModel models and components as OCI images
-- augmentation of cuelang-based component generator
+1. MeshModel capabilities browser
+2. Import/export of MeshModel models and components as OCI images
+3. Augmentation of cuelang-based component generator
+
 
 - Recommended Skills: cuelang, golang, OCI
 - Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>
 - Issue: https://github.com/cncf/tag-network/issues/24
 - LFX URL: https://mentorship.lfx.linuxfoundation.org/project/96080e3d-83e2-46ed-928c-b6e7f3154bf3
 
+## LFX Mentorship 2023 Summer Projects
+<br />
+
+### Meshery
+<br />
+
+#### Meshery UI Permissions Framework
+
+**Description**: Meshery UI lacks a permissions framework. The existing internal implementation is simple, fragile and must be completely rewritten. The approach to implemention a permmissions framework includes using React.js and CASL.js. Meshery UI's approach needs to be extensible given that this framework will be an extension point for Remote Providers to supply their own permissions. 
+
+**Expected Outcome**: Definition of permissions and their enforcement in Meshery with an aim for deep granularity and extensibility with each user interface input component carrying a unique permission key id. Each key is then put into a group of keys in a keychain, keychains assigned to user roles, in turn, roles assigned to users. With users having the ability to create own custom roles, the framework will be dynamic based on the associated server-side permissions for the currently auth’ed user.
+- Recommended Skills: React.js, CASL.js
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>, <Link to = "/community/members/abhishek-kumar">Abhishek Kumar</Link>
+- Upstream Issue (URL): https://github.com/meshery/meshery/issues/7436, https://github.com/meshery/meshery/issues/7382
+- LFX URL: https://mentorship.lfx.linuxfoundation.org/project/f4a9804f-2e46-42a4-b2ae-ad3ea7b29734
+
+#### OPA policy evaluation in-browser using WebAssembly and Rego
+
+**Description**: Meshery's highly dynamic infrastructure configuration capabilities require real-time evaluation of complex policies. Policies of various types and with a high number of parameters need to be evaluted client-side. With policies expressed in Rego, the goal of this project is to incorporate use of the https://github.com/open-policy-agent/golang-opa-wasm project into Meshery UI. 
+
+**Expected Outcome**: a powerful real-time multi-user collaboration experience.
+- Recommended Skills: Golang, Open Policy Agent, WASM
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>, <Link to = "/community/members/abhishek-kumar">Abhishek Kumar</Link>
+- Upstream Issue (URL): https://github.com/meshery/meshery/issues/7019
+- LFX URL: https://mentorship.lfx.linuxfoundation.org/project/005db8db-7efe-4433-9605-91d14174c72c
+
+#### Adopt OCI as the packaging and distribution format for Meshery MeshModels
+
+**Description**: Meshery MeshModels represent a schema-based description of cloud native infratructure. MeshModels need to be portable between Meshery deployments as well as easily versionable in external repositories. 
+
+**Expected Outcome**: 
+1. Meshery clients (mesheryctl and Meshery UI) should be able to import/export MeshModels as OCI images.
+2. Meshery clients (mesheryctl and Meshery UI) should be able to push/pull from OCI-compatible registries.
+3. Stretch Goal: OCI image signing; Verify the authenticity of MeshModels using cosign (https://github.com/sigstore/cosign).
+4. Target registries: Meshery Catalog (https://meshery.io/catalog), Artifact Hub.
+
+
+- Recommended Skills: Reactjs, Golang, GraphQL
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>
+- Upstream Issue (URL): https://github.com/meshery/meshery/issues/6447
+- LFX URL: https://mentorship.lfx.linuxfoundation.org/project/26377c30-9ffd-41e3-bfea-839bf126f8f6
+
+#### OCI compatible Kubernetes ontology
+
+**Description**: Network topologies and graph databases go hand-in-hand. The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph. Deliverables (among other items):
+1. MeshModel capabilities browser
+2. Import/export of MeshModel models and components as OCI images
+3. Augmentation of cuelang-based component generator
+
+
+- Recommended Skills: cuelang, golang, OCI
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>
+- Upstream Issue (URL): https://github.com/meshery/meshery/issues/6447
+- LFX URL: https://mentorship.lfx.linuxfoundation.org/project/bb8ddf84-31d7-4a89-9e4b-e6aa9601c0db
+
+### Service Mesh Performance
+<br />
+
+#### Service Mesh Performance IDE Plugin
+
+**Description**: The objective of this project is to develop IDE plugins that can enhance the developer experience while working with Service Mesh Performance Performance Profiles. The proposed plugins will leverage technologies such as golang and cuelang to provide features such as syntax highlighting, auto-completion, validation, and rendering previews for Service Mesh Performance profile and model definitions. 
+
+**Expected Outcome**: 
+1. Release VS Code Extension
+2. Syntax Highlighting and Auto-completion: The plugin can fetch SMP Model definitions such as cloud-native components and their relationships. This information can be used to provide syntax highlighting and auto-completion for these definitions in the JSON files, making it easier for developers to write error-free code.
+3. Validation and Reference: For Meshery MeshModel definitions such as cloud-native components and their relationships, the plugin can use the CUE language to provide validation for the CUE input and preview the rendering result. The plugin can also fetch the SMP Model schemas and display them in the IDE for reference.
+
+
+- Recommended Skills: Cuelang
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>, <Link to = "/community/members/xin-huang">Xin Huang</Link>
+- Upstream Issue (URL): https://github.com/service-mesh-performance/service-mesh-performance/issues/379
+- LFX URL: https://mentorship.lfx.linuxfoundation.org/project/4735d0fa-229f-43e7-9415-dff9220bf687
+
+
 ## Additional information
 <br />
 
 ### Previous experience with technical writers or documentation
 
-<p>Our mentors have managed teams of technical writers working on documenting enterprise-grade software at large technology companies (Cisco, Seagate, SolarWinds). During the span of time, he has worked with technical writers in DITA and post-DITA environments (from Word to FrameMaker, structured writing, online help, various CMSes, git). Our mentors have worked with technical writers on documentation strategy, creating document sets, covering the full spectrum of reader personas.</p>
+<p>Our mentors have managed teams of technical writers working on documenting enterprise-grade software at large technology companies (Cisco, Seagate, SolarWinds). During the span of time, they have worked with technical writers in DITA and post-DITA environments (from Word to FrameMaker, structured writing, online help, various CMSes, git). Our mentors have worked with technical writers on documentation strategy, creating document sets, covering the full spectrum of reader personas.</p>
 
 We interact daily over Slack, and have an open source project [meeting everyday](https://layer5.io/community/calendar), which are posted to the community [YouTube channel](https://www.youtube.com/c/Layer5io?sub_confirmation=1).
 

src/components/Card/index.js

@@ -15,7 +15,7 @@ const Card = ({ frontmatter, fields }) => {
       <div className="post-block">
         <div className="post-thumb-block">
           <Image
-            {...((isDark && frontmatter.darkthumbnail.publicURL !== frontmatter.thumbnail.publicURL)
+            {...((isDark && frontmatter.darkthumbnail && frontmatter.darkthumbnail.publicURL !== frontmatter.thumbnail.publicURL)
               ? frontmatter.darkthumbnail : frontmatter.thumbnail)}
             imgStyle={{ objectFit: "contain" }}
             alt={frontmatter.title}

src/components/CommonForm/index.js

@@ -45,7 +45,7 @@ const CommonForm = ({ form, title, submit_title, submit_body }) => {
 
   useEffect(() => {
     if (submit) {
-      axios.post("https://hook.us1.make.com/s4jo47a8ydq6uk7gg16wuukgr4l52p8c", {
+      axios.post("https://hook.us1.make.com/r5qgpjel5tlhtyndcgjvkrdkoc65417y", {
         memberFormOne,
       });
     }

src/components/Features-carousel/FeaturesCarousel.style.js

@@ -39,7 +39,7 @@ export const FeaturesWrapper = styled.div`
       }
 
       & .pagingDots {
-        top: 2rem !important;
+        top: 0.5rem !important;
         & .paging-item {
           padding :0.25rem;
         }

src/components/HandbookCard/HandbookCard.style.js

@@ -11,7 +11,7 @@ export const HandbookCardWrapper = styled.div`
 	  width: 25rem;
 	  box-shadow: 0 5px 10px ${props => props.theme.green00D3A9ToGreyE6E6E6};
 	  overflow: hidden;
-	  height: 15rem;
+	  height: 19rem;
 	  position: relative;
 		transition: 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
 	}
@@ -53,7 +53,7 @@ export const HandbookCardWrapper = styled.div`
 	  line-height: 1.75;
 	  letter-spacing: 0px;
 	  font-weight: 400;
-	  font-size: .9rem;
+	  font-size: 1.1rem;
 		transition: 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
 	}
 
@@ -95,7 +95,7 @@ export const HandbookCardWrapper = styled.div`
 	}
 
 	.handbook__card:hover {
-	  height: 17rem;
+	  height: 21rem;
 	}
 
 	.handbook__card:hover .handbook__card--head {

src/components/MeetInfo-Table/MeetInfoTable.style.js

@@ -35,7 +35,7 @@ export const TableWrapper = styled.div`
 			}
 		}
 		th {
-			background-color: ${props => props.theme.grey0E0E0EToGreen3C494F};
+			background-color: ${props => props.theme.green00D3A9ToGreen00B39F};
 			color: ${props => props.theme.white};
 			height: 4rem;
 			font-weight: 600;
@@ -54,7 +54,7 @@ export const TableWrapper = styled.div`
 			}
 			/* Highlight Community Calendar */
 			:nth-child(4) {
-				background: ${props => props.theme.saffronLightColor};
+				background: ${props => props.theme.greyFiveToBlueFive};
 			}
 			&:hover {
 				background-color: ${props => props.theme.grey323232ToGreenF3FFFD};

src/components/ScenarioCard/ScenarioCard.style.js

@@ -93,7 +93,7 @@ export const ScenarioCardWrapper = styled.div`
         a {
             color: ${props => props.theme.white};
             &:hover {
-                color: ${props => props.theme.primaryLightColorTwo};
+                color: ${props => props.theme.secondaryColor};
             }
         }
     }

src/components/service-mesh-patterns-Table/Table.js

@@ -48,7 +48,7 @@ const Table = () => {
                       : <>
                       </>}
                     {(column.Header == "Category") ?
-                      <div>{column.canFilter ? column.render("Filter") : null}</div>
+                      <div id={"service-mesh-patterns-table-filter"}>{column.canFilter ? column.render("Filter") : null}</div>
                       : <> </>
                     }
                   </div>

src/sections/Blog/Blog-single/index.js

@@ -159,7 +159,7 @@ const BlogSingle = ({ data }) => {
                   </div>
                 </div>
                 <CTA_Bottom
-                  category={"Docker"}
+                  category={"MeshMap"}
                 />
               </div>
             </div>