docs: Add additional information and tips to Backup & Restore Usage Documentation Page & Shopping List

[ChipSkylark37]

What type of PR is this?

• documentation

What this PR does / why we need it:

• Adding notes regarding the Settings > Backup page in addition to the URL
• Listed out some additional actions that can be performed in this page. Added a tip for manual review / adjustment of the database.json file in the event that a restore fails
• Changed some verbiage (removing pluralization on some items)

Which issue(s) this PR fixes:

None - I am looking through some of the documentation and looking to offer some assistance on pieces that could use clarity or an update.

Special notes for your reviewer:

This is my first PR so I wanted to make some small changes to the documentation and see what the process looks like.

[boc-the-git]

Thanks for taking the time to raise a PR @ChipSkylark37!

Whilst I haven't gone through the actual doco change in detail, there's 2 key things to address with the PR itself.

1. You'll see that the CI checks are failing, that'll be because DOCS is not an allowable prefix for the PR title - docs is what you'd be after.
2. The rest of the title itself could be more meaningful. Something generic like Update backups-and-restoring.md isn't overly useful to someone reading a changelog whereas (for example) something like Added additional information to the backup/restore documentation is a bit more meaningful.

[ChipSkylark37]

I believe I have corrected the errors and performed a new commit after syncing the latest nightly.

[ChipSkylark37]

Additionally I made some changes to the Shopping List Section.

Would it be recommended to start a new commit for each one of these? I'm still learning the system a bit so I could use some advice on that.

[ChipSkylark37]

Hey all - I was just recently moving my instance from SQL > Postgres and was going to update the documentation a bit more.

I synced the latest mealie:nightly to my own fork, which overwrote the documentation changes in my local fork.

If this PR gets merged, I can then resync and do some further updates.

Is there anything I need to do to help get these changes merged?

[boc-the-git]

Would it be recommended to start a new commit for each one of these?

Depends if you mean commit or pull request.
Generally, yes it's best to have different commits for unrelated changes - though in the case of docs that isn't critically important.

As for a pull request, the general rule is that the smaller the better, as it allows for it to be reviewed more easily. Again for docs though, it's a grey area.

[boc-the-git]

I synced the latest mealie:nightly to my own fork, which overwrote the documentation changes in my local fork.

They'd still exist on the branch they belong to - you can see them on here: https://github.com/ChipSkylark37/mealie/tree/patch-1

[ChipSkylark37]

Reviewed and make changes per conversations.

[ChipSkylark37]

Forgive me as I don't want to spam, but I believe I've made all requested changes.

Since I'm still new to this, I can't tell if there's any action needed on my part or if this is all the normal checks / waiting for someone else to review & approve.

Cheers!

[Kuchenpirat]

If you have addressed the feedback above you should be all good to go.
We are a pretty small team with a lot of things going on outside of unpaid work for mealie, so things might take time.
As this is just a little docs pr where not much testing is needed, I expect it to be addressed sooner rather than later.

[ChipSkylark37]

Reviewed suggested changes:

• (Hopefully) fixed the indentation. I used a 'Tab' instead of 'Four Spaces'
• Removed images / assets temporarily while I think about the best way to do this moving forward since I like the idea of images, but dont want to have to upload images each time.

[ChipSkylark37]

removed 'Make Later'