ThemeForest Horr - WordPress Theme

ThemeForest Horr Setup Guide for a Horror Gaming Site on WordPress

Think of ThemeForest Horr not as a finished page waiting for someone else’s images, but as a set of visual and content tools for a site about a game, studio, streamer, genre news, or a small online store. The theme has a strong identity: a high-contrast dark background, red accents, bold typography, distressed borders, expansive visual sections, news, and media. So after installation, the main question is not “Where do I change everything?” but “What path should visitors follow from the hero section to the action they came to take?”

This guide walks through that process: how to prepare WordPress, activate the theme safely, preserve the existing site structure during import, build the homepage, configure navigation and interactive elements, fill sections with video, posts, and products, check responsive layouts, and troubleshoot common failures. It is useful both for people launching a site from scratch and for editors who have inherited an installed Horr site and need to turn its demo content into a working project.

Don’t try to reproduce the demo exactly. Its images, videos, and text show how the layout works, but they do not automatically come with permission to reuse them. Keep the working framework first, then replace each content layer with your own materials: logo, covers, news, trailers, screenshots, product cards, menu links, and copy. That makes it easier to see which changes actually affect the public-facing site.

What Horr is designed for, and who its visual style suits

Horr suits a site that needs to build anticipation for a game world, not just communicate basic facts. It could be the site for a single-player horror game, a small studio, a blog with reviews and news, a streamer’s site, a collection of atmospheric games, a concept art gallery, or a store selling digital and physical products. The theme is especially effective when a project has a strong supply of visual material: large stills, a trailer, cover art, illustrations, game interface elements, characters, or environments.

Its value goes beyond the dark palette. The original concept brings together several useful roles: the hero section captures attention, statistics provide quick context, a video section creates a central scene, cards and lists lead to news or products, and lower sections give visitors a reason to stay. In WordPress, that means one homepage can connect editorial content, a media library, and a product catalog, as long as each section has a clear purpose.

When Horr is a good fit

Choose Horr if your project needs a cinematic, moody site with a strong sense of story rather than a neutral corporate storefront. For example, a team releasing a small survival horror game might use the hero section for a trailer, explain the world below it, feature development news, add a media page, and open a merch store later. The distinctive borders, red accents, and large illustrations help keep the visitor’s attention focused.

The theme can also work well for an editorial site about horror games. Its post layouts, grids, carousels, and dedicated content types for images and video are useful here. You could feature one recent review on the homepage, followed by news, a trailer roundup, editor columns, and a link to the catalog. Visitors see a sequence of content formats instead of one endless feed.

For a small storefront, Horr is most useful when paired with WooCommerce. The theme advertises compatibility with the plugin, including a popup cart, adding products without a full page reload, and a product lightbox gallery. That can work well for a focused catalog of game-related items such as an art book, poster, T-shirt, soundtrack, or digital bundle. Test the path from the product page to the cart on a staging site first, then enable the store for your main audience.

When another approach may work better

If your site is built around frequent long-form articles where calm typography and dense text matter most, Horr’s expressive styling may feel excessive. Its dark background and decorative borders call for careful attention to contrast, font size, and spacing. A catalog of thousands of unrelated products also needs a separate review of navigation, filters, and performance. The theme can style a storefront, but it does not replace a well-planned store information architecture.

Don’t choose Horr just for a dark hero image if the rest of the site needs to be bright, businesslike, and minimalist. In that case, editors will keep having to work against the theme’s default character. A theme that already fits the site’s everyday needs will be easier to maintain. Horr works best when its dark presentation is consistent throughout, from the header and menu to news cards, video pages, subscription forms, and product pages.

What gives the site its character

The theme combines demo imports, a collection of custom WordPress blocks, flexible navigation, a news ticker, a logo preloader, live search, a configurable container width, a page frame, a custom cursor, a scroll indicator, and content entrance animations. This is not a checklist to enable in full. Think of it as a toolkit: choose a few elements that support the page’s purpose.

A useful rule for Horr is to give each screen one main focal point. For example, the hero section might feature a trailer and a play button, the news section one featured post, the store one product story, and the team section portraits and roles. If you enable the preloader, custom cursor, scroll progress, intense animations, a large background video, a ticker, and several calls to action all at once, visitors will see the effects competing for attention instead of a coherent atmosphere.

Before installation: content, server, and rollback planning

Preparing for a visual theme starts before you open the archive. First decide where you can safely import the demo content. If the site is already live, don’t experiment on its only copy. A demo import may create pages, posts, menus, media files, and settings that are difficult to distinguish from existing content afterward. Use a separate staging copy or a fresh WordPress installation on a temporary address instead.

Make a short map of the site you plan to build. A gaming project usually needs a homepage, a game or project page, news, media or trailers, a team page, contact information, community rules, and possibly a catalog. For each section, note who owns the content and what is needed for launch. The homepage, for example, needs one strong image, a headline, a short description of the game, and a clear action. The news section needs at least a few posts. The game page needs a description, system requirements or other key facts, images, and video.

What to save before changing themes

Back up your files and database through your host or a backup tool you trust. Separately record your active plugins, current menu, homepage assignment, widgets, custom CSS, analytics integrations, and any code previously added to the theme. Changing themes usually does not delete pages and posts, but it can change how they are displayed, the available menu locations, widgets, and custom blocks.

Check how the homepage is assigned in the Reading settings. The old site may use the posts feed as its homepage, while the Horr demo expects a static page. Also record your permalink settings and a list of important URLs. If visitors already reach a news post, game page, or product from search or an ad, don’t change its address without a redirect plan.

A safe rollback point is more than a database backup. Before importing, record the active theme, homepage, menu, and plugin list. If an experiment goes wrong, you can restore working navigation as well as your files.

Basic technical checks

Make sure your hosting supports your WordPress version, PHP version, and active plugins, and that none are waiting for major updates. In Tools → Site Health, check for critical warnings, filesystem permissions, update status, and REST API availability. The theme and its helper plugins may not be able to load media or complete an import if the server blocks required operations or the uploads directory is not writable.

Check upload limits. Large covers, video files, and theme archives expose file size limits sooner than an ordinary post does. Don’t try to fix the problem by randomly editing system files on a live site. First check the values available in your hosting panel and WordPress settings. If the archive or media still will not upload, contact your server administrator.

