Thanks for checking out this front-end coding challenge.
Frontend Mentor challenges help you improve your coding skills by building realistic projects.
To do this challenge, you need a basic understanding of HTML, CSS and JavaScript.
Your challenge is to build out this landing page and get it looking as close to the design as possible.
You can use any tools you like to help you complete the challenge. So if you've got something you'd like to practice, feel free to give it a go.
Your users should be able to:
- View the optimal layout for the site depending on their device's screen size
- See hover states for all interactive elements on the page
- Receive an error message when the newsletter form is submitted if:
- The input field is empty
- The email address is not formatted correctly
For this challenge you'll need to:
- Create the rounded blue background shape with code
- Change the
fill
andstroke
color of the SVGs at specific points (the challenge can be completed using the singlelogo-bookmark.svg
file provided)
Want some support on the challenge? Join our Slack community and ask questions in the #help channel.
Your task is to build out the project to the designs inside the /design
folder. You will find both a mobile and a desktop version of the design.
The designs are in JPG static format. Using JPGs will mean that you'll need to use your best judgment for styles such as font-size
, padding
and margin
.
If you would like the design files (we provide Sketch & Figma versions) to inspect the design in more detail, you can subscribe as a PRO member.
You will find all the required assets in the /images
folder. The assets are already optimized.
There is also a style-guide.md
file containing the information you'll need, such as color palette and fonts.
Feel free to use any workflow that you feel comfortable with. Below is a suggested process, but do not feel like you need to follow these steps:
- Initialize your project as a public repository on GitHub. Creating a repo will make it easier to share your code with the community if you need help. If you're not sure how to do this, have a read-through of this Try Git resource.
- Configure your repository to publish your code to a web address. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, and we provide some recommendations below.
- Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes to create reusable styles.
- Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
- Write out the base styles for your project, including general content styles, such as
font-family
andfont-size
. - Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
You can host your site using one of these solutions or any of our other trusted providers. Read more about our recommended and trusted hosts.
We strongly recommend overwriting this README.md
with a custom one. We've provided a template inside the README-template.md
file in this starter code.
The template provides a guide for what to add. A custom README
will help you explain your project and reflect on your learnings. Please feel free to edit our template as much as you like.
Once you've added your information to the template, delete this file and rename the README-template.md
file to README.md
. That will make it show up as your repository's README file.
Submit your solution on the platform for the rest of the community to see. Follow our "Complete guide to submitting solutions" for tips on how to do this.
Remember, if you're looking for feedback on your solution, be sure to ask questions when submitting it. The more specific and detailed you are with your questions, the higher the chance you'll get valuable feedback from the community.
There are multiple places you can share your solution:
- Share your solution page in the #finished-projects channel of the Slack community.
- Tweet @frontendmentor and mention @frontendmentor, including the repo and live URLs in the tweet. We'd love to take a look at what you've built and help share it around.
- Share your solution on other social channels like LinkedIn.
- Blog about your experience building your project. Writing about your workflow, technical choices, and talking through your code is a brilliant way to reinforce what you've learned. Great platforms to write on are dev.to, Hashnode, and CodeNewbie.
We provide templates to help you share your solution once you've submitted it on the platform. Please do edit them and include specific questions when you're looking for feedback.
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
We love receiving feedback! We're always looking to improve our challenges and our platform. So if you have anything you'd like to mention, please email hi[at]frontendmentor[dot]io.
This challenge is completely free. Please share it with anyone who will find it useful for practice.
Have fun building! 🚀
mySoligon A school website. Project Title: mySoligon website Project Description: mySoligon website is a school website This website has three feautures
A profile: This contains the students profile which houses the profile picture and personal nformation of the student. A score box : This houses the result(scores) of the student based on past examination written in the school. A bank : This enables the student to pay fees and request for loans. The bank contains three major operations i ===> Bank Tranfer; Here a student can transfer money to another user (Although for real world application the money is supposed to go directly to the school bank) ii ===> Bank loan Here a user can request a loan from the bank if any deposit made by the user is 10% greater than the request.(i.e the user is in need of financial aid to pay fees) iii ==> Close account Here the user is able to close his/her account (although this should only be achievable by getting permission and licence from the school board) The bank also houses all transactions that has been performed by the user. Applications Used : HTML,CSS,JAVASCRIPT.
Challenges I Faced: Fixing the three main parts(The student profile, results, bank) of the website inone page was a bit difficult , since i dont know how to put each of this in a different page Implementing the transfer and loan functionality tooks hours to get through To find the account of the user based on user inputs
Feautures i hope to implement in the future : If a user decides to close his/her account, the user should be logged out of the website Dates of each transaction should be recorded The users data should be gotten from a database not hardcoded if current profile pictre is not found the image source should fall back to the in the html file.
How to se the project: i used my friends details for this project 😆😆 login credentials: username & password ous --> 1111 aao --> 2222 mpt --> 3333 kcc --> 4444 uom --> 5555 ofc --> 6666
Acknowledgment: I leanrt how to implement the bank functionalities with the "Jonas Schemedtmann" course from udemy === The complete javascript course : from zero to expert. MY cousin Ogonna Ugochukw helped me with the design