localcrag / localcragapp Goto Github PK

• Mobile optimisation
• Add new button

Separate page with users that have the local badge, with some info added liek fav boulders etc (see https://nahetalbouldering.com/die-locals/)

Implement basic crag model functionality

• Alphabetically
• As per Priority setting
• Line count
• Mean rating

Add fitting tab titles everywhere

Galeriefunktion auf Gebiets-/Sektor-/Bereichs-/Boulderebene. Man läd ein Foto direkt auf der jeweiligen Ebene hoch und es gilt für diese und alle darüber befindlichen und wird dort in der jeweiligen Galerie gelistet. Also jedes Bild bei Windei wird gelistet bei Romani und Glees.

Features:

• Configure cascade accordingly - ticks should delete on user delete
• Total ascent count should be property of line and work without querying ascends
• Plan for fast crag/sector/... ascent list loading - extra FK's needed?
• Add "Add ascent" buttons in line detail view and line list views
• Show "Add ascents" buttons in green / ticked for ticked lines
• Add navigation targets for lines etc in ascent lists
• Add user tick lists
• Add edit buttons ascent lists for own ascents
• Add edit feature
• Add delete feature in edit form
• Prevent ticking more then once?

Tests:

• Server Tests for adding ascents
• Server Tests for updating ascents
• Server Test for ascent list
• Server Test for tick list
• Server Test for deleting ascent
• Test that deleting tick doesn't cascade on line
• Test that deleting user deletes ascent but not line
• E2E Test for complete ascent workflow: Create -> Show list -> Edit -> Delete

e.g. marker('crag.infos') is in /i18n/de.json but should be in /i18n//crag/de.json.

The background image should always be the crag title image

Add fields for adding the FA date and user for a line

Title says it all.

Add "static" pages in menu that are editable. They should have a title and a text. The menu must be editable and there must be two menus: top and bottom. This way we can add e.g. imprint and other sites at the places where they belong and make them editable.

• Menu page backend
• Menu page frontend
• Menu item backend
• Menu item frontend
• Integration of menu items in menus
• Display of menu page
• Tests for menu pages
• Tests for menu items

Add async validators that prevent a duplicate crag, boulder etc to be created.

Add an option to comment on a line, this allows to cover the history of a line with comments like "Hold got chipped" "Starthold broke" etc

Add the possibility to mark a line as "broken" or "extremely dangerous" with an option of adding a describing text to it. E.g. Trapez in Kottenheim is one of those lines. TBD if it's better to include them with a warning or not include them at all.

Add an image that serves as cover photo of the crag

• Logo
• Favicon
• Name
• BG image of login view
• BG image of main views
• YouTube link
• Insta link
• Copyright owner

Eine optionale GPS-Angabe bei Bereichen, ggf. auch Sektoren, die bestenfalls auflöst in eine googlemaps

• Secret spot property for crags, sectors, areas, lines
• Persist property in create
• Persist in update and also update children!
• Add property in frontend models
• Show "secret spot" tag in lists and detail views
• Only load secret spots if user is at least member
• Clear all caches after login change

Uploader component that has to be connected to the already existing upload backend.
First integration would be the crags preview image.

Navigating from http://localhost:4200/crags/hohenfels to http://localhost:4200/crags/glees doesn't trigger any changes.

• Display of properties
• List of Sectors+
• Button for deleting a crag
• Button for editing a crag

[11:06, 10.5.2023] Peter Grabowitz Jr.: Eine Rubrik/Menüpunkt (optional) zur (dauerhafter, also kein Newspost) Präsentation lokaler (Kletter)Kultur/Menschen? @felix Wir hatten bisschen drüber geredet, hier etwas analog zur Nahetalseite zu machen. Locals bisschen vorstellen, aber auch sowas wie z.B. Stefans Text über Vögel, Sofie über Natur und mehr könnte man hinpacken.
[11:08, 10.5.2023] Peter Grabowitz Jr.: Ein Text, der die Grade in der Eifel kontextualisiert. Ein Text, der für die Pfalz erklärt, was man mit Sandstein machen sollte oder nicht. Auch Videos könnten dort (zusätzlich zu anderer Stelle) landen. Jetzt nicht einfache Begehungen, aber sowas wie "so parkt man bei uns" oder ein 20min Video über ein Gebiet. Also ein Ort, um mediale Inhalte aller Art rundum ein Gebiet zu sammeln, die permanenteren Infowert haben

[11:10, 10.5.2023] Felix: Ist es eine Option das einfach als Blogeintrag zu machen der dann verlinkt wird?
[11:11, 10.5.2023] Peter Grabowitz Jr.: ja, ich glaube schon bzw. sehr wahrscheinlich. Also im Grunde einfach eine Ecke, in der redaktionell kuratiert wird
[11:11, 10.5.2023] Peter Grabowitz Jr.: abgegrenzt von alltäglicheren Posts und normalen Begeungsvideos und -meldungen und so
[11:12, 10.5.2023] Peter Grabowitz Jr.: Wobei zumindest die permanentere locals-Präsentation eher nicht gut in Blogpostform funzt, oder?

TBD!

• Add validator for video urls in backend and frontend
• Add validator for grade name and scale in backend that includes the line type
• Add rating validator in backend

Allow admins to create badges, e.g. "Highball conqueror". Badges contain a set of boulders, when climbed, a user gets the badge.
Also, there should be default badges, e.g. all boulders in a crag or sector, names should be choosable, default to "Master of [CRAG]", but editable, e.g. "Gleesekiel" when all Boulders in Glees are climbed.

Integrate solr search.

• Solr index and search routes
• Mobile version of the search field
• "Advanced search" function that also takes filters for grade etc

Add a design for a 404 page. Include the requested url in the text.

Create routes with slugs. E.g. instead of /crags/khf3iu4ht39thkjtb34iuth34oituh have /crags/glees

Add possibility to draw lines on images and add them to the line model somehow.

• Tests
• Documentation
• Resolve todos

Use the hook functionality as for the slugs to set the ids automatically. Check if the id has been set before, to catch cases where the users was loaded previously for other reasons.

For display at crags, sectors etc. Input is a list of boulder grades. Depending on a instances level setting (which is also to design here) the grades are sorted in the level tags and displayed as in the below screenshot of the UI mock.

Eine Seite auf allen Instanzen, die das ganze erklärt und linkt zu den anderen Gebietsseiten.

• Allow registration from outside
• Allow promoting users to admins

Add a crag season graph that shows when there is enough data of logs with date