mtheme.markets.Explore the catalog ↗
← THEME LIBRARY

Attika

WordPress theme

Attika is Mikado Themes' WPBakery restaurant theme, and its restaurant-specific work sits in shortcodes: a menu list, a menu popup, a reservation form and popup, and working hours. The article covers what those elements let you build, how the OpenTable reference changes the booking picture, what the social feed removals in the 1.7 changelog mean, and where the vendor's bundled-plugin claims stop and the marketplace file list begins.

Updated November 5, 2026 · theme.markets editorial team

The restaurant features are shortcodes, not a single restaurant page

Plenty of restaurant themes ship a demo menu page and call it done. Attika's feature list instead names small, repeatable elements: Restaurant Menu List, Menu Popup, Reservation Popup, Reservation Form and Working Hours. That distinction matters more than it first appears.

A menu list shortcode is content you can place anywhere: on a home page as a teaser, inside a seasonal page, in a side area. The popup variant opens the same information without sending a visitor to a second URL. Working Hours is a piece of text that changes the page it sits on depending on where you put it, which is how most restaurants actually want to show opening times — above the fold on the contact page, in a footer column, next to a reservation prompt.

In practice you are building a set of reusable blocks rather than filling predefined restaurant templates. If your site plan involves several menus — lunch, dinner, tasting, drinks — that is a better fit than a theme that gives you one menu layout to adapt.

Everything in this section comes from the vendor's own feature list. The theme's demo at the vendor's landing URL is where you would see the elements in place.

Reservations run through OpenTable, with the popup as the on-page prompt

The vendor description says Attika includes the OpenTable plugin and that a Reservation Popup has been added to the Restaurant page. Read together with the Reservation Form shortcode, that describes two distinct pieces: something on your site that invites a booking, and a third-party service that takes it.

The practical consequence is straightforward. If the restaurant already uses OpenTable, the theme's job is presentation — the popup, the form, the working hours beside them — and the booking record, availability and confirmations stay with the platform you already pay for. If you were hoping for a self-contained booking engine with seat limits, deposits or table management inside WordPress, that is not what this element set describes. A Reservation Form shortcode is a form, and the vendor does not claim more for it.

Worth checking against your own setup before committing: how the popup and form are configured to point at your OpenTable account, and whether the demo's reservation flow matches the one your venue needs. The vendor names OpenTable explicitly, so treat the reservation feature as a handoff rather than a waitlist or cover-management system.

What version 1.7 removed, and why the social feeds are now external

The most useful part of Attika's changelog is not the list of additions. The current release, 1.7, records two removals: the Attika Twitter Feed plugin and the Attika Instagram Feed plugin, both cited against API changes at the respective platforms.

That is not a quiet deprecation. Earlier entries show both plugins had been actively maintained — version 1.5 updated the Instagram Feed to 2.0.1 and the Twitter Feed to 1.0.2, and version 1.6 fixed the Twitter Feed API connection. The theme had invested in displaying feeds natively, and that route closed with the platform APIs.

For a restaurant site, the consequence is concrete. A feed of recent dishes or a stream of tagged guest photos will not come from a bundled theme plugin. Plan on a current feed plugin, an embed block or a widget that maintains its own API credentials. The theme's feature list still mentions Twitter and Instagram social widgets alongside a Social Icons Group widget, but the changelog is the more recent statement — and the place to look when deciding how your social presence gets onto the page.

Header types and one-page anchors shape how visitors move

Attika lists five header types — Standard, Minimal, Divided, Bottom and Vertical — plus separate logo variants for dark and light header skins and a further logo slot for the mobile header. For a venue, that is a decision about where the navigation sits against food photography, not a cosmetic toggle. A minimal header keeps the hero image dominant; a divided or vertical header gives a persistent strip of links for a multi-page site.

The vendor also lists anchor link functionality for one page sites, which pairs naturally with a restaurant site of six or seven sections: about, menu, gallery, hours, reservations, contact. Combined with parallax sections and video background sections, the theme's described structure leans toward a scrolling, image-led single page or a short multi-page site rather than a large content archive.

Eight homepage examples are listed, which is the vendor's count rather than a promise that each suits your cuisine. Look at the demo before assuming a layout will carry your menu length.

