ReactFoo 2017

A conference on React

About the conference: ReactFoo is a single-day React conference by HasGeek.

We’ll be annoucing the theme shortly

Format

We are inviting proposals for:
Full-length 40 minute talks.
Crisp 15-minute talks.
Hands-on Workshop sessions, 3 and 6 hour duration.

Selection process

Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals. We might contact you to ask if you’d like to repost your content on the official conference blog.

We expect you to submit an outline of your proposed talk – either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.

Selection Process Flowchart

You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.

A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.

There is only one speaker per session. Entry to the conference is free for selected speakers. As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable: two international travel and accommodation grants, three domestic travel and accommodation grants. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer). Speaker travel grants will be given in order of preference to students, women, persons of non-binary genders, and individuals for Asia and Africa first.

Commitment to open source

HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a “sponsored session”.

Important dates:

Deadline for submitting proposals: 23 August 2017

Conference date: 14 September 2017

Contact

For more information about speaking proposals, tickets and sponsorships, contact info@hasgeek.com or call +91 76763 32020.

Please note, we will not evaluate proposals that do not have a slide deck and a video in them.

Hosted by

A community - for and of - front-end engineers to share experiences with ReactJS, performant apps with React, crafting better User Interfaces (UI) with React and GraphQL ecosystem. ReactFoo also discusses design patterns and user experience. more
Siddharth Kshetrapal

Siddharth Kshetrapal

@siddharthkp

The life of CSS and its future with React

Submitted Jun 3, 2017

CSS has come a long way from the inline styles in 1996 to the inline styles in 2017, wait wut?

There’s a lot of controversy around styling in the React ecosystem. Components are a great mental model for UI and have been around for more than you think!

Let’s take a journey through the 20 year rich life of CSS and look at the concepts that shaped user interfaces through the years. Featuring gems like isolation of styles (2007) and lego driven development (2009).

How does the current landscape of styling options in React match up? Come, find out!

Outline

Outline:

  1. A tour of the history of styling - pre CSS in the 90s
  2. Language for styling launched in 1996
  3. As time progresses, we learned how to isolate our styles (~2005)
  4. OOCSS in 2009 - starting thinking in components
  5. BEM, ITCSS, SMACSS, etc. come and establish stateful components
  6. Styling your components the React documentation way.
  7. Early days of JS in CSS - Radium, Aphrodite, etc.
  8. The best approaches right now with styled-components and glamor (All the concepts learned converge here)
  9. What the future might hold.

Requirements

Basic understanding of React

Speaker bio

Why should you let me talk about this/Why am I excited about it?

  1. I am a regular speaker at ReactJS Meetup in Bangalore. Have talked about styling, testing, performance, designing and some more
  2. I make OSS projects for building performant apps easier: cost-of-modules, recreate, reaqt, css-constructor.
  3. I obsess over interfaces, web performance and developer experience.

Links

Slides

https://speakerdeck.com/siddharthkp/styling-react-components

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Sidhartha Chatterjee

Consuming services reliably in Redux without losing your mind

With most apps being built with React these days and Redux being a very popular state management library, have we identified a standard pattern for consuming APIs? more

16 Mar 2017