Pay particular attention to email, HTTPS, and permalinks. These are not specific to Horr, but without them forms, carts, search results, and notifications may behave unpredictably. Visitors should see a secure connection. Test email delivery and password recovery before launch, while any problem can still be investigated without mistaking it for a theme bug.

Organize the media library by purpose, not by folder

Assign a role to each image in advance: hero cover, wide trailer still, square news card, vertical poster, gameplay screenshot, section background, or product image. In Horr, these shapes serve different purposes. A wide image can work as a scene but lose its meaning in a narrow card. A vertical poster may work well in a series but not as a background with text over it.

Prepare a compact but cohesive set of launch materials. Six images from the same game world are more useful than twenty unrelated pictures. Keep the original files separately, give them descriptive names, and add useful text to media items. Alt text should explain the image to someone who cannot see it, not repeat the page title. For example, use “lit entrance to an abandoned station in the game” instead of “image 1.”

Plugins: fewer unknowns make troubleshooting easier

Don’t install a dozen plugins at the same time as the theme. Start with what your content actually needs: WooCommerce for a store, Visual Portfolio for portfolios and galleries, and perhaps tools for backups, caching, image optimization, and multilingual content. WordPress plugins are separate components that extend the core, so if a conflict occurs, it makes sense to check them one at a time.

Be especially careful with multiple plugins that do the same job: two caching tools, two block builders, several JavaScript optimization plugins, or overlapping popup tools. The site may seem to work at first, but one tool could later change another tool’s markup. With Horr, that can affect animations, search, the cart, and video blocks, where script loading order matters.

Installing ThemeForest Horr and checking it before making changes

Install the theme from the package you received from the author, and inspect the package structure first. Premium theme downloads often contain documentation, a child theme, import files, and a separate installation ZIP. If you upload the entire package archive to WordPress, it may report that it could not find a valid theme. If that happens, don’t upload the same file again. Extract the package locally and find the theme ZIP or folder containing the required style.css file.

1. In the admin dashboard, go to Appearance → Themes → Add New → Upload Theme.
2. Select the ZIP archive for the theme itself, not the combined package with documentation and extra files.
3. After the upload, activate the theme and open the public homepage in a new window.
4. Check the notices in the admin dashboard. The theme or its importer may prompt you to install recommended plugins.
5. Don’t start changing colors and typography until you have confirmed that activation did not cause a fatal error and you can still access the admin dashboard.

Your first visit to the site after activation is a technical check, not a design review. Look at several pages, the search form, a post, a media page, and, if the store already exists, a product page and the cart. If part of the site has become a blank page, shows a PHP notice, or has unexpectedly empty markup, return to the minimum set of plugins and check your host’s error log. You do not need to edit theme files right away.

Use the demo import as a framework, not as a finished site

Horr advertises a one-click demo import and several ready-made demo layouts. Importing is a quick way to get a block structure, example menu, card styles, and section order. But an import does not make the site ready to publish. It may leave test pages, demo authors, sample copy, categories, media, menus, and products that do not belong to your project.

Choose the demo closest to your planned site, not simply the one that looks most dramatic. For a game with a trailer and news, start with a layout centered on the hero scene and posts. For a blog, choose a version with a clear content hierarchy. For a store, look for demo navigation that already accommodates products. The less you have to rebuild, the lower the risk of breaking spacing, responsive layouts, or connections between blocks.

Don’t delete everything after the import. First list the objects it created: pages, posts, menus, categories, images, custom post types, widgets, and homepage settings. Then replace the content from the top down. If a page is not needed, first remove it from the menu and check whether another section uses it. Delete it only after that. This order helps you avoid accidentally removing a template block that looks like a separate page but is connected to the bottom of the homepage.

Checkpoint after activation

Pause once the theme is working, the admin dashboard opens, the homepage is assigned, and you have a clear list of required plugins. Don’t move an unfinished demo to the public site. Even if it looks impressive, it may still contain someone else’s images, draft copy, empty buttons, and menu items.

It is useful to make another backup at this point. It gives you a convenient place to return to if you try a different demo or change several global settings. That is easier than later tracking down which of dozens of edits affected the header, typography, or container.

Build a clear homepage flow instead of a collection of random blocks

Horr’s hero section should answer three questions within a few seconds: what game world is this, why is it interesting, and what can visitors do next? The reference layout combines a slim header, a large word or title, a wide visual scene, and a prominent launch button. On your site, that button might play a trailer, open the game page, subscribe visitors to news, open the media library, or show the catalog. Give the button one clear action, not five equally prominent choices.

Choose one dominant image with enough open space for text. Don’t replace it with a collage of posters or cram the project’s entire backstory into the headline. A short combination works better: the game title, a genre or story hook, and one explanatory sentence. If the content is not ready, use a neutral placeholder in the staging copy and wait to publish.

The hero, trailer, and a clear call to action

Horr includes video blocks and a video button, so a central video makes sense as part of the story rather than as a decorative tile. Embed a video only if it helps visitors understand the game by showing its atmosphere, gameplay, characters, or world. If you don’t have a finished video, don’t fake it with an empty button. Use a large still and link to a detailed project page instead.

Make sure the button does not conflict with other interactive areas. If the background is a video, don’t place several identical round buttons over it. If the image links to one page and its caption links somewhere else, visitors won’t know what to expect. One clear action is easier to use and more accessible than a dramatic but ambiguous scene.

Check text over dark images on more than your own monitor. Open the page in bright ambient light, in a smaller window, and on a small laptop. Dark designs have a common trap: the author sees a beautiful texture, while the reader sees a black rectangle and a dim line of text. If needed, darken the image with a controlled overlay, increase text contrast, or move the key line to a calmer part of the image.

Use the news ticker as a signal, not motion for its own sake

The theme has a ticker area for important news above the menu. It is useful when a message is genuinely time-sensitive or recurring: a release date, the start of testing, a new development diary, a stream announcement, a schedule change, or a new product. Don’t put ordinary navigation, long headlines, or marketing slogans in the ticker. Visitors can already see the menu, and constant movement makes reading harder.

Set an editorial rule for the ticker in advance. For example, show one short update at a time, remove it when it is no longer relevant, and make sure each message has a full post or page with details. Without a rule, the ticker quickly becomes a graveyard of old announcements. Use it especially carefully on mobile, where fast-moving text is harder to read and can distract from the menu.

Statistics, progress, and proof points

The visual reference includes number cards and horizontal progress bars. Use these elements only when the numbers have a clear meaning. A studio site might show the number of chapters, unlocked areas, team members, days until an event, or localization progress, as long as the count is not misleading. A gaming blog could show the number of posts in a series or an editorial score with a clear method, rather than arbitrary “millions.”

