<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Hemp Trading Post | rickymyers | Activity</title>
	<link>https://www.hemptradingpost.com/members/rickymyers/activity/</link>
	<atom:link href="https://www.hemptradingpost.com/members/rickymyers/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for rickymyers.</description>
	<lastBuildDate>Mon, 21 Sep 2026 19:03:03 -0700</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">86caa94d5f5ba9034736075ce8aa7221</guid>
				<title>rickymyers started the topic What makes an author website design feel truly useful to readers? in the forum Growing Hemp</title>
				<link>https://www.hemptradingpost.com/forums/topic/what-makes-an-author-website-design-feel-truly-useful-to-readers/</link>
				<pubDate>Tue, 18 Aug 2026 19:36:43 -0700</pubDate>

									<content:encoded><![CDATA[<p>I’m planning my first <a href="https://vermontbookpublishers.com/author-website-design" rel="nofollow ugc">author website design</a> and want honest community input. What pages or features do readers actually find helpful, beyond the usual bio and book list? Should an author focus more on a clean reading experience, newsletter signup, blog, or something else? What mistakes should I avoid? I’d appreciate serious suggestions based on&hellip;<span class="activity-read-more" id="activity-read-more-434328"><a href="https://www.hemptradingpost.com/forums/topic/what-makes-an-author-website-design-feel-truly-useful-to-readers/" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>