These third-party cookies may be set by Vimeo in connection with embedded videos, for purposes such as (without limitation) managing video settings, storing video preferences, providing certain functionality (such as allowing you to pause a video at a particular point), associating your video viewing and other activity with your Vimeo account (if you have one), showing you advertising, and/or compiling user analytics data. The cookies whose names begin with "_ga" and "_ut" are associated with Google Analytics (which is subject to the Google Privacy Policy); the ones whose names begin with "_ceg" are associated with the Crazy Egg web analytics service (which is subject to the Crazy Egg Privacy Policy); the ones that begin with "optimizely" are associated with the Optimizely digital experience optimization service (which is subject to the Optimizely Privacy Policy); and the ones beginning with "adsense" or listed in all caps are associated with Google AdSense and/or other Google advertising services (which are also subject to the Google Privacy Policy). The Vimeo Cookie Policy does not currently disclose the normal durations of their cookies, but some are persistent cookies that may remain in your browser for as long as your individual browser settings permit; some Google Analytics cookies can persist for up to two years. For more information about how Vimeo uses the information they collect, see the Vimeo Privacy Policy. (Vimeo is a trademark of Vimeo, registered in the U.S. and other countries. AdSense and Google Analytics are trademarks of Google LLC; Google is a registered trademark of Google LLC. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a trademark of Optimizely, Inc., registered in the United States, EU, and elsewhere.)
_abexps, aka_debug, clips, continuous_play_v3, embed_preferences, has_logged_in, is_logged_in, jsessionID, player, search_click_position, Searchtoken, stats_end_date, stats_start_date, sst_aid, uid, v6f, vimeo, vuid, _ga, _gads, _utma, _utmb, _utmc, _utmv, _utmz,_ceg.s, _ceg.u, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, APISID, GAPS, HSID, NID, N_T, PREF, SAPISID, SID, SNID, SSID
Aaron, the freebie WordPress template that I’ve had the most success with is Twenty Fourteen. It has a magazine-style front page that can highlight older content in addition to the latest postings.
The problem with the non-premium templates is that they lack some really useful features. If up-front cost is the big barrier, I’d be happy to make a donation to help you get there. I imagine others would as well.
You deserve to have a website template that matches the caliber of your writing and makes production easier.
I’m wary of the annual WordPress default themes because they have quite a laissez-faire attitude toward the use of externally served third-party content, in particularly Google Fonts. As I noted, I’m particularly nervous about themes that use external hosted libraries for scripts or icons, which are hard to get rid of.
I’m reluctant to buy a premium theme for a couple of reasons, although the cost of doing so would probably be a justifiable business expense. The first is that I have to be able to maintain and tinker with the theme myself to suit my requirements. Free themes from WordPress.org are GPL-licensed, so that’s not an issue as long as one abides by the license requirements, but it may not be the case with proprietary theme code. The second is that, given the privacy regulation issues, open source tools are, by definition, transparent. Some developers are notably more helpful than others about explaining or identifying specific features, but the option always exists to inspect the code to make sure it’s not doing anything I’m not comfortable with and remove or disable those functions if I so choose. Closed-source premium software doesn’t necessarily permit that, and given the invasiveness of software companies like Microsoft, that’s risky, especially since laws like California’s put individual site operators or business owners on the hook for their service providers’ practices.
One I’m considering is Miniva, specifically because it advertises limited resource use. I’d have to set up a sandbox site to see whether the basic features would be adequate for me or not. (I don’t use WooCommerce and am not enamored of sliders, but if the basic version doesn’t allow modifying footer text or setting footer widgets, that would probably be a dealbreaker.)
I’m actually quite fond of Frontier, the current theme, which provides lots of out-of-the-box flexibility. Unfortunately, it’s apparently no longer supported. I’m not sure why, although with open source software in general, it’s not uncommon for developers to abandon a project if they no longer have time for it.