Progress bars require even more care. Don’t show “development 90%” unless that percentage represents a clear milestone. It is better to name a measurable milestone: “Demo ready,” “Applications open,” or “Update published.” If the bar is purely decorative, don’t label it with a number that looks like a commitment.

Section pacing and pauses between scenes

After the hero section, visitors need a change of scale, not more effects. A good sequence for Horr might be: atmospheric image, brief fact or proof point, a section about the game world, video or gallery, recent content, and an action. Each section should have a different purpose, not just a different background. Place a calm text section between two image-heavy sections so readers have a chance to refocus.

Don’t copy every section from the demo. Each block should have a clear answer to “Why is this here?” If it doesn’t, remove it instead of leaving an empty frame with one word in it. In a dark theme, open space often makes a stronger impression than another decorative detail.

Set up the visual system: container, colors, typography, and page frame

Once the homepage has a structure, set up the global design system. Horr advertises a custom container size, page frame, brand color, and extensive typography settings. Change these in order: first width and spacing, then the base color, then fonts, and finally smaller details. If you start by adjusting every button and heading individually, the site will feel inconsistent and be harder to maintain.

The exact place to control these settings depends on the theme version and how the site is configured. Look for sections related to the theme’s appearance, the Site Editor, theme settings, or block settings. Don’t confuse general WordPress settings with local settings for a single block. Before making changes, capture the homepage, a post, and a product page. Those screenshots will help you spot unwanted effects from a global setting.

Container width and readability

The container controls how wide the text and cards appear. A very wide text column on a dark background is tiring, especially in reviews and news posts. A container that is too narrow makes cinematic images look small and forces headings to wrap across too many lines. Set a separate width for long-form content and wide scenes if the theme allows it. Articles are easier to read with a limited line length, while a gallery or hero section benefits from more space.

Check three cases: a long headline, cards in two or three columns, and a regular paragraph. If one of them looks wrong, don’t fix it with local negative margins. Revisit the container, heading sizes, or number of columns. A global setting is useful when it improves every page, not just the homepage.

Use color to define roles

In the reference, red serves as an accent: it highlights the logo, active menu item, launch button, lines, and selected markers. Keep it in that role. If red covers half the text, borders, every button, icons, and card backgrounds, it stops guiding the eye. Choose one dark base background, one lighter surface color, a neutral main text color, a muted secondary text color, and one action accent.

Don’t confuse a dark aesthetic with low contrast. Gray text on a nearly black panel may look “atmospheric” in a mockup but become hard to read in practice. Check important elements: menu items, card headlines, post dates, prices, button states, the search field, and form labels. If text is hard to read, increase its contrast or size instead of adding another decorative effect.

Typography and hierarchy without overload

Horr supports typography settings and a wide selection of web fonts. Don’t turn that into a search for the “scariest” typeface. For body text, clear letterforms, a sufficient size, and comfortable line spacing matter more. Save an expressive font for major headings, numbers, and short labels. Use a calmer family or weight for subheadings and cards so they don’t compete with the main text.

Create a short style guide for editors: main heading size, H2 size, H3 size, body text, caption, button, and short label. It doesn’t have to be a technical document, but it should prevent every new page from getting its own scale. In a dark design, distinguish heading levels with spacing above and below the block as well as font size.

Page frame, custom cursor, and scroll indicator

The page frame, custom cursor, and scroll indicator are distinctive Horr features. Use them selectively. A frame can bring varied sections together, but if the spacing is too tight, it starts to crowd the text. A custom cursor can reinforce the gaming atmosphere on desktop, but it should not interfere with text selection, button clicks, or link recognition. It usually has no role on touchscreens, so check the mobile experience separately.

A scroll indicator can help on a long story, an in-depth review, or a series of narrative sections. On a short page, it explains very little. Don’t treat it as a required part of the style. Enable it only when visitors benefit from seeing how long the content is and how far they have moved through it.

Horr navigation: menus, search, off-canvas panel, and visitor flow

The theme offers a classic menu with dropdowns, fullscreen and hamburger menus, mega menus, a sticky header, and a sidebar off-canvas panel with widgets. That is a strong set of options, but not a reason to enable everything at once. First sketch a simple visitor path: hero section, project page, news or media, then an action. Navigation should support that path, not showcase every WordPress feature.

A site for a single game may need only a logo, four or five menu items, and one featured action. A magazine might use “News,” “Reviews,” “Videos,” “Roundups,” and “About.” A store can add “Catalog” and an easy-to-find cart. Hiding important pages inside a mega menu can hurt conversions. Visitors should not have to guess where to find the trailer or participation details.

Choose one primary menu style

A classic menu suits a site where visitors move between familiar sections. Use dropdowns only for closely related pages. For example, “Media” could expand to “Trailers,” “Screenshots,” and “Wallpapers.” A fullscreen menu can create an atmospheric pause between scenes, but it should not hide key actions behind an extra click at every screen size.

A mega menu makes sense when it helps visitors navigate a large site by showing several genres, post series, teams, or product categories. Don’t turn it into a noticeboard with dozens of links. Include only items people actually use, and check regularly that the menu opens with a keyboard and can be closed with an obvious action.

Sticky header and mobile layout

A sticky header keeps navigation within reach on long pages, but it reduces the usable height of a mobile screen. Open the page at a narrow width and check that the header does not cover headings, the video player, or a consent notice. If it takes up too much space, simplify it. Keep the logo, menu button, and one important action.

WordPress menu controls vary with the theme type and site configuration. On sites with block-based navigation, changes are usually made in the Site Editor and the Navigation block. Classic or hybrid setups use the familiar Menus screen. In either case, the final check is the same: save your changes, open the site while logged out, test the main menu, a submenu item, the mobile menu, and the route back to the previous page.

Live search: don’t promise more than it can find

Horr advertises Live AJAX Search. It is useful on a site with news, reviews, and media because results appear as visitors type. But it needs real content to search. Before launch, give posts clear titles, categories, and short excerpts. If a visitor enters a game title and gets no results or unrelated posts, the polished search form will only make the disappointment worse.

Test search with three kinds of queries: an exact title, the beginning of a word, and a common topic. Make sure results show enough context to help visitors choose, not just headlines. Then check that caching is not preventing the index from updating and that search does not conflict with another plugin that changes WordPress results.