Bundled plugins in the vendor description, code files in the marketplace list

The vendor states that Slider Revolution is included with a stated value of $26 and WPBakery Page Builder with a stated value of $46. Those are the vendor's claims about what shipping with the theme means, and they describe the editing surface: pages composed with WPBakery elements and heroes built in Slider Revolution.

The marketplace's own file field is narrower. It lists PHP Files, CSS Files and JS Files — no plugin archives and no layered design source. Treat the two statements as different kinds of information. The vendor says the plugins come with the theme; the file list describes the theme package's code contents. If plugin licensing or update rights for your install matter to you, confirm the arrangement rather than assuming a bundled copy updates itself.

Compatibility declarations, observed on 5 November 2026, list WordPress 6.5.x through 7.0.x, WooCommerce 9.x and 10.x, WPML and WPBakery. Those are vendor and marketplace claims, not results of running the theme on a particular host.

The maintenance record since 2023

Between version 1.6 in February 2023 and 1.7 in May 2026, the theme went without a listed release. The current entry then bundled a broad set of changes: WooCommerce 10.x compatibility, PHP 8.3 improvements, a new WPML config file, a Google Map API compatibility fix, updated WPBakery and Revolution Slider versions, refreshed countdown year options through 2032, and the two feed plugin removals.

Two things follow. First, if your stack is on a recent PHP version, the PHP 8.3 entry is the relevant line in the changelog. Second, the release gaps tell you the update cadence has been irregular rather than monthly, which is worth knowing when you plan how much of the site you build on theme-specific shortcodes versus portable content.

Attika suits a restaurant, bistro or chef site where WPBakery is an acceptable editing environment and the menu, hours and reservation prompts are best treated as reusable blocks. It is a weaker match if you want booking logic inside WordPress, or if a current Instagram feed is central to the design and you would rather it came bundled.

Questions & answers

Does Attika handle table bookings itself?

No. The vendor describes OpenTable as the reservation service and lists a Reservation Popup and Reservation Form among the theme's elements. The theme provides the on-page prompt; availability and booking records stay with the platform you connect.

Can I show an Instagram feed with Attika out of the box?

Version 1.7 removed the Attika Instagram Feed and Attika Twitter Feed plugins because of API changes at those platforms. Plan on a separate feed plugin or embed for social content. The feature list still names social widgets, but the changelog is the more recent statement.

Which page builder does Attika use?

WPBakery Page Builder, which the vendor states is included with the theme and lists at a stated value of $46. Slider Revolution is described the same way for slider content. The marketplace file field lists PHP, CSS and JS files only, so confirm plugin update arrangements for your own install.

Guides for this theme

Keep exploring

Alternatives to Attika

More themes with a similar focus. Find the approach that fits your project.

Also for restaurants · WPBakery

Barista

Barista is Edge Themes' WordPress theme for cafes, coffee shops and bars, and its most useful assets are venue-specific shortcodes — Cafe Menu, Working Hours, Item Showcase, Shop Masonry and pricing tables — placed inside WPBakery, which the vendor bundles alongside Slider Revolution. The article covers how those shortcodes build a menu-and-hours page, the second builder route through Elementor, the header and logo variants, and what the declared WordPress and WooCommerce ranges do and do not promise.

Explore details →
Also for restaurants · WPBakery

Chicago

Chicago, from WPCharming, leans on two operational systems rather than decoration: an event manager with recurring and multi-day events, multiple tickets, and booking approval or rejection with CSV export, plus a choice between handing reservations to OpenTable by ID or collecting them through the theme's own check-in date and time form. Four demo setups include two one-page builds, WPBakery and Slider Revolution ship with the theme, and recent changelog entries concentrate on WordPress and PHP compatibility.

Explore details →
Also for restaurants · WPBakery

Piquant

Piquant treats the menu as structured content: a Restaurant Menu custom post type rendered through list, gallery and carousel shortcodes, with either an on-site reservation form or an OpenTable handoff for bookings. A separate Restaurant page in the admin panel holds food-business settings, WPBakery and Revolution Slider are bundled for page assembly, and the vendor's changelog records the Instagram and Twitter feed plugins being removed after API changes.

Explore details →