Building technical documentation as a product at scale

Oct 2018

22 Mon

23 Tue

24 Wed

25 Thu

26 Fri 09:30 AM – 05:30 PM IST

27 Sat 09:45 AM – 05:05 PM IST

28 Sun

Make a submission

NIMHANS Convention Centre, Bangalore

Theme

Meta Refresh 2018 will cover four primary topics:

User research and design -- how user research is carried out and translated into design (whether engineering or designing user interactions).
Design systems -- how collaborations are being enabled between engineers and designers. Here, we are looking for case studies.
Tooling for design systems -- share your experiences (and evaluations) of open source tools for design systems.
Why the boundaries between UI and UX are not the way to proceed for design and designers.

Criteria to submit a conference proposal

You must be a practising web developer or designer, and must be able to show how your own work has advanced the state of the web in the past year. You are expected to present original work that your peers — this event’s audience — recognise as being notable enough to deserve a stage. If you are excited about someone’s work and believe it deserves wider recognition, we recommend you contact them and ask them to submit a proposal.

Guidelines for submission

Every proposal MUST be accompanied by:

A two minute preview video where the proposer gives an elevator pitch about the talk.
Detailed outline of the talk – either in the form of draft slides, mind map and/or textual description.
If you are proposing to speak on a topic where the code is not open-sourced yet, the editorial panel will consider your proposal only if the code is made open-source at least three weeks before the conference.

Without the above information, your proposal will not be considered for review.

If you are submitting a Workshop Proposal, you must clearly state:

Background knowledge that participants must possess in order to attend your workshop.
Details and links to software / packages which participants must install before coming to the workshop.
Laptop configuration.
Links to background reading material and GitHub repos.
Duration of the workshop.
Maximum number of participants who can attend your workshop.
Instructor’s past experience with conducting workshops.

There is only one speaker per session. Workshops can have more two or more instructors.

Entry is free for confirmed speakers.

If you are an outstation speaker, HasGeek will do its best to provide a grant that covers part of your travel and accommodation expenses in Bangalore, subject to budgetary constraints.

Format

The 2018 edition is a multi-track event with the following session formats:

Full length talks of 40 minutes
Crisp talk of 15 minutes
Workshops of 3-6 hours
Off the Record sessions (OTR)

Important Dates

Deadline for submitting proposals: TBD
Conference date: 26-27 October, 2018

Venue

Meta Refresh will be held at the NIMHANS Convention Center, Bangalore

Contact

For more information about speaking proposals, tickets and sponsorships, write to [info@hasgeek.com](mail to:info@hasgeek.com) or call +9107676332020

Hosted by

Meta Refresh

Meta Refresh is an umbrella forum for conversations about different aspects of design and product including: UX and interaction design CMS, content management, publishing and content marketing Information architecture more

All submissions

Previous Next

This submission has been added to the schedule

Building technical documentation as a product at scale

Submitted Oct 3, 2018

Section: Full talk Technical level: Beginner

In the real world, when we buy a product, it comes with a quick guide or some other form of documents which help you get going with the product. Without these documents, we’ll have to learn how to use the product leveraging solely on the ‘trial and error’ method — which is not a pleasant user experience at all.

We support and build data products for more than 15 internal teams. Our target audience includes product managers, developers, operation managers, and business analysts. Hence:

We faced problems in communicating what the Data team is working on and what is next in our product lineup.
It was getting harder to make clear that there is something missing in their life and that is our product/service.
We found ourselves handling support requests on a daily basis, consuming a lot of our core development time.
Worst of all, for developers, data engineering became equivalent to Firehose (data consumption toolkit). For business analysts, we were Dagger team (data aggregation toolkit), for OMS teams we were fronting team.