WIP: improve project detail template #12

Draft
puer-robustus wants to merge 17 commits from project_template into main
No description provided.
feat(website): parse fullDescription markdown text in project detail pages
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
7bb51b87b8
The project level jsons have a fullDescription attribute which contains
information on the project as CommonMark-formatted Markdown text. For the
webpage, the content of the field is converted to HTML by the shared
Markdown renderer and passed to Jinja as "safe" html.

Since working with Markdown in JSON string fields is neigh impossible for
humans, we provide convenience functions to export and import the
fullDescription into/from Markdown files. Those can be easily edited, but
are not supposed to be checked in into the repository (therefore gitignored
by default), but rather be imported into the JSONs.
puer-robustus force-pushed project_template from 7bb51b87b8
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
to 2b5dd20eca
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
2026-09-14 18:03:54 +02:00
Compare
puer-robustus force-pushed project_template from 2b5dd20eca
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
to c475d827f7
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
2026-09-14 18:56:47 +02:00
Compare
WIP: docs(README): update
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
87a42638d3
puer-robustus force-pushed project_template from 87a42638d3
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
to f13236b3d1
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
2026-09-14 19:31:42 +02:00
Compare
Author
Owner

TODO:

  • think about image handing for projects and dossiers
  • add more project level properties
    • hasWikiPage
    • category
    • screenshots or have them be referenced in the markdown text of the full description?
TODO: - [ ] think about image handing for projects and dossiers - [ ] add more project level properties - [x] `hasWikiPage` - [x] `category` - [ ] `screenshots` or have them be referenced in the markdown text of the full description?
fix(schema): reintroduce project level categories
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
39cc7c6f99
Closes: #13
feat(website): add Dossier object and restructure file tree
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
7812307759
To have images next to projects and dossiers, we introduce project and
dossier directories rather than them being represented as simple text files.
puer-robustus force-pushed project_template from 7812307759
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
to b9c313d3fc
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
2026-09-28 13:49:34 +02:00
Compare
puer-robustus force-pushed project_template from b9c313d3fc
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
to d173df5808
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
2026-09-28 13:56:47 +02:00
Compare
puer-robustus force-pushed project_template from d173df5808
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
to a97c263255
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
2026-09-28 15:03:42 +02:00
Compare
puer-robustus force-pushed project_template from a97c263255
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
to c1a09fed0f
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
2026-10-12 11:17:20 +02:00
Compare
This is another field which was inadvertantly dropped from the schema.

It has some validation that only projects which are freely licensed, can be
listed as an alternative to something: In the JSON schema this is
implemented via the "dependentSchemas" attribute. In the pydantic class,
this is done via a validator. Unfortunately, there is no way to only define
this logic once.
This should prevent cases of inadvertantly dropping attributes from the
project schema if we have defined them already in example or real data.
fix(schema): align pydantic Field alias and JSON attribute name
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
24bebba889
puer-robustus force-pushed project_template from 24bebba889
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
to 181684a21b
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
2026-10-12 16:59:35 +02:00
Compare
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
Required
Details
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin project_template:project_template
git switch project_template
Sign in to join this conversation.
No reviewers
No labels
app
data
schema
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ISOC-CH/tech-dossier-project-data!12
No description provided.