DEV Community: Basit Chingisi

You Don't Choose Where You Start. You Choose What You Build.

Basit Chingisi — Sun, 12 Jul 2026 09:55:02 +0000

From Quetta to WordPress: How I Became a Web Developer

I want to share how I got into web development, because it wasn't a straight line, and where I started from shaped how I build.

Where I'm From

I grew up in Quetta, Pakistan, in the Hazara Town and Mariabad neighbourhoods. It's not a place most developers you'll meet online have heard of, and for good reason: it's home to the Hazara community, which has faced targeted violence for over two decades. Growing up, safety wasn't something I could take for granted the way a lot of people can.

I'm not bringing this up for sympathy. I'm bringing it up because it's part of why I approach building things the way I do: carefully, deliberately, and with a lot of drive to make something real out of limited resources.

Getting Into Dev Work

I got my start at Icon Pro Solutions Inc., where I was thrown straight into WordPress development. Not just theming, but the full picture: site structure, SEO, how design and function need to work together, and how content and writing tie it all together.

Alongside development, I picked up Figma and started thinking more seriously about UI/UX, not just how to build a page but why it should be built a certain way. Right now I'm pushing further into building custom WordPress plugins from scratch instead of just working inside existing ones.

Writing Alongside Code

I also write, mostly about AI tools, prompts, and the same design instincts that carry over from building websites to writing clear sentences. It turns out structuring a good blog post and structuring a good page aren't that different: think clearly, organize it well, ship it.

What I've Built

Everything from that first job eventually pushed me to build my own thing. That's Slaytic, a web dev and design studio, and alongside it, Slaytic Converter (tools.slaytic.com), a free browser-based toolkit with 230+ tools for PDF, image, video, and file conversion.

The whole thing runs client-side. No server uploads, no third-party file handling. It started because I wanted a real answer to "why do I have to upload my file to some random site to convert it," and it grew from there into a full multi-tool platform built on Next.js 14, TypeScript, and Tailwind, deployed for free on Vercel.

Why I'm Writing This

I'm posting this partly to introduce myself to the Dev.to community, and partly as a reminder to myself: where you start doesn't decide where you end up. You learn what you can, take the opportunities you get, and keep shipping.

Still building. Just getting started.

I spent months building a browser-based toolkit with 238 utilities. Looking for technical feedback.

Basit Chingisi — Sat, 11 Jul 2026 20:19:37 +0000

Hi everyone,

I've been working on a solo project that's grown into a collection of 238 browser-based utilities.

The idea was to build a place where people can complete common tasks without installing software, while keeping privacy in mind by processing data locally whenever possible.

The toolkit currently includes:

PDF utilities
Image tools
AI tools
JSON, XML, CSV, and developer utilities
SEO tools
Text and writing tools
Color and design tools
Converters and calculators
Security and encoding tools
And several other categories

I'm not posting this to market it. I'm looking for feedback from other developers.

I'd appreciate any thoughts on:

Performance and load times
UI/UX
Mobile responsiveness
Browser compatibility
Accessibility
Bugs or edge cases
Features that should be added or improved

The project is available here:
https://tools.slaytic.com/

I'd really appreciate constructive criticism. If you spot something that could be built better, please let me know. I'm continuously improving the project and would rather hear honest feedback than compliments.

Thanks for taking a look!

Building a Free Online PDF Converter with Next.js: What I Learned

Basit Chingisi — Fri, 26 Jun 2026 07:28:13 +0000

PDF files are everywhere. Developers, students, businesses, and creators use them every day for documents, reports, invoices, and forms.

However, working with PDFs on the web is not always simple. Many users still need to download software just to convert a file from PDF to Word, JPG, or another format.

I wanted to solve this problem by building a free online PDF converter that works directly in the browser.

The goal was simple:

Create a fast, easy-to-use tool where users can upload a PDF, convert it, and download the result without installing anything.

Why Build a Browser-Based PDF Tool?