Use the off-canvas panel as a second layer, not a link dump

A hidden sidebar panel can hold social profiles, a short project description, a streaming schedule, a subscription form, or secondary navigation. Don’t move everything that didn’t fit in the header into the panel. If it contains widgets, limit them to a few useful blocks and check their order on a phone. An empty or overloaded panel makes the interface feel less considered.

Check keyboard focus separately. After the panel opens, focus should remain within the open layer. Once it closes, focus should return to the button that opened it. If the theme and other plugins do not provide the expected behavior, don’t try to cover the problem with a decorative animation. A site with accessibility requirements needs to be tested with a keyboard and screen reader.

Cards, blocks, and media: turn the feature set into an editorial workflow

Horr provides standard and advanced blocks for buttons, tabs, accordions, collapsible panels, FAQs, notices, icons, number cards, progress indicators, dividers, testimonials, responsive grids, columns, video, background images and video, calls to action, tables, countdowns, and contact forms. These tools let you build different kinds of pages without repeatedly writing the same markup by hand. But blocks do not replace editorial judgment.

Before adding a block, define the input, the action, and the expected outcome. Tabs make sense when visitors can look at one subject from several equally important angles: “Story,” “Characters,” “System Requirements,” and “Media.” An accordion is useful when readers have specific questions and do not need every answer visible at once. Use a grid when the cards are comparable in format. Use video when motion adds information that text cannot convey.

Don’t hide all your content in tabs and accordions

Collapsible blocks save space, but they can hide important information. Keep the page’s main point, game description, key call to action, and first important fact visible. Use tabs for alternative views and accordions for secondary details. On mobile, make sure panel headings are large enough to tap easily.

A good example is a game page. The main column contains the title, a visual scene, a short description, and a call to action. Tabs below it can cover the story, world, and gameplay features, followed by video, a gallery, and an FAQ. A poor example is a page where the whole story, system requirements, release date, contacts, and rules are hidden in ten identical accordions. Visitors will not know where to begin.

News, video, and images are different content formats

The theme supports video and image post types. For a blog, it offers classic, masonry, and slider layouts, along with grid, list, slider, and carousel blocks. Before changing the layout, decide which types of content you publish regularly. If the team posts news once a week, you need a clear list and archive. If the project centers on trailers and development diaries, a video page and a prominent place for the latest video matter more.

Don’t republish the same item in five formats. A featured review can appear as a large card on the homepage while remaining a regular post in the archive. A video can have a short article for context, but you don’t need to create another empty page just to repeat the same cover. Each post should have one primary URL and one editorial role.

Gallery layouts and Visual Portfolio

Horr advertises compatibility with Visual Portfolio for portfolios and galleries, with masonry, justified, and slider layouts, lightbox viewing, and video from external sources. This can work well for concept art, screenshots, developer materials, and covers. Start with a clear way to group the content, such as “Locations,” “Characters,” “Process,” and “Wallpapers.” Don’t mix sketches, finished promotional images, and product photos in one filter without explanation.

A masonry layout handles images with different aspect ratios well, but it can disrupt the order of a story. If you want to show a path from a sketch to a finished level, use a numbered or sequential series. A justified gallery works better for a clean showcase, while a slider suits one larger story. Test the lightbox with a keyboard: it should close and return the user to the card that opened it.

Background images and video

Horr includes blocks for background images, background video, and parallax. They can create a cinematic sense of scale, but can also hurt performance and readability. Prepare a quieter mobile alternative for every background. If a mobile device cannot show a complex video without a long wait, use a still image and a play button instead.

Don’t place important text over the most detailed part of an image. Position the heading and button first, then choose the image or overlay. With parallax, check whether the motion causes discomfort or stutters on a slower device. The atmosphere should support the content, not make it harder to finish a sentence.

Practical example: a horror game landing page with news, a trailer, and a small store

Here is a concrete example of how to use Horr without trying to build everything at once. Imagine a small game called “Echo Station,” set in a flooded research facility. The team is preparing a public demo, publishing development diaries, and selling a limited set of digital items. The site’s goal is to get visitors to watch the trailer or subscribe for updates, not to make them visit a dozen pages right away.

Define the goal and prepare the content

Gather your materials before opening the editor: one horizontal image of the flooded station, a short trailer, three news posts, four gallery images, a game description, a set of facts for an “About the Project” card, and two products. You do not need to wait until you have a complete set of marketing materials. Each block just needs to show real information instead of placeholder copy.

In WordPress, create draft pages for “Home,” “Game,” “News,” “Media,” “Store,” and “Contact.” Create news categories for “Development Diary,” “Trailers,” and “Updates.” If you are using a store, add just two test products with clear names, images, and shipping or digital access settings. Don’t connect live payment processing on the public domain at this stage.

Step 1. Build the hero section

Assign the “Home” static page in the Reading settings. Open it in the editor and use the structure from the demo’s first section, or build a new one from the theme’s available blocks. Add a background image, the title “Echo Station,” one line that sets up the situation, and a “Watch the Trailer” button. Add a short block beside or below it with three real points of interest: “Demo,” “Development Diary,” and “Media Library.”

The button should lead to the video block on the same page or to a separate trailer page. Don’t add three equally prominent buttons like “Buy,” “Play,” and “Learn More” if you have not decided whether the game will be sold. If the video is central to the page, make sure visitors can still see a cover image, heading, and alternative text description if the video is unavailable.

Step 2. Add content sections in the order visitors make decisions

After the hero section, add a short section called “Why the Station Is Dangerous.” It does not need extensive lore. Three cards are enough: flooded sectors, a signal from a lower level, and limited light. Then add two wide images with text about the setting and survival mechanics. Alternating text and images matters here. Otherwise, the homepage will look like a gallery.

Place the trailer next. Add it with a dedicated video block, give it an informative heading, and explain in one sentence what it shows. Follow it with news: one featured post in a large card and two secondary posts in a grid. Give them distinct headlines, such as “A Flooded Sector Is Now Open,” “How We Recorded the Signal Sounds,” and “A New Difficulty Mode Arrives in the Test Build.” This gives visitors a reason to keep exploring.

Step 3. Set up the menu and secondary entry points

Put five items in the header: “Game,” “News,” “Media,” “Store,” and “Contact.” If the site has only one game, the logo should lead to the homepage. The off-canvas panel can hold a subscription form, team channels, and a short schedule. Show just one current message in the ticker, such as “The demo is available for testing.” Replace it with new information when the testing period ends.

