Add blog post for back office rebranding #1305
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tblivet
commented
Aug 26, 2024
tblivet
commented
| Questions | Answers |
|---|---|
| Description? | Add blog post to introduce back office rebranding in PrestaShop v9 |
| Fixed ticket? |
|
Hello @tblivet! This is your first pull request on prestashop.github.io repository of the PrestaShop project. Thank you, and welcome to this Open Source community! |
kpodemski
requested changes
Sep 2, 2024
| --- | ||
| layout: post | ||
| title: "PrestaShop Back Office rebranding with PrestaShop 9" | ||
| subtitle: "Rebranded Back Office Themes Now Available in PrestaShop v9" |
There was a problem hiding this comment.
Suggested change
| subtitle: "Rebranded Back Office Themes Now Available in PrestaShop v9" | |
| subtitle: "Rebranded Back Office Themes Available in PrestaShop 9" |
| tags: [ "9.0", Design ] | ||
| --- | ||
|
|
||
| By the end of 2023, PrestaShop unveiled a new brand identity to strengthen its position, enhance credibility, and build trust. The PrestaShop back office is one of the last assets to receive this rebranding, and the release of PrestaShop 9 provided the perfect opportunity for this update. The rebranding involved significant changes to the PrestaShop back office, focusing on its two themes. |
There was a problem hiding this comment.
Suggested change
| By the end of 2023, PrestaShop unveiled a new brand identity to strengthen its position, enhance credibility, and build trust. The PrestaShop back office is one of the last assets to receive this rebranding, and the release of PrestaShop 9 provided the perfect opportunity for this update. The rebranding involved significant changes to the PrestaShop back office, focusing on its two themes. | |
| By the end of 2023, PrestaShop unveiled a new brand identity to strengthen its position, enhance credibility, and build trust. [We already announced]({{< relref "/news/posts/2023/new-project-branding" >}}) the new branding for the project, and the PrestaShop back office is one of the last assets to follow this change. The release of PrestaShop 9 provided the perfect opportunity for this update. The rebranding involved significant changes to the PrestaShop back office, focusing on its two themes. |
|
|
||
|  | ||
|
|
||
| ## Back Office Rebrand |
There was a problem hiding this comment.
Suggested change
| ## Back Office Rebrand | |
| ## Back office rebranding |
|
|
||
| ## Back Office Rebrand | ||
|
|
||
| ### Anatomy of the PrestaShop Back Office |
There was a problem hiding this comment.
Suggested change
| ### Anatomy of the PrestaShop Back Office | |
| ### Anatomy of the PrestaShop back office |
|
|
||
| ## Need for Refactoring | ||
|
|
||
| Updating both themes was essential to provide a consistent user experience throughout the back office. This harmonization effort focused on integrating CSS variables from the UI Kit, offering a centralized method to define design elements like colors, backgrounds, and shadows. The `_root.scss` file serves as a single source of truth for these variables, enabling efficient application of styles across both themes. |
There was a problem hiding this comment.
Suggested change
| Updating both themes was essential to provide a consistent user experience throughout the back office. This harmonization effort focused on integrating CSS variables from the UI Kit, offering a centralized method to define design elements like colors, backgrounds, and shadows. The `_root.scss` file serves as a single source of truth for these variables, enabling efficient application of styles across both themes. | |
| Updating both themes was essential to providing a consistent user experience throughout the back office. This harmonization effort focused on integrating CSS variables from the UI Kit, offering a centralized method to define design elements like colors, backgrounds, and shadows. The `_root.scss` file serves as a single source of truth for these variables, enabling efficient application style across both themes. |
|
|
||
| Updating both themes was essential to provide a consistent user experience throughout the back office. This harmonization effort focused on integrating CSS variables from the UI Kit, offering a centralized method to define design elements like colors, backgrounds, and shadows. The `_root.scss` file serves as a single source of truth for these variables, enabling efficient application of styles across both themes. | ||
|
|
||
| ## Developer Tool for the Default Theme |
There was a problem hiding this comment.
Suggested change
| ## Developer Tool for the Default Theme | |
| ## Developer tool for the default theme |
|
|
||
| CSS variables play a critical role in both the rebranding and the long-term maintainability of PrestaShop’s back office. They not only facilitate current design needs but also lay the foundation for future enhancements. | ||
|
|
||
| ### Why Use CSS Variables? |
There was a problem hiding this comment.
Suggested change
| ### Why Use CSS Variables? | |
| ### Why CSS Variables? |
| date: 2024-08-26 | ||
| author: [ ThibaultBlivet ] | ||
| icon: icon-leaf | ||
| tags: [ "9.0", Design ] |
There was a problem hiding this comment.
Suggested change
| tags: [ "9.0", Design ] | |
| tags: [ "9.0", design, ux ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.