-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop' into DDFLSBP-651-implement-cookie-blocking-pla…
…ceholder
- Loading branch information
Showing
11 changed files
with
85 additions
and
27 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Architecture Decision Record: Form Styling | ||
|
||
## Context | ||
|
||
There are various types of forms within the project, and it is always a dilemma | ||
as to whether to write specific styling per form, or to create a common set of | ||
base classes. | ||
|
||
## Decision | ||
|
||
We have decided to create a set of `default classes` to be used when building | ||
different kinds of forms, as to not create a large amount of location that | ||
contain form styling. Considering the forms within the project all look very | ||
similar/consist of elements that look the same, it will be an advantage to have | ||
a centralized place to expand/apply future changes to. | ||
|
||
As we follow the BEM class structure, the block is called `dpl-form`, which can | ||
be expanded with elements, and modifiers. | ||
|
||
## Alternatives considered | ||
|
||
We considered writing new classes every time we introduced a new form, however, | ||
this seemed like the inferior option. If a specific form element was to change | ||
styling in the future, we would have to adjust all of the specific instances, | ||
instead of having a singular definition. And in case a specific instance needs | ||
to adopt a different styling, it can be achieved by creating a specific class | ||
fot that very purpose. | ||
|
||
## Consequences | ||
|
||
As per this decision, we expect introduction of new form elements to be styled | ||
expanding the current `dpl-form` class. | ||
|
||
This currently has an exception in form of form inputs - these have been styled | ||
a long time ago and use the class `dpl-input`. | ||
|
||
### Implementation in the dpl-design-system | ||
|
||
Here is the [link to our form css file](../src/stories/Blocks/form/form.scss). |
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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
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
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
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
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
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
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