Technical Debt

[bofhgr]

Technical Debt

Each of these 'Refactor' tasks will take a considerable amount of effort to complete and will only grow more difficult with time. Refactor is a euphemism for 'I have to re-write the whole damn code from scratch'

• [ ] Refactor template.json to use dataModel
• [x] Refactor metanthropes-system to just 'metanthropes'
• [ ] Refactor CSS classes
• [ ] Refactor metaF(n) based on Functionality
• [x] Refactor to enable Multi-national Support

These tasks will take less time to pull-off compared to 'Refactor' tasks, yet are just as important to do as soon as possible to not incur additional debt as time goes on

• [x] Design new template/dataModel schema for v1.0++
• [x] Compendiums use CLI to pack/unpack
• [x] Split Content to Modules / Worlds
• [ ] Officially Support 3rd Party Modules
• [x] Refactor where appropriate to expose and use our own API
• [ ] Automate Publishing
• [ ] Consolidate Assets

These tasks are in progress and will be marked as completed when all their sub-tasks are done. This is an ongoing process, as we refactor everything to bring it up to v1.0 standards. The list below is to help track the big picture.

• [ ] Refactor all CSS to new standards
• [ ] All Actor Types now using the new Data Models framework
• [ ] All Item Types now using the new Data Models framework
• [ ] Localize all text to support English translation
• [ ] Link to Discord announcements on new builds/releases
• [ ] Utilize FVTT publishing services to automate publishing for new releases
• [ ] Adopt Conventional Commits automations to release build version numbering
• [ ] Metanthropes API v1 'final'
• [ ] Consolidated Assets require new Compendium & Journal builds

[bofhgr]

CSS class refactor notes:

is wide-spread, perhaps we should limit what kind of style we want where and be more specific about it in html

[bofhgr]

Metanthropes-system refactored to just Metanthropes before EA initial release Compendiums as of v0.9 now properly use the CLI to pack/unpack as part of the build process.

[bofhgr]

Adding a section here that need to be further investigated and expanded. We want to be changing form using es imports on everything to instead build an api for our things. this way modules can export stuff that other modules and the system can later use. Example of this case is the Roll New Actor that exists in the Core but the System is actually initiating it. This is part of a bigger redesign, probably not part of a specific subsystem, so adding this to the Debt seems more appropriate.

[bofhgr]

Well creating and using an API turns out to be very easy, barely an inconvenience! So that's one thing less to worry about!