Hi. I'm a starter theme called _s, or underscores, if you like. I'm a theme meant for hacking so don't use me as a Parent Theme. Instead try turning me into the next, most awesome, WordPress theme out there. That's what I'm here for.

Related tags

Awesome WordPress _s
Overview

Build Status

_s

Hi. I'm a starter theme called _s, or underscores, if you like. I'm a theme meant for hacking so don't use me as a Parent Theme. Instead try turning me into the next, most awesome, WordPress theme out there. That's what I'm here for.

My ultra-minimal CSS might make me look like theme tartare but that means less stuff to get in your way when you're designing your awesome theme. Here are some of the other more interesting things you'll find here:

  • A modern workflow with a pre-made command-line interface to turn your project into a more pleasant experience.
  • A just right amount of lean, well-commented, modern, HTML5 templates.
  • A custom header implementation in inc/custom-header.php. Just add the code snippet found in the comments of inc/custom-header.php to your header.php template.
  • Custom template tags in inc/template-tags.php that keep your templates clean and neat and prevent code duplication.
  • Some small tweaks in inc/template-functions.php that can improve your theming experience.
  • A script at js/navigation.js that makes your menu a toggled dropdown on small screens (like your phone), ready for CSS artistry. It's enqueued in functions.php.
  • 2 sample layouts in sass/layouts/ made using CSS Grid for a sidebar on either side of your content. Just uncomment the layout of your choice in sass/style.scss. Note: .no-sidebar styles are automatically loaded.
  • Smartly organized starter CSS in style.css that will help you to quickly get your design off the ground.
  • Full support for WooCommerce plugin integration with hooks in inc/woocommerce.php, styling override woocommerce.css with product gallery features (zoom, swipe, lightbox) enabled.
  • Licensed under GPLv2 or later. :) Use it to make something cool.

Installation

Requirements

_s requires the following dependencies:

Quick Start

Clone or download this repository, change its name to something else (like, say, megatherium-is-awesome), and then you'll need to do a six-step find and replace on the name in all the templates.

  1. Search for '_s' (inside single quotations) to capture the text domain and replace with: 'megatherium-is-awesome'.
  2. Search for _s_ to capture all the functions names and replace with: megatherium_is_awesome_.
  3. Search for Text Domain: _s in style.css and replace with: Text Domain: megatherium-is-awesome.
  4. Search for  _s (with a space before it) to capture DocBlocks and replace with:  Megatherium_is_Awesome.
  5. Search for _s- to capture prefixed handles and replace with: megatherium-is-awesome-.
  6. Search for _S_ (in uppercase) to capture constants and replace with: MEGATHERIUM_IS_AWESOME_.

Then, update the stylesheet header in style.css, the links in footer.php with your own information and rename _s.pot from languages folder to use the theme's slug. Next, update or delete this readme.

Setup

To start using all the tools that come with _s you need to install the necessary Node.js and Composer dependencies :

$ composer install
$ npm install

Available CLI commands

_s comes packed with CLI commands tailored for WordPress theme development :

  • composer lint:wpcs : checks all PHP files against PHP Coding Standards.
  • composer lint:php : checks all PHP files for syntax errors.
  • composer make-pot : generates a .pot file in the languages/ directory.
  • npm run compile:css : compiles SASS files to css.
  • npm run compile:rtl : generates an RTL stylesheet.
  • npm run watch : watches all SASS files and recompiles them to css when they change.
  • npm run lint:scss : checks all SASS files against CSS Coding Standards.
  • npm run lint:js : checks all JavaScript files against JavaScript Coding Standards.
  • npm run bundle : generates a .zip archive for distribution, excluding development and system files.

Now you're ready to go! The next step is easy to say, but harder to do: make an awesome WordPress theme. :)

Good luck!

