Skip to content

Commit

Permalink
Ran PHPStorms reformat code to make future PRs more readable
Browse files Browse the repository at this point in the history
  • Loading branch information
alexoakland committed Jun 12, 2024
1 parent 55e77e6 commit 3e51d5a
Show file tree
Hide file tree
Showing 163 changed files with 18,213 additions and 17,295 deletions.
44 changes: 22 additions & 22 deletions .github/workflows/deploy-to-wp-org.yml
Original file line number Diff line number Diff line change
@@ -1,25 +1,25 @@
name: Deploy to WordPress.org
on:
push:
tags:
- "*"
push:
tags:
- "*"
jobs:
tag:
name: New tag
runs-on: ubuntu-latest
steps:
# Clone the repo
- uses: actions/checkout@master
# Prepare the release
- run: ls
- run: "composer install --no-dev"
# Release to WordPress.org
- name: WordPress Plugin Deploy
id: deploy
uses: 10up/[email protected]
with:
generate-zip: true
env:
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SLUG: gathercontent-import
tag:
name: New tag
runs-on: ubuntu-latest
steps:
# Clone the repo
- uses: actions/checkout@master
# Prepare the release
- run: ls
- run: "composer install --no-dev"
# Release to WordPress.org
- name: WordPress Plugin Deploy
id: deploy
uses: 10up/[email protected]
with:
generate-zip: true
env:
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SLUG: gathercontent-import
42 changes: 21 additions & 21 deletions .jshintrc
Original file line number Diff line number Diff line change
@@ -1,25 +1,25 @@
{
"curly" : true,
"eqeqeq" : true,
"immed" : true,
"latedef" : true,
"newcap" : true,
"noarg" : true,
"sub" : true,
"undef" : true,
"boss" : true,
"eqnull" : true,
"validthis" : true,
"curly": true,
"eqeqeq": true,
"immed": true,
"latedef": true,
"newcap": true,
"noarg": true,
"sub": true,
"undef": true,
"boss": true,
"eqnull": true,
"validthis": true,
"globals": {
"exports" : true,
"module" : false,
"console" : true,
"require" : true,
"document" : true,
"jQuery" : true,
"wp" : true,
"Backbone" : true,
"_" : true,
"window" : true
"exports": true,
"module": false,
"console": true,
"require": true,
"document": true,
"jQuery": true,
"wp": true,
"Backbone": true,
"_": true,
"window": true
}
}
4 changes: 2 additions & 2 deletions Gruntfile.js
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ module.exports = function (grunt) {
var object = {};
var key;

glob.sync('*', {cwd: path}).forEach(function(option) {
key = option.replace(/\.js$/,'');
glob.sync('*', {cwd: path}).forEach(function (option) {
key = option.replace(/\.js$/, '');
object[key] = require(path + option);
});

Expand Down
46 changes: 35 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,15 @@ This plugin allows you to transfer content from your Content Workflow projects i

## Description ##

Installing our WordPress plugin on your site allows you to quickly perform updates of your content from your Content Workflow account to WordPress as well as push your WordPress content updates back to Content Workflow. Content can be imported as new pages/posts or custom post types, and you can also import your WordPress content back to new Content Workflow items.
Installing our WordPress plugin on your site allows you to quickly perform updates of your content from your Content
Workflow account to WordPress as well as push your WordPress content updates back to Content Workflow. Content can be
imported as new pages/posts or custom post types, and you can also import your WordPress content back to new Content
Workflow items.

The plugin allows you to map each field in your Content Workflow Templates with WordPress fields. This is accomplished by creating a Template Mapping, which allows you to map each field in Content Workflow to various fields in WordPress; title, body content, custom fields, tags, categories, Yoast fields, advanced custom fields, featured images … and many more.
The plugin allows you to map each field in your Content Workflow Templates with WordPress fields. This is accomplished
by creating a Template Mapping, which allows you to map each field in Content Workflow to various fields in WordPress;
title, body content, custom fields, tags, categories, Yoast fields, advanced custom fields, featured images … and many
more.

The module currently supports the following features:

Expand All @@ -17,7 +23,10 @@ The module currently supports the following features:

### What is Content Workflow?

Content Workflow is an online platform for pulling together, editing, and reviewing website content with your clients and colleagues. It's a reliable alternative to emailing around Word documents and pasting content into your CMS. This plugin replaces that process of copying and pasting content and allows you to bulk import structured content, and then continue to update it in WordPress with a few clicks.
Content Workflow is an online platform for pulling together, editing, and reviewing website content with your clients
and colleagues. It's a reliable alternative to emailing around Word documents and pasting content into your CMS. This
plugin replaces that process of copying and pasting content and allows you to bulk import structured content, and then
continue to update it in WordPress with a few clicks.

Connecting a powerful content production platform, to a powerful content publishing platform.

Expand All @@ -26,39 +35,54 @@ Connecting a powerful content production platform, to a powerful content publish
This section describes how to install the plugin and get it working.

### Downloading the plugin ###

1. To download the plugin, click the green "Code" button on the top right of this page.
2. Then click "Download ZIP".

For more information on how to download from GitHub please visit their [help page](https://docs.github.com/en/repositories/working-with-files/using-files/downloading-source-code-archives).
For more information on how to download from GitHub please visit
their [help page](https://docs.github.com/en/repositories/working-with-files/using-files/downloading-source-code-archives).

### Installing the plugin ###

1. Upload `content-workflow` to the `/wp-content/plugins/` directory
2. Activate the Content Workflow plugin through the 'Plugins' menu in WordPress
3. Click on the menu item "Content Workflow"
4. Link your accounts. You will need to enter your Content Workflow account URL (e.g. http://mywebsite.gathercontent.com) and your personal Content Workflow API key. You can find your API key in your [Settings area within Content Workflow](https://gathercontent.com/developers/authentication/).
4. Link your accounts. You will need to enter your Content Workflow account URL (
e.g. http://mywebsite.gathercontent.com) and your personal Content Workflow API key. You can find your API key in
your [Settings area within Content Workflow](https://gathercontent.com/developers/authentication/).

For more detailed installation instructions, please visit our [Help Centre](http://help.gathercontent.com/importing-and-exporting-content#wordpress-integration).
For more detailed installation instructions, please visit
our [Help Centre](http://help.gathercontent.com/importing-and-exporting-content#wordpress-integration).

## Support ##

If you need help, Please [visit our support documentation](http://help.gathercontent.com/importing-and-exporting-content#wordpress-integration).
If you need help,
Please [visit our support documentation](http://help.gathercontent.com/importing-and-exporting-content#wordpress-integration).

Also note, in your WordPress dashboard, under the Content Workflow menu item, you will see a Support page. On this page, you'll find a large textarea filled with technical information about your server, browser, plugin, etc. This information is very useful when debugging, and the Content Workflow support team may ask you for it at some point.
Also note, in your WordPress dashboard, under the Content Workflow menu item, you will see a Support page. On this page,
you'll find a large textarea filled with technical information about your server, browser, plugin, etc. This information
is very useful when debugging, and the Content Workflow support team may ask you for it at some point.

Below the text box is a button that will allow you to simply save all of that information to a .txt file. This allows you to easily deliver it to anyone who needs it.
Below the text box is a button that will allow you to simply save all of that information to a .txt file. This allows
you to easily deliver it to anyone who needs it.

**However**, this information contains potentially senstive data. Please be careful with where you post it. Do not post it in the WordPress support forums.
**However**, this information contains potentially senstive data. Please be careful with where you post it. Do not post
it in the WordPress support forums.

### Third-Party Services ###

This plugin relies on the following third-party services:

1. **Content Workflow**: This service is used for content management and synchronization between your WordPress site and Content Workflow. For more information, please visit [Content Workflow](https://www.bynder.com/en/products/content-workflow/). The [Terms of Service](https://gathercontent.com/legal/terms-of-service) and [Privacy Policy](https://www.bynder.com/en/legal/privacy-policy/) are available for review.
1. **Content Workflow**: This service is used for content management and synchronization between your WordPress site and
Content Workflow. For more information, please
visit [Content Workflow](https://www.bynder.com/en/products/content-workflow/).
The [Terms of Service](https://gathercontent.com/legal/terms-of-service)
and [Privacy Policy](https://www.bynder.com/en/legal/privacy-policy/) are available for review.

## Changelog

### 1.0.0 ###

* Officially supporting components by using the Advanced Custom Fields plugins
* Full rebrand to Content Workflow by Bynder
* Migration from the [GatherContent Wordpress plugin](https://wordpress.org/plugins/gathercontent-import/)
Loading

0 comments on commit 3e51d5a

Please sign in to comment.