Refresh project state documentation
This commit is contained in:
@@ -34,7 +34,7 @@ Current foundation:
|
||||
|
||||
- LibreBible packages are consumed from `W:\libre-bible-data\packages\json`.
|
||||
- App-level query contracts hide the backing storage surface.
|
||||
- Existing resources include KJV, NET, Strong's, notes, commentary, dictionaries, places/routes, and KJV audio metadata.
|
||||
- Existing resources include ASV, KJV, NET, Strong's, notes, commentary, dictionaries, places/routes, and KJV audio metadata.
|
||||
|
||||
Good next milestones:
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ The project has moved from prototype into early product architecture.
|
||||
|
||||
Working HotView behavior includes:
|
||||
|
||||
- KJV and NET Bible text.
|
||||
- ASV, KJV, and NET Bible text.
|
||||
- Strong's links and lexicon definitions.
|
||||
- Strong's pronunciation text when the package provides it.
|
||||
- KJV and NET footnotes and study notes.
|
||||
@@ -79,7 +79,7 @@ Missing or immature areas include:
|
||||
|
||||
## Recommended Next Step
|
||||
|
||||
After Phase 9, the next work should stay inside one product track at a time. The strongest near candidate is another Study Experience milestone focused on search result navigation, saved searches, richer clipping, and notebook document blocks. Cross-references should wait for a LibreBible cross-reference package.
|
||||
After Phase 10, the next work should stay inside one product track at a time. Strong near candidates are search result navigation, saved searches, richer notebook document workflows, or a Resource Ecosystem phase for cross-references and additional freely usable translations/resources. Cross-reference UI should wait for a LibreBible cross-reference package.
|
||||
|
||||
## Phase 8 Result
|
||||
|
||||
|
||||
Reference in New Issue
Block a user