Traditional PDF software often comes with problems:

Requires installation
Takes up storage space
Can be slow on older devices
Some tools require paid subscriptions

A web-based solution removes these barriers.

With modern web technologies, developers can now build powerful file processing tools that run smoothly in the browser.

I wanted to solve this problem by building a free online PDF converter that works directly in the browser.

The tool is available on Slaytic Tools:

The Technology Stack

For this project, I used a modern web stack:

Next.js for the application framework
React for the user interface
JavaScript for functionality
Browser APIs for file handling
Server-side processing where needed

Next.js makes it easier to create fast pages, manage routing, and optimize performance.

Handling PDF Files on the Web

PDF conversion is challenging because PDFs are not just simple text files.

A PDF can contain:

Text
Images
Fonts
Layout information
Metadata
Embedded objects

A good converter needs to preserve the original structure as much as possible.

The workflow usually looks like this:

User uploads a PDF file
The application validates the file
The conversion process starts
The converted file is generated
The user downloads the result

Keeping this process simple improves the user experience.

Important Performance Considerations

File tools need to feel fast.

Some improvements that matter:

Client-Side Processing

Whenever possible, processing files directly in the browser reduces server load and improves privacy.

Users feel more comfortable when their files are not unnecessarily uploaded.

File Size Limits

Large files can slow down browsers and servers.

Adding clear file size limits helps prevent performance problems.

Loading States

Users should always know what is happening.

A progress indicator or loading message helps avoid confusion during conversion.

Security Considerations

File upload tools need proper security practices.

Important things to consider:

Validate uploaded file types
Limit file sizes
Remove temporary files after processing
Prevent malicious uploads
Avoid storing user files unnecessarily

Security is especially important when handling private documents.

Making the Tool User-Friendly

A good tool is not only about technology.

The user experience matters.

A simple flow works best:

Upload file
Choose conversion type
Convert
Download

No complicated settings. No unnecessary steps.

SEO and Discoverability for Tool Websites

Building the tool is only one part.

People need to find it.

For a PDF converter, useful content can include:

How to convert PDF to Word
How to reduce PDF size
Best free PDF tools
PDF tips and tutorials

Helpful content allows search engines and AI systems to better understand what the tool does.

What I Learned Building a PDF Tool

Creating online tools looks simple from the outside, but there are many small details involved.

The biggest lessons:

Performance matters
Simplicity improves conversions
Security cannot be ignored
Good content helps users discover the product

A useful tool solves a real problem.

That is the main reason I built Slaytic Tools, a collection of free online utilities designed to make everyday tasks easier.

If you are building a web-based tool, focus on solving one clear problem and make the experience as simple as possible.

webdevelopment #nextjs #javascript #pdf #opensource

Frontend Basics: Mastering HTML and CSS

Basit Chingisi — Mon, 30 Dec 2024 07:13:12 +0000

HTML, short for HyperText Markup Language, is the foundation of every website. It structures and organizes the layout of a webpage, acting as the building block for all web creations. On the other hand, CSS (Cascading Style Sheets) focuses on styling, making web pages look attractive and visually appealing. While they serve different purposes, HTML and CSS work closely together and are often used hand-in-hand.

Think of it like this: HTML builds the skeleton of a webpage, while CSS adds the flesh, giving it life and beauty. HTML handles the structure and content, while CSS takes care of the design and layout. However, HTML can be a bit rigid when it comes to making changes, whereas CSS allows for more flexibility, making it easier to tweak and adjust styles.

Because of their interdependence, mastering both HTML and CSS is essential for creating great websites. However, as web development evolves, many programmers are moving towards more dynamic tools like React JS. React is a modern frontend framework that allows for advanced structuring and interactive designs. While it still incorporates some HTML elements, it’s not as reliant on HTML as CSS is.

Having worked on projects using only HTML, CSS, and a bit of JavaScript, I’m excited about transitioning to React JS. I look forward to exploring its capabilities further during HNG’s internship 11!