<?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>idea Improved Navigation of API Documentation in ArcGIS API for Python Ideas</title>
    <link>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idi-p/1406103</link>
    <description>&lt;P&gt;Today, I found myself down the rabbit hole trying to decipher the documentation for Feature, FeatureLayer, and FeatureLayerCollection in the API for Python.&amp;nbsp; Navigating between each of the three is workable, because I have bookmarks on the left to take me right to the top of each (marked &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;A&lt;/STRONG&gt;&lt;/FONT&gt; in the screenshot).&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MErikReedAugusta_1-1712267627023.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/100138i6874280A362C7940/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MErikReedAugusta_1-1712267627023.png" alt="MErikReedAugusta_1-1712267627023.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Problem:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;All of the contents of a given module share the same page, without break.&amp;nbsp; The bookmarks will take you to the header of the class, but the headers for properties &amp;amp; methods below that are a bit of a mess.&lt;/P&gt;&lt;P&gt;Each of the properties &amp;amp; methods (marked &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;B&lt;/STRONG&gt;&lt;/FONT&gt; in the screenshot) are immediately followed by their description and sometimes a lengthy example.&amp;nbsp; Some of those examples are actually longer than the screen area, to boot, so you can be looking at the middle of an example and not even know which method it or class it belongs to.&lt;/P&gt;&lt;P&gt;All this together means that it's easy to get lost digging through the properties and constantly be scrolling frantically up &amp;amp; down to understand the context of what you're reading.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Solution(s):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 1:&lt;/STRONG&gt; Each of these classes gets their own subpage.&amp;nbsp; You can't scroll from Feature to FeatureLayer in one continuous go; you'll have to click somewhere to navigate to the page for FeatureLayer if you want to read it.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 2:&lt;/STRONG&gt; Add another level of depth to the navigation that lists the heading level used by &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;B&lt;/STRONG&gt;&lt;/FONT&gt;; i.e., all the properties &amp;amp; methods.&amp;nbsp; This is what the horribly-sketched arrows at &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;C&lt;/STRONG&gt;&lt;/FONT&gt; are indicating.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 3:&lt;/STRONG&gt; Add a table-of-contents sort of section to the top of every class that&amp;nbsp;&lt;EM&gt;just&lt;/EM&gt; lists the property or function, but without any of the descriptions or examples.&amp;nbsp; This can then hyperlink to lower on the page where you can read more details.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Personally, my preference is&amp;nbsp;&lt;STRONG&gt;Option 2&lt;/STRONG&gt;, but I could live with any of these three.&amp;nbsp; But the current layout is unnecessarily abstruse, especially to someone trying to look something up for the first time, without knowing what the property is called.&amp;nbsp; And frankly, it's equally terrible for someone who knows more or less what they're looking for, but needs to refresh themselves on some implementation detail.&lt;/P&gt;</description>
    <pubDate>Thu, 04 Apr 2024 22:05:16 GMT</pubDate>
    <dc:creator>MErikReedAugusta</dc:creator>
    <dc:date>2024-04-04T22:05:16Z</dc:date>
    <item>
      <title>Improved Navigation of API Documentation</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idi-p/1406103</link>
      <description>&lt;P&gt;Today, I found myself down the rabbit hole trying to decipher the documentation for Feature, FeatureLayer, and FeatureLayerCollection in the API for Python.&amp;nbsp; Navigating between each of the three is workable, because I have bookmarks on the left to take me right to the top of each (marked &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;A&lt;/STRONG&gt;&lt;/FONT&gt; in the screenshot).&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MErikReedAugusta_1-1712267627023.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/100138i6874280A362C7940/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MErikReedAugusta_1-1712267627023.png" alt="MErikReedAugusta_1-1712267627023.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Problem:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;All of the contents of a given module share the same page, without break.&amp;nbsp; The bookmarks will take you to the header of the class, but the headers for properties &amp;amp; methods below that are a bit of a mess.&lt;/P&gt;&lt;P&gt;Each of the properties &amp;amp; methods (marked &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;B&lt;/STRONG&gt;&lt;/FONT&gt; in the screenshot) are immediately followed by their description and sometimes a lengthy example.&amp;nbsp; Some of those examples are actually longer than the screen area, to boot, so you can be looking at the middle of an example and not even know which method it or class it belongs to.&lt;/P&gt;&lt;P&gt;All this together means that it's easy to get lost digging through the properties and constantly be scrolling frantically up &amp;amp; down to understand the context of what you're reading.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Solution(s):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 1:&lt;/STRONG&gt; Each of these classes gets their own subpage.&amp;nbsp; You can't scroll from Feature to FeatureLayer in one continuous go; you'll have to click somewhere to navigate to the page for FeatureLayer if you want to read it.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 2:&lt;/STRONG&gt; Add another level of depth to the navigation that lists the heading level used by &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;B&lt;/STRONG&gt;&lt;/FONT&gt;; i.e., all the properties &amp;amp; methods.&amp;nbsp; This is what the horribly-sketched arrows at &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;C&lt;/STRONG&gt;&lt;/FONT&gt; are indicating.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 3:&lt;/STRONG&gt; Add a table-of-contents sort of section to the top of every class that&amp;nbsp;&lt;EM&gt;just&lt;/EM&gt; lists the property or function, but without any of the descriptions or examples.&amp;nbsp; This can then hyperlink to lower on the page where you can read more details.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Personally, my preference is&amp;nbsp;&lt;STRONG&gt;Option 2&lt;/STRONG&gt;, but I could live with any of these three.&amp;nbsp; But the current layout is unnecessarily abstruse, especially to someone trying to look something up for the first time, without knowing what the property is called.&amp;nbsp; And frankly, it's equally terrible for someone who knows more or less what they're looking for, but needs to refresh themselves on some implementation detail.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2024 22:05:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idi-p/1406103</guid>
      <dc:creator>MErikReedAugusta</dc:creator>
      <dc:date>2024-04-04T22:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: Improved Navigation of API Documentation</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idc-p/1406226#M94</link>
      <description>&lt;P&gt;Adding my +1 to this. I have the same frustrations using the API docs.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2024 07:56:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idc-p/1406226#M94</guid>
      <dc:creator>A_Schwab</dc:creator>
      <dc:date>2024-04-05T07:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: Improved Navigation of API Documentation</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idc-p/1410614#M95</link>
      <description>&lt;P&gt;We've been asking for better documentation of that API since it's inception :')&lt;BR /&gt;&lt;BR /&gt;I wish it looked more like the Javascript API documentation, but you get a +1 from me!&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 20:47:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idc-p/1410614#M95</guid>
      <dc:creator>Raul</dc:creator>
      <dc:date>2024-04-16T20:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: Improved Navigation of API Documentation</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idc-p/1597415#M144</link>
      <description>&lt;P&gt;Yes please!&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2025 11:28:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-ideas/improved-navigation-of-api-documentation/idc-p/1597415#M144</guid>
      <dc:creator>RichardHowe</dc:creator>
      <dc:date>2025-03-20T11:28:47Z</dc:date>
    </item>
  </channel>
</rss>

