Download the PHP package humanmade/hm-juicer without Composer
On this page you can find all versions of the php package humanmade/hm-juicer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download humanmade/hm-juicer
More information about humanmade/hm-juicer
Files in humanmade/hm-juicer
Package hm-juicer
Short Description Integrates with Juicer API for social feeds and allows accessible display of social media content.
License GPL-3.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package hm-juicer
HM Juicer
Integrates with Juicer API for social feeds and allows accessible display of social media content.
Installation
With Git
Step 1
cd into your desired directory (either wp-content/plugins or wp-content/mu-plugins) and clone the repository locally.
With Composer
Install the plugin via composer.
Vendor packages are installed as WordPress plugins and will need to be activated manually from the Plugins page (or explicitly loaded if installing as a mu-plugin).
For both: Configure environment
You may want to define environment variables that define your Juicer account and your site name and URLs. All of these are optional, but if any of them are not defined, a Settings page will appear in your admin to define these settings.
Step 1
Add the Juicer feed name to the wp-config.php file via the JUICER_ID constant.
This is the ID that is used in your Juicer feed URL, e.g. https://www.juicer.io/feeds/myaccountname.
Step 2
Define your site name. This will affect how links appear in the Juicer feed.
Step 3
Add the Juicer long and short URLs. This is used to determine links that are coming from your site.
Note: While the short URL is intended for URL shorteners like a custom URL or a service like bit.ly, this can be any URL that links back to your site.
For both: Install dependencies
There are a number of dependencies that need to be installed if you are going to be using the Juicer plugin for development. At this time, this also needs to be done if you are not defining the constants above. To do this, cd into the directory and run the setup command.
Usage
To add the Juicer feed to a page, simply use the function juicer_feed in your template with the correct number of posts to display (and optionally, the page to display from). Documentation on the juicer_feed function is available in the inc/README.md file.
Credits
Created by Human Made to render and display accessible social media feeds via the Juicer API.
Maintained by Chris Reynolds.
Contributors:
This plugin depends on these libraries/technologies by some awesome developers:
Contributing
If you want to contribute, you'll need to get your local environment setup. We've provided an easy setup script to get all the NPM dependencies and any required Composer dependencies installed. Simply run the following command after checking out the repository and cding into it:
In order to run unit tests locally, you'll need to make sure that you have a local version of PHP and MySQL/MariaDB installed (or run inside a virtual machine/Docker container). If your machine meets the requirements, you can run this command to get unit tests set up in your environment:
(This is not run as part of the normal setup script because not every environment will support it.)
The development process follows the standard Human Made development process.
Here's a quick summary:
- Assign issues you're working on to yourself.
- Work on a branch per issue, something like
name-of-feature. One branch per feature/bug, please. - File a PR early so it can be used for tracking progress.
- When you're finished, mark the PR for review by labelling with "Reviewer Needed".
- Get someone to review your code, and assign to them; if no one is around, the project lead can review.
Made with ❤️ by Human Made
