Last active
November 9, 2021 20:11
-
-
Save dkinzer/045b6de39174774407b1673127520657 to your computer and use it in GitHub Desktop.
Patch for BL Wiki. Updates "master" references to "main"
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| From 755639b062052ed6b752ab08e220c9ed9857d69a Mon Sep 17 00:00:00 2001 | |
| From: David Kinzer <dtkinzer@gmail.com> | |
| Date: Tue, 9 Nov 2021 14:54:55 -0500 | |
| Subject: [PATCH] Update references to 'master' branch. | |
| --- | |
| Adding-new-document-actions.md | 4 ++-- | |
| Atom-Responses.md | 2 +- | |
| Blacklight-configuration.md | 14 +++++++------- | |
| Blacklight-on-Heroku.md | 4 ++-- | |
| Configuration---Solr-fields.md | 4 ++-- | |
| ...ding-or-Modifying-Blacklight-Search-Behavior.md | 14 +++++++------- | |
| Home.md | 8 ++++---- | |
| How-to-release-a-version.md | 2 +- | |
| Internationalization.md | 2 +- | |
| Legacy-JSON-API.md | 2 +- | |
| Pagination.md | 4 ++-- | |
| Providing-your-own-view-templates.md | 4 ++-- | |
| Quickstart.md | 4 ++-- | |
| Testing-and-Developing-Blacklight.md | 2 +- | |
| Using-Webpacker-to-compile-javascript-assets.md | 4 ++-- | |
| 15 files changed, 37 insertions(+), 37 deletions(-) | |
| diff --git a/Adding-new-document-actions.md b/Adding-new-document-actions.md | |
| index 96ce5b3..50d3a09 100644 | |
| --- a/Adding-new-document-actions.md | |
| +++ b/Adding-new-document-actions.md | |
| @@ -91,7 +91,7 @@ end | |
| By convention, the action name is used to determine the route name for the action. For this email action, Blacklight will link to `email_catalog_path`. | |
| -The action will render the template [`catalog/email.html.erb`](https://github.com/projectblacklight/blacklight/blob/master/app/views/catalog/email.html.erb) template when the action is selected. This template provides a form, which, when submitted, will trigger the `email_action` method and will render the [`catalog/email_success.html.erb`](https://github.com/projectblacklight/blacklight/blob/master/app/views/catalog/email_success.html.erb) template. | |
| +The action will render the template [`catalog/email.html.erb`](https://github.com/projectblacklight/blacklight/blob/main/app/views/catalog/email.html.erb) template when the action is selected. This template provides a form, which, when submitted, will trigger the `email_action` method and will render the [`catalog/email_success.html.erb`](https://github.com/projectblacklight/blacklight/blob/main/app/views/catalog/email_success.html.erb) template. | |
| ### Removing actions | |
| @@ -100,4 +100,4 @@ Note that it is also possible to delete document actions as follows: | |
| ```ruby | |
| # app/controllers/catalog_controller.rb | |
| config.show.document_actions.delete(:citation) | |
| -``` | |
| \ No newline at end of file | |
| +``` | |
| diff --git a/Atom-Responses.md b/Atom-Responses.md | |
| index cc2516e..fa2fa68 100644 | |
| --- a/Atom-Responses.md | |
| +++ b/Atom-Responses.md | |
| @@ -48,7 +48,7 @@ Blacklight will provide atom responses for all catalog/index results. Just add " | |
| ``` | |
| -The same HTML summary included in your HTML results pages are included as an `atom:summary` element -- the atom template uses the `[[#render_document_partial|https://github.com/projectblacklight/blacklight/blob/master/app/helpers/blacklight/blacklight_helper_behavior.rb#L203]]` helper method to generate this HTML summary, so if you've over-ridden that for your app, it will be used as the `atom:summary` content instead. | |
| +The same HTML summary included in your HTML results pages are included as an `atom:summary` element -- the atom template uses the `[[#render_document_partial|https://github.com/projectblacklight/blacklight/blob/main/app/helpers/blacklight/blacklight_helper_behavior.rb#L203]]` helper method to generate this HTML summary, so if you've over-ridden that for your app, it will be used as the `atom:summary` content instead. | |
| ## API Usage | |
| The Atom response is intended to be pretty full of data, so it can fill many traditional API requests. It makes use of every relevant atom or [[OpenSearch|http://www.opensearch.org/Home]] element that could be conveniently included. | |
| diff --git a/Blacklight-configuration.md b/Blacklight-configuration.md | |
| index 16a3d5e..a9b5947 100644 | |
| --- a/Blacklight-configuration.md | |
| +++ b/Blacklight-configuration.md | |
| @@ -49,7 +49,7 @@ You can use [foreman](http://blog.daviddollar.org/2011/05/06/introducing-foreman | |
| ## Blacklight Configuration | |
| -Now that you've connected to Solr, you probably want to configure Blacklight to display your Solr fields in the search results and facets, and also use your fields for search fields, sort options. This configuration goes in your CatalogController. By convention, this is in your Rails application, and is located at [```app/controllers/catalog_controller.rb```](https://github.com/projectblacklight/blacklight/blob/master/lib/generators/blacklight/templates/catalog_controller.rb). | |
| +Now that you've connected to Solr, you probably want to configure Blacklight to display your Solr fields in the search results and facets, and also use your fields for search fields, sort options. This configuration goes in your CatalogController. By convention, this is in your Rails application, and is located at [```app/controllers/catalog_controller.rb```](https://github.com/projectblacklight/blacklight/blob/main/lib/generators/blacklight/templates/catalog_controller.rb). | |
| The CatalogController includes functionality and templates for searching and displaying documents. The CatalogController needs to be configured so it knows about your Solr fields. | |
| @@ -131,7 +131,7 @@ There's a separate section for the additional fields to display: | |
| config.add_show_field 'subtitle_display', :label => 'Subtitle:' | |
| ``` | |
| -[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/index_fields.png|frame|alt=Index Fields]] | |
| +[[https://github.com/projectblacklight/projectblacklight.github.com/raw/main/images/index_fields.png|frame|alt=Index Fields]] | |
| #### Linking a value to a facet search | |
| @@ -195,7 +195,7 @@ This will enable the highlighting component and send 'hl.fl' parameters for the | |
| ### Facet fields | |
| Faceted search allows users to constrain searches by controlled vocabulary items | |
| -[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/search_facets.png|frame|alt=Search facets in action]] | |
| +[[https://github.com/projectblacklight/projectblacklight.github.com/raw/main/images/search_facets.png|frame|alt=Search facets in action]] | |
| Note that these must be INDEXED fields in the Solr index, and are generally a single token (e.g. a string). | |
| ```ruby | |
| @@ -228,7 +228,7 @@ end | |
| ### Facet Queries | |
| Blacklight also supports Solr facet queries: | |
| -[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/query_facets.png|frame|alt=Query facets in action]] | |
| +[[https://github.com/projectblacklight/projectblacklight.github.com/raw/main/images/query_facets.png|frame|alt=Query facets in action]] | |
| ```ruby | |
| config.add_facet_field 'pub_date_query', :label => 'Publication Year', :query => { | |
| @@ -295,7 +295,7 @@ To configure this behavior in Blacklight, | |
| ### search fields | |
| Search queries can be targeted at configurable fields (or sets of fields) to return precise search results. Advanced search capabilities are provided through the [[Advanced Search Add-On|https://github.com/projectblacklight/blacklight_advanced_search]] | |
| -[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/search_fields.png|frame|alt=Search fields in action]] | |
| +[[https://github.com/projectblacklight/projectblacklight.github.com/raw/main/images/search_fields.png|frame|alt=Search fields in action]] | |
| ```ruby | |
| # [from app/controllers/catalog_controller.rb] | |
| @@ -327,7 +327,7 @@ Search queries can be targeted at configurable fields (or sets of fields) to ret | |
| config.add_sort_field 'title_sort asc, pub_date_sort desc', :label => 'title' | |
| ``` | |
| -[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/sort_fields.png|frame|alt=Sort fields in action]] | |
| +[[https://github.com/projectblacklight/projectblacklight.github.com/raw/main/images/sort_fields.png|frame|alt=Sort fields in action]] | |
| > TODO | |
| @@ -414,4 +414,4 @@ Or using custom logic in a helper method of your own creation: | |
| With this configuration, the helper method `xyz` will be called with the `SolrDocument` document and a hash of caller-supplied image options. | |
| -Given that configuration, Blacklight will render a thumbnail (by default, right aligned, under the bookmark button) as a link to the document page. If no thumbnail is available (missing data in solr, the thumbnail method returned nil), the thumbnail block is not displayed at all. | |
| \ No newline at end of file | |
| +Given that configuration, Blacklight will render a thumbnail (by default, right aligned, under the bookmark button) as a link to the document page. If no thumbnail is available (missing data in solr, the thumbnail method returned nil), the thumbnail block is not displayed at all. | |
| diff --git a/Blacklight-on-Heroku.md b/Blacklight-on-Heroku.md | |
| index e101875..63b1b73 100644 | |
| --- a/Blacklight-on-Heroku.md | |
| +++ b/Blacklight-on-Heroku.md | |
| @@ -89,7 +89,7 @@ Blacklight can be deployed on [Heroku](http://heroku.com/), a Platform-as-a-Serv | |
| ## Deploy to Heroku | |
| ```bash | |
| - $ git push heroku master | |
| + $ git push heroku main | |
| [...] | |
| $ heroku run rake db:migrate | |
| [...] | |
| @@ -98,4 +98,4 @@ Blacklight can be deployed on [Heroku](http://heroku.com/), a Platform-as-a-Serv | |
| ## Try opening up your app | |
| * Go to URL reported by Heroku above (in this example, http://vivid-winter-2427.herokuapp.com/). | |
| -* Does it work? If it doesn't, try running `heroku logs` to see where problems are cropping up. | |
| \ No newline at end of file | |
| +* Does it work? If it doesn't, try running `heroku logs` to see where problems are cropping up. | |
| diff --git a/Configuration---Solr-fields.md b/Configuration---Solr-fields.md | |
| index c9574c3..8157162 100644 | |
| --- a/Configuration---Solr-fields.md | |
| +++ b/Configuration---Solr-fields.md | |
| @@ -79,7 +79,7 @@ config.sort_fields['year'].label = "Year Created" | |
| Search queries can be targeted at configurable fields (or sets of fields) to return precise search results. | |
| -<img src="https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/search_fields.png" /> | |
| +<img src="https://github.com/projectblacklight/projectblacklight.github.com/raw/main/images/search_fields.png" /> | |
| ```ruby | |
| config.add_search_field 'all_fields', :label => 'All Fields' | |
| @@ -103,4 +103,4 @@ Search queries can be targeted at configurable fields (or sets of fields) to ret | |
| :pf => '$title_pf' | |
| } | |
| end | |
| -``` | |
| \ No newline at end of file | |
| +``` | |
| diff --git a/Extending-or-Modifying-Blacklight-Search-Behavior.md b/Extending-or-Modifying-Blacklight-Search-Behavior.md | |
| index c2f3900..cbd3c60 100644 | |
| --- a/Extending-or-Modifying-Blacklight-Search-Behavior.md | |
| +++ b/Extending-or-Modifying-Blacklight-Search-Behavior.md | |
| @@ -36,21 +36,21 @@ The request handler is often set up with default parameters: | |
| ``` | |
| ## Configuration | |
| -The default application logic (explained below) looks in configuration for things like the name of a the solr request handler to use, and default request parameters to send on every solr search request (or with every request from a certain blacklight search type/field). An example getting started configuration is generally installed into your app when you install Blacklight at [`./app/controllers/catalog_controller.rb`](https://github.com/projectblacklight/blacklight/blob/master/lib/generators/blacklight/templates/catalog_controller.rb). | |
| +The default application logic (explained below) looks in configuration for things like the name of a the solr request handler to use, and default request parameters to send on every solr search request (or with every request from a certain blacklight search type/field). An example getting started configuration is generally installed into your app when you install Blacklight at [`./app/controllers/catalog_controller.rb`](https://github.com/projectblacklight/blacklight/blob/main/lib/generators/blacklight/templates/catalog_controller.rb). | |
| ## Application logic | |
| -The logic Blacklight uses to determine how to map user-supplied parameters into Solr request parameters for a given application request is in the [#processed_parameters method in the SearchBuilder class](https://github.com/projectblacklight/blacklight/blob/master/lib/blacklight/search_builder.rb#L137). | |
| +The logic Blacklight uses to determine how to map user-supplied parameters into Solr request parameters for a given application request is in the [#processed_parameters method in the SearchBuilder class](https://github.com/projectblacklight/blacklight/blob/main/lib/blacklight/search_builder.rb#L137). | |
| -`SearchBuilder` uses an ordered list of methods, called a [`processor_chain`](https://github.com/projectblacklight/blacklight/blob/master/lib/blacklight/search_builder.rb#L11), that use the supplied user parameters and add, remove, or modify the Solr request parameters. | |
| +`SearchBuilder` uses an ordered list of methods, called a [`processor_chain`](https://github.com/projectblacklight/blacklight/blob/main/lib/blacklight/search_builder.rb#L11), that use the supplied user parameters and add, remove, or modify the Solr request parameters. | |
| At the end of processing, the resulting output builds a [RSolr](https://github.com/mwmitchell/rsolr/) request. RSolr will convert the hash into query parameters for a Solr request. | |
| -The default [`Blacklight::Solr::SearchBuilder`](https://github.com/projectblacklight/blacklight/blob/master/lib/blacklight/solr/search_builder_behavior.rb) logic is intended to handle common mapping using simple configuration options from the controller and the user-supplied URL parameters. | |
| +The default [`Blacklight::Solr::SearchBuilder`](https://github.com/projectblacklight/blacklight/blob/main/lib/blacklight/solr/search_builder_behavior.rb) logic is intended to handle common mapping using simple configuration options from the controller and the user-supplied URL parameters. | |
| -* [`blacklight_config.default_solr_params`](https://github.com/projectblacklight/blacklight/blob/master/lib/generators/blacklight/templates/catalog_controller.rb#L17) | |
| +* [`blacklight_config.default_solr_params`](https://github.com/projectblacklight/blacklight/blob/main/lib/generators/blacklight/templates/catalog_controller.rb#L17) | |
| * Default params sent to solr with every search, including the default :qt param, which determines which Solr request handler will be targetted. Some people like to use solrconfig.xml request handler defaults exclusively, and include only a :qt here; others find it more convenient to specify some defaults at the application level here. | |
| -* [`blacklight_config.search_field`](https://github.com/projectblacklight/blacklight/blob/master/lib/generators/blacklight/templates/catalog_controller.rb#L131) | |
| +* [`blacklight_config.search_field`](https://github.com/projectblacklight/blacklight/blob/main/lib/generators/blacklight/templates/catalog_controller.rb#L131) | |
| * Each search field will be presented in a select menu in the BL user interface search box. These 'search fields' don't neccesarily correspond 1-to-1 with Solr fields. What they instead correspond to is Solr parameter over-rides that will be used for this BL UI search field. Those over-rides are present here. | |
| * You could simply chose a different `:qt` Solr request handler for each search field, which has it's own default parameters in the sorlconfig.xml. This is what we started out doing with Solr, but found it led to much duplication of information in solrconfig.xml. | |
| * You can continue using the same Solr request handler, but simply specify different parameters which will be included in the http query string sent to Solr here, with the `:solr_parameters` key. This works fine, but some people don't like how it makes your Solr requests much longer/more complex in the Solr logs; and/or they prefer to control this Solr side instead of Application side. | |
| @@ -113,4 +113,4 @@ to the request handler in your `solrconfig.xml` file. If you would like this to | |
| ``` | |
| <requestHandler name="search" class="solr.SearchHandler" default="true"> | |
| ``` | |
| -By doing so, solr queries that use the "document" request handler will still give you any records with the show_b field, but solr queries with the "search" handler will not. | |
| \ No newline at end of file | |
| +By doing so, solr queries that use the "document" request handler will still give you any records with the show_b field, but solr queries with the "search" handler will not. | |
| diff --git a/Home.md b/Home.md | |
| index 2b58283..b17f2c9 100644 | |
| --- a/Home.md | |
| +++ b/Home.md | |
| @@ -52,7 +52,7 @@ Blacklight provides out-of-the-box support for many types of search interactions | |
| ### Blacklight configuration | |
| A list of available Blacklight configuration options, and their default values, is available at | |
| -[`blacklight/configuration.rb`](https://github.com/projectblacklight/blacklight/tree/master/lib/blacklight/configuration.rb). In addition to the Blacklight-defined configuration discussed here, you may also add application-specific configuration (e.g. for controlling behavior in overridden partials) or plugin-specific configuration. | |
| +[`blacklight/configuration.rb`](https://github.com/projectblacklight/blacklight/tree/main/lib/blacklight/configuration.rb). In addition to the Blacklight-defined configuration discussed here, you may also add application-specific configuration (e.g. for controlling behavior in overridden partials) or plugin-specific configuration. | |
| #### General configuration | |
| - [[Results views]] | |
| @@ -98,7 +98,7 @@ Some Blacklight developers also hang out on our IRC channel, usually during Nort | |
| * [[Bug Tracker|https://github.com/projectblacklight/blacklight/issues/]] | |
| * [[Mailing List|http://groups.google.com/group/blacklight-development]] | |
| -* [](https://travis-ci.org/projectblacklight/blacklight) | |
| +* [](https://travis-ci.org/projectblacklight/blacklight) | |
| ## Contributing to Blacklight | |
| @@ -107,7 +107,7 @@ Some Blacklight developers also hang out on our IRC channel, usually during Nort | |
| * [[Testing and Developing Blacklight]] | |
| ### Older Documentation | |
| -This wiki provides developer documentation for the ```master``` branch of Blacklight, which may include documentation of features not present in every Blacklight version. For documentation of specific Blacklight releases, see also: | |
| +This wiki provides developer documentation for the ```main``` branch of Blacklight, which may include documentation of features not present in every Blacklight version. For documentation of specific Blacklight releases, see also: | |
| * [[Home]] | |
| * [[Blacklight 5.9|https://github.com/projectblacklight/blacklight/tree/release-5.9/doc]] | |
| @@ -118,4 +118,4 @@ This wiki provides developer documentation for the ```master``` branch of Blackl | |
| * [[Blacklight 2.7|https://github.com/projectblacklight/blacklight/tree/v2.7.0/doc]] | |
| * [[Blacklight 2.6|https://github.com/projectblacklight/blacklight/tree/v2.6.0/doc]] | |
| * [[Blacklight 2.5|https://github.com/projectblacklight/blacklight/tree/v2.5.0/doc]] | |
| - * [[Blacklight 2.4|https://github.com/projectblacklight/blacklight/tree/v2.4.2/doc]] | |
| \ No newline at end of file | |
| + * [[Blacklight 2.4|https://github.com/projectblacklight/blacklight/tree/v2.4.2/doc]] | |
| diff --git a/How-to-release-a-version.md b/How-to-release-a-version.md | |
| index 5e21a1b..d13c0c8 100644 | |
| --- a/How-to-release-a-version.md | |
| +++ b/How-to-release-a-version.md | |
| @@ -1,4 +1,4 @@ | |
| -Before releasing, ensure that you're on the master branch. Run all tests and ensure that they pass. Also check the [[continuous integration server|https://travis-ci.org/projectblacklight/blacklight]] to make sure tests are passing. | |
| +Before releasing, ensure that you're on the main branch. Run all tests and ensure that they pass. Also check the [[continuous integration server|https://travis-ci.org/projectblacklight/blacklight]] to make sure tests are passing. | |
| ```bash | |
| $ bundle exec rake | |
| ``` | |
| diff --git a/Internationalization.md b/Internationalization.md | |
| index 038f2be..6d10488 100644 | |
| --- a/Internationalization.md | |
| +++ b/Internationalization.md | |
| @@ -1,4 +1,4 @@ | |
| -Blacklight uses the [Rails i18n framework](http://guides.rubyonrails.org/i18n.html) to provide multilingual version of most text in the Blacklight default templates. Blacklight ships with a set of English and French translations in [config/locales](https://github.com/projectblacklight/blacklight/blob/master/config/locales/). | |
| +Blacklight uses the [Rails i18n framework](http://guides.rubyonrails.org/i18n.html) to provide multilingual version of most text in the Blacklight default templates. Blacklight ships with a set of English and French translations in [config/locales](https://github.com/projectblacklight/blacklight/blob/main/config/locales/). | |
| In addition to multilingual support, developments can also e.g. customize the English strings in Blacklight-based applications, which provides a way to change text without overriding templates and partials. | |
| diff --git a/Legacy-JSON-API.md b/Legacy-JSON-API.md | |
| index 2b6441b..d8e1478 100644 | |
| --- a/Legacy-JSON-API.md | |
| +++ b/Legacy-JSON-API.md | |
| @@ -80,4 +80,4 @@ The JSON serialization can be overridden in a local application by providing alt | |
| in your CatalogController. | |
| -See: https://github.com/projectblacklight/blacklight/blob/master/lib/blacklight/catalog.rb#L175-L191 | |
| \ No newline at end of file | |
| +See: https://github.com/projectblacklight/blacklight/blob/main/lib/blacklight/catalog.rb#L175-L191 | |
| diff --git a/Pagination.md b/Pagination.md | |
| index 5d00e18..2350641 100644 | |
| --- a/Pagination.md | |
| +++ b/Pagination.md | |
| @@ -13,7 +13,7 @@ Or, | |
|  | |
| -The `theme => 'blacklight'` part will be passed through kaminari, and tell kaminari to use the theme that the Blacklight plugin supplies at [app/views/kaminari/blacklight](https://github.com/projectblacklight/blacklight/tree/master/app/views/kaminari/blacklight) | |
| +The `theme => 'blacklight'` part will be passed through kaminari, and tell kaminari to use the theme that the Blacklight plugin supplies at [app/views/kaminari/blacklight](https://github.com/projectblacklight/blacklight/tree/main/app/views/kaminari/blacklight) | |
| Any other arguments of ordinary kaminari paginate can also be passed in there. | |
| @@ -49,4 +49,4 @@ You will get a file in config/initializers/kaminari_config.rb that is mostly com | |
| # config.window = 4 | |
| -and change 4 to whatever number is preferable. More information on the kaminari general configuration options is available here: https://github.com/amatsuda/kaminari#general-configuration-options | |
| \ No newline at end of file | |
| +and change 4 to whatever number is preferable. More information on the kaminari general configuration options is available here: https://github.com/amatsuda/kaminari#general-configuration-options | |
| diff --git a/Providing-your-own-view-templates.md b/Providing-your-own-view-templates.md | |
| index 877fa01..880adbd 100644 | |
| --- a/Providing-your-own-view-templates.md | |
| +++ b/Providing-your-own-view-templates.md | |
| @@ -23,9 +23,9 @@ Provide an AJAX modal: | |
| ## Overriding Views (templates and partials) | |
| -As a Rails Engine, you can easily override views in your app. You can see what views and partials are provided by looking in [./app/views](https://github.com/projectblacklight/blacklight/tree/master/app/views) inside the Blacklight source. | |
| +As a Rails Engine, you can easily override views in your app. You can see what views and partials are provided by looking in [./app/views](https://github.com/projectblacklight/blacklight/tree/main/app/views) inside the Blacklight source. | |
| -Once you find the view you'd like to change, you should create a file with the same name and relative path in your own application (e.g. if you wanted to override [[./app/views/catalog/_show_partials/_default.html.erb|https://github.com/projectblacklight/blacklight/blob/master/app/views/catalog/_show_partials/_default.html.erb]] you would create `./app/views/catalog/_show_partials/_default.html.erb` in your local application. Frequently, you will start by copying the existing Blacklight view and modifying it from there. | |
| +Once you find the view you'd like to change, you should create a file with the same name and relative path in your own application (e.g. if you wanted to override [[./app/views/catalog/_show_partials/_default.html.erb|https://github.com/projectblacklight/blacklight/blob/main/app/views/catalog/_show_partials/_default.html.erb]] you would create `./app/views/catalog/_show_partials/_default.html.erb` in your local application. Frequently, you will start by copying the existing Blacklight view and modifying it from there. | |
| It is generally recommended that you override as little as possible, in order to maximize your forward compatibility. Look to override either a small, focused partial template, or a helper method of partial template called from a larger template, so your application's version can call out to those same helpers or partial templates within blacklight core code. | |
| diff --git a/Quickstart.md b/Quickstart.md | |
| index a0e8f41..cb4c7b4 100644 | |
| --- a/Quickstart.md | |
| +++ b/Quickstart.md | |
| @@ -73,7 +73,7 @@ After you've installed `solr_wrapper`, run the quickstart install template: | |
| ```console | |
| $ mkdir projects | |
| $ cd projects | |
| -$ rails new search_app -m https://raw.github.com/projectblacklight/blacklight/master/template.demo.rb | |
| +$ rails new search_app -m https://raw.github.com/projectblacklight/blacklight/main/template.demo.rb | |
| create | |
| create README.rdoc | |
| create Rakefile | |
| @@ -186,4 +186,4 @@ $ rake solr:marc:index MARC_FILE=(path to file) | |
| Note: To view your newly indexed data in Solr, you must check the "edismax" option at the bottom of the query interface in the Solr Admin, or add the following to the query URL: &defType=edismax | |
| -See [[Configuring and Customizing Blacklight]] for information about how to customize the Blacklight user interface, search experience, and more. | |
| \ No newline at end of file | |
| +See [[Configuring and Customizing Blacklight]] for information about how to customize the Blacklight user interface, search experience, and more. | |
| diff --git a/Testing-and-Developing-Blacklight.md b/Testing-and-Developing-Blacklight.md | |
| index 6e3b3bf..94afeff 100644 | |
| --- a/Testing-and-Developing-Blacklight.md | |
| +++ b/Testing-and-Developing-Blacklight.md | |
| @@ -12,7 +12,7 @@ If you want to start off clean, make sure you have removed artifacts from prior | |
| Also, you may also want to pull the latest Blacklight commits. | |
| - $ git pull origin master | |
| + $ git pull origin main | |
| Update the Solr docker containers. This will provide you the latest Solr image as specified by `SOLR_VERSION` in the `.env` file, which you are free to customize for your needs. | |
| diff --git a/Using-Webpacker-to-compile-javascript-assets.md b/Using-Webpacker-to-compile-javascript-assets.md | |
| index 053acc5..afef1fe 100644 | |
| --- a/Using-Webpacker-to-compile-javascript-assets.md | |
| +++ b/Using-Webpacker-to-compile-javascript-assets.md | |
| @@ -22,7 +22,7 @@ yarn add jquery | |
| ``` | |
| Next, change `config/webpack/environment.js` as per https://getbootstrap.com/docs/4.0/getting-started/webpack/ | |
| -and https://github.com/rails/webpacker/blob/master/docs/webpack.md#plugins to this: | |
| +and https://github.com/rails/webpacker/blob/main/docs/webpack.md#plugins to this: | |
| ```js | |
| const { environment } = require('@rails/webpacker') | |
| @@ -70,4 +70,4 @@ Add front end javascript dependencies with `yarn add package` followed by `yarn` | |
| * https://rossta.net/blog/from-sprockets-to-webpack.html | |
| * https://medium.com/statuscode/introducing-webpacker-7136d66cddfb | |
| * https://www.youtube.com/watch?v=I_GGYIWbmg0 | |
| -* https://www.neontsunami.com/posts/replacing-rails-asset-pipeline-with-webpacker | |
| \ No newline at end of file | |
| +* https://www.neontsunami.com/posts/replacing-rails-asset-pipeline-with-webpacker | |
| -- | |
| 2.31.1 | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment