distribusi-verse works with a flask blueprint for a folder of static pages.
In the end all distribusis are static pages and only the management of the users and the uploading of new material is dynamic.
This means, you can't really annotate images in the interface itself. We could add some js to every page that allows you to click an image and send a text to an endpoint, describing the image. But how will this know that you are logged in?
most straightforward solution would be to also make all distribusis dynamic...
but that feels like overkill
distribusi-verse works with a flask blueprint for a folder of static pages.
In the end all distribusis are static pages and only the management of the users and the uploading of new material is dynamic.
```
stash_page = Blueprint("stash_page", __name__, static_folder="stash")
APP.register_blueprint(stash_page)
```
This means, you can't really annotate images in the interface itself. We could add some js to every page that allows you to click an image and send a text to an endpoint, describing the image. But how will this know that you are logged in?
most straightforward solution would be to also make all distribusis dynamic...
but that feels like overkill
I am thinking an edit mode. tree structure view of all distribusis. so the view to work with the archive and the view to just see material is not the same.
I am thinking an edit mode. tree structure view of all distribusis. so the view to work with the archive and the view to just see material is not the same.
No complex tree, just flatten the folders. Single distribusi with a list of files with paths.
Then a form where you can annotate the media files.
the descriptions of media files become txt files added to the distribusi. So they get rendered as <p> tags and the archive retains its database-less state.
No complex tree, just flatten the folders. Single distribusi with a list of files with paths.
Then a form where you can annotate the media files.
the descriptions of media files become txt files added to the distribusi. So they get rendered as `<p>` tags and the archive retains its database-less state.
description -> produces a figcaption.
alltext should be functional text, that adds an alt attribute to the img tag.
search tags are not seen in the archive itself because they only function for the search engine of distrubsi-verse
description -> produces a figcaption.
alltext should be functional text, that adds an alt attribute to the img tag.
search tags are not seen in the archive itself because they only function for the search engine of distrubsi-verse
distribusi-verse works with a flask blueprint for a folder of static pages.
In the end all distribusis are static pages and only the management of the users and the uploading of new material is dynamic.
This means, you can't really annotate images in the interface itself. We could add some js to every page that allows you to click an image and send a text to an endpoint, describing the image. But how will this know that you are logged in?
most straightforward solution would be to also make all distribusis dynamic...
but that feels like overkill
I am thinking an edit mode. tree structure view of all distribusis. so the view to work with the archive and the view to just see material is not the same.
No complex tree, just flatten the folders. Single distribusi with a list of files with paths.
Then a form where you can annotate the media files.
the descriptions of media files become txt files added to the distribusi. So they get rendered as
<p>
tags and the archive retains its database-less state.currently still missing is running the file_crawling that makes db records for all files, after distribusi is launched live.
Need this later
There needs to be a good decision on alttext -> functional.
description -> figcaption.
description -> produces a figcaption.
alltext should be functional text, that adds an alt attribute to the img tag.
search tags are not seen in the archive itself because they only function for the search engine of distrubsi-verse