You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+47-26
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,6 @@ This is a solution to the [Newsletter sign-up form with success message challeng
16
16
-[Author](#author)
17
17
-[Acknowledgments](#acknowledgments)
18
18
19
-
**Note: Delete this note and update the table of contents based on what sections you keep.**
20
-
21
19
## Overview
22
20
23
21
### The challenge
@@ -32,25 +30,51 @@ Users should be able to:
32
30
- View the optimal layout for the interface depending on their device's screen size
33
31
- See hover and focus states for all interactive elements on the page
34
32
35
-
### Screenshot
36
-
37
-

38
-

39
-

40
-
41
-
42
-
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
43
-
44
-
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
45
-
46
-
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
47
-
48
-
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
- Live Site URL: [https://github.com/Deeokafor/fm-newsletter-sign-up-with-success-message-main](https://github.com/Deeokafor/fm-newsletter-sign-up-with-success-message-main)
54
78
55
79
## My process
56
80
@@ -70,17 +94,14 @@ Then crop/optimize/edit your image however you like, add it to your project, and
70
94
71
95
### Continued development
72
96
73
-
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
74
-
75
-
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
76
-
97
+
Henceforth, I am focusing on writing UI's which pass accessibilty tests and Semantic-ui's.
77
98
### Useful resources
78
99
79
-
-[w3docs](https://www.w3docs.com) - Their tutorial on adjusting the positions of custom list styles was helpful. You can check it out at [How to Adjust the Position of List Style Image](https://www.w3docs.com/snippets/css/how-to-adjust-the-position-of-list-style-image.html)
100
+
-[Tailwindcss Docs](https://www.tailwindcss.com) - having to refer to the detailed docs here when in a tight spot was so helpful.
101
+
102
+
-[w3schools](https://www.w3schools.com/cssref/css3_pr_align-self.php) - At some point in the project, I was stumped with properly aligning the elements for the `mobile-success-screen` but a little bit of practise on `align-self` rules in css, here, helped me to overcame that challenge in Tailwindcss.
80
103
81
-
-[css-tricks](https://css-tricks.com/quick-reminder-about-file-paths/) - Their short tutorial on fixed and relative filepaths was super helpful in debugging a file path issue I had with Tailwindcss. You can check it out at [Quick Reminder About File Paths](https://css-tricks.com/quick-reminder-about-file-paths/)
82
104
83
-
-[github mkdocs](https://github.com/mkdocs/mkdocs/issues/1757) - the discussions held by these helpful fellows on how github pages using the MkDocs handles file paths in production was super helpful to debug my path failure issues. You can check them out at [ Image paths can break when deploying to gh-pages #1757](https://github.com/mkdocs/mkdocs/issues/1757)
84
105
85
106
86
107
## Author
@@ -91,4 +112,4 @@ Use this section to outline areas that you want to continue focusing on in futur
91
112
92
113
## Acknowledgments
93
114
94
-
- I am thankful to []().
115
+
- I am thankful to [Google Search](google.com) :).
0 commit comments