diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..7cae7da --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,53 @@ +# Changelog + +All notable changes to this project will be documented in this file, per [the Keep a Changelog standard](http://keepachangelog.com/), and will adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). + +## [Unreleased] - TBD + +## [0.4.0] - 2020-08-06 +### Added +- Added `CustomEvent` and associated IE11 polyfill to listen for changes outside of the plugin (props [@jaredrethman](https://github.com/jaredrethman) via [#32](https://github.com/10up/post-finder/pull/32)) +- Documentation updates (props [@jeffpaul](https://github.com/jeffpaul) via [#33](https://github.com/10up/post-finder/pull/33)) + +### Changed +- Moved saved connections above the search field (props [@gthayer](https://github.com/gthayer) via [#30](https://github.com/10up/post-finder/pull/30)) +- Only loading the plugin if on WordPress context (props [@nicholasio](https://github.com/nicholasio) via [#29](https://github.com/10up/post-finder/pull/29)) +- Update `grunt-sass` package version to v2.1 (props [@jaredrethman](https://github.com/jaredrethman) via [#32](https://github.com/10up/post-finder/pull/32)) +- Versioning to follow SemVer (props [@daveross](https://github.com/daveross) via [#27](https://github.com/10up/post-finder/pull/27)) + +## [0.3.0] - 2017-07-05 +### Added +- Pagination to search results (props [@dkotter](https://github.com/dkotter) via [#21](https://github.com/10up/post-finder/pull/21)) +- Allow the option to turn off the display of the Recent Posts dropdown (props [@dkotter](https://github.com/dkotter) via [#22](https://github.com/10up/post-finder/pull/22)) +- Use Grunt for compiling (props [@dkotter](https://github.com/dkotter) via [#18](https://github.com/10up/post-finder/pull/18)) +- Internationalization support (props [@dkotter](https://github.com/dkotter) via [#19](https://github.com/10up/post-finder/pull/19)) + +### Changed +- Localization updates (props [@eugene-manuilov](https://github.com/eugene-manuilov) via [#24](https://github.com/10up/post-finder/pull/24)) +- Adjust styling to better match WordPress (props [@dkotter](https://github.com/dkotter) via [#17](https://github.com/10up/post-finder/pull/17)) +- Code formatting and cosmetic fixes (props [@dkotter](https://github.com/dkotter), [@eugene-manuilov](https://github.com/eugene-manuilov) via [#20](https://github.com/10up/post-finder/pull/20), [#25](https://github.com/10up/post-finder/pull/25)) +- `composer.json` properties updates (props [@eugene-manuilov](https://github.com/eugene-manuilov) via [#23](https://github.com/10up/post-finder/pull/23)) + +## [0.2.0] - 2017-07-05 +### Added +- Ability to add posts when none exist yet +- Proper namespacing, serialization, sanitization +- Support for limits, query args, multiple post types, template filtering +- Select works on change or click +- `composer.json` file + +### Changed +- Major updates to CSS and styles +- Overlay markup, JS improvements, issue with JS and CSS paths + +### Fixed +- Undefined variable reference, form submission denial + +## [0.1.0] - 2013-08-07 +- Initial release of Post Finder plugin. + +[Unreleased]: https://github.com/10up/post-finder/compare/trunk...develop +[0.4.0]: https://github.com/10up/post-finder/compare/0.3.0...0.4.0 +[0.3.0]: https://github.com/10up/post-finder/compare/0.2.0...0.3.0 +[0.2.0]: https://github.com/10up/post-finder/compare/cac1515...0.2.0 +[0.1.0]: https://github.com/10up/post-finder/tree/cac1515fd654ac1bbb2c5528bf8f967417f1d473 diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..e8bac02 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,76 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, sex characteristics, gender identity and expression, +level of experience, education, socio-economic status, nationality, personal +appearance, race, religion, or sexual identity and orientation. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or + advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or +reject comments, commits, code, wiki edits, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at opensource@10up.com. All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see +https://www.contributor-covenant.org/faq diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..ed8eddc --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,40 @@ +# Contributing and Maintaining + +First, thank you for taking the time to contribute! + +The following is a set of guidelines for contributors as well as information and instructions around our maintenance process. The two are closely tied together in terms of how we all work together and set expectations, so while you may not need to know everything in here to submit an issue or pull request, it's best to keep them in the same document. + +## Ways to contribute + +Contributing isn't just writing code - it's anything that improves the project. All contributions are managed right here on GitHub. Here are some ways you can help: + +### Reporting bugs + +If you're running into an issue with the plugin, please take a look through [existing issues](https://github.com/10up/post-finder/issues) and [open a new one](https://github.com/10up/post-finder/issues/new) if needed. If you're able, include steps to reproduce, environment information, and screenshots/screencasts as relevant. + +### Suggesting enhancements + +New features and enhancements are also managed via [issues](https://github.com/10up/post-finder/issues). + +### Pull requests + +Pull requests represent a proposed solution to a specified problem. They should always reference an issue that describes the problem and contains discussion about the problem itself. Discussion on pull requests should be limited to the pull request itself, i.e. code review. + +For more on how 10up writes and manages code, check out our [10up Engineering Best Practices](https://10up.github.io/Engineering-Best-Practices/). + +## Workflow + +The `develop` branch is the development branch which means it contains the next version to be released. `trunk` contains the latest released version as reflected in the WordPress.org plugin repository. Always work on the `develop` branch and open up PRs against `develop`. + +## Release instructions + +1. Branch: Starting from `develop`, cut a release branch named `release/X.Y.Z` for your changes. +2. Version bump: Bump the version number in `languages/post-finder.pot`, `post-finder.php`, and `package.json` if it does not already reflect the version being released. Update both the plugin "Version:" property and the plugin `POST_FINDER_VERSION` constant in `post-finder.php`. +3. Changelog: Add/update the changelog in `CHANGELOG.md`. +4. Props: update `CREDITS.md` with any new contributors, confirm maintainers are accurate. +5. Readme updates: Make any other `README.md` changes as necessary. +6. Merge: Make a non-fast-forward merge from your release branch to `develop` (or merge the pull request), then do the same for `develop` into `trunk` (`git checkout trunk && git merge --no-ff develop`). `trunk` contains the stable development version. +7. Push: Push your `trunk` branch to GitHub (e.g. `git push origin trunk`). +8. Release: Create a [new release](https://github.com/10up/post-finder/releases/new), naming the tag and the release with the new version number, and targeting the `trunk` branch. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the [closed issues on the milestone](https://github.com/10up/post-finder/milestone/3?closed=1). +9. Close the milestone: Edit the [X.Y.Z milestone](https://github.com/10up/post-finder/milestone/#) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description` field), then close the milestone. +10. Punt incomplete items: If any open issues or PRs which were milestoned for `X.Y.Z` do not make it into the release, update their milestone to `X+1.0.0`, `X.Y+1.0`, `X.Y.Z+1`, or `Future Release` diff --git a/CREDITS.md b/CREDITS.md new file mode 100644 index 0000000..2ebf6b4 --- /dev/null +++ b/CREDITS.md @@ -0,0 +1,19 @@ +The following acknowledges the Maintainers for this repository, those who have Contributed to this repository (via bug reports, code, design, ideas, project management, translation, testing, etc.), and any Libraries utilized. + +## Maintainers + +The following individuals are responsible for curating the list of issues, responding to pull requests, and ensuring regular releases happen. + +[Nícholas André (@nicholasio)](https://github.com/nicholasio), [Eugene Manuilov (@eugene-manuilov)](https://github.com/eugene-manuilov), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul). + +## Contributors + +Thank you to all the people who have already contributed to this repository via bug reports, code, design, ideas, project management, translation, testing, etc. + +[@micahwave](https://github.com/micahwave), [John Troynousky (@jtroynousky)](https://github.com/jtroynousky), [Joseph Chagan (@lupos)](https://github.com/lupos), [Helen Hou-Sandi (@helen)](https://github.com/helen), [Chris Marslender (@cmmarslender)](https://github.com/cmmarslender), [John Eckman (@jeckman)](https://github.com/jeckman), [Matt Gross (@mattonomics)](https://github.com/mattonomics), [Steve Grunwell (@stevegrunwell)](https://github.com/stevegrunwell), [Joey Blake (@joeyblake)](https://github.com/joeyblake), [Michael Phillips (@mphillips)](https://github.com/mphillips), [Adam Silverstein (@adamsilverstein)](https://github.com/adamsilverstein), [Ayebare (@ayebare)](https://github.com/ayebare), [Ryan Welcher (@ryanwelcher)](https://github.com/ryanwelcher), [Darin Kotter (@dkotter)](https://github.com/dkotter), [Eugene Manuilov (@eugene-manuilov)](https://github.com/eugene-manuilov), [Dave Ross (@daveross)](https://github.com/daveross), [Nícholas André (@nicholasio)](https://github.com/nicholasio), [Gary Thayer (@gthayer)](https://github.com/gthayer), [Jared Rethman (@jaredrethman)](https://github.com/jaredrethman), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul), [Tyler Cherpak (@tylercherpak)](https://github.com/tylercherpak). + +## Libraries + +The following software libraries are utilized in this repository. + +Forked from [Post Finder](https://github.com/micahwave/post-finder) by [@micahwave](https://github.com/micahwave). diff --git a/LICENSE.md b/LICENSE.md new file mode 100644 index 0000000..d159169 --- /dev/null +++ b/LICENSE.md @@ -0,0 +1,339 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Lesser General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License along + with this program; if not, write to the Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. diff --git a/README.md b/README.md index f16e73a..296da40 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,13 @@ # Post Finder -Creates a rich input field that allows a user to curate and rank content items (posts or other custom post types) +> Creates a rich input field that allows a user to curate and rank content items (posts or other custom post types) + +[![Support Level](https://img.shields.io/badge/support-stable-blue.svg)](#support-level) [![Release Version](https://img.shields.io/github/release/10up/post-finder.svg)](https://github.com/10up/post-finder/releases/latest) ![WordPress tested up to version](https://img.shields.io/badge/WordPress-v5.4%20tested-success.svg) [![GPLv2 License](https://img.shields.io/github/license/10up/post-finder.svg)](https://github.com/10up/post-finder/blob/develop/LICENSE.md) + ## Installation -Clone the plugin to your `wp-content/plugins/` directory +Clone the plugin to your `wp-content/plugins/` directory. ## Usage @@ -26,4 +29,20 @@ In your theme, you can call `pf_render( $name, $value, $options )` where you wan jQuery( document ).ready( function( $ ) { $( '.post-finder' ).postFinder(); } ); -``` \ No newline at end of file +``` + +## Support Level + +**Stable:** 10up is not planning to develop any new features for this, but will still respond to bug reports and security concerns. We welcome PRs, but any that include new features should be small and easy to integrate and should not include breaking changes. We otherwise intend to keep this tested up to the most recent version of WordPress. + +## Changelog + +A complete listing of all notable changes to Post Finder are documented in [CHANGELOG.md](https://github.com/10up/post-finder/blob/develop/CHANGELOG.md). + +## Contributing + +Please read [CODE_OF_CONDUCT.md](https://github.com/10up/post-finder/blob/develop/CODE_OF_CONDUCT.md) for details on our code of conduct, [CONTRIBUTING.md](https://github.com/10up/post-finder/blob/develop/CONTRIBUTING.md) for details on the process for submitting pull requests to us, and [CREDITS.md](https://github.com/10up/post-finder/blob/develop/CREDITS.md) for a listing of maintainers of, contributors to, and libraries used by Post Finder. + +## Like what you see? + +Work with us at 10up diff --git a/composer.json b/composer.json index e150ece..f69e50f 100644 --- a/composer.json +++ b/composer.json @@ -1,7 +1,6 @@ { "name": "10up/post-finder", "description": "Adds a UI for curating and ordering posts", - "version": "0.4.0", "type": "wordpress-plugin", "keywords": [ "wordpress" diff --git a/languages/post-finder.pot b/languages/post-finder.pot index 1960934..6be94a8 100644 --- a/languages/post-finder.pot +++ b/languages/post-finder.pot @@ -3,7 +3,7 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Post Finder 0.3.0\n" +"Project-Id-Version: Post Finder 0.4.0\n" "POT-Creation-Date: 2017-07-06 00:09+0300\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" diff --git a/package.json b/package.json index e09c2f4..413f660 100644 --- a/package.json +++ b/package.json @@ -3,9 +3,10 @@ "title": "Post Finder", "description": "Adds a UI for curating and ordering posts", "version": "0.4.0", + "license": "GPL-2.0", "repository": { "type": "git", - "url": "" + "url": "https://github.com/10up/post-finder" }, "authors": [ { diff --git a/post-finder.php b/post-finder.php index 67bb49c..51ed4ca 100644 --- a/post-finder.php +++ b/post-finder.php @@ -1,9 +1,15 @@