From df2c199101c7a508ef2cf2febddc22dd3ebfd730 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9Cyndira-flowforge=E2=80=9D?= <“yndira@flowforge.com”> Date: Tue, 4 Jul 2023 14:24:57 +0200 Subject: [PATCH 1/3] Update design process section --- src/handbook/design/process.md | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/src/handbook/design/process.md b/src/handbook/design/process.md index 698d35bc11..021e7f7447 100644 --- a/src/handbook/design/process.md +++ b/src/handbook/design/process.md @@ -1,13 +1,15 @@ -## Process +# Process -### Art Requests +## Art Requests If you want something designed or drawn, then please follow the details in [Art Requests](./art-requests.md) in order to have your request be picked up by an available designer. -### Scheduling +## Scheduling -The Design process is bound by the [Development Cadence](../development/releases/planning#cadence), +### Product design + +The Design process is bound by the [Development Cadence](../development/releases/planning#cadence). Work begins on formal design (mid and high-fidelity UX and visual design assets) two weeks prior to a release cycle beginning. @@ -16,7 +18,19 @@ been conducted on the high-level UX, and development is not blocked at the start of a release sprint. Both visual and UX design iterations will occur throughout the first two weeks of a cycle, alongside development efforts. -### Delivery of Art +### Website and rest of design assets + +In contrast to the platform, changes and updates to the web design can be implemented independently and are not limited to specific release cycles. The timing and order of these changes, as well as the creation of other design assets such as blog images, open graphs, presentations, illustrations, etc., depend on prioritization aligned with the company's interests. + +## Reviewing + +During this phase, it is essential, whenever possible, to thoroughly review the proposed content before proceeding with the implementation in code, particularly regarding UX/UI design. + +This phase aims to ensure that the design not only looks visually appealing but also effectively communicates the intended message to the audience. This includes assessing the organization of information, evaluating the readability and coherence of text, and verifying the alignment with the project's objectives. + +By including a review phase in the design process, we can identify any potential issues or areas for improvement early on. This proactive approach helps streamline the overall design workflow, minimizes the need for extensive revisions at later stages, and ultimately delivers a high-quality design that meets both aesthetic and content-related requirements. + +## Delivery of Art While the art request will include a delivery method of the assets, please be sure to also always export the asset to the [Design directory](https://drive.google.com/drive/folders/1PiuFwW3H8XuydolepmfQQ4BjcdNekVQg){rel="nofollow"} From 023f6bc9b027e3714d33f13f7f894a207fd76161 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9Cyndira-flowforge=E2=80=9D?= <“yndira@flowforge.com”> Date: Fri, 14 Jul 2023 09:17:56 +0200 Subject: [PATCH 2/3] improve writing --- src/handbook/design/process.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/handbook/design/process.md b/src/handbook/design/process.md index 021e7f7447..17e2c2b865 100644 --- a/src/handbook/design/process.md +++ b/src/handbook/design/process.md @@ -22,13 +22,15 @@ first two weeks of a cycle, alongside development efforts. In contrast to the platform, changes and updates to the web design can be implemented independently and are not limited to specific release cycles. The timing and order of these changes, as well as the creation of other design assets such as blog images, open graphs, presentations, illustrations, etc., depend on prioritization aligned with the company's interests. -## Reviewing +## Design Review -During this phase, it is essential, whenever possible, to thoroughly review the proposed content before proceeding with the implementation in code, particularly regarding UX/UI design. +This phase aims to ensure that the designs not only look visually appealing, but also effectively communicate the intended message to the audience. -This phase aims to ensure that the design not only looks visually appealing but also effectively communicates the intended message to the audience. This includes assessing the organization of information, evaluating the readability and coherence of text, and verifying the alignment with the project's objectives. +To achieve this, please assess the organization of information, evaluate the readability and coherence of text, and verify the alignment with the project's objectives. -By including a review phase in the design process, we can identify any potential issues or areas for improvement early on. This proactive approach helps streamline the overall design workflow, minimizes the need for extensive revisions at later stages, and ultimately delivers a high-quality design that meets both aesthetic and content-related requirements. +For UX/UI proposals, the design review concludes with the sign-off of Figma designs by the page owner, who is usually the DRI for the Website but may be another team member. As for the rest of the design assets, it's determined by the person who created the Art Request. + +While iterations can be made during the development phase for UX/UI design in terms of content and layout, it is recommended to facilitate feedback loops during the design phase. By getting early feedback, we aim to identify and address any potential issues before entering the development phase. This approach helps streamline the design workflow, allowing for quicker iterations and ultimately saving time. ## Delivery of Art From ff635cc27c90a8e2b5484109c3c84f7ef28beff6 Mon Sep 17 00:00:00 2001 From: Zeger-Jan van de Weg Date: Wed, 19 Jul 2023 10:13:45 +0200 Subject: [PATCH 3/3] Update src/handbook/design/process.md Co-authored-by: Yndira Escobar <129537638+Yndira-FlowForge@users.noreply.github.com> --- src/handbook/design/process.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/handbook/design/process.md b/src/handbook/design/process.md index 17e2c2b865..c42592af8a 100644 --- a/src/handbook/design/process.md +++ b/src/handbook/design/process.md @@ -28,6 +28,8 @@ This phase aims to ensure that the designs not only look visually appealing, but To achieve this, please assess the organization of information, evaluate the readability and coherence of text, and verify the alignment with the project's objectives. +All design proposals, including UX/UI and other design assets, will be presented and signed off in GitHub, ensuring one source of truth and centralizing the process for all design-related work. + For UX/UI proposals, the design review concludes with the sign-off of Figma designs by the page owner, who is usually the DRI for the Website but may be another team member. As for the rest of the design assets, it's determined by the person who created the Art Request. While iterations can be made during the development phase for UX/UI design in terms of content and layout, it is recommended to facilitate feedback loops during the design phase. By getting early feedback, we aim to identify and address any potential issues before entering the development phase. This approach helps streamline the design workflow, allowing for quicker iterations and ultimately saving time.