↵

React based Portfolios

over 6 years ago from Stephen Kempin, Front End Developer & Designer

  • Art VandelayArt Vandelay, over 6 years ago

    I'd advise against unless you understand the fallbacks.

    Biggest one being SEO/URL since you may not enable actual page refreshes or server-side rendering.

    Most folks say "oh who cares about SEO!" Which is generally true but when none of your page actually changes it can have drastic effects on how your work proliferates throughout the web.

    1 point
    • Darrell HanleyDarrell Hanley, over 6 years ago

      You could just create the project as an isomorphic react project, or if you're using this with some cms, you could just have the backend pre populate the relevant meta tags for sites like Facebook..

      0 points
      • Art VandelayArt Vandelay, over 6 years ago

        All this to say we're recreating something servers and CMS' already do just to write stuff in the "flavor of the week" JS framework.

        Not knocking your comment. Just find it funny when folks end up using something like WP with the API just because they want to bloat shit in a JS framework where 3 templates and out-of-the-box server-side rendering would've sufficed right from WP

        0 points
        • Darrell HanleyDarrell Hanley, over 6 years ago

          You're relying on server side rendering for all of your subsequent pageviews. Using React or some other front end library with its own routing will ultimately be faster for the user to load. It also allows for seamless transitions between pages.

          React is also far from being a flavor of the week JS library. It's shown incredible growth over the last few years and represents a fundamental ideological shift in how developers are thinking about Javascript and its relationship with the browser. Perhaps you should spend some time reading about React and its merits.

          1 point
          • Art VandelayArt Vandelay, over 6 years ago

            So first, there is an assumption that I haven't read up on React. False. By that merit you sound like a dickbag. But its cool, not judging.

            Second, the point I'm making is the subsequent page loads still get data from..............the server. So while yes, the page loads are fast, there is still a request to the server. Unless we're loading all subsequent page data in state? Which seems like overkill.

            And if that is the basis of an argument for React. Server (and page) caching on subsequent visits is also - fast.

            Using React just to use it is totally fine. Using it assuming its "what you're supposed to do" is terrible. Using a JS framework meant for state, etc for an entirely, otherwise, static website seems overkill. Over-engineering.

            But as I mentioned, if the other of the post wants to try React. A portfolio is a great use case.

            0 points
    • Adam Kirkwood, over 6 years ago

      I think SEO and semantic URLs are not as much of a problem now especially with solutions such as https://github.com/zeit/next.js

      I plan to rebuild my portfolio using React hosted on Zeit.co soon.

      2 points
      • Dominik LevitskyDominik Levitsky, over 6 years ago

        We used Zeit in our recent project and it turned out to be really amazing! Really easy to use and no unneeded features. Tried a lot of different alternatives before that, but Zeit won the competition.

        2 points
    • Stephen Kempin, over 6 years ago

      I believed SEO was no longer an issue with server side rendering and Google's ability to execute JS today?

      0 points
      • Art VandelayArt Vandelay, over 6 years ago

        You may be right! Last I checked it said it was asynch so if you're data wasn't there, then it keeps going. But I am probably wrong.

        0 points