methnen

Andrea Landonio

bheadrick

sburdett

CloudSearch is a flexible plugin that allows you to leverage the search index power of Amazon CloudSearch in your WordPress site. 
To use this plugin you’ll need an Amazon Web Services account. Attention: Amazon CloudSearch is a paid service and will require a credit card.
Before you can start using CloudSearch, the plugin needs to be activated and configured. Activate the plugin, then go to the menu “CloudSearch -> Settings” (you can find this menu in the sidebar of your WordPress admin panel). 
Fill the form data:
<ul>
<li>Enter Amazon access key ID, Amazon secret access key and Amazon region for your account (look for “Security Credentials” in your Amazon console to retrieve these data)</li>
<li>Enter your CloudSearch index search endpoint and the domain name (I suggest to create the CloudSearch index before you start the plugin configuration)</li>
<li>Schema settings</li>
<li>Other settings</li>
</ul>
IMPORTANT NOTES WITH RELEASE 2.0.0: 
* At least WordPress 4.4 version mandatory (for WP_Term support) 
* Changed APIs output from an array of IDs to an array of object composed by the entity ID and the entity type
Minimum requirements:
<ul>
<li>WordPress Version 4.4</li>
<li>PHP Version 5.3</li>
<li>Amazon Web Services account with CloudSearch enabled</li>
</ul>
<h4>Usage</h4>
<ol>
<li>Go to <code>CloudSearch -> Settings</code></li>
<li>Enter your <code>Amazon access key ID</code>, <code>Secret access key</code> and the <code>Amazon region</code> where you have created the CloudSearch index</li>
<li>Enter a <code>Search endpoint</code> and the <code>Domain name</code>. Get these info in your CloudSearch dashboard in AWS Console</li>
<li>Choose post types, custom fields and custom taxonomies that you want to export to the CloudSearch index</li>
<li>Set up other settings or leave defaults</li>
<li>Save settings.</li>
<li>Go to <code>CloudSearch -> Manage</code></li>
<li>Click the action <code>Create index</code>, <code>Run indexing</code> and <code>Sync all documents</code>. Between every action wait until the <code>Status</code> field is <code>Active</code>, then go on with the next task</li>
<li>After these operation your index is ready, now you can search documents in your CloudSearch index</li>
</ol>
Links: <a href="http://www.andrealandonio.it" rel="nofollow ugc">Author’s Site</a>

CloudSearch

This plugin works great and saved me a huge amount of time. The developer is also responsive and was quick to make improvements when I discovered an issue with the implementation.

Huge time saver and responsive developer

CloudSearch is a flexible plugin that allows you to leverage the search index power of Amazon CloudSearch in your WordPress site.

reefdog

freedmand

chrisamico

<a href="https://www.documentcloud.org/" rel="nofollow ugc">DocumentCloud</a> is a service that allows journalists to analyze, annotate and publish documents, hosted by Investigative Reporters & Editors. Initial development of this plugin supported by <a href="http://www.npr.org" rel="nofollow ugc">NPR</a> as part of the <a href="http://stateimpact.npr.org" rel="nofollow ugc">StateImpact</a> project.
This plugin allows you to embed DocumentCloud resources using either the raw URL on its own line:
<pre><code>Here's something you should really take a look at:

https://www.documentcloud.org/documents/282753-lefler-thesis.html

Isn't that interesting?
</code></pre>
Or a custom shortcode:
<pre><code>[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html"]
</code></pre>
When you save, WordPress fetches and stores the actual embed code HTML from the DocumentCloud servers using oEmbed. You can freely toggle between visual and HTML mode without mangling embed code, and your embed will always be up to date with the latest embed code.
By default, documents will have a responsive width (it will narrow and widen as necessary to fill available content area) and use the theme’s default height. If you want to override this, you can either set <code>responsive="false"</code> or explicitly set a <code>width</code>:
<pre><code>[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html" width="600"]
</code></pre>
You can set your own defaults in Settings > DocumentCloud, but default widths will be ignored unless <code>responsive</code> is disabled:
<pre><code>[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html" responsive="false"]
</code></pre>
To embed a single page, use any page-specific URL. Pages ignore <code>width/height</code> and always act responsively:
<pre><code>[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html#document/p1"]
</code></pre>
To embed a note, use any note-specific URL. Notes ignore <code>width/height</code> and always act responsively:
<pre><code>[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html#document/p1/a53674"]
</code></pre>
To control which view is displayed by default, use the <code>mode</code> parameter:
<pre><code>[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html" mode="notes"]
[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html" mode="text"]
[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html" mode="grid"]
</code></pre>
Here’s the full list of embed options you can pass via shortcode attributes; some are specific to the type of resource you’re embedding.
All resources:
<ul>
<li><code>url</code> (required, string): Full URL of the DocumentCloud resource.</li>
<li><code>container</code> (string): ID of element to insert the embed into; if excluded, embedder will create its own container.</li>
</ul>
Documents only:
<ul>
<li><code>height</code> (integer): Maximum height (in pixels) of the embed.</li>
<li><code>width</code> (integer): Maximum width (in pixels) of the embed.</li>
<li><code>page</code> (integer): Page number to have the document scroll to by default.</li>
<li><code>note</code> (integer): ID of the note that the document should highlight by default.</li>
<li><code>notes</code> (boolean): Hide or show notes.</li>
<li><code>search</code> (boolean): Hide or show search form.</li>
<li><code>sidebar</code> (boolean): Hide or show sidebar.</li>
<li><code>pdf</code> (boolean): Hide or show link to download original PDF.</li>
<li><code>text</code> (boolean): Hide or show text tab.</li>
<li><code>zoom</code> (boolean): Hide or show zoom slider.</li>
<li><code>mode</code> (string): Display mode for the document viewer. Valid values: <code>document</code>, <code>notes</code>, <code>text</code>, <code>grid</code>. Controls which view is shown by default.</li>
<li><code>format</code> (string): Indicate to the theme that this is a wide asset by setting this to <code>wide</code>. Defaults <code>normal</code>.</li>
</ul>
Or as a Gutenberg Block:
<pre><code>DocumentCloud
</code></pre>
Here’s the list of settings that can be used for the block: 
– <code>WIDTH</code> (number): Sets the width of the document (optional) 
– <code>HEIGHT</code> (number): Sets the height of the document (optional) 
– <code>STYLE</code> (string): Adds additional style to the embedded document (optional)
The following options can only be used for Documents: 
– <code>Show Title</code> (toggle): Determines whether to show the title of the embedded document 
– <code>Show FullScreen Button</code> (toggle): Determines whether to show a full screen icon on the document 
– <code>Only Show Organization</code> (toggle): Determines whether to only show the organization name that published the document. 
– <code>Show PDF Download Link</code> (toggle): Determines whether to show the download as pdf icon for documents.
Note – The default width and height from the Settings does not work for the Gutenberg Block.
You can read more about publishing and embedding DocumentCloud resources on https://www.documentcloud.org/help/publishing.

DocumentCloud

Embed DocumentCloud resources in WordPress content.

CloudSearch vs DocumentCloud