<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://gxplex.org/index.php?action=history&amp;feed=atom&amp;title=Development_Roadmap</id>
	<title>Development Roadmap - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://gxplex.org/index.php?action=history&amp;feed=atom&amp;title=Development_Roadmap"/>
	<link rel="alternate" type="text/html" href="https://gxplex.org/index.php?title=Development_Roadmap&amp;action=history"/>
	<updated>2026-10-07T10:45:38Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://gxplex.org/index.php?title=Development_Roadmap&amp;diff=95&amp;oldid=prev</id>
		<title>Gxplex admin: feat: add development roadmap page</title>
		<link rel="alternate" type="text/html" href="https://gxplex.org/index.php?title=Development_Roadmap&amp;diff=95&amp;oldid=prev"/>
		<updated>2026-06-22T14:59:11Z</updated>

		<summary type="html">&lt;p&gt;feat: add development roadmap page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Development Roadmap ==&lt;br /&gt;
&lt;br /&gt;
This page collects planned features, open tasks, and ideas for future development of GxPlex.&lt;br /&gt;
Items are grouped by theme. Priority is indicated in the Status column.&lt;br /&gt;
&lt;br /&gt;
=== Rating and feedback ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Feature !! Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| Loading indicator during vote submission&lt;br /&gt;
| Planned&lt;br /&gt;
| After clicking a star, the UI gives no visual feedback until the API response arrives. A spinner or disabled state on the stars during the request would improve perceived responsiveness. Relevant file: &amp;lt;code&amp;gt;extensions/VoteNY/resources/js/Vote.js&amp;lt;/code&amp;gt; — disable stars on click, re-enable in &amp;lt;code&amp;gt;.done()&amp;lt;/code&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
| Link to top-rated pages&lt;br /&gt;
| Planned&lt;br /&gt;
| VoteNY ships with [[Special:TopRatings]] — a ranked list of the highest-rated pages. Link it from [[GxPlex_Search|GxPlex Search]] and the sidebar.&lt;br /&gt;
|-&lt;br /&gt;
| Show vote count on document index&lt;br /&gt;
| Idea&lt;br /&gt;
| The &amp;lt;code&amp;gt;{{NUMBEROFVOTESPAGE:Page name}}&amp;lt;/code&amp;gt; magic word from VoteNY can display the number of votes per page. Could be added as a column to [[Document_Index|Document Index]] or the category pages.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Content and structure ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Feature !! Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| Document part as filterable property&lt;br /&gt;
| Deferred&lt;br /&gt;
| Adding &amp;lt;code&amp;gt;document_part&amp;lt;/code&amp;gt; (chapter, article, section) as an SMW property to [[Template:RegDocument]] was explicitly deferred. Would require updating all existing pages after the template change. Reopen when the document count makes this worthwhile.&lt;br /&gt;
|-&lt;br /&gt;
| Additional content templates&lt;br /&gt;
| Planned&lt;br /&gt;
| Beyond &amp;lt;code&amp;gt;{{RegDocument}}&amp;lt;/code&amp;gt;, dedicated templates for recurring document types (e.g. PSUR, CEP, PMCF report) would reduce setup time per page and improve metadata consistency.&lt;br /&gt;
|-&lt;br /&gt;
| Structured change history&lt;br /&gt;
| Idea&lt;br /&gt;
| A property or subpage convention for recording revision history of a regulatory document (who updated what, and when) separate from the wiki edit history.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Search and navigation ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Feature !! Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| Dynamic filter UI for GxPlex Search&lt;br /&gt;
| Planned&lt;br /&gt;
| The current [[GxPlex_Search|GxPlex Search]] uses a sortable table. Installing the [https://www.mediawiki.org/wiki/Extension:PageForms PageForms extension] would enable dropdown filters that query SMW properties dynamically without a full page reload.&lt;br /&gt;
|-&lt;br /&gt;
| Topic property on RegDocument&lt;br /&gt;
| Idea&lt;br /&gt;
| Adding a &amp;lt;code&amp;gt;Topic&amp;lt;/code&amp;gt; SMW property would allow filtering documents by topic in &amp;lt;code&amp;gt;Special:Ask&amp;lt;/code&amp;gt; without navigating to category pages. Currently topics are inferred from page categories only.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Communication ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Feature !! Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| Email notifications for approval workflow&lt;br /&gt;
| Planned&lt;br /&gt;
| Authors currently have no automatic notification when their page is approved or rejected. Requires SMTP configuration (&amp;lt;code&amp;gt;$wgSMTP&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;LocalSettings.php&amp;lt;/code&amp;gt;) and a hook on ApprovedRevs&amp;#039; approval/rejection events.&lt;br /&gt;
|-&lt;br /&gt;
| Discussion threads on document pages&lt;br /&gt;
| Planned&lt;br /&gt;
| The [[Special:Version|DiscussionTools extension]] is already installed but not surfaced in the UI. Enabling it would allow threaded comments on each document page without a separate talk page workflow.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Infrastructure ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Feature !! Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| Sponsor or partner slot&lt;br /&gt;
| Idea&lt;br /&gt;
| A designated area in the sidebar or footer for a sponsor link or logo. Requires a hook in &amp;lt;code&amp;gt;LocalSettings.php&amp;lt;/code&amp;gt; and a configurable wikitext snippet so non-technical admins can update the content without a deployment.&lt;br /&gt;
|-&lt;br /&gt;
| Automated accessibility regression test&lt;br /&gt;
| Idea&lt;br /&gt;
| The Pa11y and Lighthouse checks (&amp;lt;code&amp;gt;npm run a11y:all&amp;lt;/code&amp;gt;) currently run manually. Adding them to a pre-commit hook or a scheduled task would catch regressions earlier.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Gxplex admin</name></author>
	</entry>
</feed>