-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document BS2 deprication and BS5 migration. (#237) #242
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -368,9 +368,57 @@ Upgrading with a custom theme plugin | |
If you have developed a custom theme plugin for your application (for more | ||
information, see :ref:`customization-custom-theme`), you may need to perform | ||
an additional step following an upgrade to ensure that all pages are styled | ||
correctly. Please note that the instructions below are for upgrading a custom | ||
theme that continues to the Bootstrap 2 (“BS2”). Documentation for upgrading to | ||
BS5 will be provided at a later date. | ||
correctly. | ||
|
||
+++++++++++ | ||
Bootstrap 5 | ||
+++++++++++ | ||
|
||
Additional steps for tarball installations: | ||
******************************************* | ||
|
||
If not already installed, first `download the node.js binary distributuion | ||
<https://nodejs.org/en/download>`_ and export the PATH variable. | ||
|
||
The tarball is missing two required files for this: copy the | ||
`package.json <https://github.com/artefactual/atom/blob/stable/2.7.x/package.json>`_ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, good call. While making changes, I just realized that this link is to our stable/2.7.x repository - but if we don't want to have to update this GitHub link with every release, I would suggest that you update that link and the one in the other file to:
Using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We don't want them to use the qa/2.x version of those file in the stable release. Maybe this could be solved using the version var (from this docs) in the URL so it's updated based on that? |
||
and `webpack.config.js <https://github.com/artefactual/atom/blob/stable/2.7.x/webpack.config.js>`_ | ||
from the *correct stable branch* ("stable/|version|" for AtoM |version|) of our | ||
`AtoM repo <https://github.com/artefactual/atom/>`_. | ||
|
||
Test that everything has been installed correctly: | ||
|
||
.. code-block:: bash | ||
fiver-watson marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
$ npm install | ||
$ npm run build | ||
|
||
If you encounter any issues at this point, we recommend resolving them by | ||
consulting the :ref:`maintenance-troubleshooting` documentation before continuing. | ||
|
||
Rebuild BS5 theme assets: | ||
************************* | ||
|
||
.. code-block:: bash | ||
|
||
cd ~/atom | ||
npm install | ||
npm run build | ||
|
||
.. TIP:: | ||
|
||
If you are still not seeing your changes take effect, remember to | ||
:ref:`clear the Symfony cache <maintenance-clear-cache>` and your | ||
web browser's cache as well! | ||
|
||
+++++++++++ | ||
Bootstrap 2 | ||
+++++++++++ | ||
|
||
.. NOTE:: | ||
|
||
Bootstrap 2 themes have been deprecated and will be removed in a future | ||
release. Please consider switching to a Bootstrap 5 theme. | ||
|
||
Specifically, :ref:`job-details` may not appear properly styled in a custom | ||
theme without an additional step. To ensure your Jobs pages properly inherit | ||
|
@@ -413,10 +461,10 @@ Specifically, your modified files should be updated to match these lines: | |
<https://github.com/artefactual/atom/blob/HEAD/apps/qubit/modules/staticpage/templates/homeSuccess.php#L28>`__ | ||
|
||
Recompiling after making modifications | ||
-------------------------------------- | ||
====================================== | ||
|
||
After making any necessary updates to your custom theme, you should rebuild | ||
the CSS for the custom themeplugin, using the ``make`` command. Here is an | ||
the CSS for the custom theme plugin, using the ``make`` command. Here is an | ||
example of rebuilding the CSS for the ArchivesCanada theme - you can swap in | ||
the name of your plugin: | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry a bit late to the party @melaniekung and @fiver-watson. We should add
package-lock. json
to this list of files.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @jraddaoui, we've discussed internally and decided not to include the
package-lock.json
to this list since the tarball includes build versions, meant to be ready for use and not for development env. however, if you have other reasons for including thepackage-lock.json
here, please let us know.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should, these are instructions to re-build pieces of that version and the lock file is important for that process (more than for development). Even if we only allow small version variations in
package.json
, we want to be "sure" the re-build uses the same dependency tree that was tested. There are other reasons too:https://docs.npmjs.com/cli/v10/configuring-npm/package-lock-json