Echoes

Eleven skins, one fixed two-column frame

Echoes does not give you a colour panel to dial in a brand. According to the vendor's feature list, the theme ships with eleven skins: Bright, Dark, Red, Blue, Green, Yellow and Brown, plus a shaded version with a textured background. Picking a skin is the colour decision; changing it later means choosing a different skin rather than adjusting an accent value. If you need a brand palette that falls between those prepared sets, plan on editing CSS.

The same listing records a fixed layout across two columns. That frame is the structural limit of every page the theme formats. Skins change the surface; the two-column grid behind it stays. If you want a portfolio grid that behaves differently on tablet and phone, or a single-column journal layout, the theme does not offer it as a switch. The vendor says the shaded skin's textured background is intended for "easy background customization," which is the closest thing to a flexible background control in the description.

One marketplace attribute is worth stating plainly: High Resolution is marked No. The preview and demo images are not described as retina-ready assets, so treat illustrations and portfolio thumbnails as your own supply problem.

Skinned variants only work when you swap them wholesale. Decide the palette before you build pages, not after.

Five portfolio treatments and the link-versus-lightbox choice

The vendor's opening summary counts five portfolio page styles, and the feature list names four concrete variants: Portfolio with Small Thumbnails, Medium Thumbnails, Slide Buttons and Slide Thumbnails. Those are two separate decisions, not four equal options. Thumbnail size sets how much of each project image a visitor sees in the grid; the slide variants change what happens when a visitor interacts with the row.

A version 1.3 change note adds the part that often matters more day to day: portfolio items can point to a direct link or open in a lightbox popup. Direct links send the visitor to the project page or an external URL, while a lightbox keeps them on the archive. That choice determines whether your portfolio functions as a browsing surface or as a gateway. Projects with long written case studies want the direct link; image-led work suits the popup.

The vendor also describes item showcases with video and images carrying on-hover icons, and those icons signal which behaviour a tile will use. Reviews of the theme from editors should check both behaviours on the demo before committing, because the description states the capability without saying which portfolio style defaults to which.

The homepage is a set of slide modules you can leave out

The homepage options are listed as a featured block, accordion slides, scroll slides, and jQFancy slides with transition effects. These are pre-built presentational modules rather than content sections you compose. You choose which of them appear on the front page.

Version 1.3 recorded an important change: the homepage "can now switch off sections." That is genuinely useful, because it lets you keep a featured block and drop the accordion, or run slides without a featured strip above them. The same changelog entry carries a warning worth repeating, since it tells you how tightly the homepage is wired: upgrading users were told to note down the contents of their homepage before upgrading. The homepage in this theme is not an interchangeable page but a configuration the update process could disturb.

Featured slides also gained support for pages in version 1.2, so a homepage slider can point at static pages, not only posts. For a portfolio site that is the realistic route: a handful of project pages promoted on the front page rather than a dated blog feed.

How to read the old platform declarations

The marketplace lists software compatibility as WordPress 3.7, 3.6 and 3.5, with IE6 through IE9 alongside Firefox, Safari, Opera and Chrome in the browser list. Those figures describe a theme of a particular era; the vendor item page was last updated in July 2019 and the marketplace lists version 1.5. The changelog in the description stops at version 1.4 in March 2011.

This is not a reason to claim the theme breaks on your server, and there is no evidence here of how it currently behaves. It does mean you should plan on your own verification: install it on a current WordPress build in a staging environment, exercise the portfolio and homepage modules, and check the contact form, before making it the base of a client project. Anything the theme depends on for its jQuery slides is the likeliest place to see friction with newer plugin code.

Gutenberg Optimized is marked No. That says the vendor has not declared block-editor optimisation; it does not mean the block editor refuses to load. Realistically, the editing workflow the theme describes runs through theme options and its own page templates, so expect to build pages the theme's way rather than by assembling blocks.

The included file list is Layered PSD, PHP, CSS and JS. The vendor states that all PSDs are layered, named and grouped, and that a demo post content XML file ships with the theme. A designer reworking the visual language will value the PSDs; anyone maintaining the live site works in PHP templates, CSS and the theme options.

Questions & answers