Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Responsive time tracking using React js & styled components

Ven Gallardo•90
@Gepeet
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I got a bit confused with my deployment to netlify.

Any other work flow you might recommend?

I made two deployments that didn't worked for me:

  1. -made a repo in github
  • inside vscode terminal, i typed npx create-react-app fem-title
  • deploy to netlify using the github repo.
  • problem was it didn't deploy and because it could not see the page.
    • inside git bash I create-react-app fem-title
  • then I created a new repo from github website
  • after that I copied the lines on how to add a git repo to github.
  • problem was it didn't copy the file to github. It says I have another origin that is using it.

What made me deploy it... -create new github repo

  • inside vscode(with the new repo folder), npx create-react...
  • then npm run build
  • copied the build folder to netlify's create new site by drag and drop files. -then it worked.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fidel Lim•2,775
    @fidellim
    Posted almost 4 years ago

    Hi Ven,

    What you can do if you are deploying the app from GitHub is setting the base directory to fem-cha. You can do this in Netlify once you have created the site but failed. Go to Site Settings > Build & Deploy. Then on Build Settings, check Base Directory and change it. You can have a look at this link to have a better understanding. I couldn't put images here so the link I sent you will help.

    What you did is actually good too. However, the drawback of this is that you will have to keep building the file and update it to Netlify. With GitHub, you won't have to worry about this. For every git push you do. Netlify will be updated that your repository has been updated and your sit will be updated after a few mins.

    I hope it helps. :)

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

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

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub