Help:Features - Revision history

Reversedragon: category

2025-06-27T05:48:46Z

Reversedragon: WikiMarkdown

2025-06-27T05:46:00Z

WikiMarkdown

← Older revision		Revision as of 05:46, 27 June 2025
Line 2:		Line 2:

	== Cite ==		== Cite ==

			== [https://www.mediawiki.org/wiki/Extension:WikiMarkdown WikiMarkdown] ==

			This extension allows using markdown syntax in a page body.

			Please note that this extension <strong>cannot handle headings</strong>, and will throw an error if you try to look at the page without editing the heading out. You can only create sections of markdown with no headings — which, depending on your use case, could be useful if you have a very long passage of several bare paragraphs full of markdown. Using this extension to put up markdown files on your thesis portal or changing the syntax to wikitext is your choice.

	== Extensions previously removed ==		== Extensions previously removed ==
Line 7:		Line 13:
	=== [https://www.mediawiki.org/wiki/Extension:Wikibase_Client Wikibase Client] / [https://www.mediawiki.org/wiki/Extension:Wikibase_Repository Wikibase Repository] ===		=== [https://www.mediawiki.org/wiki/Extension:Wikibase_Client Wikibase Client] / [https://www.mediawiki.org/wiki/Extension:Wikibase_Repository Wikibase Repository] ===

	Neither of these proved to be as flexible or forgiving as simply putting in the data as [https://en.wikipedia.org/wiki/Semantic_wiki semantic] ~~HTML~~.		Neither of these proved to be as flexible or forgiving as simply putting in the data as [https://en.wikipedia.org/wiki/Semantic_wiki semantic text pages].

	One major reason for abandoning Wikibase and preferring text pages was interoperability. The "real" Lexeme extension ran slowly despite a modern browser and computer. As well, plain text fields proved to be a faster way to input entries and copy them to new entries, with the added benefit that Items are relatively trivial for individuals to download or archive if their source text is nearly as presentable as their displayed HTML. Inputting Items in text means that someone can theoretically edit an Item in a plaintext terminal or from emacs, and browse the Item page in the same text interface. Planning for emacs also makes it easier to subsequently plan for screen readers.		One major reason for abandoning Wikibase and preferring text pages was interoperability. The "real" Lexeme extension ran slowly despite a modern browser and computer. As well, plain text fields proved to be a faster way to input entries and copy them to new entries, with the added benefit that Items are relatively trivial for individuals to download or archive if their source text is nearly as presentable as their displayed HTML. Inputting Items in text means that someone can theoretically edit an Item in a plaintext terminal or from emacs, and browse the Item page in the same text interface. Planning for emacs also makes it easier to subsequently plan for screen readers.

Reversedragon: Special:Version

2025-06-04T03:55:58Z

Special:Version

← Older revision		Revision as of 03:55, 4 June 2025
Line 1:		Line 1:
	About MediaWiki extensions or features which have been installed on this wiki.		About MediaWiki extensions or features which have been installed on this wiki. For more fine-grained information, see [[Special:Version]].

	== Cite ==		== Cite ==

Reversedragon: Wikibase

2025-06-04T03:54:22Z

Wikibase

New page

About MediaWiki extensions or features which have been installed on this wiki.

== Cite ==

== Extensions previously removed ==

=== [https://www.mediawiki.org/wiki/Extension:Wikibase_Client Wikibase Client] / [https://www.mediawiki.org/wiki/Extension:Wikibase_Repository Wikibase Repository] ===

Neither of these proved to be as flexible or forgiving as simply putting in the data as [https://en.wikipedia.org/wiki/Semantic_wiki semantic] HTML.

One major reason for abandoning Wikibase and preferring text pages was interoperability. The "real" Lexeme extension ran slowly despite a modern browser and computer. As well, plain text fields proved to be a faster way to input entries and copy them to new entries, with the added benefit that Items are relatively trivial for individuals to download or archive if their source text is nearly as presentable as their displayed HTML. Inputting Items in text means that someone can theoretically edit an Item in a plaintext terminal or from emacs, and browse the Item page in the same text interface. Planning for emacs also makes it easier to subsequently plan for screen readers.

=== [https://www.mediawiki.org/wiki/Extension:WikibaseLexeme Wikibase Lexeme] ===

No Lexeme Entities were successfully created with this due to it requiring Item Entities that never actually got created. So, there was no real reason to keep it.

← Older revision		Revision as of 05:48, 27 June 2025
Line 20:		Line 20:

	No Lexeme Entities were successfully created with this due to it requiring Item Entities that never actually got created. So, there was no real reason to keep it.		No Lexeme Entities were successfully created with this due to it requiring Item Entities that never actually got created. So, there was no real reason to keep it.


			[[Category:Wiki editing manual]]