You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've long felt that while our home page looks good visually, it does not really convey that much useful information - or maybe at least my take from looking at it so often. I wonder if we can/should use this space to expose some of the content we post in our Medium blog, training tutorials, and/or similar content. I think some of the existing static content could be moved to an About or Get Started page to make room. The "Flyer Fundamentals" for example are nice, but I doubt many visitors to the site really take the time to read and consider those.
If we choose to do this, not sure what the mechanics would be for exposing that content and keeping it up to date, but wanted to just throw this idea out there to see if you all think it's something we might pursue.
The text was updated successfully, but these errors were encountered:
I guessing we can close this given that the blog feed has been incorporated in the new homepage designs. @lboehling do you agree? But I appreciate the work you did on this @maryshak1996 !
I've long felt that while our home page looks good visually, it does not really convey that much useful information - or maybe at least my take from looking at it so often. I wonder if we can/should use this space to expose some of the content we post in our Medium blog, training tutorials, and/or similar content. I think some of the existing static content could be moved to an About or Get Started page to make room. The "Flyer Fundamentals" for example are nice, but I doubt many visitors to the site really take the time to read and consider those.
If we choose to do this, not sure what the mechanics would be for exposing that content and keeping it up to date, but wanted to just throw this idea out there to see if you all think it's something we might pursue.
The text was updated successfully, but these errors were encountered: