This static comaps.app website is built with Zola.
We need your help to translate this site to your language on Codeberg Translate.
-
To build the site, either:
- Download the latest zola for your operating system and set up the necessary path variable.
- Run
zola servefor a local preview orzola buildto generate static site in thepublicfolder.
-
Or:
- Use the provided
compose.yamlwhich uses Zola in a container, automatically mounts the local directory, and runszola serve.
- Use the provided
-
Run
npm i && npm run formatif you want to pretty-format the Markdown and SCSS files. -
Upgrade npm dependencies with
npm run upgrade, make sure that you have installednpm-check-updatespackage.
Only the English Markdown files should be edited directly. After changing text in a .md file, please run ./tools/i18n.sh as described in TRANSLATIONS.md to propagate the english changes to all other languages.
New posts go in /content/news. There is a script at tools/new-post.sh to automatically create the correct directory structure and give you a template to edit.
There are two different types of redirects that can be created: 1. Website internal redirects (or aliases) if you want a page to be accessible under multiple slugs. 2. External redirects (if you want a link from comaps.app to redirect to an external site, like e.g. Codeberg).
In the front-matter of the markdown index.md or _index.md file, specify one or multiple aliases, like so:
aliases:
- relative/path
- another/path
For those you need to create a sub-folder that matches the redirect source you want. E.g. For creating a redirect that links comaps.app/latest to Codeberg, you need to create a content/latest/_index.md and the target into the front matter, e.g.
---
redirect_to: "https://codeberg.org/comaps/comaps/releases"
---
Components are little templates that can be embedded in your markdown pages. Here are some components that are currently available.
Use the image or image_fig component to add an image to your page.
Add a image.
{{ <image src="javi-and-rebecca-bikepackers.webp" alt="Javi and Rebecca" classes="max-w-40" /> }}
src(required) is the file name of the image. It assumes the image is placed in the same folder as the markdown page.alt(optional) is the alt tag you want to use for the image. Alt tags are always recommended to add for those who use screen readers.classes(optional) any class names you want to assign to the image.
Add an image with a caption.
{{ <image_fig src="javi-and-rebecca-bikepackers.webp" caption="Javi and Rebecca" alt="Javi and Rebecca" /> }}
{{ <image_fig src="javi-and-rebecca-bikepackers.webp" caption="Javi and Rebecca" alt="Javi and Rebecca" float={true} /> }}
{{ <image_fig src="javi-and-rebecca-bikepackers.webp" caption="Javi and Rebecca" alt="Javi and Rebecca" size="small" /> }}
src(required) is the file name of the image. It assumes the image is placed in the same folder as the markdown page.caption(required) the visible caption that describes what's in the image.alt(optional) is the alt tag you want to use for the image. Alt tags are always recommended to add for those who use screen readers. Usuallyaltandcaptionuse the same value, but not always.float(optional) if set, the figure will be on the right side of the page with the rest of the article reflowed around it.size(optional) size of the figure, set tosmallfor tall images or leave unset for regular size. Settingfloatimpliessmallsize.
Use the video or video_fig component to add a video to your page.
Add a plain video.
{{ <video src="anroid-auto-demo.webm" alt="A demonstration of Android Auto" classes="max-w-40" /> }}
src(required) is the file name of the video. It assumes the video is placed in the same folder as the markdown page.alt(optional) is the alt tag you want to use for the video. Alt tags are always recommended to add for those who use screen readers.classes(optional) any class names you want to assign to the video.
Add a video with a caption.
{{ <video_fig src="anroid-auto-demo.webm" alt="A demonstration of Android Auto" caption="A naviagtion session using Android Auto" /> }}
{{ <video_fig src="anroid-auto-demo.webm" alt="A demonstration of Android Auto" caption="A naviagtion session using Android Auto" float={true} /> }}
{{ <video_fig src="anroid-auto-demo.webm" alt="A demonstration of Android Auto" caption="A naviagtion session using Android Auto" size="small" /> }}
src(required) is the file name of the video. It assumes the video is placed in the same folder as the markdown page.caption(required) the visible caption that describes what's in the video.alt(optional) is the alt tag you want to use for the video. Alt tags are always recommended to add for those who use screen readers. Usuallyaltandcaptionuse the same value, but not always.float(optional) if set, the figure will be on the right side of the page with the rest of the article reflowed around it.size(optional) size of the figure, set tosmallfor tall videos or leave unset for regular size. Settingfloatimpliessmallsize.
Use the quote shortcode to add a blockquote to your page. For example:
{% <quote author="Brandon" work="Tuta Blog" url="https://tuta.com/blog/google-maps-alternatives-foss" date="2026-01-07"> %}
CoMaps can be used offline with or without network connection, comes with no annoying ads, and it doesn’t drain your mobile’s battery (unlike Google Maps). It’s available on Google Play, F-droid, IzzyOnDroid, Obtainium or APK download for Android, and on the App store for iOS.
{% </quote> %}
- The main quote goes between the
{% <quote> %}block and the{% </quote> %}block. author(required) the person who made the statement you're quoting. In some cases this could be a group or a company.work(optional) the name of the published work, like a book, website, etc, that the quote comes from. Think of it like the title in a citation.url(optional) a link to read the quote from it's source, if online.date(optional) adds a date representing when the quote was made.
The latest site is automatically deployed from main on the merging of a pull request.
It's also possible to manually deploy in the Actions menu.
Any good ideas and help with web site improvement are appreciated. And it's always better to discuss any improvement before implementing it to sync with our vision and plans.