<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Documentation for a custom widget in Experience Builder Custom Widgets</title>
    <link>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1692496#M687</link>
    <description>&lt;P&gt;I ended up going another route. I created a separate experience for my documentation and using this for my index.html. This way, I can update the help documentation without needing to recompile the experience and deploying it.&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;&amp;lt;!DOCTYPE html&amp;gt;
&amp;lt;html lang="en"&amp;gt;
  &amp;lt;head&amp;gt;
    &amp;lt;meta charset="UTF-8"&amp;gt;
    &amp;lt;meta name="viewport" content="width=device-width, initial-scale=1.0"&amp;gt;
    &amp;lt;meta http-equiv="X-UA-Compatible" content="ie=edge"&amp;gt;
    &amp;lt;title&amp;gt;Spatial Prioritization help&amp;lt;/title&amp;gt;
    &amp;lt;link rel="stylesheet" href="./style.css"&amp;gt;
    &amp;lt;link rel="icon" href="./favicon.ico" type="image/x-icon"&amp;gt;
  &amp;lt;/head&amp;gt;
  &amp;lt;body&amp;gt;
    &amp;lt;main&amp;gt;
        &amp;lt;!-- &amp;lt;h1&amp;gt;Spatial Prioritization help&amp;lt;/h1&amp;gt;   --&amp;gt;
    &amp;lt;/main&amp;gt;
    &amp;lt;script&amp;gt;
      window.location.replace("https://experience.arcgis.com/experience/d577837e4c5f48e8bda663bbd9da03c1/page/Settings");
    &amp;lt;/script&amp;gt;
  &amp;lt;/body&amp;gt;
&amp;lt;/html&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Mar 2026 13:11:46 GMT</pubDate>
    <dc:creator>KenBuja</dc:creator>
    <dc:date>2026-03-25T13:11:46Z</dc:date>
    <item>
      <title>Documentation for a custom widget</title>
      <link>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1681879#M660</link>
      <description>&lt;P&gt;I'm creating a&amp;nbsp;&lt;A href="https://developers.arcgis.com/experience-builder/guide/add-help-to-your-widget/" target="_self"&gt;help&lt;/A&gt; document for the widget that I'm building. I've gotten everything written out in a Word doc that approximates the layout of the standard &lt;A href="https://developers.arcgis.com/experience-builder/guide/map-layers-widget/" target="_self"&gt;widget configuration page&lt;/A&gt;. However, exporting a Word doc makes for a very messy html file.&lt;/P&gt;&lt;P&gt;Is there a template available to match the widget configuration page? If not, what have you done for your custom widget's help?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2026 21:18:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1681879#M660</guid>
      <dc:creator>KenBuja</dc:creator>
      <dc:date>2026-02-03T21:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for a custom widget</title>
      <link>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1682059#M661</link>
      <description>&lt;P&gt;My recommendation is to write your help doc in markdown and then use an opens source library like Pandoc to convert it to HTML:&amp;nbsp;pandoc.org&lt;/P&gt;&lt;P&gt;It's kind of amazing, and I think writing in markup is a lot easier than trying to wrangle a word document. And on the upside, it's more version-control friendly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 16:06:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1682059#M661</guid>
      <dc:creator>JordanCarmona</dc:creator>
      <dc:date>2026-02-04T16:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for a custom widget</title>
      <link>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1689280#M673</link>
      <description>&lt;P&gt;I'll second Jordan's suggestion. I haven't tried to replicate the help page that esri provides, but just having some text that explains how to use and configure your widget is what's most important.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've used a html and css document within my help docs in the past, and it's been fine. My markdown printing widget has a help doc section, feel free to use it as an example.&amp;nbsp;&lt;A href="https://github.com/SunshineLuke90/widgets/tree/master/MDPrint" target="_blank"&gt;https://github.com/SunshineLuke90/widgets/tree/master/MDPrint&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2026 01:00:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1689280#M673</guid>
      <dc:creator>SunshineLuke90</dc:creator>
      <dc:date>2026-03-09T01:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for a custom widget</title>
      <link>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1692496#M687</link>
      <description>&lt;P&gt;I ended up going another route. I created a separate experience for my documentation and using this for my index.html. This way, I can update the help documentation without needing to recompile the experience and deploying it.&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;&amp;lt;!DOCTYPE html&amp;gt;
&amp;lt;html lang="en"&amp;gt;
  &amp;lt;head&amp;gt;
    &amp;lt;meta charset="UTF-8"&amp;gt;
    &amp;lt;meta name="viewport" content="width=device-width, initial-scale=1.0"&amp;gt;
    &amp;lt;meta http-equiv="X-UA-Compatible" content="ie=edge"&amp;gt;
    &amp;lt;title&amp;gt;Spatial Prioritization help&amp;lt;/title&amp;gt;
    &amp;lt;link rel="stylesheet" href="./style.css"&amp;gt;
    &amp;lt;link rel="icon" href="./favicon.ico" type="image/x-icon"&amp;gt;
  &amp;lt;/head&amp;gt;
  &amp;lt;body&amp;gt;
    &amp;lt;main&amp;gt;
        &amp;lt;!-- &amp;lt;h1&amp;gt;Spatial Prioritization help&amp;lt;/h1&amp;gt;   --&amp;gt;
    &amp;lt;/main&amp;gt;
    &amp;lt;script&amp;gt;
      window.location.replace("https://experience.arcgis.com/experience/d577837e4c5f48e8bda663bbd9da03c1/page/Settings");
    &amp;lt;/script&amp;gt;
  &amp;lt;/body&amp;gt;
&amp;lt;/html&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 13:11:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/experience-builder-custom-widgets/documentation-for-a-custom-widget/m-p/1692496#M687</guid>
      <dc:creator>KenBuja</dc:creator>
      <dc:date>2026-03-25T13:11:46Z</dc:date>
    </item>
  </channel>
</rss>