Comments
  • add (very basic) sass to _s

    add (very basic) sass to _s

    We here at WebDevStudios love _s, but one of us always has to "Sassify" it. I wanted to share our basic setup, in hopes that others find it helpful - or maybe encourage some folks to give Sass a try.

    I kept it basic by splitting up each section into partials, added a few variables, and one REM mixin. Would love others to pitch in and expand!

    Note: I did not include style.css, since after being compiled, it changes the indentation.

    opened by gregrickaby 89
  • Make dropdown menus accessible by tabbing

    Make dropdown menus accessible by tabbing

    Hello, following on from issue #523 I'm submitting a possible javascript solution to making the dropdown menus in _s tabable (currently dropdowns aren't visible when you tab through the child links). As it's quite a big addition I've broken it down below:

    Summary of changes

    navigation.js

    My additions to navigation.js attempt to replicate this code from Twenty Fourteen, only without the use of jQuery. When a link in a menu is focussed the class .focus is added to the ancestors of the link, and when blurred it's removed again. This can be targeted with css to keep the appropriate menus visible. Thanks to @joshmcrty for input on combining this with the existing code.

    Note I did include one slight difference from the Twenty Fourteen code: The original adds .focus to every ancestor all the way up to the HTML tag, whereas I have included checks to only include li elements within the current menu systems.

    style.css

    To every :hover selector in the menu section I've added an equivalent .focus selector, reflecting the fact that we want tabbing through menus to be visually as close as possible to using the mouse.

    Limitations

    Currently this code uses the variable menu previously defined in the navigation toggle code. This is efficient, but does make it relativley complicated for theme authors to add tabbing support to multiple menus. If desired I can adjust this code to work from a separate array of menu IDs.

    opened by chrisdc 53
  • Menu: Renamed

    Menu: Renamed "Primary Menu" to "Primary Location" to avoid confusion for users

    In the tests run on WordPress.com we identified that themes are using “Menu” when they mean “Location” and this is a factor that contributes in confusing the users. In WordPress UI copy the “Menu” is a different object from “Location”.

    For example, wp-admin tabs are labelled clearly in this way:

    screen shot 2015-03-24 at 10 21 30

    The result is simple. This is how it was before:

    screen shot 2015-03-24 at 10 20 58

    And here's after the patch:

    screen shot 2015-03-24 at 10 21 52

    Has Patch 
    opened by folletto 37
  • Re-organize SASS structure

    Re-organize SASS structure

    While talking with several developers I sometimes get feedback that sass folder structure is complicated and hard to manage. I tend to agree.

    I investigate this more and suggest small tweaks that we might do.

    Sass Help wanted 
    opened by samikeijonen 35
  • CSS: Add package.json for linting and compiling

    CSS: Add package.json for linting and compiling

    This is obviously a first pass since it hasn't really been discussed or tested beyond my Linux desktop. But I think it could help to guide and keep uniform some of the SCSS/CSS and JS commits. A package.json would give us an agnostic build process. https://github.com/Automattic/_s/issues/1149 It's just node, which is what our CSS/JS development tools are built for. https://github.com/WordPress-Coding-Standards/stylelint-config-wordpress https://github.com/WordPress-Coding-Standards/eslint-config-wordpress

    According to the NPM docs it serves 3 main purposes:

    1. It serves as documentation for what packages your project depends on.
    2. It allows you to specify the versions of a package that your project can use using semantic versioning rules.
    3. Makes your build reproducible which means that its way easier to share with other developers.

    This file could also, I think, take the place of and hopefully allow removal of the .jscsrc and .jshintignore files in the repo. Might be time to switch to ESLint anyway. JSCS was merged into ESLint over a year ago https://core.trac.wordpress.org/ticket/31823

    Here's how it works for anybody wanting to submit a CSS pull-request: From the _s/ root directory in the command line: first npm install or yarn then npm run build:css or yarn build:css And that's it. They've linted the style.css for errors, compiled the SCSS, added prefixes according to the specified browser support, and automatically fixed some errors with the remaining errors printed in the terminal for manual fixing.

    You can replace build:css with any of the other "scripts" commands listed in the file.

    Second Opinion 
    opened by m-e-h 34
  • Tools to build CSS from Sass

    Tools to build CSS from Sass

    We have previously discussed build tools for the CSS from Sass. In 2014 we decided against as we wanted to keep _s tool agnostic. #585, #1097, #1002, #661

    we will probably revisit once Automattic/underscores.me#31 got resolved

    As it has been 2.5 years since that discussion I would like to propose a different solution.

    Before merging pull requests related to CSS we need to be able to test that the Sass to CSS conversion is working properly. To be able to this properly every maintainer would need to have create a build tasks locally. Which is related to a previous discussion #615

    What I propose we document the following command which does that without needing grunt or gulp or any other build system.

    node-sass --include-path scss sass/style.scss style.css --output-style=expanded --indent-type=tab --indent-width=1

    The only requirements for this is node and npm install node-sass which most developers are already using.

    After running this command I got the following changes. I have removed some of the code style changes that have not been factored in. I think adding another check to travis for CSS code styling is another issue that we should look at in another issue. Partially mentioned in #1146 and previously discussed in #936

    --- style.css