Add submenu items only when they make it easier to choose. “Media” could contain “Trailers,” “Screenshots,” and “Wallpapers.” There is no need to split up “News” while there are only a few posts. On mobile, check that the menu order still follows the same structure as desktop rather than turning into a random list.

Step 4. Set up the media library and gallery

Create a separate “Media” page with filters for “Locations,” “Characters,” “Sound,” and “Concept Art.” Four starter images do not need an elaborate filter system. Clear captions and a lightbox view are more important. Give each image a distinct role: showing a place, a threat, an item, a development stage, or the atmosphere.

Give each item context as well as a polished cover. For concept art, explain what the artist was trying to achieve. For a still from the trailer, say which location it shows. That turns the media library from a decorative wall into part of the story.

Step 5. Build a small store without overloading it

Connect WooCommerce only after the core pages, menu, and media are working. Add two test products: “Digital Art Book” and “Station Poster.” Give each one a quality primary image, a few additional images, a clear description, a price in your actual currency, and instructions for receiving it. For testing, use a safe test purchase flow rather than live payment processing.

Check the theme’s advertised product features: add to cart, the floating cart, the cart page, and the product gallery. If adding to cart without a page reload is enabled, make sure the cart count changes on mobile too. If the effect gets in the way or conflicts with JavaScript optimization, temporarily use a simpler and more predictable flow.

Step 6. Check the site as a visitor

Open the site while logged out. Follow this path: land on the homepage, understand what the game is, watch the trailer, open a news post, visit the media library, add a product to the cart, and return to the homepage. At every step, ask whether the next action is clear, the menu is still available, effects cover any text, a background is too large, or demo images and names are still in place.

Repeat the path on a small screen. Check what works, not just how it looks: the menu opens, search returns a result, the video button is available, the gallery closes, and the cart does not cover an important message. Finally, check the page speed with the browser cache cleared and in a separate window. If blocks shift on the first load or heavy videos and images without set dimensions are slowing the page down, fix that before launching ads or a mailing list.

In short: Horr helps you create a strong visitor path when each section handles one step: interest, context, proof, fresh content, and action. If a section does not move visitors forward, it is better to leave it out.

Editorial guidelines: keep the site from becoming a beautiful but empty storefront

After launch, teams often run into a new problem: they keep changing backgrounds, buttons, and effects without developing a clear way to publish content. This is especially noticeable with Horr. A strong visual theme can make an empty section look convincing for a few seconds, but a month later visitors may find an outdated trailer, no recent news, cards leading to identical pages, and a ticker showing an event that ended long ago.

The solution is not to publish more, but to distinguish between content formats. News reports a fact. A development diary explains a decision or process. A game page collects stable information that does not change every week. A media library presents images and video with brief context. A product page explains what the buyer will receive. When these roles overlap, authors repeat the same information in different places, and visitors cannot tell which page is the primary one.

Set guidelines for four recurring content types

Agree on a structure for news posts in advance: a clear headline, date, short opening, one primary image, the main update, a next step for the audience, and a category. Don’t start every post with a dramatic prologue. The site’s horror style already sets the mood; news is most useful when it is clear. If an update fixes a bug or introduces a new video, say so near the beginning.

Use a different rhythm for development diaries: the question, the constraint, what the team did, what changed, and what that means for players. For example, a post about a flooded location could cover more than its striking appearance. It could explain the challenges of sound, lighting, routes, and limited resources. These posts give the audience a reason to come back and provide context for future announcements.

Add a short written introduction to video posts. Say what the video shows, how long it takes to watch, whether it contains story spoilers, and where visitors might go afterward. Don’t use a headline like “New Trailer” every time. Name the subject instead: “Trailer: Lower Levels of the Station” or “Sound Diary: A Signal from Compartment B.” This helps both on-site search and visitors who arrive later.

Write gallery captions using the pattern “what is shown and why it matters.” One line may be enough. “Airlock prototype before final lighting adjustments” says more than “Screenshot.” Give each image meaningful alt text, especially if it is the only way to understand a section without reading its text.

Let the homepage change more slowly than the news feed

Don’t move every new post to the homepage. Stable top sections explain what the game or project is, while one or two editorial sections show that it is active. A good rhythm might be to update the featured item when there is a major announcement, pull recent posts into the news block automatically or manually, update the media library less often, and leave the core story of the game world stable. The homepage keeps its structure without looking abandoned.

Before changing the featured item, check whether it is connected to the hero image, call to action, ticker, and card below. A common mistake is updating the cover image while leaving the button pointed at the old trailer. Give editors a short checklist: title, background, action link, ticker text, featured news, social image, and mobile check. That prevents more errors than another decorative tweak.

Categories, tags, and filters should not duplicate each other

A category answers “Which editorial section does this post belong to?” A tag describes a specific topic. A horror game project may need only “News,” “Development Diaries,” “Video,” and “Events” as categories. Tags could describe locations, characters, game systems, or series names. Don’t create a separate category for every post. That leaves archives empty, bloats the menu, and makes search less useful.

Gallery filters should reflect an understandable way of grouping media. If the page has “Locations,” “Characters,” and “Process,” don’t add “Red,” “Poster,” and “New” alongside them unless those labels actually help people choose an image. The less visitors have to think before their first click, the better the grid works.

Assign an owner to each part of the site

One editor might manage the homepage, news, gallery, and store, but responsibilities still need to be clear. One person can own the top announcement and homepage, another the posts, and a third the products and media. If several people have access, agree on who can change global styles, menus, and theme settings. These areas are easy to damage with a change intended for one news post.

Create post templates for authors: where to set the cover image, how to write a short description, where to place a video, which category to choose, when to use a gallery, and what headline length will fit a card. This is not bureaucracy. A template reduces the risk of one post having a huge image, another having no cover, a third having five nested headings, and a fourth lacking a clear date.

Store and media, one atmosphere: keep storytelling distinct from selling

WooCommerce can be a natural part of Horr, but the store should not disrupt the site’s story. On a game page, visitors want to understand the world and see the media. On a product page, they want to know what is included, how much it costs, how they will receive it, and what restrictions apply. Don’t disguise commercial information as mysterious copy. You can keep the dark style in covers, photos, and spacing, but price, availability, options, and terms must be clear.

Start with a small catalog

