mirror of https://github.com/rancher/dashboard.git
Clarifying style and content
This commit is contained in:
parent
28c87dda57
commit
0a5fc1a64e
|
|
@ -0,0 +1,22 @@
|
||||||
|
---
|
||||||
|
title: 'Epinio Gitlab Integration'
|
||||||
|
description: Allowing the user to more easily use Gitlab directly in the Epinio UI
|
||||||
|
authors: [sorin]
|
||||||
|
tags: [Epinio]
|
||||||
|
---
|
||||||
|
|
||||||
|
Integrates GitLab directly into the application deployment workflow
|
||||||
|
|
||||||
|
<!--truncate-->
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Binary file not shown.
|
After Width: | Height: | Size: 76 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 95 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 88 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 63 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 78 KiB |
|
|
@ -1,20 +1,16 @@
|
||||||
---
|
---
|
||||||
title: 'Inactive socket timeouts'
|
title: 'Socket Timeout UX'
|
||||||
description: Inactivity notification and timeout settings in the UI
|
description: Inactivity notification and timeout settings in the UI
|
||||||
slug: Inactivity Timeout Modal
|
|
||||||
authors: [eden]
|
authors: [eden]
|
||||||
tags: [Manager, Modal, Timeout, Inactivity]
|
tags: [Manager, Modal, Timeout, Inactivity]
|
||||||
---
|
---
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
As part of Rancher Manager's wider performance improvement work, we looked at simple ways to improve the browser's performance.
|
As part of Rancher Manager's wider performance improvement work, we looked at simple ways to improve the browser's performance.
|
||||||
|
|
||||||
|
|
||||||
## User flow
|
|
||||||
|
|
||||||
Users often have many tabs open in their browser, each connecting to the Rancher backend via sockets. To reduce this load when browser tabs go unnoticed, we will implement a user-configurable time-out to disconnect any sockets the UI has open to the backend.
|
Users often have many tabs open in their browser, each connecting to the Rancher backend via sockets. To reduce this load when browser tabs go unnoticed, we will implement a user-configurable time-out to disconnect any sockets the UI has open to the backend.
|
||||||
|
|
||||||
|
<!--truncate-->
|
||||||
|
|
||||||
Once implemented, after a given time, the user will receive an intitial modal dialogue warning them of the pending socket time-out and allow them to reset the timer, signalling that the sockets should stay connected and a time-out modal when the time-out has expired.
|
Once implemented, after a given time, the user will receive an intitial modal dialogue warning them of the pending socket time-out and allow them to reset the timer, signalling that the sockets should stay connected and a time-out modal when the time-out has expired.
|
||||||
|
|
||||||
## UX Design
|
## UX Design
|
||||||
|
|
|
||||||
|
|
@ -1,19 +1,23 @@
|
||||||
---
|
---
|
||||||
title: 'Rancher Manager extensions'
|
title: 'Enhancing Rancher Manager'
|
||||||
description: Extend the functionality of the platform using extensions
|
description: Enhancing Rancher Manager
|
||||||
slug: Rancher Manager extensions
|
|
||||||
authors: [neil, alex, jordon]
|
authors: [neil, alex, jordon]
|
||||||
tags: [Manager, Extensions]
|
tags: [Manager, Extensions]
|
||||||
---
|
---
|
||||||
|
|
||||||
## Overview
|
Rancher Manager Extensions are a new feature in Rancher Manager that allows organizations to extend its functionality by adding custom tools and integrations. Extensions can be developed and deployed to Rancher Manager using a simple API, making it easy to customize and enhance the platform to meet specific requirements.
|
||||||
|
|
||||||
One of the key features of Rancher Manager is its extensibility. With Rancher Manager extensions, users can extend the functionality of the platform to meet their specific needs.
|
<!--truncate-->
|
||||||
|
|
||||||
Rancher Manager extensions are custom-built plugins that can be integrated into the Rancher Manager platform. These plugins are designed to provide additional functionality that is not available out-of-the-box. For example, an extension could be created to provide additional monitoring and logging capabilities, or to add custom security features.
|
Rancher Manager Extensions allow organizations to streamline Kubernetes management tasks by integrating with other Kubernetes tools, such as Helm and Istio. They can also be used to create custom dashboards and monitoring tools, add support for specific cloud providers, and enhance security and compliance.
|
||||||
|
Developing Rancher Manager Extensions is a straightforward process. Extensions are developed using standard web technologies, such as HTML, CSS, and JavaScript, and can be deployed to Rancher Manager using a simple API. Rancher provides extensive documentation and examples to help developers get started with Rancher Manager Extensions.
|
||||||
|
|
||||||
Extensions are built using the Rancher CLI (Command Line Interface) and are packaged as Docker containers. Once an extension is packaged, it can be uploaded to Rancher Manager and installed with just a few clicks. Once installed, the extension will be integrated seamlessly into the Rancher Manager interface.
|
To create a Rancher Manager Extension, developers need to define the extension’s user interface, create the necessary backend functionality using the Rancher API, and package the extension as a container image. Once the extension is packaged, it can be deployed to Rancher Manager using the Rancher API, and users can access it through the Rancher Manager UI.
|
||||||
|
Rancher Manager Extensions are a powerful tool for enhancing Kubernetes management workflows. By integrating with other Kubernetes tools and adding custom functionality, organizations can streamline their Kubernetes management tasks and improve operational efficiency.
|
||||||
|
|
||||||
One of the key benefits of Rancher Manager extensions is that they can be easily customized to meet the needs of individual users or organizations. This makes Rancher Manager a flexible and adaptable tool for managing containerized applications. With the ability to add custom functionality through extensions, users can tailor the platform to their specific requirements.
|
To learn more about Rancher Manager Extensions and how to develop them, check out the following resources:
|
||||||
|
- Rancher Manager Extensions Documentation: https://rancher.com/docs/rancher/v2.x/en/extend-rancher/
|
||||||
|
- Rancher Manager Extensions GitHub Repository: https://github.com/rancher/rancher-catalog
|
||||||
|
- Rancher Manager Extensions Example Repository: https://github.com/rancher/longhorn-manager-extensions
|
||||||
|
|
||||||
In conclusion, Rancher Manager extensions are a powerful feature of the Rancher Manager platform that allow users to extend the functionality of the platform to meet their specific needs. By providing a flexible and customizable tool for managing containerized applications, Rancher Manager is an ideal solution for organizations looking to streamline their container management processes.
|
In conclusion, Rancher Manager Extensions are a powerful feature of Rancher Manager that allow organizations to customize and enhance their Kubernetes management workflows. With a simple API and extensive documentation and examples, developing Rancher Manager Extensions is a straightforward process. By leveraging Rancher Manager Extensions, organizations can improve operational efficiency and streamline their Kubernetes management tasks.
|
||||||
|
|
@ -1,20 +1,16 @@
|
||||||
---
|
---
|
||||||
title: 'Application menu design'
|
title: 'Rethinking the Application Menu'
|
||||||
description: Allow the user to quickly change between apps and clusters
|
description: Allow the user to quickly change between apps and clusters
|
||||||
slug: Global app and cluster menu
|
authors: [eden, kwwii]
|
||||||
authors: [manuele, eden, kwwii]
|
|
||||||
tags: [Manager, Navigation]
|
tags: [Manager, Navigation]
|
||||||
---
|
---
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
As part of our usability review, we learned that the top level context switching mechanism for our application is hidden behine a burger menu.
|
As part of our usability review, we learned that the top level context switching mechanism for our application is hidden behine a burger menu.
|
||||||
|
|
||||||
|
|
||||||
## User flow
|
|
||||||
|
|
||||||
In order to select an application or explore a cluster the user must first expand a hidden menu. As this is an action users perform often, offering a persistent way to change between app and cluster context will improve usability.
|
In order to select an application or explore a cluster the user must first expand a hidden menu. As this is an action users perform often, offering a persistent way to change between app and cluster context will improve usability.
|
||||||
|
|
||||||
|
<!--truncate-->
|
||||||
|
|
||||||
## UX Design
|
## UX Design
|
||||||
|
|
||||||
**Overview**
|
**Overview**
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
kwwii:
|
kwwii:
|
||||||
name: Kenneth Wesley Wimer II
|
name: Kenneth Wimer
|
||||||
title: UX/UI Head
|
title: User Experience Wizard
|
||||||
url: https://github.com/kwwii
|
url: https://github.com/kwwii
|
||||||
image_url: https://github.com/kwwii.png
|
image_url: https://github.com/kwwii.png
|
||||||
|
|
||||||
|
|
@ -66,7 +66,7 @@ phil:
|
||||||
|
|
||||||
neil:
|
neil:
|
||||||
name: Neil MacDougall
|
name: Neil MacDougall
|
||||||
title: UX/UI Developer
|
title: Director - UX/UI
|
||||||
url: https://github.com/nwmac
|
url: https://github.com/nwmac
|
||||||
image_url: https://github.com/nwmac.png
|
image_url: https://github.com/nwmac.png
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,17 +1,15 @@
|
||||||
---
|
---
|
||||||
slug: welcome
|
title: The Rancher UX/UI team
|
||||||
title: Welcome
|
authors: [neil, kwwii, cody, nancy, sean, jordon, phil, giuseppe, shavin, alex, sorin, eden, richa, manuele, francesco, richard]
|
||||||
authors: [kwwii]
|
|
||||||
tags: [team, Rancher, Manager, Epinio, Opni, Desktop, Harvester, Fleet, Elemental]
|
tags: [team, Rancher, Manager, Epinio, Opni, Desktop, Harvester, Fleet, Elemental]
|
||||||
---
|
---
|
||||||
|
|
||||||
## Rancher UX/UI team
|
<!--truncate-->
|
||||||
|
|
||||||
As a team, we are dedicated to creating intuitive, user-friendly interfaces that make it easy for our customers to manage their containerized applications at scale. Our goal is to provide a seamless experience that simplifies complex tasks and enables users to focus on what matters most - their business objectives.
|
As a team, we are dedicated to creating intuitive, user-friendly interfaces that make it easy for our customers to manage their containerized applications at scale. Our goal is to provide a seamless experience that simplifies complex tasks and enables users to focus on what matters most - their business objectives.
|
||||||
|
|
||||||
We believe that good design is a combination of empathy, user research, and iterative prototyping, and we are committed to constantly improving our designs based on user feedback. We look forward to working together to create the best possible user experience for our customers.
|
We believe that good UX is a combination of empathy, user research, and iterative prototyping, and we are committed to constantly improving our UI based on user feedback. We look forward to working together to create the best possible user experience for our customers.
|
||||||
|
|
||||||
## Team Goals
|
## Our Goals
|
||||||
|
|
||||||
- Improve productivity: make it easier for users to complete tasks quickly and efficiently. This can lead to improved productivity and a more efficient use of time and resources.
|
- Improve productivity: make it easier for users to complete tasks quickly and efficiently. This can lead to improved productivity and a more efficient use of time and resources.
|
||||||
|
|
||||||
Loading…
Reference in New Issue