+++ style.css
@@ -49,7 +49,7 @@ Nicolas Gallagher and Jonathan Neal http://necolas.github.io/normalize.css/
 html {
        font-family: sans-serif;
        -webkit-text-size-adjust: 100%;
-       -ms-text-size-adjust:     100%;
+       -ms-text-size-adjust: 100%;
 }

 body {
@@ -426,7 +426,7 @@ input[type="submit"] {
        border-color: #ccc #ccc #bbb;
        border-radius: 3px;
        background: #e6e6e6;
-       color: rgba(0, 0, 0, .8);
+       color: rgba(0, 0, 0, 0.8);
        font-size: 12px;
        font-size: 0.75rem;
        line-height: 1;
@@ -473,10 +473,6 @@ textarea {
        padding: 3px;
 }

-select {
-       border: 1px solid #ccc;
-}
-
 input[type="text"]:focus,
 input[type="email"]:focus,
 input[type="url"]:focus,
@@ -496,6 +492,10 @@ textarea:focus {
        color: #111;
 }

+select {
+       border: 1px solid #ccc;
+}
+
 textarea {
        width: 100%;
 }
@@ -546,16 +546,6 @@ a:active {
        padding-left: 0;
 }

-.main-navigation li {
-       float: left;
-       position: relative;
-}
-
-.main-navigation a {
-       display: block;
-       text-decoration: none;
-}
-
 .main-navigation ul ul {
        box-shadow: 0 3px 3px rgba(0, 0, 0, 0.2);
        float: left;
@@ -570,24 +560,13 @@ a:active {
        top: 0;
 }

-.main-navigation ul ul a {
-       width: 200px;
-}
-
-.main-navigation ul ul li {
-
-}
-
-.main-navigation li:hover > a,
-.main-navigation li.focus > a {
-}
-
-.main-navigation ul ul :hover > a,
-.main-navigation ul ul .focus > a {
+.main-navigation ul ul li:hover > ul,
+.main-navigation ul ul li.focus > ul {
+       left: 100%;
 }

-.main-navigation ul ul a:hover,
-.main-navigation ul ul a.focus {
+.main-navigation ul ul a {
+       width: 200px;
 }

 .main-navigation ul li:hover > ul,
@@ -595,15 +574,14 @@ a:active {
        left: auto;
 }

-.main-navigation ul ul li:hover > ul,
-.main-navigation ul ul li.focus > ul {
-       left: 100%;
+.main-navigation li {
+       float: left;
+       position: relative;
 }

-.main-navigation .current_page_item > a,
-.main-navigation .current-menu-item > a,
-.main-navigation .current_page_ancestor > a,
-.main-navigation .current-menu-ancestor > a {
+.main-navigation a {
+       display: block;
+       text-decoration: none;
 }

 /* Small menu. */
@@ -818,7 +796,7 @@ object {
 }

 /* Make sure logo link wraps around logo image. */
-.custom-logo-link{
+.custom-logo-link {
        display: inline-block;
 }
    Work in Progress 
    opened by grappler 32
  • Add editor-style.css to _s?

    Add editor-style.css to _s?

    The editor-style.css file is far and away one of the best ways to improve a site editor's experience (at least in my experience). It makes TinyMCE much WYSIWYGier(TM) and helps users understand the connection between a theme and typography styles.

    So in that vein, I'd love to see _s add editor-style.css by default to the theme. Thinking through this, I believe that would involve doing the following:

    1. Add add_editor_style(); to functions.php
    2. Add an editor-style.css file to the theme's root and include a brief description and link to documentation in a comment.
    3. Add an editor-style.scss file to the /sass/ folder that includes the same comments as above AND @imports helpful partials including:
      • everything in /sass/typography/
      • everything in /sass/elements/
      • everything in /sass/modules/
      • normalize
      • all requires mixins and variables partials to make the above compile

    I've taken the approach in #3 with my own themes on multiple sites and have found a lot of success in autogenerating a nearly-complete set of editor styles. I don't know the _s SASS setup that well, so some input on that would be useful.

    I thought a discussion would be worthwhile before submitting a pull request, so please let me know what you think. As far as I can tell, this hasn't been considered before.

    Has Patch 
    opened by mrwweb 31
  • Use em instead of px for menu media query

    Use em instead of px for menu media query

    Using em instead of px preserves proportions across a wider range of browsers and devices for the responsive nav menu when users zoom. See http://blog.cloudfour.com/the-ems-have-it-proportional-media-queries-ftw/

    opened by joshmcrty 31
  • White screen in Safari and mobile Safari

    White screen in Safari and mobile Safari

    Hi,

    I have had an issue with safari and mobile safari on two recently built sites. You could only see blank white screen in it although in other browsers everything was working fine.

    It was ok after we removed CSS lines, for clearing:

    /* Clearing */
.clear:before,
.clear:after,
[class*="content"]:before,
[class*="content"]:after,
[class*="site"]:before,
[class*="site"]:after {
    content: '';
    display: table;
}

.clear:after,
[class*="content"]:after,
[class*="site"]:after {
    clear: both;
}

    I'm not sure why this is happening in Safari. Something with the way we built our theme?

    Thanks

    opened by ip00 27
  • Bringing back ARIA roles?

    Bringing back ARIA roles?

    We removed ARIA roles in #1132. But WAI-ARIA 1.1 and HTML 5.1 specifications have been updated. This is the biggest change for ARIA roles:

    <header> and <footer> elements will now only be exposed as header and footer, and banner and ContentInfo landmarks respectively, if these elements are direct descendants of the body tag, and therefore are scoped for the whole page.

    In _s header and footer are not direct descendants of the body tag, they are inside #page wrapper.

    My question is, should we bring back <header role="banner"> and <footer role="contentinfo">?

    Here is more information about the ARIA roles subject.

    Second Opinion Has Patch 
    opened by samikeijonen 26
  • Submenus not working/showing in _s responsive menu

    Submenus not working/showing in _s responsive menu

    Hello,

    I'm using the _s theme, and noticed that the submenu items are not showing on the built-in responsive menu.

    I haven't been able to find any threads noting similar issues online, but thought I'd check to see if this was a common issue, or one that was known and/or hopefully easily resolved.

    My html looks like this:

    <nav id="site-navigation" class="main-navigation" role="navigation">
<h1 class="menu-toggle"><?php _e( 'Menu', 'mytheme_s' ); ?></h1>
<a class="skip-link screen-reader-text" href="#content"><?php _e( 'Skip to content', 'mytheme_s' ); ?></a>
<?php wp_nav_menu( array( 'theme_location' => 'primary' ) ); ?>
</nav><!-- #site-navigation -->

    i'm not 100% sure whether i've changed anything in my css to affect this, but was wondering if there was something obvious i ought to consider when using submenus with the built-in responsive menu?

    Thanks in advance of any thoughts and advice.

    PS) I am also curious what this line of code does/means:

    <a class="skip-link screen-reader-text" href="#content"><?php _e( 'Skip to content', 'shanti_s' ); ?></a>
    opened by kat2014 26
  • Deprecated npm packages

    Deprecated npm packages

    Upon installation I did recieved a lot of warning about deprecated npm packages.

    This is the output i received:

    npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16' },
npm WARN EBADENGINE   current: { node: 'v18.12.1', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@es-joy/[email protected]',
npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16' },
npm WARN EBADENGINE   current: { node: 'v18.12.1', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated @stylelint/[email protected]: Use the original unforked package instead: postcss-markdown
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

added 1588 packages, and audited 1589 packages in 4m

219 packages are looking for funding
  run `npm fund` for details

11 vulnerabilities (3 moderate, 8 high)
    opened by c4chale 1
  • Parent Link not clickable to the link in

    Parent Link not clickable to the link in

    The Parent menu like wwww.example.com/products is not clickable to the link that displays the page on desktop. Like in the example quoted, the links displays all the products on desktop ... but in the mobile the link doesn't work ... instead toggles the sub-menu. Need a fix on the same. Probable issue with Navigation.js

    opened by mahendrakumbhar 1
  • Help ME PLEASE!

    Help ME PLEASE!

    About 4 years ago, possibly longer, my former boss's son created a website for my businesses using your coding and basic template - www.michellesantiqueappraisals.com

    It was great, looked amazing, and functioned.

    About 9 months ago the inserted text on the home page vanished and the "submit appraisal" form no longer works.

    I have paid quite a bit of money to get it fixed and no one knows what to do. Finally, I determined that 1) Bootstrap is outdated 2) I noticed that y'all have updated some code and that needs to be done on my site.

    It is built in WordPress and I have no idea where Boostrap is much less how to update it. I would like to do away with all of that and go with a stock template with some customization in color and function.

    I have two businesses online and I just don't have the time to keep up with Bootstrap. I have tried to just apply a different template and it creates a "critical error." Basically, my website vanishes.

    Any guidance that you can give me would be a great help. The slider at the top of the page needs to go but even deleting it makes the first page wonky.

    Thank you so much for any assistance. The man who built the site doesn't respond to my calls for help and I need the $$ that the page used to generate.

    Thank you, Michelle

    opened by grannysantiques 17
  • the_content doesn't work for displaying single posts

    the_content doesn't work for displaying single posts 

    	<?php
	while ( have_posts() ) :
		the_post();

		get_template_part( 'template-parts/content', get_post_type() );

		
	endwhile; // End of the loop.
	?>

</main><!-- #main -->
    opened by sunilsingh2019 0
  • Changing Page Title Tags from H2 to H1 - Please Help!

    Changing Page Title Tags from H2 to H1 - Please Help!

    Hi there!

    I need to change the home page and inner page title tags to H1 from H2. Currently they are H2 but how can I change it to H1?

    Do I need to edit the theme code? How do you I do that?

    opened by haideraides 0
  • fix php comment, remove php tag

    fix php comment, remove php tag

    With this, it is very easy for developer to add new custom header, they will simple uncomment the LINE 7.

    Changes: -Removed PHP Tag opening and closing (Since it is already opened at top) -Add comment asterisk

    Changes proposed in this Pull Request:

    Related issue(s):

    opened by adminazhar 0
Owner
Automattic
We are passionate about making the web a better place.
Automattic
GitHub http://underscores.me/
A curated list of Awesome WordPress Theme, Plugins and Framework development Resources and WordPress Communities.

Awesome WordPress A curated list of Awesome WordPress Theme, Plugins and Framework development Resources and WordPress Communities. Inspired by bayand

Dropndot Limited 91 Dec 26, 2022
This WordPress Plugin Boilerplate is meant for you to develop your own plugin on.

WordPress Plugin Boilerplate This plugin boilerplate is meant for you to develop your own plugin on. Support & collaboration Features OOP plugin core

richardev 2 May 10, 2022
Awesome Enterprise - a shortcode based low code platform for PHP and WordPress.

Awesome Enterprise Framework Awesome Enterprise is a shortcode based low code platform for PHP and WordPress. You can set it up using composer compose

WPoets - Your WordPress Experts 10 Nov 17, 2022
The most powerful all in one, SEO-friendly theme for WordPress.

Help us Become a backer via Patreon. Make one time donation with PayPal. About Seven SERP Theme Seven SERP Theme is an open source WordPress theme. Wi

Seven SERP 3 Nov 19, 2021
:rocket: Next Generation Template / Theme Framework

Gantry Framework Ready to get started with Gantry 5? That's great! We are here to help. On this page, you will get some quick tips to help you hit the

Gantry Framework 979 Dec 31, 2022
WordPress & TypeScript. Simple starter template for WordPress projects

WordPress & TypeScript. Simple starter template for WordPress projects that want to use TypeScript in combination with @wordpress/scripts

Make it WorkPress 11 Sep 27, 2022
WordPress plugin that lets you use Discourse as the community engine for a WordPress blog

WP Discourse Note: the wp-discourse plugin requires >= PHP-5.4.0. The WP Discourse plugin acts as an interface between your WordPress site and your Di

Discourse 497 Dec 10, 2022
WordPress plugin working (almost) like a child theme.

Step child Description TL;DR: WordPress plugin working (almost) like a child theme. Sometimes the project you're thrown into doesn't have a child them

Johan Jonk Stenström 2 Jun 10, 2022
WordPress Plugin that Boost CTR. Improve SEO & Rankings. Supports most of the content type. Works perfectly with Google, Bing, Yahoo & Facebook.

WordPress Plugin that Boost CTR. Improve SEO & Rankings. Supports most of the content type. Works perfectly with Google, Bing, Yahoo & Facebook.

Brainstorm Force 109 Dec 19, 2022
Wordless is a junction between a WordPress plugin and a theme boilerplate that dramatically speeds up and enhances your custom theme creation

Wordless is a junction between a WordPress plugin and a theme boilerplate that dramatically speeds up and enhances your custom theme creation. Some of

weLaika 1.4k Dec 9, 2022
A custom WordPress nav walker class to fully implement the Twitter Bootstrap 4.0+ navigation style (v3-branch available for Bootstrap 3) in a custom theme using the WordPress built in menu manager.

WP Bootstrap Navwalker This code in the main repo branch is undergoing a big shakeup to bring it in line with recent standards and to merge and test t

WP Bootstrap 3.3k Jan 5, 2023
Twenty Twenty-Two, the default WordPress theme that will launch with WordPress 5.9.

Twenty Twenty-Two Welcome to the development repository for the default theme that will launch with WordPress 5.9. About Twenty Twenty-Two is designed

null 414 Nov 28, 2022
Manuel Monteiro WP Starter Theme

_s Hi. I'm a starter theme called _s, or underscores, if you like. I'm a theme meant for hacking so don't use me as a Parent Theme. Instead try turnin

Manuel 1 Oct 25, 2021
Simple WordPress plugin starter framework.

WordPress Plugin Starter This is the official WordPress plugin starter framework for Highfivery. The purpose behind it is to improve the quality of th

Highfivery LLC 5 Oct 27, 2022
The Pronamic WordPress Basecone plugin allows you to connect your WordPress installation to Basecone.

Pronamic WordPress Basecone The Pronamic WordPress Basecone plugin allows you to connect your WordPress installation to Basecone. Table of contents Au

Pronamic 1 Oct 19, 2021
🚀WordPress Plugin Boilerplate using modern web techs like TypeScript, SASS, and so on... on top of a local development environment with Docker and predefined GitLab CI for continous integration and deployment!

WP React Starter: WordPress React Boilerplate DEPRECATED: WP React Starter was a "research project" of devowl.io for the development of our WordPress

devowl.io GmbH 344 Jan 1, 2023
Wordpress advance plugin with multi purposes features like live chat, custom post type, custom forms, word count etc

What is this? This is wordpress plugin which is created for the multi purpose uses. How to use? Simply install the plugin. Go to the plugin settigs pa

Amir Liaqat 2 Jun 23, 2022
Integrating Laravel into WordPress

WordPress Laravel Bootstrap A WordPress plugin helps you use functions, methods, libraries of Laravel in any WordPress projects Requiments Laravel >=

Duc Le 54 Feb 15, 2022
A tool box of integrations for Cardano & WordPress all packaged into a neat plugin.

CardanoPress A tool box of integrations for Cardano & WordPress all packaged into a neat plugin. This plugin allows you to integrate various Cardano b

Peter Bui 38 Oct 4, 2022