Every now and then you will see an emoji within the Callsign Info Panel, for example if you enter KI2D you'll get the following: 🤩 Sebastián - Ham2K PoLo Creator.
+
+You can expect to see any of the following, and some others too:During an operation PoLo only needs an Internet connection to enable spotting, and to pull contact data from qrz.com, all other data is stored on your device.
+
+These offline data files, those within the Settings > Offline Data area along with those in Settings Callsign Notes synchronise periodically dependant on how often they might change. Callsign Notes update daily; the well established programmes such as SOTA update every 3 months or so, but POTA and WWFF are set to update monthly due to their possibilty of expanding as more sites are included within those programmes.
+
+Each of these data sets can be refreshed manually by selecting them in the Data Settings area, and tapping Refresh on the pop-up.
diff --git a/content/ca/docs/polo-features/online-offline/refresh-1.png b/content/ca/docs/polo-features/online-offline/refresh-1.png
new file mode 100644
index 00000000..8f274c70
Binary files /dev/null and b/content/ca/docs/polo-features/online-offline/refresh-1.png differ
diff --git a/content/ca/docs/polo-features/online-offline/unknownpark.png b/content/ca/docs/polo-features/online-offline/unknownpark.png
new file mode 100644
index 00000000..648a6811
Binary files /dev/null and b/content/ca/docs/polo-features/online-offline/unknownpark.png differ
diff --git a/content/ca/docs/polo-features/operation-notes/adif.png b/content/ca/docs/polo-features/operation-notes/adif.png
new file mode 100644
index 00000000..dd69c471
Binary files /dev/null and b/content/ca/docs/polo-features/operation-notes/adif.png differ
diff --git a/content/ca/docs/polo-features/operation-notes/index.md b/content/ca/docs/polo-features/operation-notes/index.md
new file mode 100644
index 00000000..464c45cb
--- /dev/null
+++ b/content/ca/docs/polo-features/operation-notes/index.md
@@ -0,0 +1,53 @@
+---
+title: "Operation Notes"
+weight: 144
+description: Adding notes to your operation including solar and weather readings
+---
+
+Keep a track of things.. grab the solar data, grab the current weather at your location or add a note for later.
+
+Key words entered in the "Their Call" entry field will prompt either the collection of this data or further entry of a note.
+
+#### NOTE
+
+
+
+Type NOTE and you will be prompted to keep typing to add a free-form note into your operation.
+
+
+
+#### WEATHER
+
+Enter WEATHER to pull the current weather for your location. If you wait before pressing send, the weather information will be displayed on screen. If you then press send, it will be saved to the log.
+
+
+
+#### SOLAR
+
+Enter SOLAR to pull the current solar data from [hamqsl.com](https://www.hamqsl.com/solarxml.php) and display the data in a QSO line of the operation. If you wait before pressing send, the weather information will be displayed on screen. If you then press send, it will be saved to the log.
+
+
+
+Notes entered in this form are exported as additional ADIF fields in the export file. They contain multibyte characters (HTML encoded emojis). The field names are not part of the ADIF specification and will be ignored by your usual logging program.
+
+
+
+See also [Rove Operations](../rove-operations/) for and explanation of the BREAK command.
+
+#### Consuming the PoLo Notes
+
+The PoLo notes, SOLAR, WEATHER, NOTE, START, BREAK are all exported in the ADIF file as the following ADIF fields:
+
+```
+X_HAM2K_SOLAR
+X_HAM2K_SOLAR_DATA
+X_HAM2K_WEATHER
+X_HAM2K_WEATHER_DATA
+X_HAM2K_NOTE
+X_HAM2K_START
+X_HAM2K_BREAK
+```
+
+These fields will be ignored by most applications processing ADIF files but they may be of interest to some application developers.
+
+While the format of SOLAR and WEATHER are as you see them on screen, the format of the SOLAR_DATA and WEATHER_DATA fields which are exported only, is json and can be further parsed.
diff --git a/content/ca/docs/polo-features/operation-notes/note.png b/content/ca/docs/polo-features/operation-notes/note.png
new file mode 100644
index 00000000..3dae9d03
Binary files /dev/null and b/content/ca/docs/polo-features/operation-notes/note.png differ
diff --git a/content/ca/docs/polo-features/operation-notes/noteline.png b/content/ca/docs/polo-features/operation-notes/noteline.png
new file mode 100644
index 00000000..046553d1
Binary files /dev/null and b/content/ca/docs/polo-features/operation-notes/noteline.png differ
diff --git a/content/ca/docs/polo-features/operation-notes/solardata.png b/content/ca/docs/polo-features/operation-notes/solardata.png
new file mode 100644
index 00000000..8fa36249
Binary files /dev/null and b/content/ca/docs/polo-features/operation-notes/solardata.png differ
diff --git a/content/ca/docs/polo-features/operation-notes/weather.png b/content/ca/docs/polo-features/operation-notes/weather.png
new file mode 100644
index 00000000..7f70cece
Binary files /dev/null and b/content/ca/docs/polo-features/operation-notes/weather.png differ
diff --git a/content/ca/docs/polo-features/operation-templates/index.md b/content/ca/docs/polo-features/operation-templates/index.md
new file mode 100644
index 00000000..5d10cce5
--- /dev/null
+++ b/content/ca/docs/polo-features/operation-templates/index.md
@@ -0,0 +1,15 @@
+---
+title: Operation Templates
+weight: 52
+description: Previous operation setups can be used to start new ones with just a few taps.
+---
+
+We tend to keep doing the same sorts of portable operations/activities. PoLo will recognise the pattern and offer a template for your next new Operation base on prior behaviour. The templates in the offering below show the most popular operations. Selecting one will save a few taps when creating a new one.
+
+
+
+Tapping on the first template above, will create an operation for VK1AO and add a single POTA park and a single WWFF park. Assuming a GPS location has been obtained or set, both these added parks will be populated from the offline parks list. The parks added will be selected from the parks nearest to the currently set location.
+
+Sometimes the park location and your location does not reflect the exact park you are in but this can easily be changed. Often, however, the selection is done for you and saves a few more taps and keying to set the operation up.
+
+If you popularly operate as 2 or 3 operators in a group, the template will show the callsigns of all the operators and save keying them in to begin.
\ No newline at end of file
diff --git a/content/ca/docs/polo-features/operation-templates/operationtemplates.png b/content/ca/docs/polo-features/operation-templates/operationtemplates.png
new file mode 100644
index 00000000..7ff52d9b
Binary files /dev/null and b/content/ca/docs/polo-features/operation-templates/operationtemplates.png differ
diff --git a/content/ca/docs/polo-features/operations/index.md b/content/ca/docs/polo-features/operations/index.md
new file mode 100644
index 00000000..23e98cde
--- /dev/null
+++ b/content/ca/docs/polo-features/operations/index.md
@@ -0,0 +1,66 @@
+---
+title: Operations/QSO List Panel
+weight: 50
+description: Your list of QSOs.
+---
+
+In the full version of PoLo, the top of the panel is demarcated by 4 tabs - QSOs, SPOTS, MAP and OPERATION
+
+
+
+### QSOs
+
+
+
+The PoLo QSOs List is where you will interact with the application once you've set up your operation. Once your frequency and mode have been entered (which may have been picked up from your previous operation) the left pointing (or less than) arrow expands the operations panel to show all available interactions. Tapping the Controls (settings) wheel will reveal any that are available, but not set with the operation. This might be useful when a caller from an unexpected award system such as UKBOTA or SiOTA call you. Selecting them from the More Controls section will make them available for use within the Active Controls. Once the selection is complete back out of the Controls section by tapping the Controls wheel.
+
+Tapping an Active Control will provide the appropriate fields for information to be entered, eg P2P will enable park details to be entered in addition to the contact details. The Notes control is for per contact information to be added, and the More Control displays all information stored for the QSO.
+
+
+
+The Callsign/Operation Information Panel can show various pieces of information dependant on your installation and circumstances.
+
+- If you entered a qrz.com account in PoLo settings then the name and location held for your contact will be displayed.
+- If you subscribe to qrz.com then their bearing and distance will also be displayed (assuming your contact has location details set at qrz.com)
+- You should also see a country flag, and occasionally an emoji, that contact is in the Ham2K Hams of Note list. The meaning for these is covered in the emojis area of the manual.
+- If you've worked a station previously then the number of contacts and time period will be displayed.
+
+Once QSO details are entered, tapping the up arrow will save them into the operation log. Tapping that QSO or an other within the operation log will bring the details into the Callsign Information Panel where you can change them and save them by tapping the save icon, or delete the QSO with the trash can icon, which will need to be tapped twice before the QSO is lined through in the operation log. A deleted QSO can be recovered by tapping it in the operation log, then tapping the undo arrow, and saving.
+
+### SPOTS
+
+Tapping on the SPOTS tab will shift the view to the current spots which will be filtered according to your previous settings. Tapping a spot will pre-fill the QSO entry panel with the information from the spot you tapped. QSOs can be entered this way without chaging the frequency or band previously set in the QSO panel. When the QSo is saved, the previous settings return as active.
+
+### MAP
+
+Tapping on the MAP tab will shift the view to the QSO map for the current Operation. More information on Mapping can be found elsewhere in this manual.
+
+### OPERATION
+
+Finally, the OPERATION tab provides access to the settings such as your location, the activities attached to the operation and the features associated with exporting the operation logs ready for upload to 3rd party websites and your own home logging system if desired.
+
+### Callsign Lookups
+
+Tapping on the area above the callsign entry field will open the QRZ lookup for the callsign in focus. This provides further lookup data and the callsign Operator's QRZ default image. It also summarises contact history for that callsign.
+
+### QRZ images
+
+The QRZ lookup panel which displays the callsign's name and QTH details, also displays the default image from theoperator's QRZ page. This image is displayed by default, but can be turned off if your bandwidth is insufficient or you consider it unnecessary.
+
+Tap the eye icon onb the bottom left corner of the image to make it disappear. This setting is sticky and will prevent future retrievals of all such images from QRZ. To turn image retrieval back on, tap the "Show Image" button to bring them back for future lookups.
+
+
+
+### Operation Stats
+
+
+
+Tapping on the QSO summary bar will display the operation summary which contains a summary of bands, modes, DXCC entities and activity such as park2Park contacts for the programs being activated.
+
+
+
+It is also possible to access the Operation Stats by tapping on the Operation Information area.
+
+
+
+When no callsign is present in the "Their Call" field.
\ No newline at end of file
diff --git a/content/ca/docs/polo-features/operations/operationstats.png b/content/ca/docs/polo-features/operations/operationstats.png
new file mode 100644
index 00000000..5415b757
Binary files /dev/null and b/content/ca/docs/polo-features/operations/operationstats.png differ
diff --git a/content/ca/docs/polo-features/operations/qsolist.png b/content/ca/docs/polo-features/operations/qsolist.png
new file mode 100644
index 00000000..3645dec0
Binary files /dev/null and b/content/ca/docs/polo-features/operations/qsolist.png differ
diff --git a/content/ca/docs/polo-features/operations/qsopanel.png b/content/ca/docs/polo-features/operations/qsopanel.png
new file mode 100644
index 00000000..0f910fc9
Binary files /dev/null and b/content/ca/docs/polo-features/operations/qsopanel.png differ
diff --git a/content/ca/docs/polo-features/operations/showimage.png b/content/ca/docs/polo-features/operations/showimage.png
new file mode 100644
index 00000000..165c7097
Binary files /dev/null and b/content/ca/docs/polo-features/operations/showimage.png differ
diff --git a/content/ca/docs/polo-features/operations/toptabs.png b/content/ca/docs/polo-features/operations/toptabs.png
new file mode 100644
index 00000000..6df297e5
Binary files /dev/null and b/content/ca/docs/polo-features/operations/toptabs.png differ
diff --git a/content/ca/docs/polo-features/operationsummary/index.md b/content/ca/docs/polo-features/operationsummary/index.md
new file mode 100644
index 00000000..44d320d0
--- /dev/null
+++ b/content/ca/docs/polo-features/operationsummary/index.md
@@ -0,0 +1,28 @@
+---
+title: Home Screen
+weight: 48
+description: Your list of Operations.
+---
+
+PoLo opens on the Operations Summary page. A list of your operations are presented to you with your callsign, activity code/ID number, the name of the location, the number of QSOs in the activity so far and the date of the operation. The number of QSOs shown top right of the Operation band is the number of QSOs not including any QSOs marked as deleted.
+
+
+
+At the bottom of the Operations Summary is a Quick Call Lookup and Spots link.
+
+
+
+### Quick Callsign Lookup
+
+Enter a callsign in the lookup area and the lookup data will display including any Callsign Notes you have present for the callsign.
+Tap the panel to open the full QRZ callsign lookup.
+
+
+
+### Spots
+
+Tap the hamburger icon to open the Spots page. This can be handy for checking spots when not in a specific operation. Unlike the action available during an operation, tapping a spot on this view will not enter the details to start logging a QSO. You need to be in an operation for this action to apply.
+
+### Opening an Operation
+
+Tap on an operation band to open the Operation for editing. See [Operations/QSO List Panel](../operations/) for information on entering QSOs.
diff --git a/content/ca/docs/polo-features/operationsummary/operationslist.png b/content/ca/docs/polo-features/operationsummary/operationslist.png
new file mode 100644
index 00000000..8224fdd2
Binary files /dev/null and b/content/ca/docs/polo-features/operationsummary/operationslist.png differ
diff --git a/content/ca/docs/polo-features/operationsummary/qrzlookup.png b/content/ca/docs/polo-features/operationsummary/qrzlookup.png
new file mode 100644
index 00000000..50cf2c25
Binary files /dev/null and b/content/ca/docs/polo-features/operationsummary/qrzlookup.png differ
diff --git a/content/ca/docs/polo-features/operationsummary/quicklookup.png b/content/ca/docs/polo-features/operationsummary/quicklookup.png
new file mode 100644
index 00000000..086f0460
Binary files /dev/null and b/content/ca/docs/polo-features/operationsummary/quicklookup.png differ
diff --git a/content/ca/docs/polo-features/rove-operations/break.png b/content/ca/docs/polo-features/rove-operations/break.png
new file mode 100644
index 00000000..349678c2
Binary files /dev/null and b/content/ca/docs/polo-features/rove-operations/break.png differ
diff --git a/content/ca/docs/polo-features/rove-operations/break2.png b/content/ca/docs/polo-features/rove-operations/break2.png
new file mode 100644
index 00000000..f2373c51
Binary files /dev/null and b/content/ca/docs/polo-features/rove-operations/break2.png differ
diff --git a/content/ca/docs/polo-features/rove-operations/export.png b/content/ca/docs/polo-features/rove-operations/export.png
new file mode 100644
index 00000000..682cbee2
Binary files /dev/null and b/content/ca/docs/polo-features/rove-operations/export.png differ
diff --git a/content/ca/docs/polo-features/rove-operations/exportlist.png b/content/ca/docs/polo-features/rove-operations/exportlist.png
new file mode 100644
index 00000000..7dcb68fa
Binary files /dev/null and b/content/ca/docs/polo-features/rove-operations/exportlist.png differ
diff --git a/content/ca/docs/polo-features/rove-operations/index.md b/content/ca/docs/polo-features/rove-operations/index.md
new file mode 100644
index 00000000..0e6956bc
--- /dev/null
+++ b/content/ca/docs/polo-features/rove-operations/index.md
@@ -0,0 +1,47 @@
+---
+title: "Operations with changes in location"
+linkTitle: "Rove Operations"
+weight: 113
+description: >-
+ The BREAK command is used for for changing locations during an Operation.
+---
+
+Typically, PoLo operations are devoted to one location e.g. a park or summit activation. If multiple parks are activated simultaneously, PoLo will generate multiple logs, one for each reference, and one full log of the operation containing lookup/personal data depending on your preference settings.
+
+#### The BREAK Command
+
+With the use of the BREAK command it is possible to remain logging in one Operation yet insert a BREAK from your current location and start in another location. This command applies also to hunters who wish to record their new/next current location for the next batch of QSOs.
+
+See also [Operation Notes](../operation-notes/) for other "Their Call" field entry commands.
+
+#### Creating the BREAK
+
+
+
+Enter BREAK in the "Their Call" field. If you are in a General Operation, the break will show your current gridsquare as a line break in your QSO list
+
+
+
+Now change your grid square in the Operation | Location and when you return, the break line will show the new gridsquare.
+
+If you are in an activation operation, change your park or other activation reference(s) and when you return, the break will show the new park or reference ID and gridsquare.
+
+
+
+#### Log exports
+
+Continue on adding contacts until you make another break or go QRT.
+
+When you have finished the operation, the Export list of logs for the Operation will show a log for each break and an overall "full" log for all QSO across the operation.
+
+
+
+The QSOs in the full log will have the grid location and MY_SIG_INFO fields relevant to each break.
+
+
+
+As usual, the individual logs for each reference can be used to upload to your program admin and the full log can be imported to your log manager in one step.
+
+Combining contests and park activation is an ideal condidate for this type of operation setup. Your exchanges can change but you will finish up with one log which makes it easier to submit to your contest.
+
+See also [Consuming PoLo Notes](../operation-notes/#consuming-the-polo-notes)
\ No newline at end of file
diff --git a/content/ca/docs/polo-features/rove-operations/refbreak.png b/content/ca/docs/polo-features/rove-operations/refbreak.png
new file mode 100644
index 00000000..8dfd4b64
Binary files /dev/null and b/content/ca/docs/polo-features/rove-operations/refbreak.png differ
diff --git a/content/ca/docs/polo-features/satellites/addsatelliteop.png b/content/ca/docs/polo-features/satellites/addsatelliteop.png
new file mode 100644
index 00000000..f45af535
Binary files /dev/null and b/content/ca/docs/polo-features/satellites/addsatelliteop.png differ
diff --git a/content/ca/docs/polo-features/satellites/enablesatelliteop.png b/content/ca/docs/polo-features/satellites/enablesatelliteop.png
new file mode 100644
index 00000000..8a7226a0
Binary files /dev/null and b/content/ca/docs/polo-features/satellites/enablesatelliteop.png differ
diff --git a/content/ca/docs/polo-features/satellites/index.md b/content/ca/docs/polo-features/satellites/index.md
new file mode 100644
index 00000000..069ede5d
--- /dev/null
+++ b/content/ca/docs/polo-features/satellites/index.md
@@ -0,0 +1,34 @@
+---
+title: Satellite Operations
+weight: 120
+description: |
+ PoLo offers specific fields for recording QSOs via Orbiting Satellite Carrying Amateur Radio (OSCAR) satellites.
+---
+
+### Enabling a Satellite Operation
+
+
+
+Scroll down on the App Features tab to find "Other Features". Enable Satellite Operations.
+
+Next, create a New Operation and in the Activities section, add Satellite Operations.
+
+
+
+Next go to the QSO tab of the Operation and open the "More Controls" section. Tap the Sats control to bring the satellite list into view for the operation.
+
+
+
+Selecting the Stats button will provide a drop-down list of the satellites currently available in PoLo, select the one you are working. It should bring the frequencies into view for that satellite.
+
+
+
+Ensure that the satellite you are selecting is visibly selected in the control panel.
+
+
+
+The export feature will export all fields associated with these satellite contacts.
+
+[The list of satellites available for selection within PoLo can be found here](https://github.com/ham2k/polo.ham2k.com/blob/main/content/en/data/satellites.json).
+
+If you are aware of a satellite missing from this list you are highly encouraged to make edits and additions to the file for yourself and the benefit of others. It's as simple as creating a GitHub login if you do not already have one, then making the edits following the form shown in other entriese. **Don't be frightened or hesitate...** you cannot make a mistake or break anything. Any formatting issues can be corrected in the Pull Request Approval process. You may also leave a message on the The fastest, easiest, bestest way to log your amateur radio operations on the go.
+
+
+
+
+{{< blocks/link-down color="info" >}}
+{{< /blocks/cover >}}
+
+{{% blocks/lead color="primary" %}}
+
+PoLo, short for Portable Logger, is a mobile application for amateur radio operators to log their contacts on the go. It is designed to be simple, fast, and easy to use, with a focus on the most important features for logging contacts.
+
+It supports multiple activation types such as: POTA - Parks On The Air, SOTA - Summits On The Air, WWFF - Worldwide Flora & Fauna,
+Field Day, Winter Field Day, and many more.
+
+{{% /blocks/lead %}}
+
+{{% blocks/section color="dark" type="row" %}}
+
+{{% blocks/feature icon="fas fa-comments" title="Join our Community!" %}}
+
+Our [Forums](https://forums.ham2k.com/) is where you can report issues, get help, suggest ideas and more, and our [Discord Server](https://discord.gg/c4Th9QkByJ) is where you can chat with the developers and other users.
+
+{{% /blocks/feature %}}
+
+{{% blocks/feature icon="fab fa-github" title="PoLo is Open Source!" %}}
+
+Check the [source code](https://github.com/ham2k/app-polo) on **GitHub**.
+
+New contributors are always welcome!
+
+{{% /blocks/feature %}}
+
+{{% blocks/feature icon="fa fa-coins" title="Support the Project!" %}}
+
+Help keep the PoLo going with your money at [Buy Me A Coffee](https://buymeacoffee.com/ham2k). Any amount helps cover the project's costs and is greatly appreciated!
+
+{{% /blocks/feature %}}
+
+{{% /blocks/section %}}
+
+
diff --git a/content/ca/apple-appstore-badge-100.png b/content/ca/apple-appstore-badge-100.png
new file mode 100644
index 00000000..06e16e76
Binary files /dev/null and b/content/ca/apple-appstore-badge-100.png differ
diff --git a/content/ca/apple-appstore-badge.png b/content/ca/apple-appstore-badge.png
new file mode 100644
index 00000000..22fe6eee
Binary files /dev/null and b/content/ca/apple-appstore-badge.png differ
diff --git a/content/ca/apple-appstore-badge.svg b/content/ca/apple-appstore-badge.svg
new file mode 100644
index 00000000..1896ab0c
--- /dev/null
+++ b/content/ca/apple-appstore-badge.svg
@@ -0,0 +1,47 @@
+
+
diff --git a/content/ca/apple-testflight-badge.png b/content/ca/apple-testflight-badge.png
new file mode 100644
index 00000000..652b2a73
Binary files /dev/null and b/content/ca/apple-testflight-badge.png differ
diff --git a/content/ca/data/NOTES.md b/content/ca/data/NOTES.md
new file mode 100644
index 00000000..bd1ed22d
--- /dev/null
+++ b/content/ca/data/NOTES.md
@@ -0,0 +1,5 @@
+Update 03/04/2025:
+
+- Added satellites IO-86, SO-124, XW-2B, and MO-122 with information found from https://github.com/palewire/amateur-satellite-database/blob/main/data/amsat-active-frequencies.csv
+ These were added based on the most active FM Repeater and Transponder list from https://www.amsat.org/two-way-satellites/ provided by 4O4A in the HAM2K forums topic
+ linked here https://forums.ham2k.com/t/updating-satellite-list/653/10
diff --git a/content/ca/data/satellites.json b/content/ca/data/satellites.json
new file mode 100644
index 00000000..deb43e6b
--- /dev/null
+++ b/content/ca/data/satellites.json
@@ -0,0 +1,743 @@
+[
+ {
+ "name": "AO-7",
+ "number": 7530,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 29.4,
+ "upperMHz": 29.5
+ },
+ {
+ "mode": "linear",
+ "lowerMHz": 145.925,
+ "upperMHz": 145.975
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.85,
+ "upperMHz": 145.95
+ },
+ {
+ "mode": "linear",
+ "lowerMHz": 432.125,
+ "upperMHz": 432.175
+ }
+ ]
+ },
+ {
+ "name": "AO-27",
+ "number": 22825,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.795,
+ "upperMHz": 436.795
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.85,
+ "upperMHz": 145.85
+ }
+ ]
+ },
+ {
+ "name": "AO-73",
+ "number": 39444,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.95,
+ "upperMHz": 145.97
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.13,
+ "upperMHz": 435.15
+ }
+ ]
+ },
+ {
+ "name": "AO-91",
+ "number": 43017,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.96,
+ "upperMHz": 145.96
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 435.25,
+ "upperMHz": 435.25
+ }
+ ]
+ },
+ {
+ "name": "AO-92",
+ "number": 43017,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.88,
+ "upperMHz": 145.88
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 435.35,
+ "upperMHz": 435.35
+ }
+ ]
+ },
+ {
+ "name": "AO-123",
+ "number": 61781,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 435.4,
+ "upperMHz": 435.4
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.85,
+ "upperMHz": 145.85
+ }
+ ]
+ },
+ {
+ "name": "BeliefSat-0",
+ "number": 58695,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.98,
+ "upperMHz": 145.98
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 437,
+ "upperMHz": 437
+ }
+ ]
+ },
+ {
+ "name": "CAS-4A",
+ "number": 42761,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.86,
+ "upperMHz": 145.88
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.21,
+ "upperMHz": 435.23
+ }
+ ]
+ },
+ {
+ "name": "CAS-4B",
+ "number": 42759,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.915,
+ "upperMHz": 145.935
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.27,
+ "upperMHz": 435.29
+ }
+ ]
+ },
+ {
+ "name": "FO-29",
+ "number": 424278,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.8,
+ "upperMHz": 435.9
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.9,
+ "upperMHz": 146
+ }
+ ]
+ },
+ {
+ "name": "FO-99",
+ "number": 43937,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.88,
+ "upperMHz": 435.91
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.9,
+ "upperMHz": 145.93
+ }
+ ]
+ },
+ {
+ "name": "IO-86",
+ "number": 40931,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.825,
+ "upperMHz": 435.88
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.825,
+ "upperMHz": 145.88
+ }
+ ]
+ },
+ {
+ "name": "IO-117",
+ "number": 53106,
+ "modulation": "digital",
+ "downlinks": [
+ {
+ "mode": "digital",
+ "lowerMHz": 435.31,
+ "upperMHz": 435.31
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "digital",
+ "lowerMHz": 435.31,
+ "upperMHz": 435.31
+ }
+ ]
+ },
+ {
+ "name": "ARISS",
+ "number": 25544,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 437.8,
+ "upperMHz": 437.8
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.99,
+ "upperMHz": 145.99
+ }
+ ]
+ },
+ {
+ "name": "JO-97",
+ "number": 43803,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.855,
+ "upperMHz": 145.875
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.1,
+ "upperMHz": 435.12
+ }
+ ]
+ },
+ {
+ "name": "LEDSAT",
+ "number": 49069,
+ "modulation": "digital",
+ "downlinks": [
+ {
+ "mode": "digital",
+ "lowerMHz": 435.19,
+ "upperMHz": 435.19
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "digital",
+ "lowerMHz": 435.31,
+ "upperMHz": 435.31
+ }
+ ]
+ },
+ {
+ "name": "CAS-3H",
+ "number": 40908,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 437.2,
+ "upperMHz": 437.2
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 144.35,
+ "upperMHz": 144.35
+ }
+ ]
+ },
+ {
+ "name": "PO-101",
+ "number": 43678,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.9,
+ "upperMHz": 145.9
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 437.5,
+ "upperMHz": 437.5
+ }
+ ]
+ },
+ {
+ "name": "RS-44",
+ "number": 44909,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.61,
+ "upperMHz": 435.67
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.935,
+ "upperMHz": 145.995
+ }
+ ]
+ },
+ {
+ "name": "SO-50",
+ "number": 27607,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.795,
+ "upperMHz": 436.795
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.85,
+ "upperMHz": 145.85
+ }
+ ]
+ },
+ {
+ "name": "SO-121",
+ "number": 58567,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.663,
+ "upperMHz": 436.663
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.875,
+ "upperMHz": 145.875
+ }
+ ]
+ },
+ {
+ "name": "SO-124",
+ "number": 62690,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.888,
+ "upperMHz": 436.888
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.925,
+ "upperMHz": 145.925
+ }
+ ]
+ },
+ {
+ "name": "SO-125",
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.666,
+ "upperMHz": 436.666
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.875,
+ "upperMHz": 145.875
+ }
+ ]
+ },
+ {
+ "name": "TO-108",
+ "number": 44909,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.915,
+ "upperMHz": 145.935
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.27,
+ "upperMHz": 435.29
+ }
+ ]
+ },
+ {
+ "name": "XW-2A",
+ "number": 40903,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.665,
+ "upperMHz": 145.685
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.03,
+ "upperMHz": 435.05
+ }
+ ]
+ },
+ {
+ "name": "XW-2B",
+ "number": 40911,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.73,
+ "upperMHz": 145.75
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.09,
+ "upperMHz": 435.11
+ }
+ ]
+ },
+ {
+ "name": "XW-2C",
+ "number": 40906,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.975,
+ "upperMHz": 145.815
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.15,
+ "upperMHz": 435.17
+ }
+ ]
+ },
+ {
+ "name": "EO-88",
+ "number": 42017,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.96,
+ "upperMHz": 145.99
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.015,
+ "upperMHz": 435.045
+ }
+ ]
+ },
+ {
+ "name": "HO-113",
+ "number": 50466,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.165,
+ "upperMHz": 435.195
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.855,
+ "upperMHz": 145.885
+ }
+ ]
+ },
+ {
+ "name": "HO-119",
+ "number": 54816,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.165,
+ "upperMHz": 435.195
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.855,
+ "upperMHz": 145.885
+ }
+ ]
+ },
+ {
+ "name": "MO-122",
+ "number": 60209,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 435.81,
+ "upperMHz": 435.84
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 145.94,
+ "upperMHz": 145.94
+ }
+ ]
+ },
+ {
+ "name": "Tevel-2",
+ "number": 51069,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.4,
+ "upperMHz": 436.4
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.97,
+ "upperMHz": 145.97
+ }
+ ]
+ },
+ {
+ "name": "Tevel-3",
+ "number": 50988,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.4,
+ "upperMHz": 436.4
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.97,
+ "upperMHz": 145.97
+ }
+ ]
+ },
+ {
+ "name": "Tevel-4",
+ "number": 51063,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.4,
+ "upperMHz": 436.4
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.97,
+ "upperMHz": 145.97
+ }
+ ]
+ },
+ {
+ "name": "Tevel-5",
+ "number": 50998,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.4,
+ "upperMHz": 436.4
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.97,
+ "upperMHz": 145.97
+ }
+ ]
+ },
+ {
+ "name": "Tevel-6",
+ "number": 50999,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.4,
+ "upperMHz": 436.4
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.97,
+ "upperMHz": 145.97
+ }
+ ]
+ },
+ {
+ "name": "Tevel-7",
+ "number": 51062,
+ "modulation": "fm",
+ "downlinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 436.4,
+ "upperMHz": 436.4
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "fm",
+ "lowerMHz": 145.97,
+ "upperMHz": 145.97
+ }
+ ]
+ },
+ {
+ "name": "QO-100",
+ "number": 43700,
+ "modulation": "linear",
+ "downlinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 10489.5,
+ "upperMHz": 10489.8
+ },
+ {
+ "mode": "linear",
+ "lowerMHz": 10491,
+ "upperMHz": 10499.8
+ }
+ ],
+ "uplinks": [
+ {
+ "mode": "linear",
+ "lowerMHz": 2400.05,
+ "upperMHz": 2400.3
+ },
+ {
+ "mode": "linear",
+ "lowerMHz": 2401.5,
+ "upperMHz": 2409.5
+ }
+ ]
+ }
+]
diff --git a/content/ca/docs/_index.md b/content/ca/docs/_index.md
new file mode 100644
index 00000000..e93d6206
--- /dev/null
+++ b/content/ca/docs/_index.md
@@ -0,0 +1,16 @@
+---
+linkTitle: The Manual
+menu: { main: { weight: 20 } }
+weight: 20
+---
+
+
+
+This the manual for the Ham2K Portable Logger which is a mobile application currently available through the Google and Apple environments, as well as on Github as PoLo is an Open Source project.
+
+The menu will take you to the various sections on installation, configuration, and tips and tricks. If you are unable to find the answer you need then the Community section will guide to places where you can get further help.
+
+We do suggest you visit the [YouTube channel](https://www.youtube.com/@ham2kapps) for a more visual guide to the application,
+in particular the [How-Tos Playlist](https://www.youtube.com/playlist?list=PLf7WezuuytcevOjItbmQ8Vq8PJdo3JxQ9).
diff --git a/content/ca/docs/community.md b/content/ca/docs/community.md
new file mode 100644
index 00000000..d90a0937
--- /dev/null
+++ b/content/ca/docs/community.md
@@ -0,0 +1,18 @@
+---
+title: Community
+description: Where to find your fellow users.
+weight: 300
+---
+
+## Forums
+
+The [Ham2K Forums](https://forums.ham2k.com/) is the best place to report bugs, suggest new features and discuss the use of PoLo with other users.
+
+## Discord
+
+We have a [Discord Server](https://discord.gg/c4Th9QkByJ) where you can chat with other users and the development team.
+
+## Instagram
+
+The [@Ham2KApps](https://www.instagram.com/ham2kapps/) Instagram account is a great place to see what other users are doing with PoLo.
+
diff --git a/content/ca/docs/contribution-guidelines/index.md b/content/ca/docs/contribution-guidelines/index.md
new file mode 100644
index 00000000..ea47051b
--- /dev/null
+++ b/content/ca/docs/contribution-guidelines/index.md
@@ -0,0 +1,86 @@
+---
+title: Contribution Guidelines
+weight: 310
+description: How to contribute to the docs
+---
+
+{{% pageinfo %}}
+These basic sample guidelines assume that your Docsy site is deployed using Netlify and your files are stored in GitHub. You can use the guidelines "as is" or adapt them with your own instructions: for example, other deployment options, information about your doc project's file structure, project-specific review guidelines, versioning guidelines, or any other information your users might find useful when updating your site. [Kubeflow](https://github.com/kubeflow/website/blob/master/README.md) has a great example.
+
+Don't forget to link to your own doc repo rather than our example site! Also make sure users can find these guidelines from your doc repo README: either add them there and link to them from this page, add them here and link to them from the README, or include them in both locations.
+{{% /pageinfo %}}
+
+We use [Hugo](https://gohugo.io/) to format and generate our website, the
+[Docsy](https://github.com/google/docsy) theme for styling and site structure,
+and [Netlify](https://www.netlify.com/) to manage the deployment of the site.
+Hugo is an open-source static site generator that provides us with templates,
+content organisation in a standard directory structure, and a website generation
+engine. You write the pages in Markdown (or HTML if you want), and Hugo wraps them up into a website.
+
+All submissions, including submissions by project members, require review. We
+use GitHub pull requests for this purpose. Consult
+[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
+information on using pull requests.
+
+### Quick start with Netlify
+
+Here's a quick guide to updating the docs. It assumes you're familiar with the
+GitHub workflow and you're happy to use the automated preview of your doc
+updates:
+
+1. Fork the [PoLo Docs repo](https://github.com/ham2k/polo.ham2k.com) on GitHub.
+2. Make your changes and send a pull request (PR).
+3. If you're not yet ready for a review, add "WIP" to the PR name to indicate
+ it's a work in progress. (**Don't** add the Hugo property
+ "draft = true" to the page front matter, because that prevents the
+ auto-deployment of the content preview described in the next point.)
+4. Wait for the automated PR workflow to do some checks. When it's ready,
+ you should see a comment like this: **deploy/netlify — Deploy preview ready!**
+5. Click **Details** to the right of "Deploy preview ready" to see a preview
+ of your updates.
+6. Continue updating your doc and pushing your changes until you're happy with
+ the content.
+7. When you're ready for a review, add a comment to the PR, and remove any
+ "WIP" markers.
+
+### Updating a single page
+
+If you've just spotted something you'd like to change while using the docs, Docsy has a shortcut for you:
+
+1. Click **Edit this page** in the top right hand corner of the page.
+2. If you don't already have an up to date fork of the project repo, you are prompted to get one - click **Fork this repository and propose changes** or **Update your Fork** to get an up to date version of the project to edit. The appropriate page in your fork is displayed in edit mode.
+3. Follow the rest of the [Quick start with Netlify](#quick-start-with-netlify) process above to make, preview, and propose your changes.
+
+### Previewing your changes locally
+
+If you want to run your own local Hugo server to preview your changes as you work:
+
+1. Follow the instructions in [Getting started](/docs/getting-started) to install Hugo and any other tools you need. You'll need at least **Hugo version 0.45** (we recommend using the most recent available version), and it must be the **extended** version, which supports SCSS.
+
+2. Fork the [PoLo Docs repo](https://github.com/ham2k/polo.ham2k.com) repo into your own project, then create a local copy using `git clone`. Don’t forget to use `--recurse-submodules` or you won’t pull down some of the code you need to generate a working site.
+
+ ```
+ git clone --recurse-submodules --depth 1 https://github.com/ham2k/polo.ham2k.com
+ ```
+
+3. Run `hugo server` in the site root directory. By default your site will be available at http://localhost:1313/. Now that you're serving your site locally, Hugo will watch for changes to the content and automatically refresh your site.
+
+4. Continue with the usual GitHub workflow to edit files, commit them, push the
+ changes up to your fork, and create a pull request.
+
+## Creating an issue
+
+If you've found a problem in the docs, but you're not sure how to fix it yourself, please create an issue in the [PoLo Docs repo](https://github.com/ham2k/polo.ham2k.com/issues). You can also create an issue about a specific page by clicking the **Create Issue** button in the top right hand corner of the page.
+
+### Useful resources
+
+- [Docsy user guide](https://www.docsy.dev/docs/): All about Docsy, including how it manages navigation, look and feel, and multi-language support.
+- [Hugo documentation](https://gohugo.io/documentation/): Comprehensive reference for Hugo.
+- [Github Hello World!](https://guides.github.com/activities/hello-world/): A basic introduction to GitHub concepts and workflow.
+
+### How to...
+
+#### Add an Icon
+
+If you want to add an icon to a page, referencing one of the icons in the app, visit the [Material Design Icon Community Library](https://pictogrammers.com/library/mdi/), find the icon you want,
+click on the "Copy SVG" button, paste the SVG code into your page and add a `height="1.5rem"` attribute to the `