Skip to content

Custom development

When customers cannot find an answer, they email support, and your team answers the same questions every week. A good knowledge base fixes that, but only if articles are easy to find, clearly organised and simple for your team to update. I build help centres, product documentation and API reference sites with strong search, clear navigation and an editing workflow that keeps content current.

Knowledge base and documentation sites by Harsh Prajapati, freelance web developer in Ahmedabad, Gujarat, India, working with clients across India and worldwide.

Sound familiar?

  • Support answers the same questions again and again
  • Your documentation is spread across PDFs, emails and old pages
  • Developers struggle to use your API because the docs are thin or out of date

What changes

  • 01A help centre customers can search and browse
  • 02Documentation your team can update easily
  • 03API docs developers can follow on their own

What you get

  • Planning the structure: categories, article types and navigation
  • Help centres on WordPress, a headless CMS or a docs framework
  • Technical and product documentation with versioning where needed
  • API reference built from your OpenAPI file, with code examples
  • Fast search across every article, with filters by product or version
  • Article templates, related articles and feedback buttons
  • Editing workflow with drafts, reviews and roles
  • Login-protected sections for customers or partners
  • Moving existing articles from Zendesk, Freshdesk, Notion or old pages

A great fit for

  • SaaS and software companies
  • Businesses with busy support inboxes
  • Teams publishing an API for partners or developers

Usual stack

  • WordPress
  • Docusaurus
  • Next.js
  • Markdown
  • OpenAPI
  • Algolia

How it works

  1. 1Free call
  2. 2Fixed written quote
  3. 3Weekly demos
  4. 4Launch and handover
See the full process

Guides

Read before you decide

FAQs

It depends on who writes the articles. WordPress or a headless CMS suits support teams who want a visual editor. A docs framework such as Docusaurus suits developer documentation kept in Git. I recommend one after looking at your content and team.

Yes. I generate a readable API reference from your OpenAPI or Swagger file and add guides, authentication steps and code examples around it, so developers can get started without asking you.

Yes. I export articles, images and categories, rebuild them in the new site and redirect the old URLs where you control them, so links in old emails and search results still work.

Yes. Some sections can be public while others need a customer or partner login, and I set the access rules so private articles stay out of public search.

I work at USD 10 to 15 an hour, or for a fixed written quote agreed before work starts. After a short call and a look at your current site or brief, you get the scope, the price and the timeline in writing. Any software, hosting or service subscriptions are billed to you directly by the provider, every account stays in your name, and I list them in the quote so there are no surprises.

Other services

Start a project

Tell me what you need in four quick steps. I reply personally within one working day with questions or a clear next step.

Reply within 1 working dayUsually much sooner.

Free first call30 minutes, no pressure, no jargon.

Written fixed quoteScope and price agreed before work starts.

  1. 1current
  2. 2to do
  3. 3to do
  4. 4to do

Step 1 of 4

What are we building?

Project type

Prefer chat? Message me on WhatsApp. I usually reply within a day.