<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mohamed Shams El-Deen</title>
    <description>The latest articles on DEV Community by Mohamed Shams El-Deen (@moshams272).</description>
    <link>https://dev.to/moshams272</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3980448%2F4ede9d8f-ccd8-411a-9662-f91099031a25.jpeg</url>
      <title>DEV Community: Mohamed Shams El-Deen</title>
      <link>https://dev.to/moshams272</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/moshams272"/>
    <language>en</language>
    <item>
      <title>Redesigning Webpack's Documentation: My GSoC 2026 Journey</title>
      <dc:creator>Mohamed Shams El-Deen</dc:creator>
      <pubDate>Sun, 14 Jun 2026 15:28:55 +0000</pubDate>
      <link>https://dev.to/moshams272/redesigning-webpacks-documentation-my-gsoc-2026-journey-5afd</link>
      <guid>https://dev.to/moshams272/redesigning-webpacks-documentation-my-gsoc-2026-journey-5afd</guid>
      <description>&lt;p&gt;Hello, World! 😅&lt;/p&gt;

&lt;p&gt;I am participating in Google Summer of Code (GSoC) 2026, working with the Webpack to completely redesign it's Documentation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Description
&lt;/h2&gt;

&lt;p&gt;Webpack is an industry-standard JavaScript module bundler used by millions of developers to build modern web applications. It plays a foundational role in today’s frontend ecosystem and is commonly used in projects built with frameworks such as React, Vue, Angular, and many others.&lt;/p&gt;

&lt;h2&gt;
  
  
  Problem
&lt;/h2&gt;

&lt;p&gt;Webpack’s code changes a lot. Every time a developer writes or changes an API, someone from the team has to update the webpack documentation manually.&lt;/p&gt;

&lt;h2&gt;
  
  
  Solution
&lt;/h2&gt;

&lt;p&gt;So, we will build an automated tool using GitHub Actions (that works as CI/CD and update documentation automatically), taking the advantage of the TypeScript compiler (that gives us APIs in &lt;code&gt;types.d.ts&lt;/code&gt;), the &lt;code&gt;typedoc-plugin-markdown&lt;/code&gt; (that converts TypeScript APIs to markdown), and the Node.js tool &lt;code&gt;doc-kit&lt;/code&gt; (that adds links and customized UI).&lt;/p&gt;

&lt;h2&gt;
  
  
  The Roadmap
&lt;/h2&gt;

&lt;p&gt;From the previous few months, I started tackling 5 major milestones:&lt;/p&gt;

&lt;p&gt;M1: Completing the custom TypeDoc theme for accurate Markdown generation.&lt;/p&gt;

&lt;p&gt;M2: Customizing the doc-kit output and UI components to match Webpack's brand.&lt;/p&gt;

&lt;p&gt;M3: Building an end-to-end CI/CD automation pipeline.&lt;/p&gt;

&lt;p&gt;M4: Implementing core pages (Home, Download, Guides).&lt;/p&gt;

&lt;p&gt;M5: Expanding automation to fetch Loader and Plugin READMEs dynamically.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is this series about?
&lt;/h2&gt;

&lt;p&gt;I created this series to document my journey. No boring updates or simple typo fixes. I will write about the complex, interesting, and architecturally significant Pull Requests.&lt;/p&gt;

&lt;p&gt;Wait for the first PR 🔥&lt;/p&gt;

</description>
      <category>googlesummerofcode</category>
      <category>opensource</category>
      <category>webpack</category>
      <category>node</category>
    </item>
  </channel>
</rss>
