recipe 8.x-2.0-alpha1

This branch is still in development! Using this release on production sites is highly discouraged! Upgrade paths will not be included between alpha versions.

Most recipe functionality has been ported from the 7.x version. Some functionality is yet to be ported and will be included in a later alpha release. Some functionality has been dropped entirely.

A non-comprehensive list of changes

• All of the Recipe content type's fields are now provided by the Field API with no more data stored in custom tables.
• Ingredient functionality has been moved to a sub-module inside of Recipe. The sub-module can be enabled on its own without the main Recipe module, if desired.
• Ingredients have been converted into entities. They can be added, edited, and deleted. They are fieldable. An administration page (admittedly with no bulk management options for the moment) has been added at /admin/content/ingredient. A route and default view for listing ingredients on the front end has been added at /ingredient. A page for viewing individual ingredients has been added at /ingredient/%.
• A new field type has been added for referencing Ingredients with the quantity, units, and notes data. You can add this field to other entity types, just like any other field. For instance, you can use it to create custom recipe content types.
• Ingredient units have been converted into a configuration object. With a little knowledge of YAML, they can be customized by site builders while remaining translatable for multilingual sites. The units are grouped into unit sets. The U.S. Customary, SI/Metric, and Common Units sets have been ported from the 7.x branch, but custom sets can be configured. Sets are enabled or disabled in the Ingredient field settings, so they can be configured on a field-by-field basis.
• Fields whose values are added to the recipe's total time are now configurable. Any Integer field attached to the Recipe content type now has a checkbox on its settings page. If checked, the value of that integer field will be added to the Total time psuedo-field in the recipe.

Yet-to-be-ported functionality

• The views at /recipe and /ingredient are basic lists of those entities with an exposed filter for searching the titles/names. The original intent was to reproduce the recipe and ingredient Index views from the 7.x branch, but doing so proved to be troublesome and they never worked correctly. The cause of this is unknown. Thus, the views were replaced with the current, simpler versions. If someone would like to attempt to recreate the 7.x views and provide them, they may yet be included in the module.
• The Recipe sub-modules which provide import and export functionality for various formats have not yet been ported. The intent is to recreate the export formats as Views plugins. A plan has not yet been set for implementation of the recipe import functionality, but the intent is to provide it via another module and its plugins. Possible implementation via the core Migrate module or the contrib Feeds module will be investigated.

Other upcoming changes in a future alpha release

• A view will be added that overrides the default entity page at /ingredient/%. In addition to displaying any Ingredient fields, it will display a list of any nodes that reference the Ingredient.
• The Recipe module settings for configuring the Total time and Yield pseudo-fields will be moved to the Recipe content type settings, which is more appropriate and a necessary first step toward making them available for use in custom recipe content types. When the settings are moved the Recipe module settings page will no longer be needed and will be removed.
• Migration paths from the 7.x-1.3, 7.x-2.x, and 6.x-1.5 versions will be included.

Dropped functionality

• The default landing page at /recipe has been removed. A default view has been provided for the /recipe path instead. It can be customized or replaced by site builders.
• The Latest recipes block has been removed. With Views in core, it is easier than ever for site builders to create this functionality on their own.
• The Recipe summary element on Recipe content pages has been removed. If you ever tried to customize the elements in the summary in 7.x-1.x then you know the joy of having to override hook_node_view() in a custom module. This change should make life easier on site builders and themers who want more control over the elements that were previously in the summary.
• The custom yield form on Recipe content pages has been removed. In my opinion, the form never worked quite right. In a project that I developed a few years ago the client was initially in favor of using it, but immediately demanded that it be disabled once they saw it work in practice. Apparently some sites do use it though. If there is enough interest, then it may be ported to the 8.x branch in the future, hopefully with significant improvements, but I stress that there are no plans to port it at this time.