Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
3
Comments
1
P

Scott Rogener

@scottyroges50 points

I am a software engineer with many years of backend experience. I have written highly scalable systems and provided my frontend colleagues the API's needed for them to fetch and save the data of our users. But up until now I was always missing the skills to create my own products end to end.

I’m currently learning...

I decided that now was the time I would finally demystify web/mobile development for myself. I have dabbled with it over the years and have been discouraged by the sheer amount of knowledge I was lacking. But no more! I have found some great resources (like this place!) that is showing me the way.

Latest solutions

  • React + Typescript + CSS Modules + Vite

    #react#typescript#vite

    P
    Scott Rogener•50
    Submitted over 1 year ago

    1 comment
  • Vite + Typescript + React + Styled Components

    #react#styled-components#typescript#vite

    P
    Scott Rogener•50
    Submitted over 1 year ago

    2 comments
  • CSS Flexbox Solution


    P
    Scott Rogener•50
    Submitted over 1 year ago

    1 comment

Latest comments

  • Ruben•210
    @klabruben3
    Submitted over 1 year ago

    Responsive design using media queries

    #react
    1
    P
    Scott Rogener•50
    @scottyroges
    Posted over 1 year ago

    Hi @klabruben3!

    Replying here from your comment on my solution for a different challenge.

    I am by no means a Vite expert and I imagine this is probably not the preferred way for any kind of production site, but the way I got this to work was to do the following:

    1. On your local machine run npm run build. This will take all your react code and compile it to js the browse can understand. It will produce a folder called dist which has the compiled code.
    2. In my vite.config.js I added the base property so that any urls to assets would be relative instead of absolute. (This might not be needed, but it was for me)
    export default defineConfig({
      base: "",
      // other configs
    });
    

    3 In .gitignore I remove the line dist. This allows you to check in the dist folder when you commit you code. The annoying bit here is that to access your code you will need to go to {your handle}.github.io/{repo}/dist/index.html

    Because this isn't a production site I felt this was good enough to get something that I could use for testing and to submit for a solution. But Vite actually has some documentation on how to do this properly using Github actions that is probably worth a read.

    https://vitejs.dev/guide/static-deploy#github-pages

    Hope this help!

    • @scottyroges
    Marked as helpful
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