A few well-presented products are enough for the first launch. For a digital art book, explain how it is delivered, what it contains, include sample pages, and state any usage restrictions. For a physical poster, list its size, material, options, and shipping terms. Don’t publish a product page until you can answer what happens after a visitor clicks the button. The site can be atmospheric, but ordering must remain clear.

The theme advertises a popup cart and adding products without a page reload. These features should shorten the path, not hide information. After a product is added, the buyer should see a clear confirmation: which item was added, how many items are in the cart, how to open the cart, and how to return to browsing. If a floating panel covers content or appears unpredictably on a phone, favor the standard cart page instead.

A product gallery is not the same as a gallery of the game world

Images in the media library show the atmosphere and development process. Product images answer questions about the item itself. A poster needs an overall view, a close-up of the print, a sense of its size in a room, and packaging photos if relevant. A digital bundle needs clear examples of what it contains. Don’t reuse the same artwork for every product image just because it looks good. Buyers need useful information, not another version of the hero image.

If the product page uses a lightbox gallery, test it with a keyboard, on a phone, and with the close button. It should open from a clear thumbnail, not by accident while someone is trying to read the description. Place a test order with the actual tax, shipping, or digital delivery settings before sending the first audience to the page.

Make product recommendations relevant, not intrusive

Related products can be useful when they have a story or functional connection: an art book beside digital wallpapers, a location poster beside the soundtrack, or an item set beside a development post. But don’t add recommendations to every screen. On a news post, suggest a related media page or another article instead of trying to turn every visit into a purchase.

Make button labels and notices specific. “Add to Cart” is clearer and more honest than an abstract phrase based on game jargon. Don’t use a decorative tone for return, shipping, or data collection terms. Visitors must be able to find essential information quickly, even in a highly styled interface.

Connect products to the story through editorial content

If a product relates to the game, provide context nearby. A product page for an art book could point readers toward a post about the game’s art direction. A character post could mention that the media library contains the character’s sketches. This does not require adding numerous links to one page. One logical next step is enough. Likewise, don’t promise something in a story that the product does not include. Check any cover option, bonus material, or physical item before publishing.

A pre-launch and post-update check of the visitor journey

Check a Horr site as a visitor’s story, not as a set of separate pages. Every significant update could affect something nearby: a new plugin changes scripts, a media file slows the homepage, a menu loses an item, caching serves an old version, or a global color makes a product card unreadable. One short visitor journey can catch these problems before your audience does.

Test the visitor journey while logged out

1. Open the homepage in a private window and make sure the hero section quickly shows the title, main promise, and an available action.
2. Open the menu, visit two main sections, and return to the homepage through the logo.
3. Search for the game title or a news topic and check whether the first result is relevant.
4. Open one news post, one video, and one gallery item. Check the images, headlines, and close buttons.
5. If there is a store, add one test product, open the cart, and confirm its contents remain after reloading the page.
6. Repeat the key path on a phone or at a narrow viewport, checking functionality as well as appearance.

For each step, record what happened instead of writing “seems fine”: the button opened a page, the menu expanded, search found the right post, or the cart kept the product. Another editor will be able to repeat a concrete check. If you find a problem, record the URL, device, exact symptom, and most recent change. This makes it much faster to find the cause.

What to check after updating the theme or a plugin

An update will not necessarily break the site, but it should not be treated as an automatic routine on the live site. First update a staging copy or create a backup. Then check the header, menu, hero scene, blocks, post archive, individual post, gallery, product page, cart, and mobile layout. These areas matter more for Horr than a random secondary page because they use the theme’s scripts, animations, widgets, and styles.

If an update changes only spacing or an effect, compare the page with your earlier screenshots and decide whether a fix is actually needed. Don’t start restoring old CSS workarounds in bulk before finding out what changed. If a critical feature disappeared, use your rollback procedure to restore the backup or previous version, record the conflict, and continue investigating on the staging copy.

When you actually need to clear the cache

Cache matters after changing the theme, CSS, menu, hero images, scripts, or WooCommerce pages. Don’t clear everything at random. Clear the layer involved in serving the page: the plugin cache, hosting cache, content delivery network, or browser cache. Then open the page while logged out. If an administrator sees the changes but a visitor sees an old copy, the issue is almost certainly not the editor block itself.

Don’t use cache disabling as a permanent fix. Once you find the cause, restore the required optimization and configure exclusions only for dynamic pages that really cannot be cached. For a store, this usually includes the cart and checkout, but the exact list depends on your configuration.

Responsive design, performance, and accessibility in a dark gaming style

The theme advertises responsive layouts, but that does not mean all imported content will automatically be easy to read on a small screen. The most common issues appear after replacing images, headlines, logos, widgets, and long menu labels, not in the basic markup. Check the layout as you edit rather than leaving it as a final ritual before launch.

Check three real screen sizes

At a minimum, open the page on a large monitor, a narrow laptop, and a phone. On the largest screen, assess composition and open space. On the laptop, check headline wrapping and card density. On the phone, check the menu button, tap target sizes, hero height, caption readability, and video behavior. Don’t rely on a single browser preview. Text often takes up more space on an actual device than it does in a comfortable editor panel.

Note functional symptoms, not just aesthetic impressions: a heading covers a button, the menu will not close, a card does not fit, text is cut off, an image loads too late, the search field is covered by a panel, or a button is too small. Look for the cause only after you have recorded the symptom. It could be the text length, container size, block settings, custom CSS, a conflicting plugin, or cache.

Use media efficiently

Large artwork matters to Horr, but it does not justify a page that stays blank for too long. Use optimized images, set sensible dimensions, and don’t auto-load a video unless it is needed for the first action. Lazy loading and modern image formats can help, but after enabling them, check the hero section, gallery, and product page. Optimization can sometimes change the loading order and leave visible empty space.

Start by removing what you don’t need: unused demo slides, repeated animations, background videos that add nothing, duplicate libraries, and heavy plugins. That is safer than adding another optimization tool. If you use caching, clear it after changing the theme, menu, CSS, or an important block. A stale copy can make it look as though your settings did not take effect.

Motion, contrast, and accessible use

Content entrance animations, the custom cursor, and parallax should each have a clear purpose. For someone sensitive to motion, a moving background or cursor can be distracting. Don’t turn every card entrance into its own scene. Reserve movement for transitions to important content and keep it restrained.

Check heading order, visible focus states, text labels for icons, and image alt text. A button with only a play symbol may look atmospheric, but it also needs an accessible label or clear name. Color should not be the only way to indicate a state. If red marks an error or an active item, add a shape, text, or icon as well.

