roadmap
specific ideas
- Better packaging: Create a Docker image, to make the install and upgrade process a lot easier.
- Finish the datasources roadmap and document its use.
- Fix the items mentioned in issues.
- Add claim-support to the Wikidata-data fetching (and support for claim-data in the field-definitions).
- Better bookmarking UX:
- Cross-tab bookmark state-syncing
- Add datasource + datasource-global-ID support, when a topic is bookmarked
- Other idea: Being able to share bookmark-lists with others (like Spotify playlists)
- Add optional geolocation-support, so we could route a user from the current location to the location of a topic, using the OSMR routing app. See also: offline hiking-maps app
- Find and integrate a more lightweight MIDI-webcomponent, if available (html-midi-player is more than 0.5MB by itself!)
general ideas
- Conzept development vision:
- data-define software - rather than code-define - when possible. Often this first requires several code implementations/examples to explore the domain.
- Improve and maintain conceptual integrity, as vague and abstract as that term is.
- Research educational-support enhancements:
- Collaborative & social learning features (eg. p2p audio-chat and text-chat rooms for each topic)
- User-created and auto-generated presentations around a topic
- Auto-generated topic quizzes
- Auto-generated, spaced-repetition-based facts learning (for a certain topic / set of topics / topic-domain)
- ? Note-taking integration (eg.: Bangle, …)
- Better ways to indicate personal and professional interests (similar to the persona-tags setting)
- Experiences: play Chess positions (done), …
- ? Offline(-first) support with content-caching (especially useful when traveling and/or without reliable internet-connectivity).
- Example apps: hiking-map app
- ? Research creating some kind of a simple web-application interface standard for input/output/event-handling:
- URL parameter IO (iso2 language, search-string, ID, …)
- Event-handling (other view triggers, key-bindings, fullscreening, …)
- Look into using more webcomponents:
- component.gallery (overview of webcomponents)
- SPARQL-endpoint explorer (eg. Sparklis → needs CORS-issue workarounds)
- sparql-endpoint testing: query all endpoints (note: some endpoints are dead) → then open “sparql explorer 2” in the main-section
- Handle HTTP GET/POST CORS issues with the SPARQL-endpoints (not sure POST is supported in the current Conzept proxy-service)
- build steps here
- See also: SparqlExplorer
×
>
<