Fix 'Choose Template' Button Icon Overlap and Improvon Icon UX #34
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.
Overview
This PR fixes overlapping icons on the 'Choose Template' button and replaces the word doc icon with a more appropriate file lines icon for better user experience. Additionally, it updates
.gitignore
to ignore.env
files used in local development and adds a.env.example
for developers to quickly configure the.env
file.Changes
fa fa-file-word-o
with file lines iconfa-light fa-file-lines
.env
to.gitignore
file.env.example
fileNotes
Change Icon
The user experience after clicking the 'Choose Template' button is a text field where an AI policy statement is pre-populated in a text field, but the text in the field can be modified and saved. Given this user interface, the word doc icon is not the most appropriate as it typically denotes uploading / downloading a word document, which is not the case here. The file lines icon better aligns with the experience users will have once they click the the 'Choose Template' button, a field with text in it.
.env
The docker-compose locally looks for a .env file for the NGROK url where the application can be hosted and tested locally. Since developers will be asked to create a .env file, adding it to .gitignore prevents the .env file from getting picked up. Adding the .env.example gives developers an example of what their .env file should include.
References