front end developer [react and rails a +]

  • Are you an Engineer looking to revolutionize the way people innovate and build software?
  • Do you want to create something that will change the way people think about innovation, and work with cutting-edge visualization, collaboration, and social ideation technologies at the same time?
  • was founded by a proven team of Silicon Valley veterans whose last two businesses were acquired by well-known public companies.
  • to link their brilliant strategy to their team’s work and create visual roadmaps.
  • If you have the right background, we will quickly follow up with you.

As a Front End Developer at Aha!, you will have an excellent opportunity to join a breakthrough and profitable company that is growing fast.
Continue reading “front end developer [react and rails a +]”

Modern static site generation

  • There is this function called Server Side Rendering where you can produce static HTML content directly from a tree of React.js components.
  • At the time of reading this, this site will already be served by GitHub pages and the content you will see once you view the source it’s been generated by Gatsby.js.
  • Here’s my list:

    At the time that I started following them, all of them were in a very early stage and none of them could generate my site’s content the way I wanted and in the same way as my previous one so to not lose paths and certain functionalities.

  • Think of when you are caching the home page of a WordPress powered site and you are serving the cached content to every visitor.
  • Imagine that instead of having memcached caching your HTML in front of your WordPress site, you trigger a hook each time your database changes that will re-generate the frontend using Gatsby.

In this post, I will talk about static site generators. How they have evolved and why I switched from a Ghost powered site to Gatsby.js, a modern static site generator.
Continue reading “Modern static site generation”

Extracting Logic from React Components

Extracting Logic from #ReactJS Components:  by @Jack_Franklin #Javascript

  • Right now to test formatting of amounts I have to create and mount a React component, but I should be able to just call that function and check the result.
  • Let’s create which will house the function that is currently in our component.
  • To test this, we can replace the body of ’s so that it just calls the new function from our module:

    Notice that I’ve still left the function defined on ; when pulling code apart like this you should do it in small steps; doing it like this decreases the chance of inadvertently breaking the code and also makes it easier to retrace your steps if something does go wrong.

  • Sure, the function is very straightforward for now, but as it grows we can now test it very easily without any need to fire up a React component to do so.
  • By looking through our components and finding standalone functions that we can pull out, we’ve greatly simplified our component whilst increasing our test coverage and clarity of our application greatly.

In the previous screencast we took a React component that was doing too much and refactored it, splitting it into two components that are easier to maintain, use and test. Although I’d recommend watching that video first, you don’t need to have watched it to read this blog post. You can find all the code on GitHub if you’d like to run it locally.
Continue reading “Extracting Logic from React Components”

How to Lazy Load features using React and Webpack – codeburst

How to Lazy Load features using #ReactJS and #Webpack:  by @notgiorgi

  • We don’t want to load our app’s whole component library when user enters our site.
  • We need to load components on demand, and after initial load, cache them in the memory for further use.Also we want lazy loading logic to be separated from the component implementations.We can solve this problem using Webpack import functions and Higher order components.Our HOC takes two arguments, second is the component which will be shown while component is loading, because we don’t want our users to be looking at the blank screen.First argument is the getComponent function, this is where we call Webpack import:One might ask why we don’t pass the path directly to the HOC.
  • E.g. if we do something like this: Webpack will bundle all the files in the .
  • If we pass the whole string directly import(‘.
  • But we cannot do this: path = import(path), because Webpack won’t know which files to consider, it won’t have any pattern to match files against.So our HOC, calls import before it mounts and displays the spinner while component is being downloaded.This way we can easily convert any statically imported component into lazy-loadable one.

In the modern web, every kilobyte matters. We don’t want to load our app’s whole component library when user enters our site. We need to load components on demand, and after initial load, cache them…
Continue reading “How to Lazy Load features using React and Webpack – codeburst”

The New Kid on the Block

Meet @mxstrbng - a new member of our #NeosCMS team working on the #reactjs UI:

  • After that I attended the Neos Barcamp, the other two sprints since then and the Neos Conference.
  • All this was much fun especially to see the development of the project not only from a remote point of view but also to contribute to the React UI development.
  • My focus in the Neos project is clearly on the React UI rewrite which we plan to release at the end of the year, but I’m also fixing some little things in Neos or Flow if they catch my eye.
  • I’m not only interested in React, Javascript and PHP but in computer science in general and different kind of programming languages.
  • So, this is me 🙂

    if you are not sure if you want to join the development of Neos and Flow, also as a non programmer, you should join a sprint and see what’s going on there!

Hi I’m Max, 27 and I  became a Neos team member on the 5th July.
Continue reading “The New Kid on the Block”

Extracting Logic from React Components

  • Right now to test formatting of amounts I have to create and mount a React component, but I should be able to just call that function and check the result.
  • Let’s create which will house the function that is currently in our component.
  • To test this, we can replace the body of ’s so that it just calls the new function from our module:

    Notice that I’ve still left the function defined on ; when pulling code apart like this you should do it in small steps; doing it like this decreases the chance of inadvertently breaking the code and also makes it easier to retrace your steps if something does go wrong.

  • Sure, the function is very straightforward for now, but as it grows we can now test it very easily without any need to fire up a React component to do so.
  • By looking through our components and finding standalone functions that we can pull out, we’ve greatly simplified our component whilst increasing our test coverage and clarity of our application greatly.

In the previous screencast we took a React component that was doing too much and refactored it, splitting it into two components that are easier to maintain, use and test. Although I’d recommend watching that video first, you don’t need to have watched it to read this blog post. You can find all the code on GitHub if you’d like to run it locally.
Continue reading “Extracting Logic from React Components”

How to Lazy Load features using React and Webpack – codeburst

  • We don’t want to load our app’s whole component library when user enters our site.
  • We need to load components on demand, and after initial load, cache them in the memory for further use.Also we want lazy loading logic to be separated from the component implementations.We can solve this problem using Webpack import functions and Higher order components.Our HOC takes two arguments, second is the component which will be shown while component is loading, because we don’t want our users to be looking at the blank screen.First argument is the getComponent function, this is where we call Webpack import:One might ask why we don’t pass the path directly to the HOC.
  • E.g. if we do something like this: Webpack will bundle all the files in the .
  • If we pass the whole string directly import(‘.
  • But we cannot do this: path = import(path), because Webpack won’t know which files to consider, it won’t have any pattern to match files against.So our HOC, calls import before it mounts and displays the spinner while component is being downloaded.This way we can easily convert any statically imported component into lazy-loadable one.

In the modern web, every kilobyte matters. We don’t want to load our app’s whole component library when user enters our site. We need to load components on demand, and after initial load, cache them…
Continue reading “How to Lazy Load features using React and Webpack – codeburst”