Small, maintainable customizations: child theme and careful CSS

Horr includes a child theme, and WordPress recommends child themes for changes that should survive updates to the parent theme. You do not need one for every adjustment. If the theme or block interface already provides a setting for a color or margin, use it. A child theme is useful when you intentionally add custom CSS, override a template, or plan to maintain the site beyond a single campaign.

Don’t edit the active parent theme files for a small visual adjustment. The change may disappear in an update, and it will be harder to distinguish custom code during troubleshooting. Activate the included child theme on a staging copy, make sure the design still works, and only then move your customizations over.

A reversible custom contrast adjustment

If text in the hero section becomes hard to read after you replace the demo image, you can add a small CSS rule to the child theme or the built-in Additional CSS field. This is an author-created adaptation based on standard CSS, not Horr’s internal API. The selector is tied to your custom class so it does not affect every theme block.

/* Add the echo-hero class only to the hero section that needs it. */
.echo-hero {
  position: relative;
}

.echo-hero::before {
  content: "";
  position: absolute;
  inset: 0;
  background: linear-gradient(90deg, rgba(8, 9, 12, 0.82), rgba(8, 9, 12, 0.22));
  pointer-events: none;
}

.echo-hero > * {
  position: relative;
}

First add the echo-hero class only to the relevant section in its Additional CSS Classes field. Then add the rule to the child theme or Additional CSS area. Check the page at wide and narrow screen sizes. If the text is easier to read but the image has lost depth, gradually reduce the opacity in the first value. To roll back, remove the block class or the entire CSS snippet. Don’t add this rule to the parent theme files or apply it to other sections without testing.

When CSS is not the answer

Don’t add code if the problem can be solved by replacing the image, increasing spacing, using a built-in background color, adjusting font size, or changing the block settings. CSS should not compensate for a poor editorial layout. If a long headline hides the button, shorten the headline first. If cards are hard to read, revisit the number of columns and the image.

Languages, roles, and long-term care for a visual site

Horr advertises translation readiness and compatibility with WPML. That does not mean a multilingual site will appear as soon as you activate a plugin. Plan the language setup just as you would the menu or homepage: choose the languages, assign an editor, set rules for images, define the news format, and decide how translations will be published. Otherwise, one language may have current trailers and product cards while another is left with old demo text.

Translate the stable interface first

Start with the site title and description, menu items, utility pages, form text, store messages, news categories, buttons, and legal documents. These appear throughout the site and make it feel complete. Then translate the game pages and main editorial content. Don’t publish a language switcher that leads to an empty copy of a page. If a translation is not ready, use a clear approach supported by your multilingual setup instead of making the site look finished when it is not.

Pay particular attention to the hero buttons and ticker. They are short, but often contain an action verb or an important deadline. A literal translation can make a button unclear. Write concise versions for each language and make sure they fit at mobile widths.

Images and video do not need duplicates, but the context must be translated

The same trailer or artwork can be used in several languages if it does not contain embedded text that conflicts with the audience. But the heading, alt text, caption, and transcript should be available in each language. If an image contains important text, prepare a localized version or explain the information next to it. Don’t assume visitors will understand the image without context.

For videos, check the title, description, subtitles, and page where the video is embedded. In Horr’s design, video often becomes the central scene, so missing context has a greater effect than it would on a standard archive post. If there is no localized version of the video, clearly state the audio language and briefly describe what it covers.

Editor roles and access limits

WordPress makes it possible to separate editorial and technical responsibilities. A news editor does not need permission to change the global menu, plugins, theme, or code. A media editor does not need access to store settings. The more clearly you assign roles, the less likely an urgent post is to accidentally change the hero section or remove a theme setting.

Before launch, agree on who approves changes in three sensitive areas: global styles, navigation, and store pages. Other authors can work in drafts, use approved blocks, and submit their work for review. This is useful beyond security. A shared process keeps the theme consistent in spacing, typography, cards, and tone.

Monthly maintenance without busywork

Regular maintenance does not require a daily technical ritual. Periodically check backups, WordPress, theme, and plugin updates, Site Health, key URLs, forms, and the store. On the content side, review the ticker, hero section, outdated news, menu links, featured images, and media library availability.

Before each major update, create a backup and repeat your check of the visitor journey. If a change affects only one news post, there is no need to rebuild the whole theme. A global color, font, or menu change calls for checks across several types of pages. This keeps the review proportionate: you don’t test the entire site for a comma, but you also don’t publish a structural change without checking its effects.

What to record in the project log

Keep a short internal log of the update date, what changed, which backup was saved, who checked the homepage and store, which plugins were added, and which optimizations were excluded and why. Visitors don’t need to see it, but months later it can explain where custom CSS came from or why caching is disabled on a dynamic page. Record child theme changes especially carefully: the file, purpose, result, and rollback method.

A visual site is not stable because it has lots of effects. It is stable when a new editor can find the content, understand the structure, replace material without risking the navigation, and repeat the same test journey. That lets Horr remain an atmospheric tool instead of becoming a fragile demo that everyone is afraid to update.

Troubleshooting: from imports to the cart and mobile menu

Troubleshoot theme issues by following a chain: symptom, likely cause, check, safe fix, and verification. Don’t change the theme, plugins, cache, and code all at once. Otherwise, you won’t know what worked. Before making changes to a live site, create a backup or repeat the experiment on a staging copy.

WordPress says the archive does not contain a theme

Symptom: WordPress refuses to install the archive or says it could not find the stylesheet. The likely cause is that you uploaded the full package instead of the theme ZIP. This often happens with premium products that bundle documentation, a child theme, and other files in a single archive.

Check: Extract the package on your computer and find the theme ZIP or folder containing style.css. Don’t delete anything from the server or keep uploading the same archive. Fix: Upload the correct ZIP from the Add Themes screen. After activation, open the homepage and admin dashboard. If the problem persists with the correct archive, stop and check that the original download is intact or contact the vendor.

The homepage is blank or still shows the old page after import

Symptom: The import finished, but the public homepage does not resemble the demo. It shows the old post feed or a blank page. The new page may not be assigned as the homepage, the old menu may still be active, the imported content may be incomplete, or the browser or server may be serving a cached copy.

Check: Review the Reading settings, page list, and menu assignment. Open the site in a private window. Then clear the plugin and hosting cache if you use them. Fix: Assign the intended static page, connect the menu to the right location, and replace only the missing blocks. To roll back, restore the previously saved homepage and menu instead of deleting imported content blindly.

