-
Notifications
You must be signed in to change notification settings - Fork 28
Home
A partially ordered list of planned enhancements, intended as a guide to the developers who will implement these features.
Within the subheadings of "High priority" and "Next level", the individual items are unordered.
The subheading "Event horizon" means that, given the currently available resources, it may be a long time until those features will be implemented, due to the rate of arrival of higher priority requests. The event horizon will move if more development resources become available.
The "Gallery" of PreTeXt examples is difficult to maintain, so there will be a new approach: every publisher will be responsible for maintaining the information about their book(s).
Make a Showcase Document that illustrates features, good source markup, etc. Described in this issue: https://github.com/rbeezer/mathbook/issues/960 , and work has started: https://github.com/rbeezer/mathbook/tree/dev/examples/showcase
Make a turnkey script for producing the skeleton of a new project. Perhaps something that asks you for a project name, your name and info, chapter names, section names, and a copyright blurb. And then it makes all the files for such a project with open and close tags in places, and has already filled out other things like xml:id's for the chapters and so on.
Have some authors write Instructor Guides, and figure out if/how to integrate with the instructor version. Asides in the margin?
Output to ePub, Kindle, braille, what else?
Continue writing the Developers' Guide, including items mentioned in this issue: https://github.com/rbeezer/mathbook/issues/1002
Write an Instructor's Guide (generic, about PreTeXt features, which can be integrated into the specific Instructor's Guides) and a brief Student Guide (generic, about PreTeXt features).
LaTeX styling options and documentation for how to use them.
Get PreTeXt working in TeXShop.
Finish the MathbookXML to PreTeXt renaming, and move the repository to the PreTeXtBook organization.
Introduce new useful environments. "Worksheet" could use more attention. If "syllabus" or "conference" existed, then some people would use those. A "schedule" and "participantlist" would be part of a "conference". Surely there are other examples.
Make the HTML output usable when offline.
Allow linked Sage cells in knowls https://github.com/rbeezer/mathbook/issues/981
Develop and document the process of declaring an annual edition. Then have a mode where the XSL outputs HTML with tags that show changes between editions.
Divisional structuring within an "exercises". By topic, by difficulty level, by problem "type", etc.
GeoGebra within WeBWorK.
MathJax3
Have WeBWorK (and GeoGebra and other applications) as static (or image) and then loaded when selected by the user. (Important because of server and browser load.)
Make knowls more accessible https://github.com/rbeezer/mathbook/issues/1024
Fix other known accessibility issues
Allow AsciiMath in document source.
Determine proper markup for bibliographic entries, and then implement it. (Step 1: propose a set of tags. Step 2: someone (maybe someone else) writes the XSL.)
Make "units" work in math.
Better student interface for reading questions.
Enable more features in the Instructor version (such as permalinks on everything).
Set up some instructors to use reading questions in the Fall semester. (Rob report on his experience and list feature requests.)
Answering fill-in-the-blank directly in the HTML version.
Instructor give feedback to reading questions
Refactor pretext.js and more sensibly organize the various Javascript files.
Allow expanding and collapsing in the TOC.
Enable drawing on the HTML, to answer questions like "draw the derivative of this function".
Finish refactoring the CSS. Then write a brief guide for those who want to create a new layout.
Put back the missing colors, and make it easy to select the color scheme.
Make new style options for HTML (requires previous item).
sbs figures with different heights but aligned captions (short table vertically centered, next to tall image)
change HTML structure for videos, to making them browser-width words better
asides: general principles, handle "overlapping" asides, asides in knowls.
accessibility: guide for authors, standard template/statement