About the conference: ReactFoo is a single-day React conference by HasGeek.
We’ll be annoucing the theme shortly
We are inviting proposals for:
Full-length 40 minute talks.
Crisp 15-minute talks.
Hands-on Workshop sessions, 3 and 6 hour duration.
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.
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”.
Deadline for submitting proposals: 23 August 2017
Conference date: 14 September 2017
For more information about speaking proposals, tickets and sponsorships, contact firstname.lastname@example.org or call +91 76763 32020.
Please note, we will not evaluate proposals that do not have a slide deck and a video in them.
An intro to DraftJS, and its immutable data model
This talk shall focus on DraftJS, a rich text editor framework built for React apps; and how it leverages ImmutableJS; for managing the state of an editor in its entirety, with sufficient examples.
The key takeaway insights of the talk include:
- How DraftJS works under the hood — “What goes into”, and the “How to” of building rich text editors for React applications
- How one can use ImmutableJS API, to manage DraftJS’s immutable data structures (apart from the DraftJS’ user-facing API)
- The role of immutability for data models in your own application
The intended audience of the talk are JavaScipt developers who’re acquainted with ReactJS, who are either:
- interested in building rich text editors, or
- interested in learning about ImmutableJS, and the benefits of immutability, and immutable data in their apps
There are multiple paradigms of text editing on the web; WYSIWYG editors have become a defacto standard for writing long form articles
After a brief look at a couple of text editing paradigms; the inconsistent
content-editablebehaviour across browsers, and how the abstraction provided by DraftJS solves the problem…
…the core of the talk would be concentrated on how DraftJS leverages ImmutableJS to maintain the entire state of an editor — the content, the selection state, and a bunch of other things — using an immutable data model
Because of the above fact — the entire editor state being nothing but an Immutable data structure — we can conceive any imaginable state of the editor that we might want to, using the ImmutableJS API …and we shall see the same using examples, and code
Towards the end the talk shall discuss the benefits of immutability, immutable data structures; which one could consider while building data models for an application
Sai is a Developer Evangelist at Hashnode. Apart from interacting with the global Hashnode community, his work is spread across the entire Hashnode’s tech stack. Recently, he has spearheaded the “WYSIWYG editor” project at Hashnode.