A color or block change does not appear on the public site

Symptom: The editor shows the new setting, but visitors still see the old design. A common cause is caching in the browser, plugin, or server. Theme changes may not appear until the relevant cached copy has been cleared.

Check: Open the page while logged out in another browser or a private window, then clear the cache at the level that is actually in use. Make sure you edited the published page, not a duplicate or a template that is not connected to the current URL. Fix: After clearing the cache, make one small change and check it again. If it still does not appear, temporarily disable only the suspected optimization on a staging copy. Don’t disable all plugins on the live site without a plan.

The mobile menu will not open or covers the content

Symptom: The header looks fine on desktop, but on a phone the hamburger menu does not respond, opens an empty panel, or covers an important part of the page. Possible causes include overly long labels, a conflict with script optimization, an incorrectly assigned menu, or local CSS that overlaps other layers.

Check: Open the page while logged out and test the menu, a submenu item, search, and the close button. Repeat in another browser. Check that the menu is assigned to the right location and that the optimizer has not disabled theme scripts. Fix: First use shorter labels and correct the menu assignment. If a test confirms a conflict, exclude only the specific script or setting from optimization. To roll back, remove that exclusion or restore the previous optimization settings.

A video or background clip slows down the hero section

Symptom: The page stays blank for too long, the button appears after the background, a mobile browser shows a black area, or scrolling starts to stutter. A heavy video may be loading automatically, the same video may be embedded in several sections, or the background may not have a static alternative.

Check: Temporarily replace the video with one optimized image and compare the initial load. Check whether the hero section still makes sense without autoplay. Fix: Use a poster image, keep the play button, and defer loading heavy media where the selected block supports it. Rolling back is simple: restore the earlier video setting if it is needed and has been tested on the target devices.

The cart or add-to-cart feature is unstable

Symptom: A product is added, but the count does not change; the floating cart is empty; the button sends the request twice; or the item disappears after a reload. Don’t immediately blame the theme. This flow depends on WooCommerce, caching, JavaScript optimization, the theme, product settings, and the test environment.

Check: Use one simple test product. Add it from the product page, reload, open the cart, and repeat the test on a phone. Temporarily exclude the cart and checkout pages from aggressive caching according to your cache settings. Fix: Make sure WooCommerce and the required plugins are active, then disable conflicting optimizations one at a time on a staging copy. If a change makes things worse, restore the previous setting and record what you tested.

A local customization disappeared after an update

Symptom: A color, margin, or template change worked, but reverted after a theme update. The most likely cause is that the change was made directly in the parent theme. WordPress recommends child themes to preserve independent changes during parent theme updates.

Check: Find the changed file and check whether a child theme is active. Fix: Move only your documented customizations into the child theme or built-in CSS field. Do this on a staging copy first, then update the parent theme and check the result again. To roll back, temporarily activate the original theme or remove the added rule from the child theme.

The admin dashboard shows errors or the import does not finish

Symptom: Installing recommended plugins gets stuck, the import stops, WordPress displays a technical notice, or some media does not appear. Possible causes include insufficient server resources, upload limits, directory permissions, a conflicting plugin, or a network request blocked by the host.

Check: Review Tools → Site Health, the hosting error log, and permissions for the uploads directory. Compare with a minimal set of plugins on a staging copy. Fix: Work with your hosting administrator to address the specific infrastructure warning, run the import once more, and check the objects it created. Don’t repeat the import many times, as that may create duplicate pages, menus, and media.

Common questions about using Horr

Can I use Horr for just one game page?

Yes, if you still want WordPress as a foundation for news, media, and future updates. You do not need a complex hierarchy. Keep the homepage, game page, media library, contact page, and, if useful, a blog. The theme’s strengths will show in the hero section, video, visual pacing, and navigation, not in the number of published sections.

Do I have to import the demo content?

No. Importing is a quick way to see the layout, ready-made blocks, and menu connections, but it creates content you will need to clean up. If you already have a clear structure and experience with the WordPress editor, you can build the pages yourself. If you are new to it, import on a staging copy and replace the content gradually.

Can I use my own logo in the preloader?

The theme advertises a preloader screen with a custom logo. Use it only if the brief pause is justified by the content loading and the logo remains readable on a dark background. Don’t make the preloader artificially slow for effect. After setting it up, test the site on a slow connection so visitors can tell that the page is loading rather than stuck.

Is the theme suitable for a store?

Horr advertises WooCommerce compatibility and tools for the cart, adding products, and product galleries. That is enough for a small themed catalog, but you still need to prepare the store in the usual way: configure the currency, taxes, shipping, digital delivery, returns, email, and a test order. Start with one test product and check the full flow before expanding the catalog.

Should I enable the custom cursor, animations, and scroll progress?

No. These features add personality; they are not required for a correct installation. Enable only effects that support the story without hurting readability, accessibility, or speed. If you are unsure, start without the effect, compare the site on a mobile screen, and add it later if you see a clear benefit.

Why does the menu look unchanged after I save it?

First make sure you are editing the menu or navigation block used in the header. Then check the menu location, confirm that the change was saved, and clear the cache. The settings path may differ between block-based and classic configurations, but the principle is the same: creating a menu is not enough; it must be assigned to a visible part of the site.

How can I keep my customizations after an update?

Use a child theme for CSS, overrides, and small extensions. Use the theme’s built-in settings for the design options they already provide. Before updating, create a backup and capture screenshots of key pages. After the update, check the header, hero section, post page, cart, and mobile menu, since changes to the theme are most likely to show up there.

Can I use a demo as an exact copy of my future site?

No. A demo shows the layout and style, but its text and images may belong to someone else or may not suit your audience. Your project needs its own covers, messages, categories, contact information, policies, and properly licensed materials. A copied storefront often looks convincing until someone asks what is actually in it.

When ThemeForest Horr is the right choice

ThemeForest Horr works best when visual atmosphere and content structure support each other. It provides a foundation for a game page, horror blog, media library, or compact store, but the result depends on editorial discipline: one goal for the hero section, clear navigation, original materials, a limited number of effects, regular mobile checks, and customizations kept out of the parent theme files.

Start with a staging copy, import or build only the framework your project needs, and check the site after each major change. Once visitors can tell where to go, what to watch, and why to come back, you can download the ThemeForest Horr package and prepare it for your project.