Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
7
Comments
2

Tshepiso

@Gandalf-hashSouth Africa110 points

Front-End developer

I’m currently learning...

JavaScript, TypeScript, React and Angular

Latest solutions

  • HTML and CSS Blog Preview Card


    Tshepiso•110
    Submitted over 1 year ago

    1 comment
  • FAQs accordion


    Tshepiso•110
    Submitted over 1 year ago

    0 comments
  • Vite Pricing-Component-With-Toggle

    #accessibility#tailwind-css#typescript#vite

    Tshepiso•110
    Submitted over 1 year ago

    0 comments
  • Ping Coming Soon Landing Page

    #accessibility

    Tshepiso•110
    Submitted over 1 year ago

    0 comments
  • React Easy Bank Landing Page

    #accessibility#react#tailwind-css#typescript

    Tshepiso•110
    Submitted over 1 year ago

    0 comments
  • Responsive Social Proof With User Reviews

    #accessibility#react#tailwind-css

    Tshepiso•110
    Submitted over 1 year ago

    0 comments
View more solutions

Latest comments

  • Caleb Abuul•320
    @Caleb-Abuul
    Submitted over 1 year ago

    Responsive Newsletter using HTML, CSS and JavaScript

    #accessibility#webflow
    1
    Tshepiso•110
    @Gandalf-hash
    Posted over 1 year ago

    Hey Caleb, great design. I noticed some potential improvements for you while reviewing your site: what do you think about adjusting the size of your .container class and modifying the min width on the .form (I would recommend setting the .form width to 100% and a maximum width of your desired size)? Other than that, your design looks good and is accessible on different screen sizes.

  • Kate Dames•250
    @funficient
    Submitted over 1 year ago

    Ping Coming Soon

    1
    Tshepiso•110
    @Gandalf-hash
    Posted over 1 year ago

    Hello Kate, Ek hoop dit gaan goed and what a beatiful layout you have here. However when viewing the layout, I noticed that the input element seems to dominate the container, taking up around 80% of the width, leaving only 20% for the button. This may result in an imbalanced visual hierarchy. Additionally, on smaller devices, it seems that both the button and the input expand to the full width of the container, arranged in a column format.

    To improve this layout and enhance the visual appeal, I would recommend the following adjustments:

    Consider distributing the space more evenly between the input and the button. For example, you could allocate 70/30 of the width to each element respectively to achieve a more balanced appearance.

    Instead of fixed pixel values for the input and button, you might want to use relative units like percentages or viewport units.

    Lastly, Consider using CSS Grid or Flexbox layout for more fine-grained control over the positioning and sizing of your elements.

    I'll make you an example of how you might structure your CSS for equal distribution and responsiveness below:

    .container { display: flex; flex-wrap: wrap; }

    .input-container { flex: 1; max-width: 70%; }

    .button-container { flex: 1; max-width: 30%; }

    You'll just have to adjust the flex value based on the desired distribution. I Also noticed that you're based in South Africa. It's always wonderful to connect with fellow developers, especially when we're all on a learning journey. If you're open to it, I'd be delighted to connect, share insights, and learn together. thank you

Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub