From ec92c1dc874671af92171772db5f0841aa2ca644 Mon Sep 17 00:00:00 2001 From: Bo Robbrecht Date: Wed, 24 Jul 2024 14:33:19 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Friedrich Co-authored-by: Chris L --- project/audience.md | 12 ++++++------ project/brand.md | 14 +++++++------- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/project/audience.md b/project/audience.md index b3f773f..23890ea 100644 --- a/project/audience.md +++ b/project/audience.md @@ -6,9 +6,9 @@ next: --- # For whom? -The LOAMA project is created for users with a technological knowledge, but we've focused on several factors while designing the application: +The LOAMA project is created for users with a technological background, but we've focused on several factors while designing the application: - **Ease of use**: LOAMA was designed with ease of use in mind by reducing & simplifying the steps that need to be taken to assign permissions. -- **Accessibiliy**: In order to make LOAMA as accessible as possible, we omitted using technical terms to describe function. Instead, by using a combination of icons, simple sentences and colors, we indicate the status of files and divert attention of the user. +- **Accessibiliy**: To make LOAMA as accessible as possible, we omitted using technical terms to describe functions. Instead, by using a combination of icons, simple sentences and colours, we indicate the status of files and divert the attention of the user. By using the information gained during the [brand creation](/project/brand.md), we made a persona to guide us during the design process of [Loama](/loama/index.md): @@ -27,7 +27,7 @@ By using the information gained during the [brand creation](/project/brand.md), - I can't see what permissions are configured for the files in my pod - I don't see who can access my files and which permissions they have - What do the permissions actually mean within my Solid Pod? -- Why should I use Solid over other technologies or just having a company have my data? +- Why should I use Solid over other technologies or just letting a company have my data? #### Solid-enabled apps - What do the permissions actually mean within my Solid Pod? @@ -36,10 +36,10 @@ By using the information gained during the [brand creation](/project/brand.md), ### Needs > What does the users want to do within the app? #### LOAMA -- I want to see what data an person, company or application can access +- I want to see what data a person, company or application can access - I want to see when my data was accessed - I want to revoke or allow acess to my data -- I want to understand what the permissions means and the effect of when I allow them +- I want to understand what the permissions mean and the effect of allowing them #### Solid-enabled apps - I want to use my data in my Solid pod across different platforms @@ -50,5 +50,5 @@ By using the information gained during the [brand creation](/project/brand.md), - I want to be in control of my own data - I want to share the same data across platforms -- I want to easily disabled shared access to sensitive information +- I want to easily revoke access to sensitive information - I want to manage my permissions in a centralized application, not across different platforms \ No newline at end of file diff --git a/project/brand.md b/project/brand.md index 85f2103..f00df33 100644 --- a/project/brand.md +++ b/project/brand.md @@ -6,30 +6,30 @@ title: Branding For the project, we made an appropriate branding that is based on the [SOLID logo](https://solidproject.org). We did this by using several branding techniques commonly used to create a brand from scratch. ## 1. Personifying the product -In order to differentiate our brand from Solid, we trying personifying our product by asking some thought-provoking questions: -- If our product was a person, what would they wear to a party, how would they act on the party and what would be their favorite music? -- If we need to associate our product with a season, what would this be? +To differentiate our brand from Solid, we tried personifying our product by asking some thought-provoking questions: +- If our product was a person, what would they wear to a party, how would they act at the party and what would be their favorite music? +- If we had to associate our product with a season, which would it be? ## 2. Term association In order to find out which things or terms we associated with our product, we created a mindmap with terms that we associate with our product and objects we associate with those terms. ![LOAMA Mindmap](../images/loama-mindmap.png) -This gave us more insight in what we could use as a basis for naming our product. +This gave us more insight into what we could use as a basis for naming our product. ## 3. Name The name LOAMA is an acrynom: > **L**inked **O**pen **A**ccess **M**anagement **A**pp -It's a technical way to describe our project, but the acronym *(Loama)* was an unexpected inspiration for our brand, as it became a basis for which we build our brand, crest and color palette. +It's a technical way to describe our project, but the acronym *(Loama)* was an unexpected inspiration for our project's identity, as it became a basis for which we build our brand, crest and color palette. ![Loama Crest](/loama-logo.svg) ## 4. Typography & Color Usage -During the design process, we research and define a typography & color palette in order to have a consistent look & feel through the project. These elements were re-used within the design prototype, presentations, live demos and documentation. +During the design process, we researched and defined a typography & color palette in order to have a consistent look & feel through the project. These elements were re-used within the design prototype, presentations, live demos and documentation. ![Color Palette LOAMA](../images/color-palette.png) -For our font, we've decided to use a monospace font *([Jetbrains Mono](https://www.jetbrains.com/lp/mono/))* for headers, wordmark or highlight text. This allowed us to give of an technological feeling and worked great in creating a contrast with our sans-serif font. +For our font, we've decided to use a monospace font *([Jetbrains Mono](https://www.jetbrains.com/lp/mono/))* for headers, wordmark or highlighted text. This allows us to emit a technological feeling and worked great in creating a contrast with our sans-serif font. Our standard / sans-serif font of choice is the [Raleyway font](https://www.theleagueofmoveabletype.com/raleway), as it already has a usage: It's the main font style of the Solid project. Because of this, our project has a strong correlation to Solid, but can differentiate itself by using the mono font. \ No newline at end of file