GrabDavid KhuProblem & solution
Facilitating Docs-as-Code implementation for users unfamiliar with Markdown
Summary
Grab introduced a rich-text, WYSIWYG editor in its TechDocs portal to help non-engineering contributors work within a Docs-as-Code process despite limited familiarity with Markdown and GitLab. The editor keeps GitLab as the central storage system, uses Lexical to import and export Markdown, and supports page reordering, renaming, deletion, formatting, diagrams, and switching between normal and Markdown views. Three user journeys cover editing existing TechDocs and creating stand-alone or entity-linked documentation, with GitLab OAuth2, merge-request creation, repository access checks, and scheduler-based entity-catalog registration after merges. A phased rollout added drafts, image uploads, diagram integrations, concurrent-session visibility, and live preview, while pending-MR displays and conflict-resolution tools address collaboration risks.
Context
Non-engineering contributors responsible for engineering-facing documents found Markdown syntax, GitLab workflows, and tools such as MkDocs and entity catalogs difficult to use. This created a barrier to adopting Docs-as-Code beyond engineering teams.
Approach / What changed
The TechDocs editor provides a WYSIWYG interface over a Git workflow while retaining GitLab as central storage. It uses Lexical for Markdown transformation, integrates GitLab OAuth2 and merge requests, provides live preview and editing safeguards, and was delivered through a phased rollout covering existing and newly created documentation.
Takeaways
Lexical was selected over Markdown-based tools such as Toast UI because its extensibility supports features including autocomplete and non-standard Markdown elements such as Kroki diagrams.
The editor creates or updates GitLab merge requests, checks repository access, and uses scheduler jobs to register or refresh entity catalogs after merges.
Live preview renders the document beside the editor so contributors can verify images, tables, diagrams, and formatting, although larger documents and external resources can create performance delays.
Source and freshness
- Source
- engineering.grab.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.