Wikibooks:Requests for deletion

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Wikibooks</sitename>
    <dbname>enwikibooks</dbname>
    <base>https://en.wikibooks.org/wiki/Main_Page</base>
    <generator>MediaWiki 1.48.0-wmf.1</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">Wikibooks</namespace>
      <namespace key="5" case="first-letter">Wikibooks talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="102" case="first-letter">Cookbook</namespace>
      <namespace key="103" case="first-letter">Cookbook talk</namespace>
      <namespace key="108" case="first-letter">Transwiki</namespace>
      <namespace key="109" case="first-letter">Transwiki talk</namespace>
      <namespace key="110" case="first-letter">Wikijunior</namespace>
      <namespace key="111" case="first-letter">Wikijunior talk</namespace>
      <namespace key="112" case="first-letter">Subject</namespace>
      <namespace key="113" case="first-letter">Subject talk</namespace>
      <namespace key="710" case="first-letter">TimedText</namespace>
      <namespace key="711" case="first-letter">TimedText talk</namespace>
      <namespace key="828" case="first-letter">Module</namespace>
      <namespace key="829" case="first-letter">Module talk</namespace>
      <namespace key="1728" case="first-letter">Event</namespace>
      <namespace key="1729" case="first-letter">Event talk</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Wikibooks:Requests for deletion</title>
    <ns>4</ns>
    <id>385</id>
    <revision>
      <id>4678524</id>
      <parentid>4678444</parentid>
      <timestamp>2026-10-27T17:32:22Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Template:Qr-twwp */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678524</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="39599" sha1="tepwddsuf1m5thaa371b3i2v1yfil7z" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt; 

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)

== [[Template:Qr-twwp]] ==
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

:I would support that merge—do you have a proposal for which elements to keep? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:31, 23 October 2026 (UTC)
: @[[User:JJPMaster|JJPMaster]] Would this be a simple redirect or would that require the usage of [[Special:MergeHistory]]? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:32, 27 October 2026 (UTC)

== [[Wikibooks:FlaggedRevs Extension]] ==
Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC)

:Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC)
:: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC)
:::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC)
: {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC)
::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC)
== [[On 2D Inverse Problems]] ==
While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly &quot;off the rails&quot;.

First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory &amp; &quot;No Problems&quot;]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like &quot;Digital veggies&quot; and &quot;The apple &amp; onion case&quot; with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to &quot;images as EMP&quot; in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book.

Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response:
* [[On 2D Inverse Problems/About the book]] (&quot;That is a remarkably sharp insight! You hit the nail right on the head...&quot;)
* [[On 2D Inverse Problems/The Cure]] (&quot;That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...&quot;)
* [[On 2D Inverse Problesm/Genes]] (&quot;That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...&quot;)
* [[On 2D Inverse Problems/Eta]] (&quot;That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...&quot;)
* [[On 2D Inverse Problems/Complex]] (&quot;That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...&quot;)
* [[On 2D Inverse Problems/Papirus]] (&quot;Good morning! You are on an absolute roll today...&quot;)
And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC)
:{{Comment}}. &lt;blockquote&gt;For example, all of the following pages contain text which is obviously a chatbot response:&lt;/blockquote&gt;. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC)
::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style  check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC)
::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC)
:::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC)
:::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC)
:I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC)
:The book chapter structure has sections and subsections, it's a tree 🌳. &quot;The digital veggies&quot; title is reference to digital and real/continuous world, which is the main theme of the book. &quot;The apple and onion 🌰 case&quot; is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC)
:{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase &lt;blockquote&gt;The structural outline of your Wikibook **&quot;On 2D Inverse Problems&quot;** on Wikibooks is mapped out into five distinct volumes/sections:&lt;/blockquote&gt; appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC)
::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC)
::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC)</text>
      <sha1>tepwddsuf1m5thaa371b3i2v1yfil7z</sha1>
    </revision>
    <revision>
      <id>4678625</id>
      <parentid>4678524</parentid>
      <timestamp>2026-10-27T23:19:54Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>/* Template:Qr-twwp */ Reply</comment>
      <origin>4678625</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40120" sha1="4eh26qwswe502uvbtbv6l0vwaxve5ak" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt; 

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)

== [[Template:Qr-twwp]] ==
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

:I would support that merge—do you have a proposal for which elements to keep? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:31, 23 October 2026 (UTC)
: @[[User:JJPMaster|JJPMaster]] Would this be a simple redirect or would that require the usage of [[Special:MergeHistory]]? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:32, 27 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] and @[[User:Kittycataclysm|Kittycataclysm]]: Template merging generally ends up reducing to a simple blank-and-redirect, which I think should be done here. No history merge is needed, as these are currently two distinct pages with no cut-and-paste move ever having occurred from one to the other. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 23:19, 27 October 2026 (UTC)

== [[Wikibooks:FlaggedRevs Extension]] ==
Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC)

:Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC)
:: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC)
:::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC)
: {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC)
::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC)
== [[On 2D Inverse Problems]] ==
While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly &quot;off the rails&quot;.

First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory &amp; &quot;No Problems&quot;]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like &quot;Digital veggies&quot; and &quot;The apple &amp; onion case&quot; with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to &quot;images as EMP&quot; in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book.

Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response:
* [[On 2D Inverse Problems/About the book]] (&quot;That is a remarkably sharp insight! You hit the nail right on the head...&quot;)
* [[On 2D Inverse Problems/The Cure]] (&quot;That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...&quot;)
* [[On 2D Inverse Problesm/Genes]] (&quot;That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...&quot;)
* [[On 2D Inverse Problems/Eta]] (&quot;That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...&quot;)
* [[On 2D Inverse Problems/Complex]] (&quot;That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...&quot;)
* [[On 2D Inverse Problems/Papirus]] (&quot;Good morning! You are on an absolute roll today...&quot;)
And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC)
:{{Comment}}. &lt;blockquote&gt;For example, all of the following pages contain text which is obviously a chatbot response:&lt;/blockquote&gt;. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC)
::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style  check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC)
::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC)
:::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC)
:::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC)
:I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC)
:The book chapter structure has sections and subsections, it's a tree 🌳. &quot;The digital veggies&quot; title is reference to digital and real/continuous world, which is the main theme of the book. &quot;The apple and onion 🌰 case&quot; is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC)
:{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase &lt;blockquote&gt;The structural outline of your Wikibook **&quot;On 2D Inverse Problems&quot;** on Wikibooks is mapped out into five distinct volumes/sections:&lt;/blockquote&gt; appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC)
::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC)
::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC)</text>
      <sha1>4eh26qwswe502uvbtbv6l0vwaxve5ak</sha1>
    </revision>
    <revision>
      <id>4678630</id>
      <parentid>4678625</parentid>
      <timestamp>2026-10-27T23:41:47Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Puredyne */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678630</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40430" sha1="gyecknkgi3dli3ikyzadx462cjt4lr0" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt; 

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)
: {{comment}}. If we are going to archive this, it would be some time before [[Wikibooks:Outdated books]] would get approved as either a guideline or a policy. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:41, 27 October 2026 (UTC)

== [[Template:Qr-twwp]] ==
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

:I would support that merge—do you have a proposal for which elements to keep? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:31, 23 October 2026 (UTC)
: @[[User:JJPMaster|JJPMaster]] Would this be a simple redirect or would that require the usage of [[Special:MergeHistory]]? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:32, 27 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] and @[[User:Kittycataclysm|Kittycataclysm]]: Template merging generally ends up reducing to a simple blank-and-redirect, which I think should be done here. No history merge is needed, as these are currently two distinct pages with no cut-and-paste move ever having occurred from one to the other. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 23:19, 27 October 2026 (UTC)

== [[Wikibooks:FlaggedRevs Extension]] ==
Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC)

:Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC)
:: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC)
:::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC)
: {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC)
::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC)
== [[On 2D Inverse Problems]] ==
While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly &quot;off the rails&quot;.

First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory &amp; &quot;No Problems&quot;]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like &quot;Digital veggies&quot; and &quot;The apple &amp; onion case&quot; with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to &quot;images as EMP&quot; in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book.

Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response:
* [[On 2D Inverse Problems/About the book]] (&quot;That is a remarkably sharp insight! You hit the nail right on the head...&quot;)
* [[On 2D Inverse Problems/The Cure]] (&quot;That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...&quot;)
* [[On 2D Inverse Problesm/Genes]] (&quot;That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...&quot;)
* [[On 2D Inverse Problems/Eta]] (&quot;That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...&quot;)
* [[On 2D Inverse Problems/Complex]] (&quot;That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...&quot;)
* [[On 2D Inverse Problems/Papirus]] (&quot;Good morning! You are on an absolute roll today...&quot;)
And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC)
:{{Comment}}. &lt;blockquote&gt;For example, all of the following pages contain text which is obviously a chatbot response:&lt;/blockquote&gt;. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC)
::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style  check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC)
::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC)
:::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC)
:::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC)
:I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC)
:The book chapter structure has sections and subsections, it's a tree 🌳. &quot;The digital veggies&quot; title is reference to digital and real/continuous world, which is the main theme of the book. &quot;The apple and onion 🌰 case&quot; is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC)
:{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase &lt;blockquote&gt;The structural outline of your Wikibook **&quot;On 2D Inverse Problems&quot;** on Wikibooks is mapped out into five distinct volumes/sections:&lt;/blockquote&gt; appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC)
::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC)
::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC)</text>
      <sha1>gyecknkgi3dli3ikyzadx462cjt4lr0</sha1>
    </revision>
    <revision>
      <id>4678633</id>
      <parentid>4678630</parentid>
      <timestamp>2026-10-27T23:44:53Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Template:Qr-twwp */ Done.</comment>
      <origin>4678633</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40658" sha1="i3efsqfc56p2is4hkdekj287x2yk7yk" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt; 

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)
: {{comment}}. If we are going to archive this, it would be some time before [[Wikibooks:Outdated books]] would get approved as either a guideline or a policy. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:41, 27 October 2026 (UTC)

== [[Template:Qr-twwp]] ==
{{closed|{{done}}, now redirected to [[Template:Copypaste]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:44, 27 October 2026 (UTC)}}
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

:I would support that merge—do you have a proposal for which elements to keep? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:31, 23 October 2026 (UTC)
: @[[User:JJPMaster|JJPMaster]] Would this be a simple redirect or would that require the usage of [[Special:MergeHistory]]? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:32, 27 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] and @[[User:Kittycataclysm|Kittycataclysm]]: Template merging generally ends up reducing to a simple blank-and-redirect, which I think should be done here. No history merge is needed, as these are currently two distinct pages with no cut-and-paste move ever having occurred from one to the other. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 23:19, 27 October 2026 (UTC)
{{end closed}}

== [[Wikibooks:FlaggedRevs Extension]] ==
Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC)

:Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC)
:: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC)
:::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC)
: {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC)
::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC)
== [[On 2D Inverse Problems]] ==
While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly &quot;off the rails&quot;.

First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory &amp; &quot;No Problems&quot;]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like &quot;Digital veggies&quot; and &quot;The apple &amp; onion case&quot; with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to &quot;images as EMP&quot; in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book.

Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response:
* [[On 2D Inverse Problems/About the book]] (&quot;That is a remarkably sharp insight! You hit the nail right on the head...&quot;)
* [[On 2D Inverse Problems/The Cure]] (&quot;That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...&quot;)
* [[On 2D Inverse Problesm/Genes]] (&quot;That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...&quot;)
* [[On 2D Inverse Problems/Eta]] (&quot;That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...&quot;)
* [[On 2D Inverse Problems/Complex]] (&quot;That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...&quot;)
* [[On 2D Inverse Problems/Papirus]] (&quot;Good morning! You are on an absolute roll today...&quot;)
And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC)
:{{Comment}}. &lt;blockquote&gt;For example, all of the following pages contain text which is obviously a chatbot response:&lt;/blockquote&gt;. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC)
::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style  check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC)
::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC)
:::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC)
:::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC)
:I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC)
:The book chapter structure has sections and subsections, it's a tree 🌳. &quot;The digital veggies&quot; title is reference to digital and real/continuous world, which is the main theme of the book. &quot;The apple and onion 🌰 case&quot; is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC)
:{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase &lt;blockquote&gt;The structural outline of your Wikibook **&quot;On 2D Inverse Problems&quot;** on Wikibooks is mapped out into five distinct volumes/sections:&lt;/blockquote&gt; appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC)
::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC)
::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC)</text>
      <sha1>i3efsqfc56p2is4hkdekj287x2yk7yk</sha1>
    </revision>
  </page>
  <page>
    <title>High School Mathematics Extensions</title>
    <ns>0</ns>
    <id>1317</id>
    <revision>
      <id>4678590</id>
      <parentid>4633165</parentid>
      <timestamp>2026-10-27T20:17:58Z</timestamp>
      <contributor>
        <username>~2026-57520-83</username>
        <id>3629549</id>
      </contributor>
      <comment>/* Introduction */</comment>
      <origin>4678590</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5321" sha1="1any84hh8emhvj1bn1e4uppadzdilce" xml:space="preserve">{{denest}}
&lt;div style=&quot;display:block;margin:30px;text-align:center;border-top:solid 1px #777;border-bottom:solid 1px #777;font-size:350%;&quot;&gt;&lt;p&gt;High School&lt;/p&gt;&lt;p&gt;Pure Maths  Extensions&lt;/p&gt;&lt;/div&gt;

{{featured book|PDF=High School Mathematics Literacy Extensions|platinum}}

== Introduction ==
{{Reading level|Intermediate}}
{{RenderPNG}}
{{Print version}}
This online and awesome textbook is intended for, but not limited to, high school students that do not have a rigorous understanding and knowledge of university-level mathematics. Therefore, the text's language reflects the expected mathematical maturity of the intended audience.

This book introduces several interesting topics not covered in the standard high school curriculum of most countries.

The materials presented can be challenging, but at the same time, we strive to make this book readable to all who are a few years from applying to higher education.

''' From the authors '''

It is our firm belief that math textbooks should not just be a collection of mathematical facts carefully laid out for rote memorization and cram sessions.  A math textbook, especially for the youth, should be full of questions, not just exercises.  These questions require some thought to answer and spark curiosity.  After all, the questions keep the students engaged, not the answers.

:''&quot;In mathematics the art of proposing a question must be held of higher value than solving it.&quot;''
:- [[w:Georg_Cantor|Georg Cantor]]

We sincerely hope to interest, stimulate, and challenge all those who may read this book.

==Topics==
{| class=wikitable cellpadding=&quot;3&quot; style=&quot;text-align: center;&quot;
 ! colspan=&quot;6&quot; | Table of Contents
 |-
 ! # || Chapter || Status || Pages || Solutions || Commentary
 |-
 | 0
 |style=&quot;text-align:left;&quot;|[[/Supplementary|Supplementary Chapters]]
 |{{decistage|5}}|| 5
 | [[/Supplementary/Solutions|ES]] - [[/Supplementary/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|Basic counting. Polynomial division. Partial fractions. Summation. Complex numbers. Differentiation.
 |-
 | 1
 |style=&quot;text-align:left;&quot;|[[/Primes|Primes and Modular Arithmetic]]
 |{{decistage|10}}|| 24
 | [[/Primes/Solutions|ES]] - [[/Primes/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
Fundamental Theorem of Arithmetic, Divisibility/Division, Primes 
|-
 | 2
 |style=&quot;text-align:left;&quot;|[[/Logic/]]
 |{{decistage|7}}|| 18
 | [[/Logic/Solutions|ES]] - [[/Logic/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 3
 |style=&quot;text-align:left;&quot;|[[/Mathematical Proofs/]] 
 |{{decistage|8}}|| 11
 | [[/Mathematical Proofs/Solutions|ES]] - [[/Mathematical Proofs/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 4
 |style=&quot;text-align:left;&quot;|[[/Set Theory and Infinite Processes/]]
 |{{decistage|5}}|| 10
 | [[/Set Theory and Infinite Processes/Solutions|ES]] - [[/Set Theory and Infinite Processes/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 5
 |style=&quot;text-align:left;&quot;|[[/Counting and Generating Functions/]]
 |{{decistage|7}}|| 14
 | [[/Counting and Generating Functions/Solutions|ES]] - [[/Counting and Generating Functions/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 6
 |style=&quot;text-align:left;&quot;|[[/Discrete Probability/]]
 |{{decistage|3}}|| 12
 | [[/Discrete Probability/Solutions|ES]] - [[/Discrete Probability/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 7
 |style=&quot;text-align:left;&quot;|[[/Matrices/]]
 |{{decistage|9}}|| 31
 | [[/Matrices/Solutions|ES]] - [[/Matrices/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 8
 |style=&quot;text-align:left;&quot;|[[/Further Modular Arithmetic/]] 
 |{{decistage|6}}|| 14
 | [[/Further Modular Arithmetic/Solutions|ES]] - [[/Further Modular Arithmetic/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 9
 |style=&quot;text-align:left;&quot;|[[/Mathematical Programming/]] 
 |{{decistage|1}}|| 4
 | [[/Mathematical Programming/Solutions|ES]] - [[/Mathematical Programming/Problem Set/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 10
 |style=&quot;text-align:left;&quot;|[[/Markov Chains/]]
 |{{decistage|0}}|| 1
 | [[/Markov Chains/Solutions|ES]] - [[/Markov Chains/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
 | 11
 |style=&quot;text-align:left;&quot;|[[/Peano's Axioms/]]
 |{{decistage|0}}|| 1
 | [[/Peano's Axioms/Solutions|ES]] - [[/Peano's Axioms/Solutions|PS]]
 |style=&quot;text-align:left;&quot;|
 |-
|}

==Authors &amp; Contributors==
A number of persons not listed below have also made important contributions to this book. Contributors are encouraged to edit and include themselves in this list.

{| border=&quot;0&quot; cellspacing=&quot;5&quot; cellpadding=&quot;5&quot; style=&quot;margin:auto;&quot;
 !Name
 !Role
 !Affiliation
 !Quote
 |-
 |[[User:Xiaodai|Zhuo Jia Dai]] 
 |Author
 |Former Honours Student of University of Sydney
 |''Welcomes any criticism or praise.''
 |-
 |[[User:R3m0t|R3m0t]]
 |Corrections
 |Student of JFS Secondary School
 |''&quot;To iterate is human; to recurse, divine.&quot;''
 |-
 |[[User:Mmartin|Martin Warmer]]
 |Corrections &amp; Solutions
 |Student of HBL High School
 |''Welcomes all corrections and other help.''
 |-
 |[[User:Lemontea~enwikibooks|Tom Lam]]
 |Supplementaries &amp; Solutions
 |Student of Sha Tin Methodist College
 |''&quot;Answer is merely the fuel for more questions.&quot;''
 |}

{{shelves|K-12 mathematics}}
{{alphabetical|H}}
{{Status|50%}}

[[ja:高等学校数学]]</text>
      <sha1>1any84hh8emhvj1bn1e4uppadzdilce</sha1>
    </revision>
  </page>
  <page>
    <title>Dutch/Lesson 1</title>
    <ns>0</ns>
    <id>3585</id>
    <revision>
      <id>4678552</id>
      <parentid>4413612</parentid>
      <timestamp>2026-10-27T18:47:10Z</timestamp>
      <contributor>
        <username>~2026-57661-42</username>
        <id>3629539</id>
      </contributor>
      <comment>Stoop into stop</comment>
      <origin>4678552</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="39451" sha1="o64kmsqrc6d1az6ciew4n5q3do431ss" xml:space="preserve">{{Dutch/Navigation|type=les|n=1|suff=|head2=Eenvoudige Gesprekken ~ Simple Conversations|t1=Simple conversations|t2=Grammar: Pronouns: I, me etc.|t3=Polite and clitic forms}}

==Grammatica 1-1 ~ Grammar versus what children do==
===Why grammar?===
[[File:Toothbrush 20050716 004.jpg|thumb|200px|de {{knp2|tandenborstel}}]]
Children learn their mother tongue without knowing the parts of speech such as verbs, nouns and phrases. However these are helpful for anyone attempting to learn a second language from a book or a website. Of course the children have it right: the ''best'' way to learn a language is to listen to a mother tongue speaker and simply repeat. Then just use the word in a similar situation and see how people react. Children are masters at acquiring language this way and are generally smiled at when they use a word incorrectly. Being an adult, people are often not so forgiving to you and you feel foolish when people laugh and point out to you that you just said &quot;toothbrush&quot;  while you meant &quot;toothpick&quot;. Besides, native speakers may not always be available to you. Or if they are they are not eager to spend time playing 'child' with you. This book will try to compensate this by addition of audio files and visual information, -as the figure to the right- but that is still only a cumbersome substitute. We do recommend that you use them as much as you can. Firefox seems to give easier access to them than other browsers. So, please go ahead, push that arrow and learn to say 'toothbrush' properly. Your first Dutch word? Congrats.

Although clearly children are superior in language acquisition, grown ups do have an advantage: they can analyze language better in terms of its grammar. This course therefore uses both approaches: it will deal with grammar, but it will also ask you to be a child and listen and repeat or look at some pictures while playing a sound clip. Don't be afraid to be a bit childish! It serves a purpose.

One important observation about children should be mentioned: they always learn language ''in a certain context''.

===Is it all just grammar here then?===
'''No!''' There is much more. Audio files are inserted into the main lessons as much as possible, even though they aim at gradually introducing grammar and syntax. The parallel series of practice lessons (1A, 2A etc.) provide additional practice, vocabulary building, sound material and quizzes. The example pages (Vb. 1 etc.) follow the contextual path of learning like children do and involve nursery rhymes, poems, stories, songs and the like. And there are [[Dutch/Vocabulary|audio-visual vocabulary pages]] to help you learn more words.

===What is the best way?===
So, what is the best way to learn a language? The best way is to '''''do something everyday'''''. What you do is often less important than simply doing it. Children are champions in language acquisition and they never worry about what they do. Oh, and what you do, may very well be doing that same exercise again. Children love doing things &quot;again&quot;. Ever watched the Teletubbies? ''Repeating'' is an important key to language acquisition. Being &quot;efficient&quot; and saying: &quot;oh, I have done that before, let me skip that!&quot; is a bad adult habit that children would never stop to, until they get really bored with something. (Which is when they already know it). So, push that button below the toothbrush again! And tomorrow come back here and do the same.

===Other assets===
Another thing to exploit is the other languages you already know. English speakers will find many strong parallels between their language and Dutch. German speakers even more so, but there are also differences. Where possible we will try to point out the similarities and the differences and exploit them.

However, as noted in the [[Dutch/Introduction|introduction]], Dutch grammar is more complex than English grammar, and identifying the meaning of words in a Dutch sentence is difficult without understanding the clues to word function that come from the grammatical rules. The basic lessons of this textbook are set up to first introduce the parts of speech, and then bring in the rules that govern these. Pay particular attention to sentence word order as you progress through the lessons.

===Some tricks this course uses===
====Hovering====

Some words will be {{C|underlined|this is cribbing of course, but if you don't know a word you may}}. Try to hover your mouse over such words.

====Topics and vocabulary====
There are pages to help you build [[Dutch/Vocabulary|vocabulary]] in a visual / auditive way.

====Audio files====
Whenever you see one of the following:
*[[file:nl-Nederlander.ogg]]
Or:
*{{knop|Vlaming}}

Please click and listen! (If you do not see any buttons now: try a different browser. Firefox and Chrome seem to work. Internet Explorer does not.)&lt;br/&gt;
After listening, pronounce the word the best you can and then click again. Keep doing that till you are satisfied with your own result. It is useful to then leave it be for, say 20 minutes and do it again. Then perhaps once more the next day.

====Vocabulary / Pronunciation boxes====
{|class=&quot;wikitable collapsible collapsed&quot; style=&quot;float:right&quot;
|-
!colspan=&quot;3&quot;|Vocabulary
|-
|de {{Nlwikt|uitspraak}}||[[file:nl-uitspraak.ogg]]||pronunciation
|-
|de {{Nlwikt|woordenschat}}||[[file:nl-woordenschat.ogg]]||vocabulary
|}
For many texts there is a box on the right that you can open to look at the vocabulary being trained and listen to the pronunciations. Click it to open it and start listening and reading.

===Using other sites===
====Wiktionary====
Throughout the texts and in the vocabulary lists there are blue links that take you to the Dutch version of [http://nl.wiktionary.org/wiki/Hoofdpagina  our sister project Wiktionary]. It is called WikiWoordenboek. Of course the layout is in Dutch and you may not immediately understand everything, but that is not a disaster. If you want to learn a language you also should learn to be a bit of a detective: you often need to get the gist of something with a few pieces of the puzzle missing. Don't let that scare you off! Here are a few useful topics used on WikiWoordenbook:

#There usually is an English translation of a word under the heading '''''Vertalingen''''', marked '''Engels''' 
#There is also a ''geluidsopname'' (sound recording) or a phonetic description under '''''Uitspraak'''''. 
#There are tables, usually to the right giving the various forms of the word, say, the plural or the past tense.
#There are usually example sentences putting the word in context
#There are usually antonyms, synonyms, derivatives or related terms

If you are really lost use the interwiki link to the English version (or any other language you know) as back up, but don't give in to it too easily! Use it to figure out what you did not quite get on the Dutch version.

We encourage you to use the links to expand your vocabulary. First guess what a word means, then click!

Just try it on the verb {{Nlwikt|slapen}}; look at the box with three forms on the right. What is the past tense? (It is the middle one in the box)

====Quizlet and Memrise====
There are plenty other sites that allow you to expand your growing knowledge of Dutch. They all have their pros and cons. For example [http://www.memrise.com/home/ Memrise]  and [https://quizlet.com/ Quizlet] have an interesting way to boost vocabulary, but teach zero syntax or grammar and usually little other context. But if you want a vocabulary boost it's great and we are in the process of creating practice sets dedicated to the material of the lessons here. Some already have a quizlet link on the bottom of the page. It is therefore recommended to register for '''Quizlet'''. (It is for free).

====YouTube====
YouTube has a plethora of videos, that we will even send you to at times. Again: good for listening, vocabulary building, often less so on grammar and syntax, but plenty of other context.

====But do come back: the context====
There is a pertinent Dutch proverb: ''Verandering van spijs doet eten''  - ''Change of food makes you eat''. Children also vary what they play with. Variety of learning is healthy. Besides children never learn a word outside context. When they learn a new word, it always goes together with the context of:
# the words around it (semantic context), 
# the way they interrelate (the grammatical context), 
# the order in which they are used (the syntactic context), 
# whether convey anger, sweetness, seriousness (the emotional context), 
# in what kind situations it is used: a school squabble, a church service (social context), 
# in which time period they are/were used (temporal context), 
# by what kind of people: punks, managers, construction workers, kings, pimps, doctors (register context). 

One aim of this book is to provide as much of that context as possible. This is why conversations, stories, texts, poems and songs are important: they give context to the words you are learning.

So, enough talk! Let's get started. And we'll start in the context of a simple conversation

==Gesprek 1-1 ~ Vrienden: Jan en Karel==

We will put such text material in a colored box. What you are supposed to do with such material is the following. 
#First click on the arrow button to ''listen'' to the story and try to read along. 
#Then use the hover method to see an instant translation of a certain word and try to piece together the meaning of the story. 
#Then use the ''Vocabulary'' box on the right to concentrate on single words and start memorizing. 
#Once you have an idea of the gist of the story you can open up the drop down box and read the ''translation'' to see if you were right.
#Then click the arrow again and see if you understand what is being said, first while reading along, then with your eyes closed.

When learning a new language it is very important to be able to deduce meaning from limited information, because you will often not know all the words used. Picking up their meaning from context is an important skill. This is why the hovering is important.

You may notice that Dutch sometimes strings words together a bit differently than English. Dutch word order is quite different and a difficult aspect of the language, but we will revisit that many times. So don't worry about it for the moment, just observe.

{{Dutch/Textbox|
[[Image:Dutch_Lesson1_vrienden.OGG|40px|noicon]]

;{{C|Vrienden|Friends}}

:{{C|Jan|John}} {{C|komt|komt tegen: run into}} {{C|Karel|Charles}} {{C|op|on, in}} {{C|straat|street}} tegen. {{C|Ze|They}} {{C|zijn|are}} {{C|vrienden|friends}}.

::''Jan'': {{C|Hoi|Hi}}, Karel!  {{C|Hoe|how}} {{C|gaat|goes}} {{C|het|it}} {{C|met|with}} {{C|je|you}}?
:::''Karel'': Hoi! {{C|Dank je|Thank you}}, {{C|met|with}} {{C|mij|me}} gaat het {{C|goed|good, well}}. {{C|En|And}} met {{C|jou|you}}?
::''Jan'': Dank je, met mij gaat het {{C|ook|also}} goed. '''''{{C|Tot ziens|See you later}}'''''.
:::''Karel'': Tot ziens, Jan!
}}
{|class=&quot;wikitable collapsible collapsed&quot; style=&quot;float:right&quot;
|-
!colspan=&quot;3&quot;|Vocabulary
|-
!Word!!Audio!!Meaning
|-
|{{Nlwikt|tegenkomen}}||[[file:nl-tegenkomen.ogg]]||to encounter
|-
|de {{Nlwikt|straat}}||[[file:nl-straat.ogg]]||street
|-
|{{Nlwikt|ze}}||[[file:nl-ze.ogg]]||they, them, she, her
|-
|{{Nlwikt|zijn}}||[[file:nl-zijn.ogg]]||to be; his
|-
|{{Nlwikt|vrienden}}||[[file:nl-vrienden.ogg]]||friends
|-
|{{Nlwikt|hoe}}||[[file:nl-hoe.ogg]]||how
|-
|{{Nlwikt|gaat}}||[[file:nl-gaat.ogg]]||goes
|-
|{{Nlwikt|met}}||[[file:nl-met.ogg]]||with
|-
|{{Nlwikt|mij}}||[[file:nl-mij.ogg]]||me
|-
|{{Nlwikt|jou}}||[[file:nl-jou.ogg]]||you (obj.)
|-
|{{Nlwikt|dank}}||[[file:nl-dank.ogg]]||thanks, gratefulness
|-
|{{Nlwikt|goed}}||[[file:nl-goed.ogg]]||good, well
|}
[[File:Dutch people speaking on the street.jpg|thumb|200px|{{knop|vrienden}} Vrienden]]
{{Dutch/Translation|Gesprek 1-1|
::Friends
:::John runs into Charles in the street. They are friends.
:::''John'': Hello Charles. How are you?
:::''Charles'': Hi, thank you, I'm fine. And you?
:::''John'': Thank you, I'm doing fine as well. Goodbye.
:::''Charles'': Goodbye John!
}}

===Pronunciation===
Dutch pronunciation varies with region and speaker, and you may have been shocked at some of the sounds of the language. You can visit [[Dutch/Alfabet]] if that is the case. Dutch spelling is not really phonetic, but pretty systematic (much more so than English) and once you learn the system you should be able to pronounce an unknown word on sight pretty well.

It is not easy to render the sounds in writing, but the following rendition in IPA gives a reasonable idea. Try running the sound file again while reading the IPA version. 

:{{IPA|'vrin.də(n)}}
:{{IPA|'jɑn.kɔmt.'ka.rəl.ɔp.'stra.'te.ɣə(n) zə.zɛɪn.vrin.də(n)}}
::{{IPA|ɦɔj,'ka.rəl.ɦu.'ɣat.ət.'mɛ.cə}}
::{{IPA|ɦɔj,dɑŋ.k&lt;sup&gt;j&lt;/sup&gt;ə,mɛt.'mɛɪ.'ɣat.ət.xut.ʔɛn.'mɛ.'cɑʊ}}
::{{IPA|dɑŋ.k&lt;sup&gt;j&lt;/sup&gt;ə,mɛt.mɛɪ.'ɣat.ət.'ok.xut. tɔ.'tsins}}
::{{IPA|tɔ.'tsins.jɑn}}

:Notice sounds like {{IPA|[ɣ]}} and {{IPA|[x]}}? And how t+j run together into {{IPA|[c]}}? And how about {{IPA|[ɦ]}}? Or the vowel {{IPA|[u]}}? 
:Notice also that vowels often occur in two varieties: {{IPA|a/ɑ, e/ɛ, o/ɔ}}. They are often called 'long' and 'short', but those names are misleading: they are really different sounding vowels.&lt;ref&gt;This is particularly a point of difficulty for speakers of Slavic languages like Russian or Czech.&lt;/ref&gt; The length difference is rather secondary, if there is any.

If you prefer other renditions than IPA try [[Dutch/Gesprek 1-1|this page]]

==Grammatica 1-2 ~ Forms==
We will use the material in the colored boxes to point at grammatical phenomena and introduce the grammar that way, step by step. 
===Clitic forms===
{|style=&quot;float:right&quot;
|{{knop|jou}} jou||{{knop|je}} je
|}
Did you notice the difference between &quot;Hoe gaat het '''met ''je'''''&quot;? and &quot;En '''met ''jou'''''?&quot; in the conversation?  Both translate literally into '''with ''you''''', but there is a difference in emphasis. ''Jou'' carries emphasis, ''je'' does not. In Dutch, there are often two forms of the same pronoun: a strong one and a weak ('clitic'&lt;ref&gt;There are other languages that show similar differences. Gaelic e.g. has ''tu'' and ''tusa''. French also has the difference between ''tu'' and ''toi'' but the usuage is a bit different than in Dutch.&lt;/ref&gt;) one. This is particularly true in spoken, colloquial Dutch. In the written language the clitic ones are not always shown as such. 

*The full forms have full vowels or diphthongs (like in j'''ou''') and can either carry stress or not.
*The clitic forms cannot have emphasis and the vowel in a clitic is often reduced to a neutral 'schwa' [ə] (like in j''e''') or omitted entirely. 

In colloquial English the same thing can be heard at times: ''seeya!'' instead of ''see you!''. In Dutch the use of clitics is very common; it already was in the Middle Dutch period before 1500.

For now remember: '''never stress a clitic'''

===Polite forms===
The above conversation was between two good friends. It utilizes the '''familiar''' form of the personal pronoun (''je'', ''jou'') where English uses ''you''. However, Dutch also has a '''polite''' or formal form of the personal pronoun for the second person (you), '''[[wikt:u#Dutch|u]]'''. Many languages have this distinction. It is e.g. comparable with  {{Nlwikt|sibh}} in Gàidhlig, [[wikt:Sie|Sie]] in German,  [[wikt:vous|vous]] in French, [[wikt:usted|usted]] in Spanish, [[wikt:Вы|Вы]] in Russian, or [[wikt:anata|anata]] in Japanese. When to use one or the other is not always easy to decide. Someone unknown, particularly if older, is generally ''u'', an old friend typically ''je, jou''. The latter roughly corresponds with the 'first name basis' in English.  Notice the use of ''u'' in the conversation below that takes place between colleagues rather than close friends. They would never say: &quot;hoi!&quot; to each other.

===Regional forms===

In the South of the area where Dutch is spoken (Flanders mostly), , the familiar form when speaking in familiar fashion is ''gij'' (clitic: ''ge'', object: ''u''). ''Gij'' is mostly used when speaking dialect, although it gets used more and more in polite situations and on tv. In the north it has become obsolete since about 1800. It is used much like ''you'' in English for both singular and plural. In the North ''gij'' is now only encountered there in archaic phrases like: ''gij zult niet stelen'' - ''thou shalt not steal''. Like ''thou'' the pronoun ''gij'' takes its own verb forms. This course is mostly based on northern usage as this is the most widely accepted, including in Suriname and the Antilles, but some important differences will be pointed out and we will see ''gij'' occasionally when we look at some older poetry.

==Gesprek 1-2 ~ Collega's: De handelaars==
{|class=&quot;wikitable collapsible collapsed&quot; style=&quot;float:right&quot;
|-
!colspan=&quot;3&quot;|Vocabulary
|-
|{{Nlwikt|goedendag}}||[[file:nl-goedendag.ogg]]||good day
|-
|de {{Nlwikt|mevrouw}}||[[file:nl-mevrouw.ogg]]||lady, mrs.
|-
|de {{Nlwikt|meneer}}||[[file:nl-meneer.ogg]]||sir, mr.
|-
|de {{Nlwikt|handelaar}}||[[file:nl-handelaar.ogg]]||merchant
|-
|{{Nlwikt|u}}||[[file:nl-u.ogg]]||you (polite)
|-
|{{Nlwikt|zeer}}||[[file:nl-zeer.ogg]]||very
|-
|{{Nlwikt|uit}}||[[file:nl-uit.ogg]]||out
|-
|{{Nlwikt|al}}||[[file:nl-al.ogg]]||already
|-
|{{Nlwikt|goed}}||[[file:nl-goed.ogg]]||good
|-
|het {{Nlwikt|bezoek}}||[[file:nl-bezoek.ogg]]||visit
|-
|het {{Nlwikt|Nederlands}}||[[file:nl-Nederlands.ogg]]||Dutch (language)
|}
Push the button and listen to the following text. It is recommended to first just listen.

Then read the following conversation. It is a bit more formal than the one before. If you are not sure of the meaning of a word, hover your mouse over it, if it is underlined. A translation will pop up. Or use the vocabulary box to the right. Make sure you know the gist of the story before opening the translation box. If you cheat, you cheat yourself... Finally, listen to the recording again with your eyes closed. Can you understand what is being said?
{{Dutch/Textbox|
*[[Image:Dutch-Lesson1-handelaars.ogg|40px|noicon]]


:Meneer Jansen [[wikt:nl:tegenkomen|komt]] [[wikt:nl:mevrouw|mevrouw]] De Vries [[wikt:nl:tegenkomen|tegen]]. Het zijn {{C|handelaars|business people, merchants}}.
* ''Meneer Jansen'': {{C|Goedendag|good day}}, {{C|mevrouw|mrs}} De Vries!
* ''Mevrouw De Vries'': Goedendag, {{C|meneer|mr.}} Jansen!
* ''Meneer Jansen'': {{C|Hoe|how}} {{C|gaat|goes}} {{C|het|it}} {{C|met|with}} {{C|u|you (polite)}}?
* ''Mevrouw De Vries'': {{C|Zeer|very}}&lt;ref&gt;De Vries is being rather stiff and formal by using 'zeer'. It is pretty dated. A more neutral register word would be 'heel'.&lt;/ref&gt; {{C|goed|good, well}}, {{C|dank|thank}} u {{C|wel|well}}. {{C|En|and}} met u?
* ''Meneer Jansen'': {{C|Ook|also}} goed.
* ''Mevrouw De Vries'': {{C|Mooi|nice, pretty}}. {{C|Kent|know}} u [[wikt:nl:meneer|meneer]] Standish? {{C|Bent|are}} u {{C|hem|him}} {{C|al|already}} {{C|tegengekomen|encountered}}?
* ''Meneer Jansen'': {{C|Uit|out of}} Engeland? {{C|Nee|no}}. Is {{C|hij|he}} {{C|op|on, at}} {{C|bezoek|visit}}?
* ''Mevrouw De Vries'': {{C|Ja|yes}}. Hij {{C|spreekt|speaks}} {{C|Nederlands|Dutch}}. {{C|Tot ziens|See you}}, meneer Jansen!
* ''Meneer Jansen'': Tot ziens, mevrouw De Vries.
}}
&lt;br clear=&quot;all&quot;&gt;
:Have you figured out the gist yet? Then open the translation box to see if you were right:

{{Dutch/Translation|Gesprek 1-2|

:::* Mr. Johnson encounters Mrs. De Vries. They are merchants.
:::*''Mr. Johnson'': Good day, Mrs. de Vries!
:::*''Mrs. De Vries'' Good day, Mr. Johnson! 
:::*''Mr. Johnson'': How do you do?
:::*''Mrs. De Vries'' Very well, thank you. And how are you?
:::*''Mr. Johnson'': Fine as well.
:::*''Mrs. De Vries'': Good! Do you know Mr. Standish? Have you met him yet?
:::*''Mr. Johnson'': From England? No, is he visiting?
:::*''Mrs. De Vries'' Yes, he is. He speaks Dutch. Goodbye, Mr. Johnson.
:::*''Mr. Johnson'': Goodbye, Mrs. De Vries.
}}
Go back to the pronunciation, close your eyes and see how much you understand now. You may have to repeat the process a few times.
{{Dutch/Exercise|Waar of niet waar|

:''dit is waar'' - this is true
:''dit is niet waar'' - this is not true

Answer the following questions with either ''waar'' or ''niet waar''

# Mevrouw De Vries is meneer Standish al tegengekomen.
# Meneer Jansen en mevrouw De Vries zijn goede vrienden.
# Meneer Jansen en mevrouw de Vries zeggen (they say) ''je'' en ''jou'' tegen elkaar (to each other)
# De Engelsman, meneer Standish is op bezoek.
# Het gaat goed met meneer Jansen.
#
|

# Mevrouw De Vries is meneer Standish al tegengekomen. - niet waar
# Meneer Jansen en mevrouw De Vries zijn goede vrienden. - niet waar, zij zijn collega's
# Meneer Jansen en mevrouw de Vries zeggen (they say) ''je'' en ''jou'' tegen elkaar (to each other) - niet waar, zij zeggen ''u'' tegen elkaar
# De Engelsman, meneer Standish is op bezoek. - dit is waar
# Het gaat goed met meneer Jansen. - waar
}}

== Quiz ==
How are you doing so far? Do this little quiz to find out!

&lt;quiz display=&quot;simple&quot;&gt;

{ What is this? [[File:nl-tandenborstel.ogg]]
| type=&quot;[]&quot; }
-toothpick
-friend
+toothbrush
-visit

{ What is this? [[File:nl-jou.ogg]]
| type=&quot;[]&quot; }
-me
-sir
+you (object)
-you (subject)

{ Select the correct translation
| type=&quot;[]&quot; }
|straat|goed|hoe|al|handelaar
---+- already
+---- street
----+ merchant
-+--- good
--+-- how

&lt;/quiz&gt;

==Grammatica 1-3 ~ Introduction to pronouns==


A '''[[Wikipedia:Pronoun|pronoun]]''' is a short word that takes the place of a noun previously mentioned in the sentence, paragraph, or conversation. 

'''''Recall''''': Kent u ''meneer Standish''? Bent u ''hem'' al tegengekomen?

''Hem'' refers back to ''meneer Standish''. It is a ''pronoun'' that stands ''for'' (pro- !) meneer Standish.

There is a variety of pronouns like personal, possessive, relative and indefinite ones. Let's look at the personal pronouns first.

===Personal pronouns===

Both English and Dutch have had a system of case endings in the past, as languages like German and Russian still do today. In English most of the system fell into disuse starting with the Viking invasions of the 9th and 10th Centuries, and especially after the Norman invasion in 1066. The collapse of the system in spoken Dutch dates mostly from the 16th century and in the written language it was scrapped as recently as 1947. That means that Dutch has more remnants of the case system left than English and we will even devote [[Dutch/Lesson 15|lesson 15]] to those remnants. The personal pronouns actually still show some case differences in both languages.

Personal pronouns are quite familiar in English: They are words like I,you,he,she,we,you and they. &lt;br&gt;At least this is the case for the subject (nominative '''''case'''''). As object (accusative) some of them are different: ''me'',you,''him'',''us'',you,''them''. Compare:

::&lt;span style=&quot;color:blue;&quot;&gt;I&lt;/span&gt; see you.
::You see &lt;span style=&quot;color:blue;&quot;&gt;me&lt;/span&gt;.

Notice how '''I''' turns into '''me''' when used as an object. '''You''' remains the same.

Much like in English, '''ik''' (subject) turns into '''mij''' as object in Dutch, whereas '''je''' remains the same in both roles:

::&lt;span style=&quot;color:blue;&quot;&gt;Ik&lt;/span&gt; zie je.
::Je ziet &lt;span style=&quot;color:blue;&quot;&gt;mij&lt;/span&gt;.

The system in Dutch resembles the English one quite a bit, after all the languages are close relatives:

*As in English there are three '''''persons''''' in Dutch grammar: first (I), second (you) and third (he) 
*As in English there is a distinction in '''''number''''' between singular (I) and plural (we). 
*As in English there are '''''gender''''' distinctions in the third person singular (he, she, it) 
*As in English there are '''''case''''' distinctions between subject and object (he, him)

Nevertheless the Dutch system is a little more involved, as we have seen there are:

*familiar and polite forms: ''je'' versus ''u''. 
*weak (clitics) and strong forms: ''je'' versus ''jou''.

In addition there are
# Regional differences:  (jij/jullie  - u) (North) versus (gij/gullie - u) (South) 
# A growing rift between how inanimate and animate nouns are treated
#:In English ''he'' and ''she'' are reserved for ''animate'' nouns -usually persons- and this is increasingly the case in Dutch as well, certainly in Northern usage. We will revisit this point later.
# Pronominal replacement: the combination preposition + pronoun (e.g. with it) is usually replaced by an adverb
#:We will revisit that in lesson 8

Let's leave most of these complications aside for the moment and concentrate on the forms of the pronouns. There are a few more than in English.

===Subject case (nominative)===
{|class=&quot;wikitable&quot;
|- bgcolor=#FFDEAD
!Person
!singular
!clitic
!{{blue|English}}
!plural
!clitic
!{{blue|English}}
|-
!1st 
|{{knp2|ik}}||{{knop|'k}} ('k)||{{blue|I}}||{{knp2|wij}}||{{knp2|we}}||{{blue|we}}
|-
!2nd (fam.)
|{{knp2|jij}}||{{knp2|je}}||rowspan=&quot;3&quot;|{{blue|you}}||{{knp2|jullie}}||-||rowspan=&quot;3&quot;|{{blue|you}}
|-
!2nd (polite)
|{{knp2|u}}||-||{{knp2|u}}||-
|-
!2nd (South)
|{{knp2|gij}}||{{knp2|ge}}||{{knp2|gij}}||{{knp2|ge}}
|-
!3rd
|{{knp2|hij}}&lt;br /&gt; {{knp2|zij}}&lt;br&gt; {{knp2|het}}||{{knop|ie}} (-ie)&lt;br/&gt; {{knp2|ze}}&lt;br /&gt;{{knop|'t}} ('t)||{{blue|he}}&lt;br/&gt;{{blue|she}}&lt;br/&gt;{{blue|it}}&lt;br/&gt;||{{knp2|zij}}||{{knp2|ze}}||{{blue|they}}
|}

===Object case (accusative)===
{|class=&quot;wikitable&quot;
|- bgcolor=#FFDEAD
!person
!singular
!clitic
!{{blue|English}}
!plural
!clitic
!{{blue|English}}
|-
!1st 
|{{knp2|mij}}||{{knp2|me}}||{{blue|me}}||{{knp2|ons}}|| - ||{{blue|us}}
|-
!2nd (fam.)
|{{knp2|jou}}||{{knp2|je}}||rowspan=&quot;3&quot;|{{blue|you}}||{{knp2|jullie}}|| -||rowspan=&quot;3&quot;|{{blue|you}}
|-
!2nd (polite)
|{{knp2|u}}||-||{{knp2|u}}||-
|-
!2nd (South)
|{{knp2|u}}||-||{{knp2|u}}||-
|-
!3rd
|{{knp2|hem}}&lt;br&gt; {{knp2|haar}}&lt;br&gt; {{knp2|het}}||{{knop|'m}}('m)&lt;br/&gt; {{knop|d'r}}(d'r)&lt;br/&gt; {{knop|'t}}('t)||{{blue|him}}&lt;br/&gt;{{blue|her}}&lt;br/&gt;{{blue|it}}&lt;br/&gt;||{{knp2|hen}}&lt;br /&gt;{{knop|hun}}hun*||{{knp2|ze}}||{{blue|them}}
|}

====Remarks====

# As you see not all pronouns have clitics and some of them (shown in parentheses) are not often used in the written language.
# *In prescriptive grammar ''hun'' is dative and hen is ''accusative''. But in speaking, Dutch speakers generally do not make this distinction. This is because the ''hen'' form was artificially created by the grammarians of the past &lt;ref&gt; &quot;Dutch&quot; by Jan G. Kooij in ''The world's major languages'' edt. Bernard Comrie {{ISBN|0-19-520521-9}} Oxford University Press 1987&lt;/ref&gt; and in the whole rest of the language there are no other words that make a distinction between dative and accusative. In the spoken language ''hen'' and ''hun'' are often used interchangeably (as synonyms) or people avoid the issue by opting for the clitic ''ze''.

==Exercises 1-1==
===Quizlet===
This is the point where it is '''your turn''' to put in some effort yourself, because obviously you have some memorization to do.

There is a [https://quizlet.com/85109848/dutch-personal-pronouns-wikibook-lesson-1-flash-cards/ '''Quizlet practice set'''] (27 terms) to help you with memorizing the pronouns. But it is recommended to ''first'' use the above tables. Unfortunately, the pronunciation of some of the clitics with apostrophes is wrong at Quizlet.  So click the arrow buttons here to listen to the pronunciation and speak it out loud yourself until you feel confident that you know them, then go to Quizlet. Do make sure you can hear sound at Quizlet.&lt;ref&gt;Sometimes you need to restart your browser to make it work.&lt;/ref&gt;First scan through the cue cards, then do some of the other methods available. It should take you an hour or so and you will know some of the most frequently used words in the language.

===Pronunciation drill===
{{Dutch/Exercise|Ik, jij, wij, jullie, mij pronunciation drill
|
[[Image:Nl-Dutch-ch1-pronoun-drill.ogg|noicon]]
Push the button, repeat in the pauses and say the requested words in Dutch
|
}}
===Translation exercise===
{{Dutch/Exercise|pronouns 1: translation exercise|

Translate into Dutch:

# How are you, Mr. Bush?
# How are you, Jan?
# Are you merchants?
# John runs into us.
# We meet John in the street
# He is visiting
# We are from England
|

# How are you, Mr. Bush?
#: Hoe gaat het met u, meneer Bos
# How are you, Jan?
#: Hoe gaat het met je, Jan
# Are you merchants?
#: Zijn jullie handelaars?
# John runs into us.
#: Jan komt ons tegen
# We meet John in the street
#: Wij komen Jan op straat tegen
# He is visiting
#: Hij is op bezoek
# We are from England
#: Wij zijn* uit Engeland

:(komen* to come would be better) 
}}
===Identification exercise===
{{Dutch/Exercise|pronouns 2: identification exercise|
Identify all personal pronouns in the two above conversations (in the colored boxes) by person, case, number polite/familiar form and weak/strong form.
:Are there any cases where the case is different from what the English translation has? Why?
|
Jan komt Karel op straat tegen. '''Ze''' zijn vrienden. 
:::(3rd person plural nominative weak)
:''Jan'': Goedendag, Karel.  Hoe gaat het met '''je'''? 
:::(2nd person singular accusative weak)
:''Karel'': Goedendag. Dank je, met '''mij''' gaat het goed. En met '''jou'''?
:::(1st person singular accusative strong / 2nd person singular accusative strong)
:''Jan'': Dank '''je''', met '''mij''' gaat het goed. Tot ziens.
:::(2nd person singular accusative weak / 1st person singular accusative strong)
:''Karel'': Tot ziens, Jan!

In the expression ''hoe gaat het met jou'', ''jou'' is in the object case, because it follows a preposition ''met'' (with). Literally it says ''how goes it with you''. English would say: How are you? In that case ''you'' is subject, not object.

:Meneer Jansen komt mevrouw De Vries tegen. '''Het''' zijn handelaars. 
:::(3rd person singular nominative neuter) Note that Dutch often uses 'it are' to indicate generality.
::''Meneer Jansen'': Goedendag, mevrouw De Vries!
::''Mevrouw De Vries'': Goedendag, meneer Jansen!
::''Meneer Jansen'': Hoe gaat het met '''u'''? 
:::(2nd person singular accusative polite)
::''Mevrouw De Vries'': Zeer goed, bedankt. En met '''u'''? 
:::(same)
::''Meneer Jansen'': Ook goed.
::''Mevrouw De Vries'': Mooi. Bent '''u''' meneer Standish al tegengekomen? 
:::(2nd person singular nominative polite)
::''Meneer Jansen'': Uit Engeland? Nee. Is '''hij''' op bezoek?
:::(3rd person singular nominative)
::''Mevrouw De Vries'': Ja. Tot ziens, meneer Jansen!
::''Meneer Jansen'': Tot ziens, mevrouw De Vries
}}
{{Dutch/Exercise|Turn into clitics
|
Turn the personal pronouns into their clitic forms if possible:

:Jij komt hen tegen.
:Zegt hij goedendag of hoi?
:Zij is ook op bezoek
:Jullie zijn goede vrienden
:Gij zijt uit Engeland
:Gaat het goed met jou?
:Zij groeten mij met &quot;hoi&quot;.
:Het gaat goed met ons
:U spreekt Nederlands met hen
:Wij spreken Engels
|
:J'''e''' komt '''ze''' tegen.
:Zegt-'''ie''' goedendag of hoi?
:'''Ze''' is ook op bezoek
:Jullie zijn goede vrienden '''no change'''
:'''Ge''' zijt uit Engeland
:Gaat het goed met '''je'''?
:'''Ze''' groeten '''me''' met &quot;hoi&quot;.
:''''t''' Gaat goed met ons
:U spreekt Nederlands met '''ze'''
:'''We''' spreken Engels

Notice though that you have shifted the emphasis of each sentence by doing this replacement. E.g. in &quot;wij spreken Engels&quot; the emphasis is mostly on ''we'' (not: you or them), in &quot;we spreken Engels&quot; it is mostly on English (not: e.g. Dutch)
}}

==Woordenlijst 1==
You have already encountered quite a few words above. Now make sure you own them! Listen to their pronunciation, sort the table by English and read back to Dutch, check the pronunciation again. Click on the blue link to go to the Dutch wiktionary and try to figure out what you may. If you do not understand, follow the interwiki link to go to the English wiktionary.

In short: there are many ways to use this table and you can try one thing one day and come back another to try something different.
{|class=&quot;wikitable sortable&quot; style=&quot;text-align:left; float:left; clear:right; margin: 0.5em 0 0 0; border-style: solid; border: 1px solid #AAAAAA; border-right-width: 1px; border-bottom-width: 1px; border-collapse: collapse; font-size: 100%;&quot;
! Dutch word!!audio file!!English translation
|-
|de {{Nlwikt|appendix}}    ||[[file:nl-appendix.ogg]] ||                appendix, supplement
|-
|het {{Nlwikt|bezoek}}     ||[[file:nl-bezoek.ogg]] ||                 visit, attendance
|-
|(het) {{Nlwikt|Engeland}}   ||[[file:nl-Engeland.ogg]] ||                 England
|-
|het {{Nlwikt|Nederlands}}  ||[[file:nl-Nederland.ogg]] ||                Dutch
|-
|de {{Nlwikt|vriend}}, vrienden  ||[[file:nl-vriend.ogg]] ||          friend, friends
|-
|de {{Nlwikt|handelaars}}    ||[[file:nl-handelaar.ogg]] ||              business people, businessmen, tradesmen, merchants (''pl.'')
|-
|het {{Nlwikt|gesprek}}, gesprekken ||[[file:nl-gesprek.ogg]] ||        conversation, conversations
|-
|de {{Nlwikt|grammatica}}  ||[[file:nl-grammatica.ogg]] ||                grammar
|-
|de {{Nlwikt|les}}     ||[[file:nl-les.ogg]] ||                    lesson
|-
|de {{Nlwikt|straat}}    ||[[file:nl-straat.ogg]] ||                  street
|-
|de {{Nlwikt|woordenlijst}}  ||[[file:nl-woordenlijst.ogg]] ||              word list
|-
|de {{Nlwikt|woordenschat}}  ||[[file:nl-woordenschat.ogg]] ||              vocabulary
|-
| {{Nlwikt|op}} {{Nlwikt|straat}}   ||[[file:nl-straat.ogg]] ||                on (in) the street
|-
| {{Nlwikt|tot}} {{Nlwikt|ziens}}   ||[[file:nl-tot ziens.ogg]] ||                goodbye (''lit'': see you again)
|-
| {{Nlwikt|uit}} Engeland ||[[file:nl-uit.ogg]] ||               from England
|-
| Met mij gaat het goed || ||      I am fine (''lit'': With me goes it well)
|-
| {{Nlwikt|goedendag}}! ||[[file:nl-goedendag.ogg]] ||                 Good day (greeting)
|-
|(de) {{Nlwikt|dag}}!   ||[[file:nl-dag.ogg]] ||                     (Good) day! Hi! Hello!
|-
| {{Nlwikt|goed}} ||[[file:nl-goed.ogg]] ||                       good
|-
| En met jou? ||[[file:nl-jou.ogg]] ||                And how are you? (''lit'': And with you?)
|-
| Hoe gaat het met jou (u)?|| ||   How are you (''lit'': How goes it with you?)
|-
| {{Nlwikt|hoe}}  ||[[file:nl-hoe.ogg]] ||                       how
|-
| {{Nlwikt|gaan}} ||[[file:nl-gaan.ogg]] ||                       to go
|-
| {{Nlwikt|het}} {{Nlwikt|gaat}} ||[[file:nl-gaat.ogg]] ||                   it goes
|-
| {{Nlwikt|met}} ||[[file:nl-met.ogg]] ||                        with
|-
| is op {{Nlwikt|bezoek}} ||[[file:nl-bezoek.ogg]] ||               is visiting 
|-
| {{Nlwikt|tegenkomen}} ||[[file:nl-tegenkomen.ogg]] ||                 to meet, come across, encounter, run into
|-
| komt ... tegen|| ||              comes across , runs into, meets
|-
| {{Nlwikt|bezoeken}} ||[[file:nl-bezoeken.ogg]] ||                   to visit
|-
| {{Nlwikt|maar}} ||[[file:nl-maar.ogg]] ||                       but, however
|-
| {{Nlwikt|ook}} ||[[file:nl-ook.ogg]] ||                        also, too, as well
|-
| {{Nlwikt|dank}} je, dank u.|| ||            thank you;
|-
| {{Nlwikt|bedankt}} ||[[file:nl-bedankt.ogg]] ||                    thanks
|-
| {{Nlwikt|simpel}} ||[[file:nl-simpel.ogg]] ||                     simple
|-
| {{Nlwikt|het}} ||[[file:nl-het.ogg]] ||                        it (pronoun)
|-
| {{Nlwikt|mevrouw}} ||[[file:nl-mevrouw.ogg]] ||                    Ms., Miss, or Mrs.
|-
| {{Nlwikt|meneer}}  ||[[file:nl-meneer.ogg]] ||                    Mr.
|-
| {{Nlwikt|mij}}||[[file:nl-mij.ogg]] ||                         me
|-
| {{Nlwikt|nee}} ||[[file:nl-nee.ogg]] ||                        no
|-
| {{Nlwikt|ja}}  ||[[file:nl-ja.ogg]] ||                        yes
|-
| {{Nlwikt|correct}} ||[[file:nl-correct.ogg]] ||                    correct
|-
| {{Nlwikt|al}}  ||[[file:nl-al.ogg]] ||                        already, yet
|-
| {{Nlwikt|mooi}} ||[[file:nl-mooi.ogg]] ||                       beautiful (in this case, 'nice' or 'fine')
|-
| {{Nlwikt|zeer}}||[[file:nl-zeer.ogg]] ||                        very
|-
| {{Nlwikt|en}}   ||[[file:nl-en.ogg]] ||                       and 
|}
&lt;br clear=&quot;all&quot;&gt;

===Quizlet===
The vocabulary of this lesson can be trained at [https://quizlet.com/85125945/dutch-wikibook-vocabulary-lesson-1-flash-cards/ Quizlet]. (33 terms)

===Your turn! Building vocabulary 1===

When learning a language you need to start building up your vocabulary. There are various ways of doing that. One is to study the above conversations well. Often words are easier to remember when put in context. We will add vocabulary building exercises to each lesson to make it easier for you to memorize it all.

{{Dutch/Exercise|vocabulary
|
Go to [[Dutch/Vocabulary/Personal pronouns/hover test]] to check your knowledge of Dutch personal pronouns.&lt;br&gt;
Go to [[Dutch/Vocabulary/Lesson 1/hover test]] to check your knowledge of the above vocabulary.
|
}}
{{Dutch/Exercise|Additional vocabulary|
 
Go to the [[Dutch/Vocabulary/Survival kit]] to learn the 56 most important words in the Dutch language. The same set has been created at [https://quizlet.com/84964137/survival-kit-of-56-most-common-dutch-words-flash-cards/ Quizlet] if you prefer to use their methods. Once you know them all, try to translate the following:
#Wil jij misschien een vrouw?
#Dit is erg slecht, denk ik.
#Na het leven is er de dood
#Ik hoor hier mensen beneden 
#Er is een tijd en een plaats voor alle dingen
#Goed en slecht, klein en groot, kort en lang zijn niet dezelfde dingen
#Zet een klein deel voor, een ander deel achter , iets meer boven en de rest beneden
|

#Do you want a woman perhaps?
#That is very bad, I think
#After life there is death
#I hear people down here
#There is a time and a place for all things
#Good and bad, small and big, short and long are not the same things
#Put a small part in front, another part behind, a bit more on top and the rest below.
}}

==Progress made==
If you have studied the above well, you should
#Know more about the process of language acquisition. This should allow you to tailor your own learning better to your specific needs and preferences
#Started tuning your ears and your mouth to the pronunciation
#Gained vocabulary: 27 pronouns, 33 terms introduced in the lesson, 56 of the most often used words in the language, '''116''' terms in total.
#Learned about the use of personal pronouns, including their clitic, polite and regional forms.

==Further practice==
This lesson is accompanied by two pages that are intended to practice and reinforce what you have learned above. They do that with a bit different approach

* [[Dutch/Lesson 1A|Les 1A]] will give you more conversations and practice.
* [[Dutch/Example 1|Voorbeeld 1]] uses the simplest pieces of literature: nursery rhymes to teach language in a playful and amusing way.

It is recommended that you first work on the material in these two modules before you move on to lesson two, but of course this depends on your level of understanding and one of the nice things about the wiki-system is that one can use it whichever way you see fit. (Which is what children would do, but they are used to running into new things that they do not fully comprehend.)

==Appendix==
&lt;small&gt;&lt;&lt; [[Dutch/Introduction|Lesson Layout Guide]]&lt;br&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;[[Dutch/Alfabet|Pronunciation Guide]] &gt;&gt; &lt;/small&gt;
{{BookCat}}
&lt;references/&gt;</text>
      <sha1>o64kmsqrc6d1az6ciew4n5q3do431ss</sha1>
    </revision>
  </page>
  <page>
    <title>Lucid Dreaming/Using</title>
    <ns>0</ns>
    <id>4071</id>
    <revision>
      <id>4678569</id>
      <parentid>4526854</parentid>
      <timestamp>2026-10-27T19:56:03Z</timestamp>
      <contributor>
        <username>User97104</username>
        <id>3562800</id>
      </contributor>
      <comment>/* Hard */ Im</comment>
      <origin>4678569</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19995" sha1="g4j6zi3valtv2cq59kf3u0gdq9s88ss" xml:space="preserve">{{LDTOC}}

==Introduction==
Conduction is the part of lucid dreaming that treats of stabilizing, controlling, and terminating lucid dreams. It is best to learn about induction first because conduction relies on being in a lucid dream. Remember to do what works best for you. Best of Luck!
==Dream stabilization==
Once you are able to dream lucidly, you may find that it is difficult to stay in the dream; for example, you may wake instantly or the dream may start “fading” which is characterized by loss or degradation of any of the senses, especially vision. Alternatively, a new lucid dreamer could easily forget that they are in a dream, as a result of the shock of the sensation.

Don't worry if you wake immediately after becoming lucid. As you gain more experience of becoming lucid, it will come as less of a shock and you’ll be less likely to wake up. Make sure you do a reality check to be sure you’re not still dreaming. As you gain more experience, you will have an easier time identifying when and remembering that you are dreaming.

You can avoid more gradual fadings by '''stimulating your senses'''. This means listening for sounds, feeling around with your hands, and paying attention to what you see and smell. The idea here is to load your senses with stimulation from the dream so that your senses cannot shift to the real world. If you close your eyes, you are removing a great deal of sensory information and might wake up. Staring at a single point can cause effectively the same problem if you stop seeing everything else in your peripheral vision, or don't see enough movement. If you hear something loud in real life and are hearing nothing in the dream, your senses may shift to the real world, causing you to wake up.

Ideally you should be able to use the techniques below to stabilize your dream ''before'' it starts to fade (or “black out”). As always, prevention is better than treatment - and the more stable and vivid your dreams are, the more enjoyable they will be.  However, if that doesn't work you may be able to use stabilization techniques to stop the fading; the spinning technique is probably the most effective in this case.

If you still can’t stabilize your dream, you may decide to try and wake up with the aim of remembering your dream as accurately as possible while its still fresh in your mind.

===Hand Touching===
Rub your hands together and concentrate on the rubbing. You should feel the friction and the heat of your hands. If you can concentrate on the feelings that this action generates, your dream is likely to stabilize and become more vivid and detailed. You can also keep one hand on your arm while exploring the dream for a constant sense of stimulation.  This technique is most effective when used in conjunction with the “Slowing it down” technique, by staring at your hands while rubbing them together.

===Spinning===
You spin around in your dream much as you would if you suddenly want to feel dizzy in real life. The sensation of movement is the key here to stabilizing the dream. Many people report success with this technique, but it also tends to cause a complete change of your dream scene (see [[#Changing the dream environment|Changing the dream environment]] below). If the dream scene disappears  completely (e.g., becomes black), it is necessary to visualize the dreamscape to return to the dream.

===Slowing it down===
Some people like to stabilize the dream by “stopping to smell the roses” and slowly staring at a dream object until it becomes clear. The dreamer would then look around elsewhere, noticing how detailed everything is, thereby stimulating the visual portion of the dream. ''However, others find this can cause their lucid dream to end.'' If you focus on one object for too long to the exclusion of everything else, you will likely wake up or lose the dream. It works best to pay attention to everything in your vision, including your peripheral vision, not just the center of the object you're staring at. If staring at a single object doesn't work for you, try to let your eyes wander around instead.

===Touching your dream===
If you feel that your dream is too abstract and fear that it might be fading, you can prevent this by grabbing hold of a solid object in your dream and focus on how real the sensation is. A good tip is to find something you know is stuck, for instance a table nailed to the ground, and pull it with all your muscular power (no ''supernatural'' powers!), and you should feel how solid it is. The idea is that you convince yourself that the dream is solid and real — through tactile stimulation — and nothing abstract.

===Regaining waking memory or skills===
This is also likely to enhance your degree of lucidity. Try to remember facts from your waking life, such as your phone number, address, etc., or do some simple math. Or, start reciting the lyrics to your favorite song. Or perhaps try some sports practice you know well — this all depends on which senses / methods of thought process you tend to rely on most in your waking life.

=== Dream Guide ===
Summon a DC (Dream character) that you expect to Guide you through the dream. Summoning is easier if you always expect this Guide to be there in a dream. The Guide is useful for escaping scary or unpredicted environments (&quot;whooshing&quot; you away, killing or unsummoning the threat, reminding you that you are in control.). Imagine this Guide as powerful, knowledgeable, and protective over you. Guides can also walk you through summoning, flying, shapeshifting, etc. and be useful for learning and controlling your dreams.

=== False awakening ===
A couple of the users on the ld4all.com forums have had success with creating a false awakening to stabilize a dream. If the above techniques are failing and you find your dream still fading, ''and you really want to continue your lucid dream'', do the following:

# Expect to have a false awakening.
# When you think you wake up, perform a reality check.

You will either have a false awakening, reality check, and then end up with an even more vivid lucid dream, or will really wake up, perform a reality check, and realize that you just woke up (bad luck!).

The most important part of this is the reality check. This is what will continue your lucid dream. You should be performing reality checks when you wake up. If you plan to induce false awakenings in order to stabilize a dream, the reality check that you perform as you wake up is as important as the one that got you lucid, if not more.

Perform every check in the book until you are '''positively, absolutely, and completely sure''' that you aren’t dreaming. A series of 10 reality checks is more likely to produce dream results in a dream, especially if you are expecting dream results. This technique is for those who are desperate!

''If you have had a good experience with this technique, please go to the talk page and post your experiences, as there have not been many anecdotes of it working yet.''
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Recovering from lost visuals==
There are a few things you can try to do if you lose your vision. Most of these are less likely to help prolong your dream than the above techniques.

You can also try these if you have just woken up and are lying in your bed. You may be able to return to your dream.

===Autosuggestion===
You can repeat over and over a phrase similar to “I can see my dream,” or otherwise enforce in your mind that you can see a dreamscape. (See [[w:Autosuggestion|Autosuggestion]])

===Visualising===
You can visualise the scene as it would be if you could see it. You could take this as an opportunity to change the dreamscape by visualising a different environment from the previous one in the dream. This can be made easier by spinning as you visualize. (See [[#Changing the dream environment|Changing the dream environment]] below)

==Altering the dream==
===Changing the dream environment===
You can change the dreamscape by simply visualizing a different environment. Stephen LaBerge, author of ''Exploring the World of Lucid Dreaming'', suggests closing your eyes, spinning around, and visualizing a new location. Alan Worsley, a famous lucid dreamer, describes another technique of summoning a television and remote to switched dreamscapes. By simply “changing the channel” on the remote, imagine your surroundings switching to your desired location, as though you were switching through various television programs. 

In both of these methods, details are key. The more details you provide for your next dreamscape, the easier it will be to get there. For example, if you wanted go to the Superbowl in your dreams, you might simply state:

:'''“I want to be at the Superbowl.”'''

But this statement could be improved by adding details:

:'''&quot;I want be in the endzone seats, drinking a Coke, and wearing my favorite player's jersey at the Super Bowl.&quot;'''

===Summoning objects into your dream===
At some point in your lucid dreaming experience, you'll probably want to handle various objects, or talk with certain people. Both of these needs can be fulfilled by using your mind, and the power of suggestion. There is no set way to &quot;make&quot; things in the dream world; in fact, many lucid dreamers devise their own methods through experimentation. However, here are some of the more common &quot;summoning&quot; techniques:

* Try reaching for objects that are not within your field of vision. For example, think to yourself: “When I reach into my pocket, there will be a green box of mints.” Then, attempt to actually take a green box of mints out of your pocket. Other variations of this include reaching behind you for an object, or reaching through a mirror in hopes of getting a hold of what you want.
* To summon a person, you might say to yourself: “When I turn around, [person's name] will be standing in front of me,” or “When I walk through this mirror, I will see [person's name],” or “In a few moments, [person's name] will walk through that door (or around that corner).”
* More experienced lucid dreamers can try making the object materialize right before their eyes. This will require a fair amount of concentration. Here is an example of this process:&lt;br /&gt;

: I am lucid dreaming in my backyard, and it's currently night. Now, I don't like the dark in my lucid dreams because I'm more likely to wake up, and I fear there are monsters lurking around every corner. So, I want to '''make the sun appear''' so that it'll be daytime. Focusing on the horizon, I visualize the sun rising above it.&lt;br /&gt;
:At first nothing happens, but I continue focusing and...yes! There's some light filtering over the horizon! And now the sun is rising to the sky and it settles there; so far, so good. But wait...the sky is still black. Peering at bit closer at the sun, I can just make out a faint ring of blue sky encircling it. Lifting my hand towards it I shout, &quot;Blue!&quot;. The blue ring quickly spreads across the sky, creating the full daytime effect.”&lt;br /&gt;

* Some dreamers may have success by closing their eyes and imagining the desired object in front of them once when they open their eyes . 
* Try using mechanical devices within the dream, such as a nearby lightswitch or button, to summon objects or people. (i.e. &quot;When I flip this switch/press this button, X will appear.&quot;)
*Convince yourself you have magical powers (or scientific). Then, use them to summon objects, shapeshift, etc. This can help you believe the creation of objects more easily. 
*(This one is dumb, but it works.) Begin singing ''Friend Like Me'', and summon stuff to the beat. They may disappear after you finish singing, or start dancing, but hey, it's pretty darn fun.

Remember, in the dream world, your expectations shape your surroundings. If you think a big, scary monster is going to step out of the shadows and attack you...well, a big, scary monster probably ''is'' going to step out of the shadows and attack you. So, don't be a victim; take control of your thoughts and use them to your advantage.
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==What you can do==
This final section should see you off with a few ideas of what to do in a dream.

It is advised to have a ''clear purpose'' for your lucid dreams whenever you go to sleep. In other words, every night you consider what you want to do when you have a lucid dream, and select one thing, or perhaps two or three if you are skilled. Avoid this:

: &quot;What am I gonna do what am I gonna do? I wanna fly, walk through walls, eat until my stomach explodes, spy on my neighbours, drive in a car real fast, woooeeey I'm gonna . . .&quot; &lt;!--- thanks to BuLLeT-PrOOf at the ld4all.com forums, this is a perfect example of what not to do! ---&gt;

You will either end up doing none of these things in your dream or getting overexcited and waking up.

Now that that’s clear, here’s a list of possible things you could do, ordered in difficulty. Remember that you might find some things unusually hard (or easy) compared to most lucid dreamers, this is perfectly normal! This is a very rough guide — if you’ve managed something in the Easy section, don't be scared to try for something from the Medium section.
===Easy===
* Fly
*: Most people enjoy flying around in dreams. There are different styles of flight that people use, each with a varied level of success for each individual. Methods such as “swimming through the air”, “Superman style” (one arm outstretched), “Neo style” (both arms at your side), and “Airplane style” (both arms out) ,&quot;eagle style&quot; (gliding through the air currents, using your fingered wings to navigate altitudes) are often used. There are a few methods of getting up into the air, such as simply jumping (you can jump really high in dreams if you believe it) or imagining a great force pushing you from your feet or walking up on air as though it is a staircase. Some people summon jetpacks and slip them on to fly. Be creative and dream up your own methods.
* Explore your dream world
*: Be warned, you are quite likely to forget you are dreaming when exploring! Doing reality checks often and muttering to yourself about how real everything seems can help to avoid this. You can also ask a dream character to tag along with you and remind you when you forget that you’re dreaming.
* Walk through a mirror or wall
*: You can pass through dream objects such as walls, glass, trees, and everything else. Confidence is really the key here. Some variations on going through stuff can be going in slowly, wiggling your finger in first, or running quickly into the object and telling yourself you would go through it. Some people particularly like to go through mirrors because of the unpredictable effects this action produces. However, if you tell yourself you will end up at a certain location before passing through a mirror, you can change the dream scene quickly. Be warned, some people experience nothing and wake up after passing through. You may want to hold your arm to keep yourself in the dream.
* Look at the sky
*: People often report amazing skies in lucid dreams. You can also shout colors at it and paint some sunrises.
* Show off to your friends (“Hey guys; I can go through this wall!”)
* Do plenty of sports (trampolining, skiing, swimming, dancing, etc.)
* Use various power such as Telekinesis and magic (a shortcut if you are having problems would be to summon a magic wand/staff or other device)
* Try to read a book that you have never read and remember the content
* Try to browse the Internet and visit sites that you've never visited
* Use things that you have never used
* Last but not least: Edit Wikipedia/Wikibooks articles (see question 124 of the [[w:Wikipedia:Are You a Wikipediholic Test|Wikipediholic Test]]) and see if the changes remain when you awake!

===Medium===
* Eat until you’re near bursting!
* Teleport
* Create some dream characters (possibly from a book or film)
* Try to find your spirit guide
* Experiments (in fact, researchers will often want people of various skills)
* Body swapping/possession (where you enter a different body)
* Morph
* Take some drugs (this is more realistic if you’ve done so in real life)
*: Many people have also experienced realistic effects when trying drugs in dreams that they have never taken in real life.
* Drive a vehicle (This is especially fun if you haven't ever driven in real life)
* Fight
*: Nobody can tell you what you should and should not do in your dreams; the choice remains up to you.
** Use weapons
**: It is usually more interesting to use melee weapons (knives, swords, brass knuckles) than projectile weapons. Machine guns and pistols often run out of ammo and summoning it can be difficult. Misfires and jamming is also common. ''(Your subconscious expectations will shape your dreamscape in all manner of ways, If you believe it is hard to accomplish, if you believe it will jam or misfire, it will. I have had no issues with weaponry such as firearms in my dreams what-so-ever, take this &quot;advice&quot; lightly.)'' However this can be overcome by using Directed Energy Weapons (Lasers, Plasma/pulse rifles), or weapons that can't jam (bows, simple firearms like muskets and so on).
* &quot;Beat up&quot; your enemies

===Hard===
* Have sex
*: The excitement, or closing your eyes, can cause you to wake up. An additional reason for waking up may be fixing your eyes on your partner, as holding a gaze for long is also known to cause waking up. Also your dream partner has a strange way of transforming in the midst of ecstasy. Finding a sex partner isn't very hard, it's keeping them that is difficult. That is why it is best to not panic when they are transforming and accept them for what your subconscious brings you. 
* More morphing like 360 degree vision, [[w:sonar|sonar vision]], etc.
* Create false memories, etc. False memories can be made by having a lucid dream, but scripting it so you will think it is real, e.g. you think what happened in your dream happened in real life. This is hard because you will have to forget it is a dream while staying lucid (knowing it is a dream).
* Compose music or poems (or request them from your subconscious)
* Build a fantasy dream world! (some people build a dream world naturally)
** [http://lucidcrossroads.co.uk Lucid Crossroads]
** [https://web.archive.org/web/20230530232446/http://www.astralpulse.com/astralpulseisland.html Astral Pulse Island]
** H.P. Lovecraft's [[w:Dreamlands|Dreamlands]]
* Have precognition (your subconscious can be very good at predicting the future with relationships and career)
* Experience death. This could be a very harsh experience, and depending on your religious or philosophical beliefs may summon you into a different world or nothingness.
* Ask the dream to show you your worst fears/deepest traumas/etc. (be prepared for some bad stuff to surface)
* Build/use impossible objects, such as [[w:Hypercube|hypercubes]], [[w:Klein bottle|Klein bottles]], etc.
* Rewind time
* Or, try something nobody's done before!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Conclusion==
With all the techniques in this book, you may feel overwhelmed and uncertain of what to do next. Don't worry — just choose a few techniques to “map your way to lucidity”, decide on a few things you will want to do from this page, and start!

If you are still unsure of what to do, don’t worry — you might happen to have a lucid dream tonight!

If you are beginning to feel a compulsive thirst for ''more'' information about dreams, head over to the [[Lucid Dreaming/Further Reading|Further Reading]] section for the sites to satisfy your cravings. Remember to come back occasionally and help make the wikibook grow!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;
{{LDTOC}}

[[es:Sueño lúcido/Uso]]
[[it:Sogno lucido/Uso]]</text>
      <sha1>g4j6zi3valtv2cq59kf3u0gdq9s88ss</sha1>
    </revision>
    <revision>
      <id>4678594</id>
      <parentid>4678569</parentid>
      <timestamp>2026-10-27T20:25:16Z</timestamp>
      <contributor>
        <username>User97104</username>
        <id>3562800</id>
      </contributor>
      <comment>/* Hard */</comment>
      <origin>4678594</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20041" sha1="1o9dlvd4jrjlhuwtjagiqux1ecbaarf" xml:space="preserve">{{LDTOC}}

==Introduction==
Conduction is the part of lucid dreaming that treats of stabilizing, controlling, and terminating lucid dreams. It is best to learn about induction first because conduction relies on being in a lucid dream. Remember to do what works best for you. Best of Luck!
==Dream stabilization==
Once you are able to dream lucidly, you may find that it is difficult to stay in the dream; for example, you may wake instantly or the dream may start “fading” which is characterized by loss or degradation of any of the senses, especially vision. Alternatively, a new lucid dreamer could easily forget that they are in a dream, as a result of the shock of the sensation.

Don't worry if you wake immediately after becoming lucid. As you gain more experience of becoming lucid, it will come as less of a shock and you’ll be less likely to wake up. Make sure you do a reality check to be sure you’re not still dreaming. As you gain more experience, you will have an easier time identifying when and remembering that you are dreaming.

You can avoid more gradual fadings by '''stimulating your senses'''. This means listening for sounds, feeling around with your hands, and paying attention to what you see and smell. The idea here is to load your senses with stimulation from the dream so that your senses cannot shift to the real world. If you close your eyes, you are removing a great deal of sensory information and might wake up. Staring at a single point can cause effectively the same problem if you stop seeing everything else in your peripheral vision, or don't see enough movement. If you hear something loud in real life and are hearing nothing in the dream, your senses may shift to the real world, causing you to wake up.

Ideally you should be able to use the techniques below to stabilize your dream ''before'' it starts to fade (or “black out”). As always, prevention is better than treatment - and the more stable and vivid your dreams are, the more enjoyable they will be.  However, if that doesn't work you may be able to use stabilization techniques to stop the fading; the spinning technique is probably the most effective in this case.

If you still can’t stabilize your dream, you may decide to try and wake up with the aim of remembering your dream as accurately as possible while its still fresh in your mind.

===Hand Touching===
Rub your hands together and concentrate on the rubbing. You should feel the friction and the heat of your hands. If you can concentrate on the feelings that this action generates, your dream is likely to stabilize and become more vivid and detailed. You can also keep one hand on your arm while exploring the dream for a constant sense of stimulation.  This technique is most effective when used in conjunction with the “Slowing it down” technique, by staring at your hands while rubbing them together.

===Spinning===
You spin around in your dream much as you would if you suddenly want to feel dizzy in real life. The sensation of movement is the key here to stabilizing the dream. Many people report success with this technique, but it also tends to cause a complete change of your dream scene (see [[#Changing the dream environment|Changing the dream environment]] below). If the dream scene disappears  completely (e.g., becomes black), it is necessary to visualize the dreamscape to return to the dream.

===Slowing it down===
Some people like to stabilize the dream by “stopping to smell the roses” and slowly staring at a dream object until it becomes clear. The dreamer would then look around elsewhere, noticing how detailed everything is, thereby stimulating the visual portion of the dream. ''However, others find this can cause their lucid dream to end.'' If you focus on one object for too long to the exclusion of everything else, you will likely wake up or lose the dream. It works best to pay attention to everything in your vision, including your peripheral vision, not just the center of the object you're staring at. If staring at a single object doesn't work for you, try to let your eyes wander around instead.

===Touching your dream===
If you feel that your dream is too abstract and fear that it might be fading, you can prevent this by grabbing hold of a solid object in your dream and focus on how real the sensation is. A good tip is to find something you know is stuck, for instance a table nailed to the ground, and pull it with all your muscular power (no ''supernatural'' powers!), and you should feel how solid it is. The idea is that you convince yourself that the dream is solid and real — through tactile stimulation — and nothing abstract.

===Regaining waking memory or skills===
This is also likely to enhance your degree of lucidity. Try to remember facts from your waking life, such as your phone number, address, etc., or do some simple math. Or, start reciting the lyrics to your favorite song. Or perhaps try some sports practice you know well — this all depends on which senses / methods of thought process you tend to rely on most in your waking life.

=== Dream Guide ===
Summon a DC (Dream character) that you expect to Guide you through the dream. Summoning is easier if you always expect this Guide to be there in a dream. The Guide is useful for escaping scary or unpredicted environments (&quot;whooshing&quot; you away, killing or unsummoning the threat, reminding you that you are in control.). Imagine this Guide as powerful, knowledgeable, and protective over you. Guides can also walk you through summoning, flying, shapeshifting, etc. and be useful for learning and controlling your dreams.

=== False awakening ===
A couple of the users on the ld4all.com forums have had success with creating a false awakening to stabilize a dream. If the above techniques are failing and you find your dream still fading, ''and you really want to continue your lucid dream'', do the following:

# Expect to have a false awakening.
# When you think you wake up, perform a reality check.

You will either have a false awakening, reality check, and then end up with an even more vivid lucid dream, or will really wake up, perform a reality check, and realize that you just woke up (bad luck!).

The most important part of this is the reality check. This is what will continue your lucid dream. You should be performing reality checks when you wake up. If you plan to induce false awakenings in order to stabilize a dream, the reality check that you perform as you wake up is as important as the one that got you lucid, if not more.

Perform every check in the book until you are '''positively, absolutely, and completely sure''' that you aren’t dreaming. A series of 10 reality checks is more likely to produce dream results in a dream, especially if you are expecting dream results. This technique is for those who are desperate!

''If you have had a good experience with this technique, please go to the talk page and post your experiences, as there have not been many anecdotes of it working yet.''
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Recovering from lost visuals==
There are a few things you can try to do if you lose your vision. Most of these are less likely to help prolong your dream than the above techniques.

You can also try these if you have just woken up and are lying in your bed. You may be able to return to your dream.

===Autosuggestion===
You can repeat over and over a phrase similar to “I can see my dream,” or otherwise enforce in your mind that you can see a dreamscape. (See [[w:Autosuggestion|Autosuggestion]])

===Visualising===
You can visualise the scene as it would be if you could see it. You could take this as an opportunity to change the dreamscape by visualising a different environment from the previous one in the dream. This can be made easier by spinning as you visualize. (See [[#Changing the dream environment|Changing the dream environment]] below)

==Altering the dream==
===Changing the dream environment===
You can change the dreamscape by simply visualizing a different environment. Stephen LaBerge, author of ''Exploring the World of Lucid Dreaming'', suggests closing your eyes, spinning around, and visualizing a new location. Alan Worsley, a famous lucid dreamer, describes another technique of summoning a television and remote to switched dreamscapes. By simply “changing the channel” on the remote, imagine your surroundings switching to your desired location, as though you were switching through various television programs. 

In both of these methods, details are key. The more details you provide for your next dreamscape, the easier it will be to get there. For example, if you wanted go to the Superbowl in your dreams, you might simply state:

:'''“I want to be at the Superbowl.”'''

But this statement could be improved by adding details:

:'''&quot;I want be in the endzone seats, drinking a Coke, and wearing my favorite player's jersey at the Super Bowl.&quot;'''

===Summoning objects into your dream===
At some point in your lucid dreaming experience, you'll probably want to handle various objects, or talk with certain people. Both of these needs can be fulfilled by using your mind, and the power of suggestion. There is no set way to &quot;make&quot; things in the dream world; in fact, many lucid dreamers devise their own methods through experimentation. However, here are some of the more common &quot;summoning&quot; techniques:

* Try reaching for objects that are not within your field of vision. For example, think to yourself: “When I reach into my pocket, there will be a green box of mints.” Then, attempt to actually take a green box of mints out of your pocket. Other variations of this include reaching behind you for an object, or reaching through a mirror in hopes of getting a hold of what you want.
* To summon a person, you might say to yourself: “When I turn around, [person's name] will be standing in front of me,” or “When I walk through this mirror, I will see [person's name],” or “In a few moments, [person's name] will walk through that door (or around that corner).”
* More experienced lucid dreamers can try making the object materialize right before their eyes. This will require a fair amount of concentration. Here is an example of this process:&lt;br /&gt;

: I am lucid dreaming in my backyard, and it's currently night. Now, I don't like the dark in my lucid dreams because I'm more likely to wake up, and I fear there are monsters lurking around every corner. So, I want to '''make the sun appear''' so that it'll be daytime. Focusing on the horizon, I visualize the sun rising above it.&lt;br /&gt;
:At first nothing happens, but I continue focusing and...yes! There's some light filtering over the horizon! And now the sun is rising to the sky and it settles there; so far, so good. But wait...the sky is still black. Peering at bit closer at the sun, I can just make out a faint ring of blue sky encircling it. Lifting my hand towards it I shout, &quot;Blue!&quot;. The blue ring quickly spreads across the sky, creating the full daytime effect.”&lt;br /&gt;

* Some dreamers may have success by closing their eyes and imagining the desired object in front of them once when they open their eyes . 
* Try using mechanical devices within the dream, such as a nearby lightswitch or button, to summon objects or people. (i.e. &quot;When I flip this switch/press this button, X will appear.&quot;)
*Convince yourself you have magical powers (or scientific). Then, use them to summon objects, shapeshift, etc. This can help you believe the creation of objects more easily. 
*(This one is dumb, but it works.) Begin singing ''Friend Like Me'', and summon stuff to the beat. They may disappear after you finish singing, or start dancing, but hey, it's pretty darn fun.

Remember, in the dream world, your expectations shape your surroundings. If you think a big, scary monster is going to step out of the shadows and attack you...well, a big, scary monster probably ''is'' going to step out of the shadows and attack you. So, don't be a victim; take control of your thoughts and use them to your advantage.
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==What you can do==
This final section should see you off with a few ideas of what to do in a dream.

It is advised to have a ''clear purpose'' for your lucid dreams whenever you go to sleep. In other words, every night you consider what you want to do when you have a lucid dream, and select one thing, or perhaps two or three if you are skilled. Avoid this:

: &quot;What am I gonna do what am I gonna do? I wanna fly, walk through walls, eat until my stomach explodes, spy on my neighbours, drive in a car real fast, woooeeey I'm gonna . . .&quot; &lt;!--- thanks to BuLLeT-PrOOf at the ld4all.com forums, this is a perfect example of what not to do! ---&gt;

You will either end up doing none of these things in your dream or getting overexcited and waking up.

Now that that’s clear, here’s a list of possible things you could do, ordered in difficulty. Remember that you might find some things unusually hard (or easy) compared to most lucid dreamers, this is perfectly normal! This is a very rough guide — if you’ve managed something in the Easy section, don't be scared to try for something from the Medium section.
===Easy===
* Fly
*: Most people enjoy flying around in dreams. There are different styles of flight that people use, each with a varied level of success for each individual. Methods such as “swimming through the air”, “Superman style” (one arm outstretched), “Neo style” (both arms at your side), and “Airplane style” (both arms out) ,&quot;eagle style&quot; (gliding through the air currents, using your fingered wings to navigate altitudes) are often used. There are a few methods of getting up into the air, such as simply jumping (you can jump really high in dreams if you believe it) or imagining a great force pushing you from your feet or walking up on air as though it is a staircase. Some people summon jetpacks and slip them on to fly. Be creative and dream up your own methods.
* Explore your dream world
*: Be warned, you are quite likely to forget you are dreaming when exploring! Doing reality checks often and muttering to yourself about how real everything seems can help to avoid this. You can also ask a dream character to tag along with you and remind you when you forget that you’re dreaming.
* Walk through a mirror or wall
*: You can pass through dream objects such as walls, glass, trees, and everything else. Confidence is really the key here. Some variations on going through stuff can be going in slowly, wiggling your finger in first, or running quickly into the object and telling yourself you would go through it. Some people particularly like to go through mirrors because of the unpredictable effects this action produces. However, if you tell yourself you will end up at a certain location before passing through a mirror, you can change the dream scene quickly. Be warned, some people experience nothing and wake up after passing through. You may want to hold your arm to keep yourself in the dream.
* Look at the sky
*: People often report amazing skies in lucid dreams. You can also shout colors at it and paint some sunrises.
* Show off to your friends (“Hey guys; I can go through this wall!”)
* Do plenty of sports (trampolining, skiing, swimming, dancing, etc.)
* Use various power such as Telekinesis and magic (a shortcut if you are having problems would be to summon a magic wand/staff or other device)
* Try to read a book that you have never read and remember the content
* Try to browse the Internet and visit sites that you've never visited
* Use things that you have never used
* Last but not least: Edit Wikipedia/Wikibooks articles (see question 124 of the [[w:Wikipedia:Are You a Wikipediholic Test|Wikipediholic Test]]) and see if the changes remain when you awake!

===Medium===
* Eat until you’re near bursting!
* Teleport
* Create some dream characters (possibly from a book or film)
* Try to find your spirit guide
* Experiments (in fact, researchers will often want people of various skills)
* Body swapping/possession (where you enter a different body)
* Morph
* Take some drugs (this is more realistic if you’ve done so in real life)
*: Many people have also experienced realistic effects when trying drugs in dreams that they have never taken in real life.
* Drive a vehicle (This is especially fun if you haven't ever driven in real life)
* Fight
*: Nobody can tell you what you should and should not do in your dreams; the choice remains up to you.
** Use weapons
**: It is usually more interesting to use melee weapons (knives, swords, brass knuckles) than projectile weapons. Machine guns and pistols often run out of ammo and summoning it can be difficult. Misfires and jamming is also common. ''(Your subconscious expectations will shape your dreamscape in all manner of ways, If you believe it is hard to accomplish, if you believe it will jam or misfire, it will. I have had no issues with weaponry such as firearms in my dreams what-so-ever, take this &quot;advice&quot; lightly.)'' However this can be overcome by using Directed Energy Weapons (Lasers, Plasma/pulse rifles), or weapons that can't jam (bows, simple firearms like muskets and so on).
* &quot;Beat up&quot; your enemies

===Hard===
* Have sex
*: The excitement, or closing your eyes, can cause you to wake up. An additional reason for waking up may be fixing your eyes on your partner, as holding a gaze for long is also known to cause waking up. Also your dream partner has a strange way of transforming in the midst of ecstasy. Finding a sex partner isn't very hard, it's keeping them that is difficult. That is why it is best to not panic when they are transforming and accept them for what your subconscious brings you. 
* More morphing like 360 degree vision, [[w:sonar|sonar vision]], etc.
* Create false memories, etc. False memories can be made by having a lucid dream, but scripting it so you will think it is real, e.g. you think what happened in your dream happened in real life. This is hard because you will have to forget it is a dream while staying lucid (knowing it is a dream).
* Compose music or poems (or request them from your subconscious)
* Build a fantasy dream world! (some people build a dream world naturally)
** [http://lucidcrossroads.co.uk Lucid Crossroads]
** [https://web.archive.org/web/20230530232446/http://www.astralpulse.com/astralpulseisland.html Astral Pulse Island]
** H.P. Lovecraft's [[w:Dreamlands|Dreamlands]]
* Have precognition (your subconscious can be very good at predicting the future with relationships and career)
* Experience death. This could be a very harsh experience, and depending on your religious or philosophical beliefs may summon you into a different world or nothingness.
* Ask the dream to show you your worst fears/deepest traumas/etc. (be prepared for some bad stuff to surface)
* Build/use impossible objects, such as [[w:Hypercube|hypercubes]], [[w:Klein bottle|Klein bottles]], etc.
* Rewind time
* Have a lucid dream ''inside'' a lucid dream
* Or, try something nobody's done before!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Conclusion==
With all the techniques in this book, you may feel overwhelmed and uncertain of what to do next. Don't worry — just choose a few techniques to “map your way to lucidity”, decide on a few things you will want to do from this page, and start!

If you are still unsure of what to do, don’t worry — you might happen to have a lucid dream tonight!

If you are beginning to feel a compulsive thirst for ''more'' information about dreams, head over to the [[Lucid Dreaming/Further Reading|Further Reading]] section for the sites to satisfy your cravings. Remember to come back occasionally and help make the wikibook grow!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;
{{LDTOC}}

[[es:Sueño lúcido/Uso]]
[[it:Sogno lucido/Uso]]</text>
      <sha1>1o9dlvd4jrjlhuwtjagiqux1ecbaarf</sha1>
    </revision>
    <revision>
      <id>4678601</id>
      <parentid>4678594</parentid>
      <timestamp>2026-10-27T20:33:53Z</timestamp>
      <contributor>
        <username>User97104</username>
        <id>3562800</id>
      </contributor>
      <comment>/* Hard */ y</comment>
      <origin>4678601</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20142" sha1="dkje14zvm187avejvtcn7641z1d3iqg" xml:space="preserve">{{LDTOC}}

==Introduction==
Conduction is the part of lucid dreaming that treats of stabilizing, controlling, and terminating lucid dreams. It is best to learn about induction first because conduction relies on being in a lucid dream. Remember to do what works best for you. Best of Luck!
==Dream stabilization==
Once you are able to dream lucidly, you may find that it is difficult to stay in the dream; for example, you may wake instantly or the dream may start “fading” which is characterized by loss or degradation of any of the senses, especially vision. Alternatively, a new lucid dreamer could easily forget that they are in a dream, as a result of the shock of the sensation.

Don't worry if you wake immediately after becoming lucid. As you gain more experience of becoming lucid, it will come as less of a shock and you’ll be less likely to wake up. Make sure you do a reality check to be sure you’re not still dreaming. As you gain more experience, you will have an easier time identifying when and remembering that you are dreaming.

You can avoid more gradual fadings by '''stimulating your senses'''. This means listening for sounds, feeling around with your hands, and paying attention to what you see and smell. The idea here is to load your senses with stimulation from the dream so that your senses cannot shift to the real world. If you close your eyes, you are removing a great deal of sensory information and might wake up. Staring at a single point can cause effectively the same problem if you stop seeing everything else in your peripheral vision, or don't see enough movement. If you hear something loud in real life and are hearing nothing in the dream, your senses may shift to the real world, causing you to wake up.

Ideally you should be able to use the techniques below to stabilize your dream ''before'' it starts to fade (or “black out”). As always, prevention is better than treatment - and the more stable and vivid your dreams are, the more enjoyable they will be.  However, if that doesn't work you may be able to use stabilization techniques to stop the fading; the spinning technique is probably the most effective in this case.

If you still can’t stabilize your dream, you may decide to try and wake up with the aim of remembering your dream as accurately as possible while its still fresh in your mind.

===Hand Touching===
Rub your hands together and concentrate on the rubbing. You should feel the friction and the heat of your hands. If you can concentrate on the feelings that this action generates, your dream is likely to stabilize and become more vivid and detailed. You can also keep one hand on your arm while exploring the dream for a constant sense of stimulation.  This technique is most effective when used in conjunction with the “Slowing it down” technique, by staring at your hands while rubbing them together.

===Spinning===
You spin around in your dream much as you would if you suddenly want to feel dizzy in real life. The sensation of movement is the key here to stabilizing the dream. Many people report success with this technique, but it also tends to cause a complete change of your dream scene (see [[#Changing the dream environment|Changing the dream environment]] below). If the dream scene disappears  completely (e.g., becomes black), it is necessary to visualize the dreamscape to return to the dream.

===Slowing it down===
Some people like to stabilize the dream by “stopping to smell the roses” and slowly staring at a dream object until it becomes clear. The dreamer would then look around elsewhere, noticing how detailed everything is, thereby stimulating the visual portion of the dream. ''However, others find this can cause their lucid dream to end.'' If you focus on one object for too long to the exclusion of everything else, you will likely wake up or lose the dream. It works best to pay attention to everything in your vision, including your peripheral vision, not just the center of the object you're staring at. If staring at a single object doesn't work for you, try to let your eyes wander around instead.

===Touching your dream===
If you feel that your dream is too abstract and fear that it might be fading, you can prevent this by grabbing hold of a solid object in your dream and focus on how real the sensation is. A good tip is to find something you know is stuck, for instance a table nailed to the ground, and pull it with all your muscular power (no ''supernatural'' powers!), and you should feel how solid it is. The idea is that you convince yourself that the dream is solid and real — through tactile stimulation — and nothing abstract.

===Regaining waking memory or skills===
This is also likely to enhance your degree of lucidity. Try to remember facts from your waking life, such as your phone number, address, etc., or do some simple math. Or, start reciting the lyrics to your favorite song. Or perhaps try some sports practice you know well — this all depends on which senses / methods of thought process you tend to rely on most in your waking life.

=== Dream Guide ===
Summon a DC (Dream character) that you expect to Guide you through the dream. Summoning is easier if you always expect this Guide to be there in a dream. The Guide is useful for escaping scary or unpredicted environments (&quot;whooshing&quot; you away, killing or unsummoning the threat, reminding you that you are in control.). Imagine this Guide as powerful, knowledgeable, and protective over you. Guides can also walk you through summoning, flying, shapeshifting, etc. and be useful for learning and controlling your dreams.

=== False awakening ===
A couple of the users on the ld4all.com forums have had success with creating a false awakening to stabilize a dream. If the above techniques are failing and you find your dream still fading, ''and you really want to continue your lucid dream'', do the following:

# Expect to have a false awakening.
# When you think you wake up, perform a reality check.

You will either have a false awakening, reality check, and then end up with an even more vivid lucid dream, or will really wake up, perform a reality check, and realize that you just woke up (bad luck!).

The most important part of this is the reality check. This is what will continue your lucid dream. You should be performing reality checks when you wake up. If you plan to induce false awakenings in order to stabilize a dream, the reality check that you perform as you wake up is as important as the one that got you lucid, if not more.

Perform every check in the book until you are '''positively, absolutely, and completely sure''' that you aren’t dreaming. A series of 10 reality checks is more likely to produce dream results in a dream, especially if you are expecting dream results. This technique is for those who are desperate!

''If you have had a good experience with this technique, please go to the talk page and post your experiences, as there have not been many anecdotes of it working yet.''
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Recovering from lost visuals==
There are a few things you can try to do if you lose your vision. Most of these are less likely to help prolong your dream than the above techniques.

You can also try these if you have just woken up and are lying in your bed. You may be able to return to your dream.

===Autosuggestion===
You can repeat over and over a phrase similar to “I can see my dream,” or otherwise enforce in your mind that you can see a dreamscape. (See [[w:Autosuggestion|Autosuggestion]])

===Visualising===
You can visualise the scene as it would be if you could see it. You could take this as an opportunity to change the dreamscape by visualising a different environment from the previous one in the dream. This can be made easier by spinning as you visualize. (See [[#Changing the dream environment|Changing the dream environment]] below)

==Altering the dream==
===Changing the dream environment===
You can change the dreamscape by simply visualizing a different environment. Stephen LaBerge, author of ''Exploring the World of Lucid Dreaming'', suggests closing your eyes, spinning around, and visualizing a new location. Alan Worsley, a famous lucid dreamer, describes another technique of summoning a television and remote to switched dreamscapes. By simply “changing the channel” on the remote, imagine your surroundings switching to your desired location, as though you were switching through various television programs. 

In both of these methods, details are key. The more details you provide for your next dreamscape, the easier it will be to get there. For example, if you wanted go to the Superbowl in your dreams, you might simply state:

:'''“I want to be at the Superbowl.”'''

But this statement could be improved by adding details:

:'''&quot;I want be in the endzone seats, drinking a Coke, and wearing my favorite player's jersey at the Super Bowl.&quot;'''

===Summoning objects into your dream===
At some point in your lucid dreaming experience, you'll probably want to handle various objects, or talk with certain people. Both of these needs can be fulfilled by using your mind, and the power of suggestion. There is no set way to &quot;make&quot; things in the dream world; in fact, many lucid dreamers devise their own methods through experimentation. However, here are some of the more common &quot;summoning&quot; techniques:

* Try reaching for objects that are not within your field of vision. For example, think to yourself: “When I reach into my pocket, there will be a green box of mints.” Then, attempt to actually take a green box of mints out of your pocket. Other variations of this include reaching behind you for an object, or reaching through a mirror in hopes of getting a hold of what you want.
* To summon a person, you might say to yourself: “When I turn around, [person's name] will be standing in front of me,” or “When I walk through this mirror, I will see [person's name],” or “In a few moments, [person's name] will walk through that door (or around that corner).”
* More experienced lucid dreamers can try making the object materialize right before their eyes. This will require a fair amount of concentration. Here is an example of this process:&lt;br /&gt;

: I am lucid dreaming in my backyard, and it's currently night. Now, I don't like the dark in my lucid dreams because I'm more likely to wake up, and I fear there are monsters lurking around every corner. So, I want to '''make the sun appear''' so that it'll be daytime. Focusing on the horizon, I visualize the sun rising above it.&lt;br /&gt;
:At first nothing happens, but I continue focusing and...yes! There's some light filtering over the horizon! And now the sun is rising to the sky and it settles there; so far, so good. But wait...the sky is still black. Peering at bit closer at the sun, I can just make out a faint ring of blue sky encircling it. Lifting my hand towards it I shout, &quot;Blue!&quot;. The blue ring quickly spreads across the sky, creating the full daytime effect.”&lt;br /&gt;

* Some dreamers may have success by closing their eyes and imagining the desired object in front of them once when they open their eyes . 
* Try using mechanical devices within the dream, such as a nearby lightswitch or button, to summon objects or people. (i.e. &quot;When I flip this switch/press this button, X will appear.&quot;)
*Convince yourself you have magical powers (or scientific). Then, use them to summon objects, shapeshift, etc. This can help you believe the creation of objects more easily. 
*(This one is dumb, but it works.) Begin singing ''Friend Like Me'', and summon stuff to the beat. They may disappear after you finish singing, or start dancing, but hey, it's pretty darn fun.

Remember, in the dream world, your expectations shape your surroundings. If you think a big, scary monster is going to step out of the shadows and attack you...well, a big, scary monster probably ''is'' going to step out of the shadows and attack you. So, don't be a victim; take control of your thoughts and use them to your advantage.
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==What you can do==
This final section should see you off with a few ideas of what to do in a dream.

It is advised to have a ''clear purpose'' for your lucid dreams whenever you go to sleep. In other words, every night you consider what you want to do when you have a lucid dream, and select one thing, or perhaps two or three if you are skilled. Avoid this:

: &quot;What am I gonna do what am I gonna do? I wanna fly, walk through walls, eat until my stomach explodes, spy on my neighbours, drive in a car real fast, woooeeey I'm gonna . . .&quot; &lt;!--- thanks to BuLLeT-PrOOf at the ld4all.com forums, this is a perfect example of what not to do! ---&gt;

You will either end up doing none of these things in your dream or getting overexcited and waking up.

Now that that’s clear, here’s a list of possible things you could do, ordered in difficulty. Remember that you might find some things unusually hard (or easy) compared to most lucid dreamers, this is perfectly normal! This is a very rough guide — if you’ve managed something in the Easy section, don't be scared to try for something from the Medium section.
===Easy===
* Fly
*: Most people enjoy flying around in dreams. There are different styles of flight that people use, each with a varied level of success for each individual. Methods such as “swimming through the air”, “Superman style” (one arm outstretched), “Neo style” (both arms at your side), and “Airplane style” (both arms out) ,&quot;eagle style&quot; (gliding through the air currents, using your fingered wings to navigate altitudes) are often used. There are a few methods of getting up into the air, such as simply jumping (you can jump really high in dreams if you believe it) or imagining a great force pushing you from your feet or walking up on air as though it is a staircase. Some people summon jetpacks and slip them on to fly. Be creative and dream up your own methods.
* Explore your dream world
*: Be warned, you are quite likely to forget you are dreaming when exploring! Doing reality checks often and muttering to yourself about how real everything seems can help to avoid this. You can also ask a dream character to tag along with you and remind you when you forget that you’re dreaming.
* Walk through a mirror or wall
*: You can pass through dream objects such as walls, glass, trees, and everything else. Confidence is really the key here. Some variations on going through stuff can be going in slowly, wiggling your finger in first, or running quickly into the object and telling yourself you would go through it. Some people particularly like to go through mirrors because of the unpredictable effects this action produces. However, if you tell yourself you will end up at a certain location before passing through a mirror, you can change the dream scene quickly. Be warned, some people experience nothing and wake up after passing through. You may want to hold your arm to keep yourself in the dream.
* Look at the sky
*: People often report amazing skies in lucid dreams. You can also shout colors at it and paint some sunrises.
* Show off to your friends (“Hey guys; I can go through this wall!”)
* Do plenty of sports (trampolining, skiing, swimming, dancing, etc.)
* Use various power such as Telekinesis and magic (a shortcut if you are having problems would be to summon a magic wand/staff or other device)
* Try to read a book that you have never read and remember the content
* Try to browse the Internet and visit sites that you've never visited
* Use things that you have never used
* Last but not least: Edit Wikipedia/Wikibooks articles (see question 124 of the [[w:Wikipedia:Are You a Wikipediholic Test|Wikipediholic Test]]) and see if the changes remain when you awake!

===Medium===
* Eat until you’re near bursting!
* Teleport
* Create some dream characters (possibly from a book or film)
* Try to find your spirit guide
* Experiments (in fact, researchers will often want people of various skills)
* Body swapping/possession (where you enter a different body)
* Morph
* Take some drugs (this is more realistic if you’ve done so in real life)
*: Many people have also experienced realistic effects when trying drugs in dreams that they have never taken in real life.
* Drive a vehicle (This is especially fun if you haven't ever driven in real life)
* Fight
*: Nobody can tell you what you should and should not do in your dreams; the choice remains up to you.
** Use weapons
**: It is usually more interesting to use melee weapons (knives, swords, brass knuckles) than projectile weapons. Machine guns and pistols often run out of ammo and summoning it can be difficult. Misfires and jamming is also common. ''(Your subconscious expectations will shape your dreamscape in all manner of ways, If you believe it is hard to accomplish, if you believe it will jam or misfire, it will. I have had no issues with weaponry such as firearms in my dreams what-so-ever, take this &quot;advice&quot; lightly.)'' However this can be overcome by using Directed Energy Weapons (Lasers, Plasma/pulse rifles), or weapons that can't jam (bows, simple firearms like muskets and so on).
* &quot;Beat up&quot; your enemies

===Hard===
* Have sex
*: The excitement, or closing your eyes, can cause you to wake up. An additional reason for waking up may be fixing your eyes on your partner, as holding a gaze for long is also known to cause waking up. Also your dream partner has a strange way of transforming in the midst of ecstasy. Finding a sex partner isn't very hard, it's keeping them that is difficult. That is why it is best to not panic when they are transforming and accept them for what your subconscious brings you. 
* More morphing like 360 degree vision, [[w:sonar|sonar vision]], etc.
* Create false memories, etc. False memories can be made by having a lucid dream, but scripting it so you will think it is real, e.g. you think what happened in your dream happened in real life. This is hard because you will have to forget it is a dream while staying lucid (knowing it is a dream).
* Compose music or poems (or request them from your subconscious)
* Build a fantasy dream world! (some people build a dream world naturally)
** [http://lucidcrossroads.co.uk Lucid Crossroads]
** [https://web.archive.org/web/20230530232446/http://www.astralpulse.com/astralpulseisland.html Astral Pulse Island]
** H.P. Lovecraft's [[w:Dreamlands|Dreamlands]]
* Have precognition (your subconscious can be very good at predicting the future with relationships and career)
* Experience death. This could be a very harsh experience, and depending on your religious or philosophical beliefs may summon you into a different world or nothingness.
* Ask the dream to show you your worst fears/deepest traumas/etc. (be prepared for some bad stuff to surface)
* Build/use impossible objects, such as [[w:Hypercube|hypercubes]], [[w:Klein bottle|Klein bottles]], etc.
* Rewind time
* Have a lucid dream ''inside'' a lucid dream
* Have a lucid dream ''inside'' a lucid dream ''inside'' a lucid dream... as many times as you want 
* Or, try something nobody's done before!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Conclusion==
With all the techniques in this book, you may feel overwhelmed and uncertain of what to do next. Don't worry — just choose a few techniques to “map your way to lucidity”, decide on a few things you will want to do from this page, and start!

If you are still unsure of what to do, don’t worry — you might happen to have a lucid dream tonight!

If you are beginning to feel a compulsive thirst for ''more'' information about dreams, head over to the [[Lucid Dreaming/Further Reading|Further Reading]] section for the sites to satisfy your cravings. Remember to come back occasionally and help make the wikibook grow!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;
{{LDTOC}}

[[es:Sueño lúcido/Uso]]
[[it:Sogno lucido/Uso]]</text>
      <sha1>dkje14zvm187avejvtcn7641z1d3iqg</sha1>
    </revision>
    <revision>
      <id>4678605</id>
      <parentid>4678601</parentid>
      <timestamp>2026-10-27T20:37:20Z</timestamp>
      <contributor>
        <username>User97104</username>
        <id>3562800</id>
      </contributor>
      <comment>/* Hard */</comment>
      <origin>4678605</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20198" sha1="pbw74lfmtyrz96de34ndqzr3qw4s5p1" xml:space="preserve">{{LDTOC}}

==Introduction==
Conduction is the part of lucid dreaming that treats of stabilizing, controlling, and terminating lucid dreams. It is best to learn about induction first because conduction relies on being in a lucid dream. Remember to do what works best for you. Best of Luck!
==Dream stabilization==
Once you are able to dream lucidly, you may find that it is difficult to stay in the dream; for example, you may wake instantly or the dream may start “fading” which is characterized by loss or degradation of any of the senses, especially vision. Alternatively, a new lucid dreamer could easily forget that they are in a dream, as a result of the shock of the sensation.

Don't worry if you wake immediately after becoming lucid. As you gain more experience of becoming lucid, it will come as less of a shock and you’ll be less likely to wake up. Make sure you do a reality check to be sure you’re not still dreaming. As you gain more experience, you will have an easier time identifying when and remembering that you are dreaming.

You can avoid more gradual fadings by '''stimulating your senses'''. This means listening for sounds, feeling around with your hands, and paying attention to what you see and smell. The idea here is to load your senses with stimulation from the dream so that your senses cannot shift to the real world. If you close your eyes, you are removing a great deal of sensory information and might wake up. Staring at a single point can cause effectively the same problem if you stop seeing everything else in your peripheral vision, or don't see enough movement. If you hear something loud in real life and are hearing nothing in the dream, your senses may shift to the real world, causing you to wake up.

Ideally you should be able to use the techniques below to stabilize your dream ''before'' it starts to fade (or “black out”). As always, prevention is better than treatment - and the more stable and vivid your dreams are, the more enjoyable they will be.  However, if that doesn't work you may be able to use stabilization techniques to stop the fading; the spinning technique is probably the most effective in this case.

If you still can’t stabilize your dream, you may decide to try and wake up with the aim of remembering your dream as accurately as possible while its still fresh in your mind.

===Hand Touching===
Rub your hands together and concentrate on the rubbing. You should feel the friction and the heat of your hands. If you can concentrate on the feelings that this action generates, your dream is likely to stabilize and become more vivid and detailed. You can also keep one hand on your arm while exploring the dream for a constant sense of stimulation.  This technique is most effective when used in conjunction with the “Slowing it down” technique, by staring at your hands while rubbing them together.

===Spinning===
You spin around in your dream much as you would if you suddenly want to feel dizzy in real life. The sensation of movement is the key here to stabilizing the dream. Many people report success with this technique, but it also tends to cause a complete change of your dream scene (see [[#Changing the dream environment|Changing the dream environment]] below). If the dream scene disappears  completely (e.g., becomes black), it is necessary to visualize the dreamscape to return to the dream.

===Slowing it down===
Some people like to stabilize the dream by “stopping to smell the roses” and slowly staring at a dream object until it becomes clear. The dreamer would then look around elsewhere, noticing how detailed everything is, thereby stimulating the visual portion of the dream. ''However, others find this can cause their lucid dream to end.'' If you focus on one object for too long to the exclusion of everything else, you will likely wake up or lose the dream. It works best to pay attention to everything in your vision, including your peripheral vision, not just the center of the object you're staring at. If staring at a single object doesn't work for you, try to let your eyes wander around instead.

===Touching your dream===
If you feel that your dream is too abstract and fear that it might be fading, you can prevent this by grabbing hold of a solid object in your dream and focus on how real the sensation is. A good tip is to find something you know is stuck, for instance a table nailed to the ground, and pull it with all your muscular power (no ''supernatural'' powers!), and you should feel how solid it is. The idea is that you convince yourself that the dream is solid and real — through tactile stimulation — and nothing abstract.

===Regaining waking memory or skills===
This is also likely to enhance your degree of lucidity. Try to remember facts from your waking life, such as your phone number, address, etc., or do some simple math. Or, start reciting the lyrics to your favorite song. Or perhaps try some sports practice you know well — this all depends on which senses / methods of thought process you tend to rely on most in your waking life.

=== Dream Guide ===
Summon a DC (Dream character) that you expect to Guide you through the dream. Summoning is easier if you always expect this Guide to be there in a dream. The Guide is useful for escaping scary or unpredicted environments (&quot;whooshing&quot; you away, killing or unsummoning the threat, reminding you that you are in control.). Imagine this Guide as powerful, knowledgeable, and protective over you. Guides can also walk you through summoning, flying, shapeshifting, etc. and be useful for learning and controlling your dreams.

=== False awakening ===
A couple of the users on the ld4all.com forums have had success with creating a false awakening to stabilize a dream. If the above techniques are failing and you find your dream still fading, ''and you really want to continue your lucid dream'', do the following:

# Expect to have a false awakening.
# When you think you wake up, perform a reality check.

You will either have a false awakening, reality check, and then end up with an even more vivid lucid dream, or will really wake up, perform a reality check, and realize that you just woke up (bad luck!).

The most important part of this is the reality check. This is what will continue your lucid dream. You should be performing reality checks when you wake up. If you plan to induce false awakenings in order to stabilize a dream, the reality check that you perform as you wake up is as important as the one that got you lucid, if not more.

Perform every check in the book until you are '''positively, absolutely, and completely sure''' that you aren’t dreaming. A series of 10 reality checks is more likely to produce dream results in a dream, especially if you are expecting dream results. This technique is for those who are desperate!

''If you have had a good experience with this technique, please go to the talk page and post your experiences, as there have not been many anecdotes of it working yet.''
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Recovering from lost visuals==
There are a few things you can try to do if you lose your vision. Most of these are less likely to help prolong your dream than the above techniques.

You can also try these if you have just woken up and are lying in your bed. You may be able to return to your dream.

===Autosuggestion===
You can repeat over and over a phrase similar to “I can see my dream,” or otherwise enforce in your mind that you can see a dreamscape. (See [[w:Autosuggestion|Autosuggestion]])

===Visualising===
You can visualise the scene as it would be if you could see it. You could take this as an opportunity to change the dreamscape by visualising a different environment from the previous one in the dream. This can be made easier by spinning as you visualize. (See [[#Changing the dream environment|Changing the dream environment]] below)

==Altering the dream==
===Changing the dream environment===
You can change the dreamscape by simply visualizing a different environment. Stephen LaBerge, author of ''Exploring the World of Lucid Dreaming'', suggests closing your eyes, spinning around, and visualizing a new location. Alan Worsley, a famous lucid dreamer, describes another technique of summoning a television and remote to switched dreamscapes. By simply “changing the channel” on the remote, imagine your surroundings switching to your desired location, as though you were switching through various television programs. 

In both of these methods, details are key. The more details you provide for your next dreamscape, the easier it will be to get there. For example, if you wanted go to the Superbowl in your dreams, you might simply state:

:'''“I want to be at the Superbowl.”'''

But this statement could be improved by adding details:

:'''&quot;I want be in the endzone seats, drinking a Coke, and wearing my favorite player's jersey at the Super Bowl.&quot;'''

===Summoning objects into your dream===
At some point in your lucid dreaming experience, you'll probably want to handle various objects, or talk with certain people. Both of these needs can be fulfilled by using your mind, and the power of suggestion. There is no set way to &quot;make&quot; things in the dream world; in fact, many lucid dreamers devise their own methods through experimentation. However, here are some of the more common &quot;summoning&quot; techniques:

* Try reaching for objects that are not within your field of vision. For example, think to yourself: “When I reach into my pocket, there will be a green box of mints.” Then, attempt to actually take a green box of mints out of your pocket. Other variations of this include reaching behind you for an object, or reaching through a mirror in hopes of getting a hold of what you want.
* To summon a person, you might say to yourself: “When I turn around, [person's name] will be standing in front of me,” or “When I walk through this mirror, I will see [person's name],” or “In a few moments, [person's name] will walk through that door (or around that corner).”
* More experienced lucid dreamers can try making the object materialize right before their eyes. This will require a fair amount of concentration. Here is an example of this process:&lt;br /&gt;

: I am lucid dreaming in my backyard, and it's currently night. Now, I don't like the dark in my lucid dreams because I'm more likely to wake up, and I fear there are monsters lurking around every corner. So, I want to '''make the sun appear''' so that it'll be daytime. Focusing on the horizon, I visualize the sun rising above it.&lt;br /&gt;
:At first nothing happens, but I continue focusing and...yes! There's some light filtering over the horizon! And now the sun is rising to the sky and it settles there; so far, so good. But wait...the sky is still black. Peering at bit closer at the sun, I can just make out a faint ring of blue sky encircling it. Lifting my hand towards it I shout, &quot;Blue!&quot;. The blue ring quickly spreads across the sky, creating the full daytime effect.”&lt;br /&gt;

* Some dreamers may have success by closing their eyes and imagining the desired object in front of them once when they open their eyes . 
* Try using mechanical devices within the dream, such as a nearby lightswitch or button, to summon objects or people. (i.e. &quot;When I flip this switch/press this button, X will appear.&quot;)
*Convince yourself you have magical powers (or scientific). Then, use them to summon objects, shapeshift, etc. This can help you believe the creation of objects more easily. 
*(This one is dumb, but it works.) Begin singing ''Friend Like Me'', and summon stuff to the beat. They may disappear after you finish singing, or start dancing, but hey, it's pretty darn fun.

Remember, in the dream world, your expectations shape your surroundings. If you think a big, scary monster is going to step out of the shadows and attack you...well, a big, scary monster probably ''is'' going to step out of the shadows and attack you. So, don't be a victim; take control of your thoughts and use them to your advantage.
&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==What you can do==
This final section should see you off with a few ideas of what to do in a dream.

It is advised to have a ''clear purpose'' for your lucid dreams whenever you go to sleep. In other words, every night you consider what you want to do when you have a lucid dream, and select one thing, or perhaps two or three if you are skilled. Avoid this:

: &quot;What am I gonna do what am I gonna do? I wanna fly, walk through walls, eat until my stomach explodes, spy on my neighbours, drive in a car real fast, woooeeey I'm gonna . . .&quot; &lt;!--- thanks to BuLLeT-PrOOf at the ld4all.com forums, this is a perfect example of what not to do! ---&gt;

You will either end up doing none of these things in your dream or getting overexcited and waking up.

Now that that’s clear, here’s a list of possible things you could do, ordered in difficulty. Remember that you might find some things unusually hard (or easy) compared to most lucid dreamers, this is perfectly normal! This is a very rough guide — if you’ve managed something in the Easy section, don't be scared to try for something from the Medium section.
===Easy===
* Fly
*: Most people enjoy flying around in dreams. There are different styles of flight that people use, each with a varied level of success for each individual. Methods such as “swimming through the air”, “Superman style” (one arm outstretched), “Neo style” (both arms at your side), and “Airplane style” (both arms out) ,&quot;eagle style&quot; (gliding through the air currents, using your fingered wings to navigate altitudes) are often used. There are a few methods of getting up into the air, such as simply jumping (you can jump really high in dreams if you believe it) or imagining a great force pushing you from your feet or walking up on air as though it is a staircase. Some people summon jetpacks and slip them on to fly. Be creative and dream up your own methods.
* Explore your dream world
*: Be warned, you are quite likely to forget you are dreaming when exploring! Doing reality checks often and muttering to yourself about how real everything seems can help to avoid this. You can also ask a dream character to tag along with you and remind you when you forget that you’re dreaming.
* Walk through a mirror or wall
*: You can pass through dream objects such as walls, glass, trees, and everything else. Confidence is really the key here. Some variations on going through stuff can be going in slowly, wiggling your finger in first, or running quickly into the object and telling yourself you would go through it. Some people particularly like to go through mirrors because of the unpredictable effects this action produces. However, if you tell yourself you will end up at a certain location before passing through a mirror, you can change the dream scene quickly. Be warned, some people experience nothing and wake up after passing through. You may want to hold your arm to keep yourself in the dream.
* Look at the sky
*: People often report amazing skies in lucid dreams. You can also shout colors at it and paint some sunrises.
* Show off to your friends (“Hey guys; I can go through this wall!”)
* Do plenty of sports (trampolining, skiing, swimming, dancing, etc.)
* Use various power such as Telekinesis and magic (a shortcut if you are having problems would be to summon a magic wand/staff or other device)
* Try to read a book that you have never read and remember the content
* Try to browse the Internet and visit sites that you've never visited
* Use things that you have never used
* Last but not least: Edit Wikipedia/Wikibooks articles (see question 124 of the [[w:Wikipedia:Are You a Wikipediholic Test|Wikipediholic Test]]) and see if the changes remain when you awake!

===Medium===
* Eat until you’re near bursting!
* Teleport
* Create some dream characters (possibly from a book or film)
* Try to find your spirit guide
* Experiments (in fact, researchers will often want people of various skills)
* Body swapping/possession (where you enter a different body)
* Morph
* Take some drugs (this is more realistic if you’ve done so in real life)
*: Many people have also experienced realistic effects when trying drugs in dreams that they have never taken in real life.
* Drive a vehicle (This is especially fun if you haven't ever driven in real life)
* Fight
*: Nobody can tell you what you should and should not do in your dreams; the choice remains up to you.
** Use weapons
**: It is usually more interesting to use melee weapons (knives, swords, brass knuckles) than projectile weapons. Machine guns and pistols often run out of ammo and summoning it can be difficult. Misfires and jamming is also common. ''(Your subconscious expectations will shape your dreamscape in all manner of ways, If you believe it is hard to accomplish, if you believe it will jam or misfire, it will. I have had no issues with weaponry such as firearms in my dreams what-so-ever, take this &quot;advice&quot; lightly.)'' However this can be overcome by using Directed Energy Weapons (Lasers, Plasma/pulse rifles), or weapons that can't jam (bows, simple firearms like muskets and so on).
* &quot;Beat up&quot; your enemies

===Hard===
* Have sex
*: The excitement, or closing your eyes, can cause you to wake up. An additional reason for waking up may be fixing your eyes on your partner, as holding a gaze for long is also known to cause waking up. Also your dream partner has a strange way of transforming in the midst of ecstasy. Finding a sex partner isn't very hard, it's keeping them that is difficult. That is why it is best to not panic when they are transforming and accept them for what your subconscious brings you. 
* More morphing like 360 degree vision, [[w:sonar|sonar vision]], etc.
* Create false memories, etc. False memories can be made by having a lucid dream, but scripting it so you will think it is real, e.g. you think what happened in your dream happened in real life. This is hard because you will have to forget it is a dream while staying lucid (knowing it is a dream).
* Compose music or poems (or request them from your subconscious)
* Build a fantasy dream world! (some people build a dream world naturally)
** [http://lucidcrossroads.co.uk Lucid Crossroads]
** [https://web.archive.org/web/20230530232446/http://www.astralpulse.com/astralpulseisland.html Astral Pulse Island]
** H.P. Lovecraft's [[w:Dreamlands|Dreamlands]]
* Have precognition (your subconscious can be very good at predicting the future with relationships and career)
* Experience death. This could be a very harsh experience, and depending on your religious or philosophical beliefs may summon you into a different world or nothingness.
* Ask the dream to show you your worst fears/deepest traumas/etc. (be prepared for some bad stuff to surface)
* Build/use impossible objects, such as [[w:Hypercube|hypercubes]], [[w:Klein bottle|Klein bottles]], etc.
* Rewind time
* Have a lucid dream ''inside'' a lucid dream
* Have a lucid dream ''inside'' a lucid dream ''inside'' a lucid dream... as many times as you want!
* Experiment with different decisions in the dreamworld
* Or, try something nobody's done before!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;

==Conclusion==
With all the techniques in this book, you may feel overwhelmed and uncertain of what to do next. Don't worry — just choose a few techniques to “map your way to lucidity”, decide on a few things you will want to do from this page, and start!

If you are still unsure of what to do, don’t worry — you might happen to have a lucid dream tonight!

If you are beginning to feel a compulsive thirst for ''more'' information about dreams, head over to the [[Lucid Dreaming/Further Reading|Further Reading]] section for the sites to satisfy your cravings. Remember to come back occasionally and help make the wikibook grow!

&lt;div style=&quot;text-align: right; font-size: small&quot;&gt;[[#top|top]]&lt;/div&gt;
{{LDTOC}}

[[es:Sueño lúcido/Uso]]
[[it:Sogno lucido/Uso]]</text>
      <sha1>pbw74lfmtyrz96de34ndqzr3qw4s5p1</sha1>
    </revision>
  </page>
  <page>
    <title>User:Panic2k4</title>
    <ns>2</ns>
    <id>15928</id>
    <revision>
      <id>4678621</id>
      <parentid>4668732</parentid>
      <timestamp>2026-10-27T21:46:41Z</timestamp>
      <contributor>
        <username>Panic2k4</username>
        <id>2865</id>
      </contributor>
      <origin>4678621</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8223" sha1="i7snwyifndcd3lubkcnygccehpt9ijf" xml:space="preserve">[[User:Panic2k4/Sandbox/RapidEdit|*]] - [[User:Panic2k4/Sandbox/Embedded C++|+]]- [[User:Panic2k4/Sandbox/ShareMemory|&amp;]] - '''Tools:[http://tools.wikimedia.de/~dapete/catgraph/ Catgraph] - [[Special:Collection|Collections]] - [[Special:PrefixIndex|PrefixIndex]] - [http://tools.wmflabs.org/meta/crossactivity/ Cross Activity] - [http://stats.wikimedia.org/wikibooks/EN/Wikibooks_EN.htm Statistics per Wikibook]&lt;br&gt;[https://tools.wmflabs.org/xtools/adminstats/?project=enwikibooks Sysops' statistics &amp; Yet Another Edit Counter]'''
----

{| cellspacing=&quot;3&quot; 
|- style=&quot;vertical-align:top&quot;
|style=&quot;width:75%; border: 1px solid #000000; background-color: #c0c0c0;{{text default color}};&quot;|
&lt;div style=&quot;padding: .4em .9em .9em&quot;&gt;
;'''Wikibooks''': To me a Wikibook is like a sand castle. Imagine it as constructing a sand castle on a communal sand box, participation is welcomed, but not required and as all people contribute some sand, there is plenty of sand for all, there is no need to fight over it or how the castle should be built, and when the castle is built, it still is only sand, it will be used again. What is important is that the sand will continue to be added and people come to build new and improved castles with it.
----
;'''Like''': [[Subject:C++ programming language|Programming, C/C++]], All things SiFi (including literature), Japanese cinema portraying medieval times ([[w:Samurai cinema|Samurai cinema]], [[w:Zatoichi|Zatoichi]], etc.), very few TV Shows (Game of Thrones), [[Dogs]], Meerkat (Suricata suricatta), Dolphins, [[w:Damascus goat|Damascus goat]] ...
----
;'''Dislike''': War, organized religion, organized and professional sports, Reality TV, Microsoft (and most big or multinational corporations), Software patents, .Net (and VM languages in general), Pepsi (I avoid non-natural drinks in general but I really dislike it), Kiwi (as food), Cephalopods (as food, except fried or heavy grilled), Cats (as companion animal)...
----
;'''Life Philosophy''':
I consider myself a [[w:Tao|Tao]] [[w:Pantheism|Pantheist]], and believe in Buddhism interpretation of [[w:Karma|Karma]] in the sense that every action creates a reaction as in [[w:Chaos theory|chaos theory]].
----
;'''Social order''':
My favorite social order is [[w:Anarchist communism|Anarcho Communism]].
----
'''At this moment I'm mostly interested in C++, P2P, the ending of IP, fighting DRM and ...'''&lt;br&gt;
{{small/top}}
The Salticidid Portia  [http://www.ontariosciencecentre.ca/scizone/question/default.asp?teaserIdEN=384 “Perilous Portia”], [http://lemonodor.com/archives/001409.html “...when we look into Portia's dark, bulging eyes, the lights are on, somebody's at home, and a lot more than an eight-legged automaton is staring back.”]&lt;small&gt;&lt;small&gt;(can't find a decent link)&lt;/small&gt;&lt;/small&gt;

[[w:Epigenetics|Epigenetics]] and Human Genetics, regarding non-negative mutations [ [http://www.disaboomlive.com/Blogs/saydrah/archive/2009/04/03/super-toddler-liam-hoekstra-age-3-his-rare-genetic-condition-makes-him-uniquely-gifted.aspx Liam Hoekstra], [http://www.usatoday.com/sports/olympics/beijing/swimming/2008-07-31-phelps_N.htm Michael Phelps], [[w:Brooke Greenberg|Brooke Greenberg]] ]

Non-obvious Physics [ [[w:Zero-point energy|Zero-point energy]], [[w:Sonoluminescence|Sonoluminescence]], [[w:Emdrive|Emdrive]], thought and emotions effect on environment (&quot;water memory&quot;, plants etc.) ]

Lost Technologies/Historic Conundrums [ [[w:Terra preta|Terra preta]], [[w:Antikythera mechanism|Antikythera mechanism]], [[w:Baghdad Battery|Baghdad Battery]], [[w:Starlite|Starlite]] ]

Sustainable Technologies [ [[w:Permaculture|Permaculture]] ]
{{small/end}}
----
;'''Wikimedia projects'''
I'm registered on the main projects (except Wikipedia), but I rarely log onto other projects and don't particularly fallow what is happening in relation to Wikimedia software and other project's policies... 
----
'''Other Cool Wikibooks projects'''&lt;small&gt;&lt;small&gt; by order of subject relevance to me&lt;/small&gt;&lt;/small&gt;&lt;br&gt;
&lt;small&gt;[[More C++ Idioms]] - [[Algorithm Implementation]] - [[Reverse Engineering]] - [[x86 Disassembly]] - [[Data Compression]] - [[Cryptography]] - [[Linux Applications Debugging Techniques]] - [[Data Structures]] - [[Colonizing Outer Space]] - [[Self Interest and Social Behavior]] - [[Space Transport and Engineering Methods]] - [[Python Programming]] - [[Getting Started as an Entrepreneur]] - [[Fundamentals of Transportation]] - [[Climate Change]] - [[Science Fiction Literature]] - [[Mythology]] - [[C Programming]] - [[Computer programming]] - [[Operations Research]] - [[Nanotechnology]] - [[Movie Making Manual]] - [[Rhetoric and Composition]] - [[Elements of Political Communication‎‎]] - [[Communication Theory]] - [[Basic Writing]] - [[Control Systems]] - [[Compiler Construction]] - [[The Voynich Manuscript]] - [[X86 Assembly]] - [[Practical Electronics]] - [[Signals and Systems]]- [[Java Programming]] - [[Windows Programming]] - [[The Cold War]] - [[Editing Wikitext]] - [[Learning the vi Editor]] - [[Lucid Dreaming]]&lt;/small&gt;

&lt;/div&gt;
|style=&quot;width:30%; border: 1px solid #000000; color: #000; background-color: #ffc0c0;{{text default color}};&quot;|
&lt;div style=&quot;padding: .4em .9em .9em&quot;&gt;
&lt;h1&gt;Me, Myself and I...&lt;/h1&gt;
&lt;small&gt; [http://www.bibsonomy.org/user/panic My WEB (Urls/Booksmarks) at BibSonomy]&lt;/small&gt;

&lt;div style=&quot;text-align: center;&quot;&gt;I have also customized Google Co-op to use my del.icio.us pages and other personal preferences to provide a more useful search results you can see it here [http://www.google.com/custom?hl=en&amp;lr=&amp;client=google-coop&amp;cof=BGC%3A%23FFFFFF%3BT%3A%23000000%3BLC%3A%230000CC%3BVLC%3A%230000CC%3BALC%3A%230000CC%3BGALT%3A%23008000%3BGFNT%3A%23000000%3BGIMP%3A%23000000%3BDIV%3A%230000CC%3BLBGC%3A%23FFFFFF%3BAH%3Acenter%3BCX%3APanic%2527s%2520Pages%3B&amp;q=&amp;btnG=Search&amp;cx=015397482836322967076%3A_zhaog5negg Panic's KB @ Google Co-op]&lt;/div&gt;
 
----

&lt;h2&gt;What I know about...&lt;/h2&gt;
{| style=&quot;width:100%&quot;
| style=&quot;background-color: #ffc20f;{{text default color}}; border: solid 1px #ffeaa5; padding: 1em; margin: auto; vertical-align:top&quot;|'''Programming  &amp; Languages'''
 ASM (PIC, z80, MC68000-060 and others)
 BASIC (many tastes GWBasic - VB6)
 PASCAL (too many incarnations + DELPHI)
 Lisp
 UML
 [[w:Smalltalk|Smalltalk]]
 C/C++ (POSIX,WIN32,MFC,STL)
 Java (J2EE) ,Javascript, ASP and PHP
 HTML, XML, CSS
 P/SQL
|}
{| style=&quot;width:100%&quot;
| style=&quot;background-color: #f0ad00;{{text default color}}; border: solid 1px #ffeaa5; padding: 1em; vertical-align:top&quot;|'''Operating Systems'''
Amiga OS, Be OS, UNIX &amp; Linux and all flavors of Windows minus Windows CE and Vista.
|}&lt;/div&gt;
&lt;div style=&quot;padding: .4em .9em .9em&quot;&gt;
'''Books I'm an author at Wikibooks'''&lt;br&gt;
#[[C++ Programming]]
#[[The World of Peer-to-Peer (P2P)|Peer-to-Peer (P2P)]]
#[[Hypnosis]]
#[[On spies and stratagems]]
#[[Understanding Global Trade Policy]]
#[[Remembering the Templars]]
#[[Video Game Design]]
'''Other books I will attempt to provide content at Wikibooks'''&lt;br&gt;
[[FLTK]], [[When It Hits the Fan]], [[House Construction]], [[History of Computers]], [[Science Fiction Literature]], [[Dogs]] and any of the other ones on my favorite list...
----
&lt;small&gt;I will keep this lists here since they may have some useful to others than myself, and I would like to know other Wikibookians that have similar resources especially if they exclude any commercial interests around the lists.&lt;br&gt;
[[User:Panic2k4/Books Read|SF &amp; Fantasy Books I've read]]&lt;br&gt;
[[User:Panic2k4/Podcasts and Audiobooks|Podcasts and Audiobooks I've listen to]]&lt;br&gt;
[[User:Panic2k4/Videos|Technical or Cultural Videos I've seen and liked]]&lt;br&gt;
[[User:Panic2k4/TV, movies and documentaries|TV shows, movies and documentaries]]&lt;/small&gt;
&lt;/div&gt;
|
|- 
|colspan=&quot;2&quot; style=&quot;width:100%; border: 1px solid #000000; color: #000; background-color: #c0ffc0;{{text default color}};&quot;|
= &lt;small&gt;&lt;small&gt;&lt;small&gt;&lt;small&gt;Public Announcement Postings  [[http://en.wikibooks.org/wiki/User:Panic2k4/Archive Archive]]&lt;div style=&quot;text-align: right; direction: ltr; margin-left: 1em;&quot;&gt;[[User:Panic2k4/Sandbox/Central|My listed public posts elsewhere]]&lt;/div&gt;&lt;/small&gt;&lt;/small&gt;&lt;/small&gt;&lt;/small&gt; =
&lt;div style=&quot;text-align: center;&quot;&gt;
----
&lt;/div&gt;

{{Userpage}}
|}</text>
      <sha1>i7snwyifndcd3lubkcnygccehpt9ijf</sha1>
    </revision>
  </page>
  <page>
    <title>C programming/C compilers reference list</title>
    <ns>0</ns>
    <id>42794</id>
    <revision>
      <id>4678650</id>
      <parentid>4652696</parentid>
      <timestamp>2026-10-28T05:30:43Z</timestamp>
      <contributor>
        <username>~2026-57448-04</username>
        <id>3629584</id>
      </contributor>
      <comment>Fixed broken MinGW link</comment>
      <origin>4678650</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3513" sha1="4wnl7zubgimbyvreeifrgqmawcsrv0p" xml:space="preserve">{{Nav}}

For a brief introduction to setting up and using some of the more beginner-friendly compilers and IDEs, see [[../Using a Compiler/]].

== Free (or with a free version) ==

* [[w:Ch_interpreter|Ch_interpreter]] (http://www.softintegration.com) - The software works in Windows, Linux, Mac OS X, Freebsd, Solaris, AIX and HP-UX. The Ch Standard Edition is free for noncommercial use.
* [[w:Interactive C|Interactive C]] (http://www.botball.org/educational-resources/ic.php)
** target platform: Handy Board (Freescale 68HC11); Lego RCX
* [[w:CINT|CINT]] is an interpreter for C and C++ code, included in the data-analysis package [[ROOT]]. The CINT interpreter is licensed under the X11/MIT license. ( https://root.cern.ch/drupal/content/cint ).
* &lt;!-- was https://github.com/zsaleeba/picoc --&gt; [https://gitlab.com/zsaleeba/picoc PicoC] is a very small C interpreter, intended for small embedded systems with very little code space or data space.
** PicoC target platform: x86-32, x86-64, powerpc, arm, ultrasparc, HP-PA and blackfin processors; and is easy to port to new targets.
* [http://sourceforge.net/projects/eic/ Extensible Interactive C (EiC)]
* [[w:lcc-win32|lcc-win32]] (http://www.cs.virginia.edu/~lcc-win32) -  Software copyrighted by Jacob Navia. It is free for non-commercial use. Windows (98/ME/XP/2000/NT).
* [[w:GNU Compiler Collection|GNU Compiler Collection]] (http://gcc.gnu.org) - GNU Compiler Collection. GNU General Public License / GNU Lesser General Public License.
** [[w:MinGW|MinGW]] (https://www.mingw-w64.org/) provides GCC for Windows
* [[w:LLVM|clang (LLVM)]] (http://clang.llvm.org/) - Almost everywhere
* [[w:Open Watcom|Open Watcom]] (http://www.openwatcom.org) Open Source development community to maintain and enhance the Watcom C/C++ and Fortran cross compilers and tools. Version 1.4 released in December 2005.
**'''Host Platforms:''' Win32 systems (IDE and command line), 32-bit OS/2 (IDE and command line), DOS (command line), and Windows 3.x (IDE) 
**'''Target Platforms:''' DOS (16-bit), Windows 3.x (16-bit), OS/2 1.x (16-bit), Extended DOS, Win32s, Windows 95/98/Me, Windows NT/2000/XP, 32-bit OS/2, and Novell NLMs 
**'''Experimental / Development:''' Linux, BSD, *nix, PowerPC, Alpha AXP, MIPS, and Sparc v8
*[[w:Tiny C Compiler|Tiny C Compiler]] (http://www.tinycc.org) - A small C compiler designed to work for slow computers with little disk space (e.g. on rescue disks).
* [[w:Portable C Compiler|Portable C Compiler]] (http://pcc.ludd.ltu.se) - Portable C Compiler. BSD Style License(s).
* [[w:Small Device C Compiler|Small Device C Compiler]] (SDCC)
** target platforms: Intel 8051-compatibles; Freescale (Motorola) HC08; Microchip PIC16 and PIC18.
* [[w:FpgaC|FpgaC]]. Target platform: FPGA hardware via XNF or VHDL files.
* C compilers for many digital signal processors (DSPs), many of them are free, and are listed in the [http://www.bdti.com/faq/3.htm comp.dsp FAQ].
* [[w:Microsoft Visual C++|Microsoft Visual C++]] (http://msdn.microsoft.com/visualc) - Free (partially limited) version available (Express|Community Edition)
* C Playground - Online C Programming IDE by Programiz - Free Online IDE to practice C Programming

== Paid ==
* [[w:Intel C Compiler|Intel C Compiler]] (http://software.intel.com/en-us/intel-compilers) - Windows, Linux, Mac, QNX, and embedded C/C++ compilers.  Optimized for Intel 32-bit and 64-bit CPUs.
* [[w:Impulse C|Impulse C]] - Target platform: FPGA hardware via Hardware Description Language (HDL) files.

{{Nav}}</text>
      <sha1>4wnl7zubgimbyvreeifrgqmawcsrv0p</sha1>
    </revision>
    <revision>
      <id>4678651</id>
      <parentid>4678650</parentid>
      <timestamp>2026-10-28T05:41:01Z</timestamp>
      <contributor>
        <username>~2026-57448-04</username>
        <id>3629584</id>
      </contributor>
      <comment>Changed the wiki link to the MinGW-w64 page instead of the MinGW page. The original MinGW is 32-bit only and the project is dead. The MinGW-w64 fork carries on that old project’s goals and works with modern windows and is still supported.</comment>
      <origin>4678651</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3529" sha1="lzy07zqyk2rvop6vuiwa3c166ylwm08" xml:space="preserve">{{Nav}}

For a brief introduction to setting up and using some of the more beginner-friendly compilers and IDEs, see [[../Using a Compiler/]].

== Free (or with a free version) ==

* [[w:Ch_interpreter|Ch_interpreter]] (http://www.softintegration.com) - The software works in Windows, Linux, Mac OS X, Freebsd, Solaris, AIX and HP-UX. The Ch Standard Edition is free for noncommercial use.
* [[w:Interactive C|Interactive C]] (http://www.botball.org/educational-resources/ic.php)
** target platform: Handy Board (Freescale 68HC11); Lego RCX
* [[w:CINT|CINT]] is an interpreter for C and C++ code, included in the data-analysis package [[ROOT]]. The CINT interpreter is licensed under the X11/MIT license. ( https://root.cern.ch/drupal/content/cint ).
* &lt;!-- was https://github.com/zsaleeba/picoc --&gt; [https://gitlab.com/zsaleeba/picoc PicoC] is a very small C interpreter, intended for small embedded systems with very little code space or data space.
** PicoC target platform: x86-32, x86-64, powerpc, arm, ultrasparc, HP-PA and blackfin processors; and is easy to port to new targets.
* [http://sourceforge.net/projects/eic/ Extensible Interactive C (EiC)]
* [[w:lcc-win32|lcc-win32]] (http://www.cs.virginia.edu/~lcc-win32) -  Software copyrighted by Jacob Navia. It is free for non-commercial use. Windows (98/ME/XP/2000/NT).
* [[w:GNU Compiler Collection|GNU Compiler Collection]] (http://gcc.gnu.org) - GNU Compiler Collection. GNU General Public License / GNU Lesser General Public License.
** [[wikipedia:Mingw-w64|MinGW-w64]] (https://www.mingw-w64.org/) provides GCC for Windows
* [[w:LLVM|clang (LLVM)]] (http://clang.llvm.org/) - Almost everywhere
* [[w:Open Watcom|Open Watcom]] (http://www.openwatcom.org) Open Source development community to maintain and enhance the Watcom C/C++ and Fortran cross compilers and tools. Version 1.4 released in December 2005.
**'''Host Platforms:''' Win32 systems (IDE and command line), 32-bit OS/2 (IDE and command line), DOS (command line), and Windows 3.x (IDE) 
**'''Target Platforms:''' DOS (16-bit), Windows 3.x (16-bit), OS/2 1.x (16-bit), Extended DOS, Win32s, Windows 95/98/Me, Windows NT/2000/XP, 32-bit OS/2, and Novell NLMs 
**'''Experimental / Development:''' Linux, BSD, *nix, PowerPC, Alpha AXP, MIPS, and Sparc v8
*[[w:Tiny C Compiler|Tiny C Compiler]] (http://www.tinycc.org) - A small C compiler designed to work for slow computers with little disk space (e.g. on rescue disks).
* [[w:Portable C Compiler|Portable C Compiler]] (http://pcc.ludd.ltu.se) - Portable C Compiler. BSD Style License(s).
* [[w:Small Device C Compiler|Small Device C Compiler]] (SDCC)
** target platforms: Intel 8051-compatibles; Freescale (Motorola) HC08; Microchip PIC16 and PIC18.
* [[w:FpgaC|FpgaC]]. Target platform: FPGA hardware via XNF or VHDL files.
* C compilers for many digital signal processors (DSPs), many of them are free, and are listed in the [http://www.bdti.com/faq/3.htm comp.dsp FAQ].
* [[w:Microsoft Visual C++|Microsoft Visual C++]] (http://msdn.microsoft.com/visualc) - Free (partially limited) version available (Express|Community Edition)
* C Playground - Online C Programming IDE by Programiz - Free Online IDE to practice C Programming

== Paid ==
* [[w:Intel C Compiler|Intel C Compiler]] (http://software.intel.com/en-us/intel-compilers) - Windows, Linux, Mac, QNX, and embedded C/C++ compilers.  Optimized for Intel 32-bit and 64-bit CPUs.
* [[w:Impulse C|Impulse C]] - Target platform: FPGA hardware via Hardware Description Language (HDL) files.

{{Nav}}</text>
      <sha1>lzy07zqyk2rvop6vuiwa3c166ylwm08</sha1>
    </revision>
  </page>
  <page>
    <title>Help:Tracking changes</title>
    <ns>12</ns>
    <id>49109</id>
    <revision>
      <id>4678513</id>
      <parentid>4677875</parentid>
      <timestamp>2026-10-27T16:39:09Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Reviewing pages */ Changing to</comment>
      <origin>4678513</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="51287" sha1="00ht56oij3z52i987soo0idl6tahufk" xml:space="preserve">{{shortcut|WB:TRACK}}
{{Wikibooks help}}

Wikibooks is a [[w:wiki|wiki]], and as such is designed to allow anyone to edit pages and thus contribute to the collection of textbooks here.  On popular books it is necessary to collaborate and coordinate with others.  But how can you do so if you cannot keep track of changes other editors are making?  Fortunately, Wikibooks' software makes it easy to monitor revisions to pages.  You can follow changes to [[#Recent changes|any page in the wiki]], [[#Related changes|pages linked from a particular page]], [[#Watching pages|pages in a list of your choosing]], and [[#Page history|a single page]].  You can also see [[#User contributions|changes made by a particular user]].  The software has a useful [[#Viewing diffs|interface]] for seeing what has been added and/or removed from a page.  In an environment where anyone can change pages, even those without [[Help:Account management|accounts]], vandalism can be a concern.  Wikibooks has a system where pages can be [[#Reviewing pages|reviewed]] to verify that changes by new or unregistered users are beneficial.  With all these tools at your disposal, you won't miss a thing!
&lt;br style=&quot;clear:left;&quot; /&gt;

=={{anchor|Recent Changes}}Recent changes==
{{shortcut|WB:RC}}

The '''[[Special:RecentChanges|Recent Changes]]''' page lets you see the most recent changes made to pages at Wikibooks.  Using this page, you can monitor and review the work of other users, allowing mistakes to be corrected and vandalism to be eliminated.  There is a link to the Recent Changes page in the sidebar of each page. You can also create a link to the page as &lt;nowiki&gt;[[Special:RecentChanges]]&lt;/nowiki&gt;.

==={{anchor|Related Changes}}Related changes ===
The '''Related Changes''' page lets you see the most recent changes for pages linked to from the current page, or for pages that link to the current page. Using this page, you can monitor and review relates works. The parent links created by the software on a subpage do not count as page links to show changes for. There is a link to the Related Changes pages in the toolbox for most skins. You can also create a link for a page with &lt;nowiki&gt;[[Special:RecentChangesLinked/PageName]]&lt;/nowiki&gt;. All of the [[#Preferences|preferences]] and limitations that apply to Recent Changes also apply to Related Changes.

===Preferences===
Logged-in users can set preferences to adjust the appearance of these pages.  For help in doing this, see [[WB:LOGIN|how to log in]] and [[WB:PREFS|how to set preferences]].  The options that affect these pages are:

* '''Days to show in recent changes''' – You may select the number of days to be shown by default on the Recent Changes page.
* '''Number of edits to show by default''' – You may select the number of changes which will be shown by default. Once on that page, links are provided for other options. In the case of Enhanced Recent Changes this number of changes includes those that are initially hidden.
* '''Use enhanced recent changes''' – with this option enabled, multiple edits are grouped together. This option uses [[JavaScript]], and won't work in every browser.
* '''Hide minor edits in recent changes''' – this hides all edits that have been marked as minor by logged-in users.
* '''Hide reviewed edits in recent changes''' – this hides all edits that have been [[#Reviewing pages|reviewed]].

==={{anchor|Enhanced Recent changes}}Enhanced Recent Changes===
Enhanced Recent Changes groups recent changes per day, where &quot;day&quot; is defined according to local time. For each day, it groups the changes by page, and displays the titles of the changed pages in order from new to old latest change of the day concerned, or in the case of hiding minor edits, latest major change.

Multiple edits on the same day to a single page are grouped together on the Recent Changes screen. Only a summary line is shown, info about the individual edits is loaded into the browser right away but only shown by clicking on the blue arrow on the left. This option uses [[JavaScript]] and does not work in every browser (see [[m:Browser issues with MediaWiki|Browser issues with MediaWiki]]).

This feature applies also to [[#Related changes|Related Changes]] and the enhanced [[#Watching pages|watchlist]]. The latter is simply a selection of the enhanced Recent Changes, namely a restriction to watched pages, without the bolding.

===Appearance===
The default Recent Changes looks like this:

* ([[#Diff|diff]]) ([[#Page history|hist]]) . . '''&lt;span class=&quot;unpatrolled&quot;&gt;!&lt;/span&gt;''' [[Wikijunior:Dinosaurs/Pterosaurs]] &lt;span style=&quot;background:#ffff00;{{Text default color}}; font-weight:bold;&quot;&gt;&lt;nowiki&gt;[&lt;/nowiki&gt;[[#Reviewing pages|review]]&lt;nowiki&gt;]&lt;/nowiki&gt;&lt;/span&gt;; 10:06 . . &lt;span class='mw-plusminus-pos'&gt;(+1,864)&lt;/span&gt; . . [[Special:Contributions/111.222.33.44|111.222.33.44]] ([[User talk:111.222.33.44|talk]]) ''(Add examples)''
* (diff) ([[#Page history|hist]]) . . '''N''' [[Wikijunior:Dinosaurs/Pterosaurs]]; 10:04 . . &lt;span class='mw-plusminus-pos'&gt;(+890)&lt;/span&gt; . . [[User:Anthere|Anthere]] ([[User talk:Anthere|talk]] | [[#User contributions|contribs]]) ''(links)''
* (diff) ([[#Page history|hist]]) . . '''N''' [[Wikijunior:Dinosaurs]]; 10:04 . . &lt;span class='mw-plusminus-pos'&gt;(+3394)&lt;/span&gt; . . [[User:Brion VIBBER|Brion VIBBER]] ([[User talk:Brion VIBBER|talk]] | [[#User contributions|contribs]]) ''(New page)''
* ([[Special:Log/move|Move log]]); 10:03 . . [[User:Maveric149|Maveric149]] ([[User talk:Maveric149|talk]] | [[#User contributions|contribs]]) ''(moved [[Main page]] to [[Main Page]])''

Enhanced Recent Changes shows changes to one page on the same line, with an arrow next to it:

[[File:Arrow r.svg|link=|alt=]] '''{{mono|1=N}}'''&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{{mono|1=10:06}} [[Wikijunior:Dinosaurs/Pterosaurs]] &lt;span style=&quot;background:#ffff00;{{Text default color}}; font-weight:bold;&quot;&gt;&lt;nowiki&gt;[&lt;/nowiki&gt;[[#Reviewing pages|review]]&lt;nowiki&gt;]&lt;/nowiki&gt;&lt;/span&gt; ([[#Diff|2 changes]] | [[#Page history|hist]]) . . &lt;span class='mw-plusminus-pos'&gt;(+2754)&lt;/span&gt; . . {{font|size=-1|&lt;nowiki&gt;[&lt;/nowiki&gt;[[Special:contributions/111.222.33.44|111.222.33.44]]; [[User:Anthere|Anthere]]&lt;nowiki&gt;]&lt;/nowiki&gt;}}&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;'''{{mono|1=N}}'''&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{{mono|1=10:04}} [[Wikijunior:Dinosaurs]] (diff | [[#Page history|hist]]) . . &lt;span class='mw-plusminus-pos'&gt;(+3394)&lt;/span&gt; . . [[User:Brion VIBBER|Brion VIBBER]] ([[User talk:Brion VIBBER|talk]] | [[#User contributions|contribs]]) ''(New page)''&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{{mono|1=10:03}} ([[Special:Log/move|Move log]]) . . [[User:Maveric149|Maveric149]] ([[User talk:Maveric149|talk]] | [[#User contributions|contribs]]) moved [[Main page]] to [[Main Page]] (''better location'')

Clicking this arrow expands the entry so you can see all the changes made:

[[File:Arr_d.png|link=|alt=]]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{{mono|1=10:06}} [[Wikijunior:Dinosaurs/Pterosaurs]] &lt;span style=&quot;background:#ffff00;{{Text default color}}; font-weight:bold;&quot;&gt;&lt;nowiki&gt;[&lt;/nowiki&gt;[[#Reviewing pages|review]]&lt;nowiki&gt;]&lt;/nowiki&gt;&lt;/span&gt; ([[#Diff|2 changes]] | [[#Page history|hist]]) . . &lt;span class='mw-plusminus-pos'&gt;(+2754)&lt;/span&gt; . . {{font|size='-1'|&lt;nowiki&gt;[&lt;/nowiki&gt;[[Special:contributions/111.222.33.44|111.222.33.44]]; [[User:Anthere|Anthere]]&lt;nowiki&gt;]&lt;/nowiki&gt;}}&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;'''&lt;span class=&quot;unpatrolled&quot;&gt;!&lt;/span&gt;''' {{mono|1=10:06}} ([[Main Page|cur]] | [[Main Page|prev]]) . . &lt;span class='mw-plusminus-pos'&gt;(+1,864)&lt;/span&gt; . . [[Special:contributions/111.222.33.44|111.222.33.44]] ([[user talk:111.222.33.44|talk]]) ''(Add examples)''&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;'''{{mono|1=N}}'''&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; {{mono|1=10:04}} ([[Main Page|cur]] | [[Main Page|prev]]) . . &lt;span class='mw-plusminus-pos'&gt;(+890)&lt;/span&gt; . . [[User:Anthere|Anthere]] ([[user talk:Anthere|talk]] | [[#User contributions|contribs]]) ''(links)''&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;'''{{mono|1=N}}'''&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; {{mono|1=10:04}} [[Wikijunior:Dinosaurs]] (diff | [[#Page history|hist]]) . . &lt;span class='mw-plusminus-pos'&gt;(+3394)&lt;/span&gt; . . [[User:Brion VIBBER|Brion VIBBER]] ([[User talk:Brion VIBBER|talk]] | [[#User contributions|contribs]]) ''(New page)''&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{{mono|1=10:03}} ([[Special:Log/move|Move log]]) . . [[User:Maveric149|Maveric149]] ([[User talk:Maveric149|talk]] | [[#User contributions|contribs]]) moved [[Main page]] to [[Main Page]] (''better location'')

Each indicates four edits: the first by a user who is not logged in, to [[Wikijunior:Dinosaurs/Pterosaurs]]; the second by Anthere to [[Wikijunior:Dinosaurs]]; the third by Maveric149 to [[Main page]]; and the fourth by Brion VIBBER to [[Wikijunior:Dinosaurs]].

What each element used means:
* &quot;[[#Diff|diff]]&quot; links to the diff-page for this edit; it is not available for new pages, or for page moves
* The &quot;[[#Page history|hist]]&quot; link corresponds to the ''Page history'' link on the edited page: it shows not just this edit but also older and newer ones. For page moves, the hist link leads to the history of the new page title
* A bold '''m''' indicates that the user marked the edit &quot;minor&quot;. Only logged in users can mark edits minor, to avoid abuse.
* A bold '''N''' indicates that the page is &quot;new&quot;, i.e., previously did not exist.  It is possible for a change to possess both the &quot;minor&quot; and &quot;new&quot; indicators; this is typically used for new [[Help:Editing#Redirecting|redirect]]s.
* A bold '''b''' indicates that the edit is made by a bot (an account with bot flag), or that the edit is hidden by an administrator.
* A bold '''&lt;span class=&quot;unpatrolled&quot;&gt;!&lt;/span&gt;''' indicates that the page is unreviewed.  For more information see  ''[[#Reviewing pages|Reviewing pages]]'' below.
* The next link is a link to the current version of the page in question.
** A bold '''[[Help:Editing#Links|link]]''' indicates this page is part of your [[#Watching pages|watchlist]].
* The &lt;span style=&quot;background:#ffff00;color:var(--color-base-fixed,#202122); font-weight:bold;&quot;&gt;&lt;nowiki&gt;[&lt;/nowiki&gt;[[#Reviewing pages|review]]&lt;nowiki&gt;]&lt;/nowiki&gt;&lt;/span&gt; tag next to the page title will take you to a page that shows the [[#Diff|diff]] between the last [[#Reviewing pages|reviewed]] edit to the page and the most recent edit.
* 10:06 refers to the time in [[w:UTC|UTC]]. You can change the time to your time zone using your preferences - see [[WB:PREFS|how to set preferences]].
* &lt;span class='mw-plusminus-pos'&gt;(+1,864)&lt;/span&gt; (generally a green number with a +, or a red number with a -) refers to the number of bytes that have been added or removed.
* For [[WB:LOGIN|logged in]] users, the next link is a link to their user homepage (as usual with internal links, the view page if the page exists, the edit page if it does not, the two being styled differently). For users who are not logged in, the link is to their ''[[#User contributions|user contributions]]''.
* There is a link to the user's talk page (the same remarks regarding existence apply).
* Finally, there is a link to the user's contributions if the user is logged in.
* For page moves, a link is given to both the old and new title.

==Watching pages==
{{shortcut|WB:WATCH|WB:WATCHLIST}}

'''Watching pages'''  allows any [[WB:LOGIN|logged-in]] user to keep a list of &quot;watched&quot; pages and to generate a list of recent changes made to those pages (and their associated talk pages). In this way you can keep track of and react to what's happening to pages you have created or are otherwise interested in.

===Controlling which pages are watched===
[[File:Unwatched page in Vector.png|thumb|300px|This screenshot shows a page that is not on the watchlist of the user. Clicking on the star will add it to the watchlist.]]
[[File:Watched page in Vector.png|thumb|300px|The star on this page is blue to indicate that it is on the watchlist of the user.]]
There are four ways to control which pages you have on your watchlist:
#When viewing a page, click the star sign between the 'View history' tab and the search box at the very top of the page (for the default appearance, in some other versions, click on the &quot;watch&quot; or &quot;unwatch&quot; tab), to respectively add or remove the page from your watchlist.
#When editing a page, check or uncheck &quot;Watch this page&quot; before saving (above the ''[[Help:Editing#Show preview button|Show preview]]'' button).
#Click &quot;View and edit watchlist&quot; or &quot;Edit raw watchlist&quot; at the top of the watchlist page to view or alter the list of watched pages directly. The first option takes you to [[Special:Watchlist/edit]], where the watched pages are listed with checkboxes which can be used to remove items. The second takes you to [[Special:Watchlist/raw]], which has a text area with a list of watched pages, one title per line, sorted by [[Help:Pages#Namespaces|namespace]] number and then alphabetically. You can edit the list directly, copy it to an external editor or replace it with a list created elsewhere. Duplicates are automatically removed on saving.

If you check &quot;Add pages I [[Help:Editing|edit]] to my watchlist&quot; on the &quot;Watchlist&quot; tab of your user [[WB:PREFS|preferences]], then the &quot;Watch this page&quot; checkbox will always be checked by default when you edit pages. Other similar options are &quot;Add pages I create to my watchlist&quot;, &quot;Add pages I [[WB:MOVE|move]] to my watchlist&quot;, &quot;Add pages I [[#Reviewing pages|review]] to my watchlist&quot;, and (for [[Wikibooks:Administrators|administrators]]) &quot;Add pages I delete to my watchlist&quot;.

It should also be noted that:
*Talk pages are not listed at [[Special:Watchlist/edit]] or [[Special:Watchlist/raw]], but they are automatically watched whenever their corresponding non-talk pages are watched.
*It is not possible to watch automatically generated pages, such as [[Special:SpecialPages|Special pages]]. Watching a [[Help:Categories|category]] page will pick up changes to the text of the category page itself, but not to the lists of subcategories and pages contained in the category. Similarly, watching an [[Help:Files|file]] will not detect uploads of new versions of the file.
*Additional page titles may sometimes appear on your watchlist as a result of page moves (see [[#Moves, creations and deletions|Moves, creations, and deletions]] below).
*When a watched page contains transcluded text, such as [[Help:Templates|templates]], the form of the page may change as a result of changes to the transcluded pages. These changes will not show up on your watchlist unless you are watching the transcluded pages as well.

==== Watching all pages in a book ====
For watching all pages in a particular book, see [[Using Wikibooks/How To Edit A Wikibook#Watching All Pages in a Book]].

===How to read a watchlist===
When you are [[WB:LOGIN|logged in]] to Wikibooks, a link, &lt;code&gt;my watchlist&lt;/code&gt; appears at the top of every page.
This links to the special page [[Special:Watchlist]], reporting recent changes to your watched pages.  It is a list separated by days, ordered backwards according to the time of the edit. 

Each line shows details of each edit: whether [[Help:Editing#Minor edit|minor]] ('''m'''), whether made by a [[Wikibooks:Bots|bot]] ('''b'''), the time, a link to the page, a link to the difference (&quot;[[#Diff|diff]]&quot;) made by the edit in question, a link to the page history (&quot;[[#Page history|hist]]&quot;), the editor's user name or IP address, the increase (green) or decrease (red) in the number of [[w:bytes|bytes]], e.g. &lt;span class='mw-plusminus-pos'&gt;(+76)&lt;/span&gt;, &lt;span class='mw-plusminus-neg'&gt;(-490)&lt;/span&gt; or, if over 500, in bold: &lt;strong class='mw-plusminus-pos'&gt;(+794)&lt;/strong&gt;, &lt;strong class='mw-plusminus-neg'&gt;(-2,412)&lt;/strong&gt;, and the [[Help:Editing#Edit summary|edit summary]].  Technically, the watchlist is just another way to filter [[#Recent changes|recent changes]].

===Options===
There are various options available to control how the list of changes is displayed:
*You may choose to hide or show minor edits, bot edits, one's own edits, edits by anonymous users, and edits by logged-in users (links for this purpose appear at the top of the watchlist page). Initially the default behavior for all of these is &quot;show&quot;; this can be changed using the options available on the &quot;Watchlist&quot; tab of your user preferences.
*You can choose how many hours or days you want the list of changes to go back, using the links at the top of the watchlist. For the maximum (30 days), select &quot;all&quot;. For non-standard values, select one of the available links and then edit the value after &quot;days=&quot; in the [[w:URL|URL]]. The default value, which must be a number of days not greater than 7, is set on the &quot;Watchlist&quot; tab of user preferences. Note that there may be a later cut-off due to the limit on the number of displayed changes, described below.  
*You can restrict the list to changes in a specified [[Help:Pages#Namespaces|namespace]], using the &quot;Namespace&quot; drop-down box (check &quot;Invert selection&quot; to ''exclude'' the specified namespace).
*You can elect to display only the last edit to each watched page (&quot;Simple watchlist&quot;). This is currently the default, but can produce misleading results (for example, if the last edit to a page was minor, then there is no indication that a previous non-minor edit occurred). ''To ensure that all changes are displayed, check the &quot;Expand watchlist...&quot; option on the &quot;Watchlist&quot; tab of your user preferences.''
*Having selected the expanded watchlist, you can choose &quot;[[#Enhanced recent changes|enhanced]]&quot; display mode, which groups together all changes made to each page on a given day. Click on the blue arrows to the left of the list to expand or collapse each group. This option applies to both the watchlist and recent changes, and for this reason appears on the &quot;Recent changes&quot; tab of user preferences, not the &quot;Watchlist&quot; tab.
*You may choose to set the &quot;Maximum number of changes to show in expanded watchlist&quot; (on the &quot;Watchlist&quot; tab of user preferences). The maximum possible number of changes to display is currently 1000. If this causes a later time cutoff than you desired, you can see earlier changes by filtering by type or namespace, as described above.

===Effects of watching a page===
When you view [[#Recent changes|Recent Changes]], [[#Enhanced recent changes|Enhanced Recent Changes]] or [[#Related changes|Related Changes]], entries relating to pages you are watching appear '''bolded'''. This means that it may be beneficial to mark pages as &quot;watched&quot; even if you do not intend viewing the [[Special:Watchlist]] page.

===Moves, creations, and deletions===
Actions affecting watched pages (page [[WB:MOVE|moves]], page [[WB:CREATE|creations]] and [[WB:DEL|deletions]], [[Help:Editing#Protected pages|protection]]) also appear in the watchlist. For example, if you watch a page that does not yet have a talk page, you will see on your watchlist when someone creates that talk page. 

You can watch a page even if neither the content page nor the talk page exists. To do that, go to the page's URL, either by typing the URL directly or following a (broken) link, and then press the watch button.

If a page you have watched is moved to a new title, the new title will be automatically added to your watchlist.  Even if the page is later moved back (and even if the page at the new title is deleted), the new title will remain in your watchlist along with the old one. If you notice mysterious nonexistent pages appearing on your watchlist, this is the most likely explanation.

===Alternatives to watchlists===
An account can have only one watchlist. However, it is possible to set up watchlist-like functionality using the &quot;[[#Related changes|Related changes]]&quot; feature, in a way that effectively enables a user to achieve multiple watchlists. To do this, create a page (normally in your own [[Wikibooks:User pages|user space]]) containing links to the pages you wish to watch. Changes to those pages can then be monitored by going to the user page and clicking &quot;Related changes&quot;. Note that in this case the talk pages corresponding to &quot;watched&quot; pages are ''not'' automatically included (though [[Template:La2]] can be used to do so), and that changes to the user page itself will not be picked up.

Related Changes can also be used to monitor changes to pages belonging to a [[Help:Categories|category]], including the addition of pages to the category (which is not picked up by placing the category on a watchlist). However, the removal of pages from the category is ''not'' detected.

==Page history==
{{shortcut|WB:PH}}

Every editable page on Wikibooks has an associated '''page history''' (sometimes called '''revision history''' or '''edit history'''), which is accessed by clicking the &quot;history&quot; tab at the top of the page. The page history contains a list of the page's previous revisions, including the date and time (in [[w:UTC|UTC]]) of each edit, the username or IP address of the user who made it, and their [[Help:Editing#Edit summary|edit summary]]. 

=== Using a history page ===
On a history page:
*All past changes to the page in question are listed in reverse-chronological order. 
*To view a specific version, click a date.
*To compare an old version with the current version, click '''cur'''.
*To compare a version with its predecessor, click '''prev'''.
*To compare two specific versions, tick the left-column radio button of the older version and the right-column radio button of the newer version, and then click the &quot;Compare selected versions&quot; button.
*[[Help:Editing#Minor edit|Minor edits]] are denoted as '''m'''.

Below is a detailed example of a page history using the default skin:

[[File:Screenshot page history.png|900px]]

Edits are shown from newest to oldest. Each edit takes up one line which shows; time &amp; date, the contributor's name or IP and the [[Help:Editing#Edit summary|edit summary]], as well as other diagnostic information.
Let's look at some of the functions of this page:
# &quot;Revision history of&quot; is added to the page name and the &quot;View History&quot; tab is highlighted.
# These links take you to the most recent edits ''(Latest)'', oldest edits ''(Earliest)'' or the next or previous page of edits ''(Next n / Previous n)''. Note that the black text in parentheses will become links, when applicable.
# The blue numbers list the number of edits displayed on a page - 20, 50, 100, 250 or 500. A higher number increases the length of a page but reduces the number of pages The number you select replaces ''n'' in the links to the previous or next pages, e.g., ''(Next 100 / Previous 100)''.
# ''(cur)'' takes you to a [[#Diff|diff]] page, showing the difference between that edit and the current version. The current revision appears below the changes, so you can see how the page is now rendered.
# ''(prev)'' takes you to a diff page showing the changes between that edit and the previous version. The most recent version (the one on the same line as the &quot;last&quot; you clicked on) appears below the changes, so you can see how the page was rendered.
# The two columns of [[w:radio button|radio buttons]] can be used to select any two versions on the page. The current selection is marked by a special background. The two most recent versions are selected by default when you first view the history (that is why they appear framed and have a different background, see horizontal area around 4 and 6). Let's say you want to compare the versions corresponding to numbers 10 &amp; 11 on the image. First, click the left radio button next to number 11. The right column of buttons will then fill as far as number 11. Then click the right button next to number 10. Finally, click ''Compare selected versions''. This takes you to a diff page showing the changes between the two versions. The most recent version (in this case number 10) appears below the changes, so you can see how the page was rendered.
# This gives the time and date of the edit, expressed in local time according to the preference setting. The date and time link to the version of that day and time. Thus, the  first line links to the version that was current at the time of loading this revision history, and therefore the result may differ from that of following the link on the page margin to the current version. Even if the page has not changed in the meantime, the [[MediaWiki:Revision-info|Revision-info message]] appears.
# The username or IP  of the contributor appears here.
# This is the edit summary. It is the text the user wrote in the edit summary box (below the edit box).
# This edit summary begins with an arrow link and grey text. This means the user has only edited a section of the page (named in the grey text). This text is automatically added when you edit a section. A standard edit summary can be added by the user. This appears in black text.
# '''m''' stands for minor edit.

It is possible to restore an old version of a page by following the link to that version, clicking &quot;edit&quot; and then saving. This should be done with caution, as it means that ''all'' changes made to the page since the time of that version will be lost.

In rare cases, all or part of a page history entry may be shown in grey, struck out by a horizontal line. This indicates that information has been hidden from public view by an [[Wikibooks:Administrators|administrator]].

===Moved and deleted pages===
When a page is [[WB:MOVE|moved]] (renamed), the entire edit history of the page, before and after the move, is shown. The old title becomes a [[WB:REDIRECT|redirect]] and loses its edit history. 

If instead of a move, the entire content was [[w:cut and paste|cut and paste]]d into a new substitute page, the page history gets spread across two pages. The histories can be merged in this case.

When two pages are merged, typically one becomes a redirect. In this case, the revision history of the redirect is kept.

When a page is deleted, its revision history remains in the database and can be retrieved by an administrator, who can also undelete the page.

Administrators can also remove selected revisions from a page history, for example if they contain defamatory text.

===Files===
A file can be edited, or, more generally, be replaced by a different file, by uploading a new file with the same name. Again, all versions are kept. The file's history listing forms part of the [[Help:Files#File page|description page]], which appears when clicking on the file. The file's history consists of this and the old versions themselves.

===Linking to a specific version===
It is sometimes useful to link to a specific version of a page (a snapshot of it). For example, one might have done a [[#Reviewing pages|review]] of a Wikibooks page and want to indicate which particular version was reviewed. 

If the version is not the current version, one can use the page history to view the old version of the page. The URL of this old version is suitable for use to permanently reference this version, and can usually be obtained from the browser's location bar.

However, if a page contains transcluded text (such as a [[Help:Templates|template]]), or a time-based [[Help:Variables|variable]] (such as &lt;nowiki&gt;CURRENTTIME&lt;/nowiki&gt;), it will be rendered according to the current state of the template or the time now, possibly producing a different result than was rendered at the time the old version was saved.

==User contributions==
{{shortcut|WB:CONTRIBS}}

'''User contributions pages''' are automatically generated pages that list the edits that a particular user has made.

You can check your own contributions to refresh your memory about which pages you have worked on (and to easily access these again), and also to find out whether there have been any subsequent edits (see [[#Page history|page history]]). This can be a useful quick alternative to accessing your [[#Watching pages|watchlist]], particularly if your watchlist contains a large number of pages. Other users' user contribution pages can also be accessed and are useful for seeing how other users have contributed. They can be used to track down [[Wikibooks:Vandalism|vandalism]], serial [[WB:COPYVIO|copyright violations]], etc.

===Accessing a user contributions page===
To access your own user contributions page, click &quot;my contributions&quot; at the top of the page, or visit [[Special:MyContributions]].

To access the contributions of a [[WB:LOGIN|logged-in]] user (named account), go to the user page (User:XXX) and click on &quot;User contributions&quot; listed under the &quot;Toolbox&quot; menu on the left-hand side of the screen. This works even if the user page has not been created yet (i.e. an edit box displays).

To access the contributions of an anonymous user (identified by [[w:IP address|IP address]]), use one of the following methods:
* Click on the IP address where it appears on your [[#Watching pages|watchlist]], in [[#Recent changes|Recent changes]] or in [[#Page history|Page history]].
* Put the IP address in the search box and press Enter on your keyboard.
*If the user is currently [[Wikibooks:Blocking policy|blocked]], a notice will be displayed at the very top of the contributions screen [[Special:Contributions/Willy on Wheels!|like this example]].

Bear in mind that a public IP address may have been used by different users at different times. (And conversely, that a given user may have used multiple IP addresses and/or usernames.)

===Appearance of a user contributions page===
Below is an example of a user contributions page:

[[File:User contributions en-wikibooks.png|Example of a user contributions page]]

# The username or IP of the contributor
# A search form, allowing you to search by username, IP address (or range), date, or [[Help:Pages#Namespaces|namespace]] (such as ''Template''). IP range search uses a [[w:wildcard character|wildcard]] asterisk, such as ''10.11.12.*'' or ''192.168.*''. This requires you are logged in and check &quot;Allow /16 and /24 – /32 CIDR ranges on Special:Contributions forms (uses API), as well as wildcard prefix searches&quot; under Gadgets in [[Special:Preferences]].
# A list of edits, shown from newest to oldest. Each edit takes up one line which contains:
# The time and date of the edit, displayed in your preferred format.
# ''(hist)'' takes you to the [[#Page history|page history]], so you can see all edits made to that page. This can be useful if someone has updated a page you have worked on, and you want to see their changes.
# ''(diff)'' takes you to a [[#Diff|diff]] page showing the changes between that edit and the previous revision. The revision after the edit appears below the changes so you can see the result of the edit.
# '''m''' indicates a [[Help:Editing#Minor edit|minor edit]]; '''N''' indicates a new page.
# The current name of the page that was edited.
# The [[Help:Editing#Edit summary|edit summary]], a description written by the editor (or generated automatically, in certain cases). If a summary begins with an arrow link and grey text, the user has only edited the stated [[Help:Editing#Section|section]] of the page. Wikibooks automatically adds this when you edit a section.
# '''(top)''' signifies that the edit is the current revision. The page is as the user last saved it. This can be used to watch pages (if your last edit to the page does not display '''(top)''', the page has been changed).
# If an editor has made more edits than will fit on one page, this line provides links to the most recent edits ''(latest)'', oldest edits ''(earliest)'' or the next or previous page of edits ''(newer n / older n)''.
# The blue numbers list the number of edits displayed on a page: 20, 50, 100, 250 or 500. The number you select replaces ''n'' in the links to the previous or next pages e.g. ''(newer 100 / older 100)''. Views of up to 5000 edits per page are possible by modifying the URL.

[[Wikibooks:Administrators|Administrators]] and other users with special tools may have additional options on contributions pages.

The following information normally does not appear:
* Edits from a page that has been deleted afterwards (unless the page, including the revision concerned, has been restored).
* Uploading of a new file with the same name as one that already exists, thus replacing it
* Deletion or restoration (undeletion) of a page (if the user is an administrator). Use [[Special:Logs]] or click &quot;Logs&quot; on the user contributions page for viewing these actions.

=={{anchor|Diff|Diffs}}Viewing diffs==
{{shortcut|WB:DIFF}}

A '''diff''' is a page or panel showing the difference between two versions of the wikitext of an editable page.

Links to the diffs corresponding to specific edits appear in various lists, including [[#Page history|page histories]], a user's [[#User contributions|contributions]], [[#Recent changes|Recent Changes]], [[#Related changes|Related Changes]], and [[#Watching pages|watchlists]]. There may also be links to the diffs between the specified version and the current (last) version. In page histories it is possible to generate a diff between ''any'' two versions – select the left [[w:radio button|radio button]] for the older version, the right radio button for the newer version, and click ''Compare selected versions''.

Diffs can also be displayed while editing a page, via the ''Show changes'' button, to see clearly what changes you are about to make. The diff is also shown during an [[Help:Editing#Edit conflict|edit conflict]], so you can see exactly what you need to reintegrate.

===Appearance of diffs===
This example shows the top of the diff page (some of the links are dummies). The older version is shown on the left, the newer version on the right.
&lt;blockquote style=&quot;border:1px solid black; padding: 1em;&quot;&gt;
{| style=&quot;border:none; padding:4px;&quot;
|- style=&quot;text-align:center;&quot;
| colspan=&quot;2&quot; style=&quot;width:50%;&quot; | &lt;span style=&quot;background:#f0f8ff;;{{Text default color}}; font-weight:bold;&quot;&gt;[checked revision]&lt;/span&gt;&lt;br /&gt;&lt;strong&gt;[[#Page history|Revision as of 22:32, Aug 03, 2003]] ([[Help:Editing|edit]])&lt;/strong&gt;&lt;br/&gt;
[[User:Example|Example]] ([[User_talk:Example|Talk]] | [[#User contributions|contribs]])&lt;br/&gt;
&lt;span class=&quot;comment&quot;&gt;([[Help:Editing#Edit summary|Edit summaries]] in diffs are great)&lt;/span&gt;&lt;br/&gt;
← [[#Page history|Previous edit]]
| colspan=&quot;2&quot; class=&quot;diff-ntitle&quot; |&lt;span style=&quot;background:#f9f9f9;{{Text default color}}; font-weight:bold;&quot;&gt;[pending revision]&lt;/span&gt;&lt;br /&gt;&lt;strong&gt;[[#Page history|Revision as of 00:10, Aug 18, 2003]] ([[Help:Editing|edit]]) ([[Help:Editing#Reverting|undo]])&lt;/strong&gt;&lt;br/&gt;
[[User:Angela|Angela]] ([[User_talk:Angela|Talk]] | [[#User contributions|contribs]])&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;'''['''[[Help:Editing#Rollback|rollback]]''']'''&lt;br/&gt;
&lt;span class=&quot;minor&quot;&gt;m&lt;/span&gt;  &lt;span class=&quot;comment&quot;&gt;(correction, + [[MediaWiki User's Guide]])&lt;/span&gt;&lt;br/&gt;
|-
| colspan=&quot;2&quot; | '''Line 8:'''
| colspan=&quot;2&quot; | '''Line 8:'''
|- 
| style=&quot;text-align:right;&quot; | 
| style=&quot;background: #eee;{{Text default color}};font-size: smaller&quot; |  For administrators, a &lt;nowiki&gt;[[Help:Editing#Rollback|rollback]]&lt;/nowiki&gt; button is shown allowing them to revert from the new version to the old one.
| style=&quot;text-align:right;&quot; | 
| style=&quot;background: #eee;{{Text default color}};font-size: smaller&quot; |  For administrators, a &lt;nowiki&gt;[[Help:Editing#Rollback|rollback]]&lt;/nowiki&gt; button is shown allowing them to revert from the new version to the old one.
|- 
| style=&quot;text-align:right;&quot; | &amp;nbsp;
| style=&quot;text-align:right;&quot; | &amp;nbsp;
| style=&quot;text-align:right;&quot; | &amp;nbsp;
| style=&quot;text-align:right;&quot; | &amp;nbsp;
|- 
| style=&quot;text-align:right;&quot; | -
|style=&quot;background: #ffa;{{Text default color}};font-size: smaller;&quot; | This is only shown when viewing the diff between the &lt;span style=&quot;color: red;font-weight: bold&quot;&gt;current &lt;/span&gt;version and the one &lt;span style=&quot;color: red;font-weight: bold&quot;&gt;immediately preceding it&lt;/span&gt;.
|align=&quot;right&quot; | +
|style=&quot;background: #cfc;{{Text default color}};font-size: smaller;&quot; | This is only shown when viewing the diff between the &lt;span style=&quot;color: red;font-weight: bold&quot;&gt;recent &lt;/span&gt;version &lt;span style=&quot;color: red;font-weight: bold&quot;&gt;of a page &lt;/span&gt;and &lt;span style=&quot;color: red;font-weight: bold&quot;&gt;the last version by an author other than &lt;/span&gt;the one &lt;span style=&quot;color: red;font-weight: bold&quot;&gt;of the most current version&lt;/span&gt;. 
|-
| style=&quot;text-align:right;&quot; | 
| style=&quot;background: #eee;{{Text default color}};font-size: smaller&quot; |This example shows the top of the diff page, with links the described above.
| style=&quot;text-align:right;&quot; | 
| style=&quot;background: #eee;{{Text default color}};font-size: smaller&quot; |This example shows the top of the diff page, with links the described above.
|-
| colspan=&quot;2&quot; | '''Line 25:'''
| colspan=&quot;2&quot; | '''Line 25:'''
|- 
| style=&quot;text-align:right;&quot; | 
| style=&quot;background: #eee;{{Text default color}};font-size: smaller;&quot; | &lt;nowiki&gt;&lt;/table&gt;&lt;/nowiki&gt;
| style=&quot;text-align:right;&quot; |
| style=&quot;background: #eee;{{Text default color}};font-size: smaller;&quot; | &lt;nowiki&gt;&lt;/table&gt;&lt;/nowiki&gt;
|- 
| style=&quot;text-align:right;&quot; | 
| style=&quot;text-align:right;&quot; | 
| style=&quot;text-align:right;&quot; | +
|style=&quot;background: #cfc;{{Text default color}};font-size: smaller;&quot; | &lt;nowiki&gt;[[MediaWiki User's Guide]]&lt;/nowiki&gt;
|- 
| style=&quot;text-align:right;&quot; | 
| style=&quot;text-align:right;&quot; | 
| style=&quot;text-align:right;&quot; | +
| style=&quot;background: #cfc;{{Text default color}};font-size: smaller;&quot; | 
|}
&lt;/blockquote&gt;

==== Explanation of colors ====
Unchanged text is black on grey (only parts before and after changed text are shown). Paragraphs which have changed are highlighted in yellow on the old version side, and green on the new version side. Where whole paragraphs have been removed or inserted, the other side is blank (white). Removed text is shown in red on the old version. New text is shown in red on the new version.

{| class=&quot;wikitable&quot;
|+ Color key
! style=&quot;text-align:center; width:200px;&quot; | Old version
! style=&quot;text-align:center; width:200px;&quot; | New version
|-
| style=&quot;text-align:center; background:#eee;{{Text default color}};&quot; |unchanged
| style=&quot;text-align:center; background:#eee;{{Text default color}};&quot; |unchanged
|-
| style=&quot;text-align:center; background:#FFa;{{Text default color}};&quot; |paragraph changed
| style=&quot;text-align:center; background:#cfc;{{Text default color}};&quot; |paragraph changed
|-
| style=&quot;text-align:center; background:#FFa;{{Text default color}};&quot; |paragraph removed
| style=&quot;text-align:center; background:#ffffff;{{Text default color}};&quot; |&amp;nbsp;
|-
| style=&quot;text-align:center; background:#ffffff;{{Text default color}};&quot; |&amp;nbsp;
| style=&quot;text-align:center; background:#cfc;{{Text default color}};&quot; |paragraph added
|-
| style=&quot;text-align:center; color: red&quot; |removed text
| style=&quot;text-align:center; color: red&quot; |added text
|}

==== Controls and links ====
The links &quot;Revision as of ''date''&quot; link to each version. If the newer version is the latest one, the link will be to the usual page and the wording will be &quot;Current revision (''date'')&quot; instead.  For administrators and [[Wikibooks:Reviewers|reviewers]], a  revision with &quot;[checked revision]&quot; above it has been [[#Reviewing pages|reviewed]] while a revision with &quot;[pending revision]&quot; above it has not yet been reviewed.  Revisions with &quot;[unreviewed revision]&quot; above them occur on a page where no revision at all has been reviewed.

The &quot;(edit)&quot; link will take you to the page for editing that version. You may be warned that you are editing an out-of-date revision; if you ignore this and continue, you will revert all the edits made since after that revision. 

The &quot;(undo)&quot; link on the newer revision's side will [[Help:Editing#Reverting|revert]] that specific edit. When you click the link you can check the diff page of the edit you are going to make, and the [[Help:Editing#Edit summary|edit summary]] will be automatically filled in with the phrase of [[MediaWiki:undo-summary]] ({{MediaWiki:undo-summary}}). This summary can be edited before you submit your edit. When you are undoing several edits at once, the auto-summary may not work. Though the link exists on all diff pages, it does not function when the revisions conflict. Often versions older than the current one cannot be undone in this way. If it does not work, you will be told that the edit could not be undone and end up in the regular editing page of the current version.

Below that are links to the user page and talk page of the each user who edited the older or the newer versions. Links to the users' contribution lists are also shown. For administrators and [[Wikibooks:Reviewers|reviewers]], a &quot;[rollback]&quot; button also appears where applicable, allowing them to revert all of the edits made by that user.

Then the [[WB:ES|edit summaries]] are shown in a parenthesis. If the user has used links in their edit summary, these act as links on the diff page as well. If the editor marked the edit as an [[WB:MINOR|minor edit]], &lt;span class=&quot;minor&quot;&gt;m&lt;/span&gt; appears before the summary.

The &quot;Previous edit&quot; and &quot;Next edit&quot; links lead to earlier or later diffs. When you are viewing the diff between two non-consecutive versions of a page, you will also see the message &quot;(x intermediate revisions not shown.)&quot;.

After the table of differences, the latest of the two compared versions is shown fully, unless you have specified in your preferences that this is not to be done.

===Linking to a diff===
If you need to create a link to a specific diff (for use on a talk page or noticeboard, for example), then locate the diff from the [[#Page history|page history]], go to the diff page, and copy the [[w:URL|URL]] from your browser's address bar. Then paste this URL (the whole of it, including &lt;nowiki&gt;http://&lt;/nowiki&gt;) into the text of the page where you want the link to appear, putting single square brackets [...] around it.

The URL for a diff is based on the &lt;code&gt;oldid&lt;/code&gt; value of the old revision. If a revision has oldid value 12345678, so its URL is:

*&lt;code&gt;&lt;nowiki&gt;http://en.wikibooks.org/w/index.php?title=PAGETITLE&amp;oldid=12345678&lt;/nowiki&gt;&lt;/code&gt;

then URLs for its diffs may take the forms:

*diff with the current version: &lt;code&gt;&lt;nowiki&gt;http://en.wikibooks.org/w/index.php?title=PAGETITLE&amp;diff=cur&amp;oldid=123456789&lt;/nowiki&gt;&lt;/code&gt;
*diff with the previous version: &lt;code&gt;&lt;nowiki&gt;http://en.wikibooks.org/w/index.php?title=PAGETITLE&amp;diff=prev&amp;oldid=123456789&lt;/nowiki&gt;&lt;/code&gt;
*diff with version 10000001: &lt;code&gt;&lt;nowiki&gt;http://en.wikibooks.org/w/index.php?title=PAGETITLE&amp;diff=100000001&amp;oldid=123456789&lt;/nowiki&gt;&lt;/code&gt;

Another way of creating links to diffs is described at [[Template:Diff]].

The previously described means will generate ''external'' links.
For an ''internal'' link write
* &lt;code&gt;&lt;nowiki&gt;[[Special: Diff/100000001]]&lt;/nowiki&gt;&lt;/code&gt; for a link to a specific diff
* &lt;code&gt;&lt;nowiki&gt;[[Special: Diff/100000001/123456789]]&lt;/nowiki&gt;&lt;/code&gt; for a comparison of two revisions.
You can format such links like any internal link, that means you may define a label so something like {{nowrap|&lt;code&gt;&lt;nowiki&gt;[[Special: Diff/1|very first edit]]&lt;/nowiki&gt;&lt;/code&gt;}} will emit [[Special: Diff/1|very first edit]].
See the [https://www.mediawiki.org/wiki/Help:Diff MediaWiki documentation on “Diff”] for more details.

==Reviewing pages==
{{shortcut|WB:REVIEW|WB:FR}}
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;''See also [[mw:Help:Extension:FlaggedRevs|FlaggedRevs extension help at MediaWiki]]''

The ''pending changes'' system (also known as ''edit review'' and ''flagged revisions'') was a system that allowed ''reviewers'' to review page revisions for quality. This has since been deprecated on this site in favour of a standard patrolling system, similar to that found on Wikimedia Commons and many other sister projects.

Regular contributors were automatically given [[Wikibooks:Reviewers|reviewer status]] by the software. Reviewers automatically patrol pages when they save, so active books will usually have contributions by non-reviewers patrolled shortly after they are committed.
&lt;!--
Pages can be ‎reviewed by pressing the &lt;span class=&quot;flaggedrevs-pending&quot;&gt;'''[review]'''&lt;/span&gt; link on pages like [[Special:RecentChanges]] and [[Special:Watchlist]]. Otherwise, pages can also be reviewed by using the following technique (which is needed if the page is previously unreviewed):
# Go to the bottom of the page.
# There should be a &quot;Review this revision&quot; dialog. 
# Press the &quot;Accept revision&quot; button.

===Stable version===
Except for the Wikijunior namespace, by default the latest version of a page, reviewed or not, is shown to readers. In the Wikijunior namespace, by default readers are served only the last reviewed version of a page (if there is a reviewed version, otherwise the latest unreviewed version; but on Wikijunior we try to be sure there is a reviewed version). This is called the ''stable version''. [[Wikibooks:Administrators|Administrators]] are able to change the settings for pages so that the stable version (the latest reviewed version of a page) is shown by default to logged-out readers. For logged-in readers, whether the stable version or latest version is shown by default can be altered in [[Special:Preferences#mw-prefsection-rc|preferences]]. 

This is used primarily for [[Wikijunior]] books, but any book can opt in to this.  Regardless of what version is initially shown, in cases where there are pending unreviewed changes to a page, there will be tabs titled ''Read'' and ''Latest draft'' to switch between the stable version and the most recent edit.

=== Quality criteria and levels ===
A page can be reviewed based on its quality. Four levels of review are available for revisions, with each level incorporating the previous levels: 

*'''poor/unrated''': the default rating for unreviewed revisions, or for revisions that don't reach &quot;minimal&quot; quality.
*'''minimal''': proofread for spelling, punctuation, grammar, paragraph structure, and paragraph consistency; it is also the default for certain actions (see below).
*'''average''': typography and language is found to be consistent with the book's [[Help:Local manuals of style|local manual of style]], but not thoroughly examined otherwise.
*'''good''': thoroughly examined to ensure ideas and concepts are consistent, neutral, accurate, and verifiable.

Please note that &quot;minimal&quot; does '''not''' necessarily refer to the quality of the revision, but can instead refer to the '''quality of the review itself''', in other words how thoroughly it is carried out. &quot;Minimal&quot; is also the default level for contributions from editors who hold the &lt;code&gt;autoreview&lt;/code&gt; right; other editors will default to &quot;poor/unrated&quot;. &quot;Minimal&quot; reviews can also occur during patrols for basic quality control of revisions; these include basic checks for:

* [[Wikibooks:VANDALISM|Vandalism and spam]].
* Potentially inaccurate information, or other potential errors.
* Potential problems with conforming to various [[Wikibooks:Policies and guidelines|policies and guidelines]].

If most of the pages in a book have a revision that has been flagged as &quot;good&quot;, the book may be a good candidate to be nominated as a [[WB:FB|featured book]].

As a non-enforceable but documented bit of culture, reviewers are discouraged from reviewing pages in books at the &quot;good level&quot; (called ''approving a page'') if the book contributors do not want to take part in having their pages reviewed.  The good level may be useful as a matter of internal review by the book contributors, or an external review such as in a request to have the book be [[Wikibooks:Good books|featured]], etc.

===Monitoring reviewing===
* [[Special:Log/review]]: logs of page reviews
* [[Special:ValidationStatistics]]: page review statistics
* [[Special:PendingChanges]]: pages with pending changes
* [[Special:UnreviewedPages]]: unreviewed pages (reviewers/administrators only)
* [[Special:ConfiguredPages]]: pages with review configurations

===Edit review interface===
A user can configure whether the interface for indicating a page's review status is detailed or minimal in [[Special:Preferences]], influencing the way pages in Wikibooks appear.

{{gallery
|width=400
|height=100
|lines=1
|File:Unreviewed version detailed.png|alt1=Full bar across screen with a grey circle stating &quot;This page may need to be reviewed for quality&quot;.|Unreviewed version, detailed interface
|File:Unreviewed version minimal.png|alt2=Box in upper right with a grey circle stating &quot;Unreviewed&quot;.|Unreviewed version, minimal interface
|File:Reviewed version with pending detailed.png|alt3=The &quot;Read&quot; tab is selected.  Full bar across screen with a yellow eye stating &quot;This is the latest reviewed version, checked as on 9 December 2010.  There is 1 pending change awaiting review&quot;.|Reviewed version with pending edits, detailed interface
|File:Reviewed version with pending minimal.png|alt4=The &quot;Read&quot; tab is selected. Box in upper right with a yellow eye stating &quot;Checked [review pending changes]&quot;.|Reviewed version with pending edits, minimal interface
|File:Pending version detailed.png|alt5=The &quot;Latest draft&quot; tab is selected. Full bar across screen with a grey circle stating &quot;This is the latest reviewed version, checked as on 9 December 2010.  There is 1 pending change awaiting review&quot;.|Viewing the pending version of a reviewed page, detailed interface
|File:Pending version minimal.png|alt6=The &quot;Latest draft&quot; tab is selected.  Full bar across screen stating &quot;This is a pending revision of this page.  It was last reviewed at 9 December 2010.  This version may differ slightly from the latest reviewed revision.&quot;|Viewing the pending version of a reviewed page, minimal interface
|File:Reviewed version configured no pending detailed.png|alt7=Full bar across screen with a magnifying glass over papers and a yellow eye stating &quot;This is the latest reviewed version, checked on 13 December 2010&quot;.|Reviewed page configured to show reviewed by default, detailed interface
|File:Reviewed version configured no pending minimal.png|alt8=Box in upper right with a magnifying glass over papers and a yellow eye stating &quot;Checked&quot;.|Reviewed page configured to show reviewed by default, minimal interface
|File:Reviewed version no pending.png|alt9=No bar or box visible on this page.|Reviewed page with no pending edits (same for both interfaces)
|File:Reviewing toolbar unreviewed revision.png|alt10=Radio buttons for quality, allowing choices for poor/unrated, minimal, average, and good.  Button to submit review titled &quot;Accept revision&quot;.|Reviewing toolbar for unreviewed revision
|File:Reviewing toolbar reviewed revision.png|alt11=Radio buttons for quality, allowing choices for poor/unrated, minimal, average, and good.  Button to submit new review titled &quot;Accept revision&quot; or remove current review titled &quot;Unaccept revision&quot;.|Reviewing toolbar for reviewed revision
|File:Diff reviewing toolbar.png|alt12=Box stating &quot;Please review any pending changes (shown below) made since the latest reviewed revision.  Radio buttons for quality, allowing choices for poor/unrated, minimal, average, and good.  Button titled &quot;Accept revision&quot; and button titled &quot;Reject changes&quot;.|Reviewing toolbar above [[WB:DIFF|diff]] seen via &quot;review&quot; or &quot;pending changes&quot; links
}}
--&gt;
{{Wikibooks editor navigation}}</text>
      <sha1>00ht56oij3z52i987soo0idl6tahufk</sha1>
    </revision>
  </page>
  <page>
    <title>Help:Editing</title>
    <ns>12</ns>
    <id>50573</id>
    <revision>
      <id>4678504</id>
      <parentid>4678452</parentid>
      <timestamp>2026-10-27T15:47:52Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Edit toolbar */ Adding nowiki tags.</comment>
      <origin>4678504</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="68806" sha1="m568nt9qsn6264sgmri5d0qasrl0639" xml:space="preserve">{{shortcut|WB:EDIT}} {{Wikibooks help}}

Wikibooks is a [[w:Wiki|wiki]], which means that anyone can easily edit any unprotected page and save those changes immediately to that page. After your first edit, you are a Wikibooks editor! To request a change to a protected page, you may add your suggestion to the talk page. If you just want to experiment, please do so in the [[Wikibooks:sandbox|sandbox]].

Editing a Wikibooks page is very easy. Simply click on the ''Edit'' tab at the top of a Wikibooks page. This will bring you to a new page with a text box containing the editable text of the original page. Once you're done, write a short edit summary in the small field below the edit box. You may use shorthand to describe your changes, and when you have finished, press the ''Show preview'' button to see how your changes will look. You can also see the difference between the page with your edits and the previous version of the page by pressing the ''Show changes'' button. If you're satisfied with what you see, be bold and press the ''Save page'' button. Your changes will immediately be visible to other Wikibooks users.

{{TOC left|limit=3}} [[File:English Wikibooks editing.png|475px|thumb|center|What you'll see when you go to edit a page and choose the ''Edit'' option.]] {{Clear}}

== Composition of an edit page ==
The editing page consists of these sections:

* [[#Edit toolbar|Edit toolbar]]
* Editing text box
* [[#Edit summary|Edit summary]] box
* [[#Minor edit checkbox|Minor edit]], [[Help:Tracking changes#Watching pages|Watch this page]] checkboxes
* Save page, [[#Show preview button|Show preview]], [[Help:Tracking changes#Viewing diffs|Show changes]] buttons
* Cancel, Editing help links
* A list of [[Help:Template|template]]s used on the page
* A preview, if you have requested one. Your preferences may place the preview at the top of the page instead.

===Edit toolbar===
The '''edit toolbar''' above the editing text box helps you produce '''wiki markup''', instructions used to stylize text on a wiki page. In the edit toolbar above the editing text box seen when editing a page, if you click ''Help'' you can see what effects are possible with wiki markup. Another way you can learn how to produce specific effects is to click ''Edit'' on a page that contains the effect you wish to copy and see what markup is used.

{| class=&quot;wikitable&quot; style=&quot;width:100%;&quot;
 ! width=&quot;26%&quot; | Name
 ! width=&quot;36%&quot; | Markup
 ! width=&quot;37%&quot; | Displays
 |-
 ! colspan=&quot;3&quot; style=&quot;text-align:left; background-color:#cccccc;{{Text default color}};&quot; | Basic
 |-
 | [[File:Toolbaricon_bold_B.png|link=]] Bold
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;Make text '''bold'''&lt;/syntaxhighlight&gt;
 | Make text '''bold'''
 |-
 | [[File:Toolbaricon_italic_I.png|link=]] Italic
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;Make text ''italic''&lt;/syntaxhighlight&gt;
 | Make text ''italic''
 |-
 | [[File:Button_underline_he.png|link=]] Underline
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;Make text&lt;u&gt;underlined&lt;/u&gt;&lt;/syntaxhighlight&gt;
 | Make text &lt;u&gt;underlined&lt;/u&gt;
 |-
 | [[File:Vector_strikeout.png|link=]] Strikeout
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;s&gt;Strike out&lt;/s&gt; text&lt;/syntaxhighlight&gt;
 | &lt;s&gt;Strike out&lt;/s&gt; text
 |-
 | [[File:Vector_toolbar_insert_link_button.png|link=]] [[#Links|Link]]
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;Link to [[Help:Contents|a page]], [[#Sections|a section of a page]] or an [http://www.wikimedia.org external page].&lt;/syntaxhighlight&gt;
 | Link to [[Help:Contents|a page]], [[#Sections|a section of a page]] or an [http://www.wikimedia.org external page].
 |-
 | [[File:Vector toolbar insert image button.png|link=]] Embed [[Help:Files|file]]
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;[[File:Vector toolbar insert image button.png]]&lt;/syntaxhighlight&gt;
 | [[File:Vector toolbar insert image button.png]]
 |- 
 | [[File:Vector toolbar insert reference button.png|link=]] Insert [[#References|references]] 
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;Example text&lt;ref&gt;It is a note!&lt;/ref&gt;&lt;/syntaxhighlight&gt;
 | Example text&lt;span style=&quot;color:#002bb8&quot;&gt;&lt;sup&gt;[1]&lt;/sup&gt;&lt;/span&gt;
 |-
 | [[File:Vector toolbar signature button.png|link=]] Signature
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;Thanks guys --~~~~&lt;/syntaxhighlight&gt;
 | Thanks guys --[[User:Example|Example]] &lt;nowiki&gt;07:46, 27 November 2005 (UTC)&lt;/nowiki&gt;
 |-
 ! colspan=&quot;3&quot; style=&quot;text-align:left; background-color:#cccccc;{{Text default color}};&quot; | Advanced
 |-
 | &lt;span style=&quot;padding: 4px; color: #333; border:1px solid silver; background: white;{{Text default color}}; cursor: pointer&quot;&gt; Heading [[File:MediaWiki_Vector_skin_action_arrow.png|link=]]&lt;/span&gt; Dropdown list for headings of different levels
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;
== Level 2 (Section heading) ==
=== Level 3 ===
==== Level 4 ====
===== Level 5 =====&lt;/syntaxhighlight&gt;
 | {{hiddenh2|Level 2 (Section heading)}}{{hiddenh3|Level 3}}{{hiddenh4|Level 4}}{{hiddenh5|Level 5}}
 |-
 | &lt;span style=&quot;padding: 4px; color: #333; border:1px solid silver; background: white;{{Text default color}}; cursor: pointer&quot;&gt; Text Type [[File:MediaWiki_Vector_skin_action_arrow.png|link=]]&lt;/span&gt; Dropdown list for text or programming code of different types
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;tt&gt;Teletype text&lt;/tt&gt;, &lt;code&gt;inline code&lt;/code&gt;, &lt;source lang=&quot;text&quot;&gt;generic source code&lt;/source&gt;&lt;/syntaxhighlight&gt;
 | &lt;!--&lt;tt&gt;Teletype text&lt;/tt&gt;,--&gt; &lt;code&gt;inline code&lt;/code&gt;, &lt;syntaxhighlight lang=&quot;text&quot;&gt;generic source code&lt;/syntaxhighlight&gt;
 |-
 | [[File:Vector toolbar bulleted list button.png|link=]] Insert a bulleted [[#Lists|list]] item
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;* Bulleted list item&lt;/syntaxhighlight&gt;
 |
* Bulleted list item
 |-
 | [[File:Vector toolbar numbered list button.png|link=]] Insert a numbered [[#Lists|list]] item
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;# Numbered list item&lt;/syntaxhighlight&gt;
 | 
# Numbered list item
 |-
 | [[File:Vector toolbar indentation button.png|link=]] Text indentation
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;:Indented line&lt;/syntaxhighlight&gt;
 | 
:Indented line
 |-
 | [[File:Vector toolbar no wiki formatting button.png|link=]] Ignore wiki markup
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;nowiki&gt;&lt;math&gt;2^3&lt;/math&gt;&lt;/nowiki&gt;&lt;/syntaxhighlight&gt;
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;math&gt;2^3&lt;/math&gt;&lt;/syntaxhighlight&gt;
 |-
 | [[File:Vector toolbar insert new line button.png|link=]] Insert new line
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt; example &lt;br /&gt; text&lt;/syntaxhighlight&gt;
 | example &lt;br /&gt; text
 |-
 | [[File:Vector toolbar big text button.png|link=]] Big text
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;big&gt;Big text&lt;/big&gt;&lt;/syntaxhighlight&gt;
 | &lt;big&gt;Big text&lt;/big&gt;
 |-
 | [[File:Vector toolbar small text button.png|link=]] Small text
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;small&gt;Small text&lt;/small&gt;&lt;/syntaxhighlight&gt;
 | &lt;small&gt;Small text&lt;/small&gt;
 |-
 | [[File:Vector toolbar superscript button.png|link=]] Superscript text
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;sup&gt;Superscript text&lt;/sup&gt;&lt;/syntaxhighlight&gt;
 | &lt;sup&gt;Superscript text&lt;/sup&gt;
 |-
 | [[File:Vector toolbar subscript button.png|link=]] Superscript text
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;&lt;sub&gt;Subscript text&lt;/sub&gt;&lt;/syntaxhighlight&gt;
 | &lt;sub&gt;Subscript text&lt;/sub&gt;
 |-
 | [[File:Vector toolbar insert picture gallery button.png|link=]] Insert picture [[Help:Files#Galleries|gallery]]
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;
&lt;gallery&gt;
File:Example.jpg|Caption1
File:Example.jpg|Caption2
&lt;/gallery&gt;&lt;/syntaxhighlight&gt;
 |
&lt;gallery&gt;
File:Example.jpg|Caption1
File:Example.jpg|Caption2
&lt;/gallery&gt;
 |-
 | [[File:Vector toolbar insert table button.png|link=]] Insert [[Help:Tables|table]] (opens a configuration window to select the number of rows and columns and some other options)
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;
{| class=&quot;wikitable&quot;
|-
! Header text
|-
| Example
|}
&lt;/syntaxhighlight&gt;
 | 
{| class=&quot;wikitable&quot;
|-
! Header text
|-
| Example
|}
 |-
 | [[File:Vector toolbar redirect button.png|link=]] Page [[#Redirecting|redirect]]
 | &lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;#REDIRECT [[WB:HELP]]&lt;/syntaxhighlight&gt;
 | [[File:Redirect arrow without text.svg|link=|#REDIRECT]] [[WB:HELP]]
 |-
 | [[File:Vector toolbar search-replace button.png|link=]] Search and replace
 | Opens the search and replace window
 |}

==={{anchor|Edit summaries}}Edit summary===
{{shortcut|WB:ES|WB:SUMMARY}}
An '''edit summary''' is a brief explanation of an edit to a Wikibooks page. When you edit a page, there is a small text entry field, which is labeled &quot;Edit summary&quot;, located under the main edit box and above the &quot;Save page&quot; button. Edit summaries are displayed in lists of changes (such as [[Help:Tracking changes#Page history|page histories]] and [[Help:Tracking changes#Watching pages|watchlists]]), and at the top of [[Help:Tracking changes#Viewing diffs|diff]] pages.

It is good practice to fill in the &quot;Edit summary&quot; field, or add to it in the case of [[#Sections|section editing]], as this helps others to understand the intention of your edit. To avoid accidentally leaving edit summaries blank, you can select &quot;Prompt me when entering a blank edit summary&quot; on the Editing tab of your [[Special:Preferences|user preferences]], if you have created an account.

====Always provide an edit summary====
It is considered good practice to always provide an edit summary, but it is especially important when [[#Reverting|reverting]] the actions of other editors, or if you delete any text; otherwise, people may question your motives for the edit.

Accurate summaries help other editors decide whether it is worthwhile for them to check a change, and to understand it if they choose to check it. Summaries are less essential for &quot;[[#Minor edit|minor changes]]&quot;, but a summary like &quot;fixed spelling&quot; is helpful even then.

====Qualities of good summaries====
* ''Summarize''. Summarize the change, even if only briefly; even a short summary is better than no summary.
* ''Explain''. Give reasons for the change, if there is a reasonable chance that other editors may be unclear as to why it was made.
* ''Abbreviations''. Experienced users, especially those with many edits to make, will often use abbreviations in order to save time; for example, &quot;rv&quot; for &quot;[[#Reverting|revert]]&quot;, or shortcuts for Wikibooks policies and related pages, e.g., &quot;WB:WIW&quot; for [[Wikibooks:What is Wikibooks]] (see [[Wikibooks:Shortcuts]]). Abbreviations should be used with care, although they save one editor time they may cost readers much more time to figure out what they mean, they can be confusing for inexperienced users, but they are generally fine for small edits such as formatting and grammar changes.
* ''Talk pages''. When editing [[WB:TALK|talk pages]], consider copying your comment to the edit summary, especially if it is brief; this allows users to check Recent changes, Page history and User contributions very efficiently. It also reduces the load on the servers.
* ''Harmony between text and edit summary''. Make sure that important information is not only included in the edit summary. This applies especially on talk pages. Readers who only see the text may miss that important information, and they may then respond inappropriately through no fault of their own. Try to prevent misunderstandings. If an edit requires more explanation than will fit in the edit summary box, use the ''Discussion'' page instead, and put in the edit summary &quot;see talk&quot; or &quot;see discussion&quot;.
* ''Avoid misleading summaries''. Mentioning one change but not another one can be misleading to someone who finds the other one more important; add &quot;and misc.&quot; to cover the other changes.
* ''Avoid inappropriate summaries''. Editors should explain their edits, but not be overly critical or harsh when editing or reverting others' work. This may be perceived as uncivil, and cause tension or bad feelings, which makes collaboration more difficult. Explain what you changed, and cite the relevant policies, guidelines, or principles of good writing, but try not to single out others in a way that may come across as an attack.

====Properties====
* ''Limited to 200 characters''. The edit summary box can hold one line of 200 characters. If you attempt to type or paste more, only the first 200 characters will be displayed—the rest will be discarded. For example attempting to add 10 new characters (at the end or in between) to a summary already containing 195 characters will result in the first 5 new characters being inserted and the second 5 being disregarded.
* ''Can be previewed''. The [[#Show preview button|&quot;Show preview&quot; button]] also provides a preview of the edit summary to facilitate checking links.
* ''Can't be changed after saving''. After you save the page, you cannot change the edit summary.
* ''Doesn't appear in searches''. The [[WB:SEARCH|search function]] cannot search edit summaries, and they are not indexed by external search engines.
* ''Wikilinks always rendered; other wikitext coding ignored''. Text in edit summaries renders internal links, including [[#Pipe links|piped links]], and [[#Interwiki links|interwiki links]], even when enclosed within &lt;nowiki&gt;&lt;nowiki&gt; and &lt;/nowiki&gt;&lt;/nowiki&gt;. Therefore, copying wikitext in the edit summary box may be preferable to copying text from the preview, except when one wants to save space. Other wikitext coding is not interpreted.
* ''URLs''. When copying an external link from the preview into the edit summary box then, depending on the operating system, the &quot;printable version&quot; is copied, i.e., how it is normally rendered, and in addition, between parentheses, the URL; hence the same information as in the wikitext, but in a different format, as well as a possible sequential number.

=== {{anchor|Minor edits|Minor edit}}Minor edit checkbox ===

{{shortcut|WB:MINOR}}
A check to the '''minor edit''' box signifies that only superficial differences exist between the current version and the previous version.  Examples include typographical corrections, formatting and presentational changes, rearrangement of text without modification of content, etc. A ''minor edit'' is one that the editor believes requires no review and could never be the subject of a dispute, such as changing &quot;teh&quot; to &quot;the&quot;. An edit of this kind is marked in its page's [[Help:Tracking changes#Page history|revision history]] with a lower case, bolded &quot;m&quot; character ('''m''').

By contrast, a major edit is one that should be reviewed for its acceptability to all concerned editors. Therefore, any change that affects the ''meaning'' of a page is not minor, even if the edit concerns a single word; for example, the addition or removal of &quot;not&quot;, which can change the meaning of a sentence, is a major edit.

Because editors may choose to ignore minor edits when reviewing [[Help:Tracking changes#Recent changes|recent changes]], the distinction between major and minor edits is significant. Logged-in users might even set their preferences to not display minor edits. If there is any chance that another editor might dispute a change, it is best not to mark the edit as minor.

Users who are not [[WB:LOGIN|logged in]] to Wikibooks are not permitted to mark changes as minor because of the potential for vandalism. The ability to mark changes as minor is one of many reasons to register.

A good rule of thumb is that edits consisting solely of spelling corrections, formatting changes, or rearrangement of text without modification of content should be flagged as minor edits.

==== When to mark an edit as a minor edit ====
* Spelling and grammatical corrections.
* Simple formatting (''e.g.'', capitalization, punctuation, or properly adding italics to non-English words, like ''folie des grandeurs'').
* Formatting that does not change the meaning of the page (''e.g.'', moving a picture, splitting one paragraph into two—where this is not contentious).
* Obvious factual errors (''e.g.'', changing &quot;Nixon resigned in 1874&quot; to &quot;Nixon resigned in 1974&quot;).
* Fixing layout errors.
* Adding or correcting [[#Wikilinks|wikilinks]], or fixing broken references already present in the page.
* Removing [[Wikibooks:Vandalism|vandalism]] and graffiti.

==== Things to remember ====
* Any change to the source text, even if it does not affect the presentation of the page in [[HTML]] (if it involves adding a space or a line break, for example) will still be treated as a change according to the database.
* Marking a major change as a minor one is considered poor etiquette, especially if the change involves the deletion of some text.
* [[#Reverting|Reverting]] a page is not likely to be considered minor under most circumstances. When the status of a page is disputed, and particularly if an [[Help:Glossary#edit war|edit war]] is brewing, then it is better not to mark ''any'' edit as minor. Reverting blatant vandalism is an exception to this rule.
* If you ''accidentally'' mark an edit as minor when it was in fact a major edit, you should make a second edit, or dummy edit, noting in the dummy's edit summary that the previous edit was major. As a trivial edit to be made for this purpose, just opening the edit box and saving (''i.e.'' changing nothing) will not work; neither will adding a blank space at the end of a line or a blank line at the end of the page—in these cases the edit is cancelled and the edit summary discarded. However, one can, for example, add an extra space between two words.  This will be preserved in the wikitext and recorded as a change, although it will not change the page's appearance when rendered.
* It may be worth communicating any disagreement about what is minor via Talk or a message to the contributor, being careful to avoid a flame war (&quot;I thought your change was a bit more than minor—maybe I am being over-sensitive?&quot;). There is a grey area, and many contributors will appreciate feedback on whether they've got it right.
* Marking your change as minor affects how it displays in some [[Help:Tracking changes#Watching pages|editors' watchlists]].  If, for example, you mark your talk page comments as &quot;minor&quot;, then fewer editors are likely to notice your comment.

==== Exceptions ====
[[Wikibooks:Administrators|Administrators]] and [[Wikibooks:Reviewers|reviewers]] can semi-automatically revert the edits of the last editor of a page; all such [[#Rollback|rollback]] reversions are marked as minor by the wiki software. The intended use of the rollback feature is for cases of vandalism, where the act of reverting any vandalism should be considered minor (and can be ignored in the recent changes list).

==={{anchor|Showing previews|Show preview}}Show preview button===
{{shortcut|WB:PREVIEW}}
Below the edit box is a '''Show preview''' button. Pressing this will show you what the page will look like without actually saving it. It is strongly recommended that you use this prior to saving. This allows you to check what the page will look like first and to check that you haven't made any errors. It also prevents the need for multiple saves. Saving the same page numerous times in quick succession makes it harder for people to check what changed, and clogs up the [[Help:Tracking changes#Page history|page history]].

It is helpful, to save the page before moving, breaking apart, or combining sections of the page, if you have been making small edits to the page.  The difference display is not good at showing paragraph moves, and will not display the small edits clearly if sections are then moved around.

Saving only once is also a way of avoiding [[#Edit conflict|edit conflicts]], as people will not see the page on [[Help:Tracking changes#recent changes|recent changes]], and therefore they are less likely to try editing it at the same time as you.

If you are [[WB:LOGIN|logged in]], you can set your [[Special:Preferences|preferences]] to show the preview before the edit box instead of after it. If you select this option, the preview will be displayed above the edit box when you click the &quot;Show preview&quot; button while editing a page. See [[Help:Account management#Preferences]].

Using show preview also prevents your login timing out, which would mean your edits would not be attributed to your username. Clicking preview regularly will restart the timer, so you remain logged in. Also, if you are no longer logged in, showing a preview will make you aware of this so you can log in and save your work after that. You can check this by seeing if your username appears in the upper-right corner when you press preview. If you are not logged in, open [[Special:UserLogin]] in a separate window (right-click &quot;Log in&quot; and hit &quot;Open link in new window&quot; or similar). Log in, then go back to your editing and hit &quot;preview&quot; again to make sure all is well. Note that this will clear the minor edit and watch checkboxes, so make sure they're set appropriately again before you finally save the page.

When utilizing this feature during a major edit, consider copying the content into your [[w:clipboard (software)|clipboard]]. On extremely rare occasions, the Wikibooks servers have hiccups, and you could lose your work.

When pressing &quot;Show preview&quot;, a preview of the [[#Edit summary|edit summary]] is also obtained; thus (for example) links can be checked.

==Composition of a book page==
{{shortcut|WB:SECTION}}
==={{anchor|Section}}Sections===
'''Sections''' are created by creating their headings, as below.

&lt;pre&gt;
==Section==

===Subsection===

====Sub-subsection====
&lt;/pre&gt;
Please ''do not'' use only one equals sign on a side (&lt;nowiki&gt;=Heading=&lt;/nowiki&gt;). This would cause a section heading to be as large as the page's name (title).

Heading names of sections (including subsections) should be unique on a page. Using the same heading more than once on a page causes problems:
* An [[#Wikilinks|internal link (wikilink)]] to a section, in the form &lt;nowiki&gt;[[Pagename#Section heading]]&lt;/nowiki&gt;, will only link to the first section  on the page with that name, which may not be the intended target of the link. See [[#Section linking (anchors)|section linking]] on linking to a section.
* When a section with a duplicate name is edited, the [[Help:Tracking changes#Page history|edit history]] and [[#Edit summary|summary]] will be ambiguous as to which section was edited.
* When saving the page after a section edit, the editor's browser may navigate to the wrong section.

===={{anchor|TOC|Table of contents}}Table of contents (TOC)====
{{Shortcut|WB:TOC}}

For each page with more than three section headings, a '''table of contents (TOC)''' is automatically generated from the section headings, unless:
*(for a user) [[WB:PREFS|preferences]] are set to turn it off
*(for a page) the [[Help:Variables|magic word]] &lt;code&gt;&lt;nowiki&gt;__NOTOC__&lt;/nowiki&gt;&lt;/code&gt; (with ''two underscores'' on either side of the word) is added to the page

{{anchor|Positioning the TOC}}'''Positioning the TOC'''

When either &lt;code&gt;&lt;nowiki&gt;__FORCETOC__&lt;/nowiki&gt;&lt;/code&gt; or &lt;code&gt;&lt;nowiki&gt;__TOC__&lt;/nowiki&gt;&lt;/code&gt; (with ''two underscores'' on either side of the word) is placed in the wikitext, a TOC is added even if the page has fewer than four headings.

With &lt;code&gt;&lt;nowiki&gt;__FORCETOC__&lt;/nowiki&gt;&lt;/code&gt;, the TOC is placed before the first section heading. With &lt;code&gt;&lt;nowiki&gt;__TOC__&lt;/nowiki&gt;&lt;/code&gt;, it is placed at the same position where this code is placed. There may be some introductory text before the TOC, known as the &quot;lead&quot;. Although usually a heading after the TOC is preferable, &lt;code&gt;&lt;nowiki&gt;__TOC__&lt;/nowiki&gt;&lt;/code&gt; can be used to avoid being forced to insert a meaningless heading just to position the TOC correctly, i.e., not too low.

{{anchor|Floating the TOC}}'''Floating the TOC'''

The TOC can, in some instances, be floated either right or left using {{tl|TOC right}} or {{tl|TOC left}} when it is beneficial to the layout of the page, or when the default TOC gets in the way of other elements. Before changing the default TOC to a floated TOC, consider the following guidelines:

# If a page will be adversely affected by the change, don't float the TOC.
# When floating a TOC, check whether the page layout will be harmed if the TOC is hidden by the user.
# Long lists may create very long TOCs. The TOC should not be longer than necessary, whether it is floated or not.  Limiting the depth of the TOC can be used to reduce the length of the TOC by hiding nested subsections, rather than using a floating TOC (see below).
# The default TOC is placed before the first headline, but after any introductory text (unless changed by the page's editors). If the introductory summary is long enough that a typical user has to scroll down to see the top of the TOC, you may float the TOC so it appears closer to the top of the page.
# Floating a wide TOC will produce a narrow column of text for users with low resolutions. If the TOC's width exceeds 30% of the user's visible screen (about twice the size of the Wikibooks navigation bar to the left), then it is not suitable for floating. (Percentages assume a typical user setup.)
# If the TOC is placed in the general vicinity of other floated images or boxes, it can be floated as long as the flowing text column does not become narrower than 30% of the average user's visible screen width.
# A left-floated TOC may affect bulleted or numbered lists.

{{anchor|Limiting the depth of the TOC}}'''Limiting the depth of the TOC'''

When a page has a very large number of subsections (such as this page), it may be appropriate to hide lower-level subsections from the TOC. You can specify a limit for the lowest-level section that should be displayed using {{tlx|TOC|limit{{=}}''n''}}, where ''n'' is the number of = signs that are used on each side of the lowest-level section header that should be displayed (e.g. 3 to show ===sections=== but hide ====sections====). The limit=''n'' parameter can also be given to {{tl|TOC left}} or {{tl|TOC right}} the same way.

{{anchor|Linking to the TOC}}'''Linking to the TOC'''

You can make a link to the TOC using the following:
* Same page:
** wikicode: &lt;nowiki&gt;[[#toc|Contents]]&lt;/nowiki&gt;
** link: [[#toc|Contents]]
* Different page:
** wikicode: &lt;nowiki&gt;[[Help:Wiki markup#toc|Contents]]&lt;/nowiki&gt;
** link: [[Help:Templates#toc|Contents of Templates Help page]]

====Sections vs. separate pages====
Advantages of separate pages:
# [[WB:WLH|what links here]] feature
# separate [[WB:PH|edit histories]]
# some [[Help:Templates|template]] limits apply ''per page''
# automatic [[#Redirect|redirect]] on renaming
# loading ''one'' small page is faster than loading ''one'' large page—but are readers more likely to want to use just one section or to browse many of the sections of the topic?—see advantages of combined pages
# ''one'' small page is easier to navigate than ''one'' large page—but see above
# can separately be put in [[Help:Categories|categories]]

Advantages of one combined page with sections:
# loading ''one combined'' page is ''faster and more convenient'' than loading ''several divided'' ones
# searching within one large page or its wikitext with a local search function is faster and has advantages over searching several pages using the site search engine or a web search engine
# the automatic table of contents provides for convenient navigation.
# more likelihood of editorial cohesion of a concept compared to having several pages likely to be independently edited
# duplication of items relevant to each section is avoided

==={{anchor|Link}}Links===
{{shortcut|WB:LINK}}
{{Meta|Help:Link}}
'''Links''' give readers one-click access to other Wikibooks pages, other [[w:Wikimedia project|Wikimedia project]]s, and external websites.

===={{anchor|Wikilink}}Wikilinks====

A '''wikilink''' or '''internal link''' links a page to another page within English Wikibooks.

*&lt;nowiki&gt;[[Main Page]]&lt;/nowiki&gt; gives [[Main Page]] (link to ''Main Page'', labeled ''Main Page'').
*&lt;nowiki&gt;[[Main Page|Home]]&lt;/nowiki&gt; gives [[Main Page|Home]] (link to ''Main Page'', labeled ''Home'').
*&lt;nowiki&gt;[[Main Page]]s&lt;/nowiki&gt; gives [[Main Page]]s, just like &lt;nowiki&gt;[[Main Page|Main Pages]]&lt;/nowiki&gt; does: [[Main Page|Main Pages]].
*&lt;nowiki&gt;[[Main Page|Home]]s&lt;/nowiki&gt; gives [[Main Page|Home]]s, just like &lt;nowiki&gt;[[Main Page|Homes]]&lt;/nowiki&gt; does: [[Main Page|Homes]].
*&lt;nowiki&gt;[[Main Page]]'s&lt;/nowiki&gt; gives [[Main Page]]'s (''punctuation'' is not appended to the link).
*&lt;nowiki&gt;[[Main Page]]&lt;&lt;/nowiki&gt;nowiki&gt;s&lt;/nowiki&gt; gives [[Main Page]]&lt;nowiki&gt;s&lt;/nowiki&gt;.
*&lt;nowiki&gt;[[Main Page]]''s''&lt;/nowiki&gt; gives [[Main Page]]''s''.
*&lt;nowiki&gt;''[[Main Page]]s''&lt;/nowiki&gt; gives ''[[Main Page]]''s.
*&lt;nowiki&gt;[[Cookbook|Cook]]book&lt;&lt;/nowiki&gt;nowiki&gt;s&lt;/nowiki&gt; gives [[Cookbook|Cook]]book&lt;nowiki&gt;s&lt;/nowiki&gt;.

Links with a specified label are said to be &quot;[[#Piped links|piped]]&quot; because of the pipe symbol used ( | ). For certain types of link, the label will be generated automatically if a pipe is typed with no label after it (thus saving you typing). See [[#Piped links|piped links]] below.

The link target is ''case-sensitive except for the first character'' (so [[calculus]] links to [[Calculus]], but [[CAlculus]] does not).

If the target of a wikilink does not exist, it is displayed red, and is called a [[Help:Glossary#red link|red link]]. If a red link is clicked, the user is taken to a page where it is possible to create a page under the red-linked title. Red links to a particular (non-existent) title can be detected using the [[WB:WLH|What links here]] feature.

If the target of a link is the same as the page on which it appears (a self-link), it is displayed in bold, as in [[Help:Editing]].

Attempting to link normally to a [[Help:Files|file]] page, [[Help:Categories|category]] page or [[#Interlanguage links|interlanguage link]] will produce a different effect: it will place the image on the page, add the page to the category or create an interlanguage link at the edge of the page. To override this behavior, add an initial colon, as in &lt;code&gt;&lt;nowiki&gt;[[:File:Mediawiki.png]]&lt;/nowiki&gt;&lt;/code&gt;, &lt;code&gt;&lt;nowiki&gt;[[:Category:Help]]&lt;/nowiki&gt;&lt;/code&gt;, &lt;code&gt;&lt;nowiki&gt;[[:fr:Help:Contents]]&lt;/nowiki&gt;&lt;/code&gt;.

===={{anchor|Piped link|Pipe trick}}Piped links====
A '''piped link''' is an internal [[#Wikilinks|link]] or [[#Interwiki links|interwiki link]] where the link target and link label are both specified. This is needed in the case that they are not equal, while also the link label is not equal to the link target with the last word extended. This allows linking a word or phrase within the text of a page rather than using &quot;see also&quot;, even if the wording does not exactly correspond with the name of the target page. With a suitable browser and depending on the [[WB:PREFS|preferences]] set, one can still see the link target: when you point at the link, the name shows up in a hover box and is also shown in the status bar.

For instance: &lt;nowiki&gt;[[Help:Contents|Help]]&lt;/nowiki&gt; will show as [[Help:Contents|Help]].

If in a piped link the part after the &quot;|&quot; is left empty, it is converted to an abbreviated form of the page name on the left, as follows:

#any word before the first colon (:), as well as the colon itself, is removed. This word may or may not be a namespace prefix (such as &quot;Help:&quot;) or an [[#Interwiki links|interwiki prefix]] (such as &quot;commons:&quot;).
#if there is text in parentheses at the end it will be removed
#if there are no parentheses but there is a comma, the comma and everything after it is removed
#the link will be in whatever case is used.

Just like for the four tildes when adding a signature, in a preview, the result already shows up in the preview itself, but the conversion in the edit box is not yet shown. Press &quot;Show changes&quot; to see the change in the wikitext.

'''Colon'''
* &lt;nowiki&gt;[[Help:Templates|]]&lt;/nowiki&gt; is converted to &lt;nowiki&gt;[[Help:Templates|Templates]]&lt;/nowiki&gt;, which is rendered as [[Help:Templates|Templates]]
* &lt;nowiki&gt;[[Programming:C++|]]&lt;/nowiki&gt; is converted to &lt;nowiki&gt;[[Programming:C++|C++]]&lt;/nowiki&gt;, which is rendered as [[Programming:C++|C++]] - even though &quot;Programming:&quot; is not a [[Help:Pages#Namespaces|namespace]] the shortcut works anyway
* &lt;nowiki&gt;[[w:Key Largo (film)|]]&lt;/nowiki&gt; is converted to &lt;nowiki&gt;[[w:Key Largo (film)|Key Largo]]&lt;/nowiki&gt;, which is rendered as [[w:Key Largo (film)|Key Largo]]

'''Case'''
*&lt;nowiki&gt;[[w:pipeline (Unix)|]]&lt;/nowiki&gt; is converted to &lt;nowiki&gt;[[w:pipeline (Unix)|pipeline]]&lt;/nowiki&gt; which is rendered as [[w:pipeline (Unix)|pipeline]]. 
*&lt;nowiki&gt;[[w:Pipeline (Unix)|]]&lt;/nowiki&gt; is converted to &lt;nowiki&gt;[[w:Pipeline (Unix)|]]&lt;/nowiki&gt; which is rendered as [[w:Pipeline (Unix)|Pipeline]].

'''Comma'''
* &lt;nowiki&gt;[[commons:Boston, Massachusetts|]]&lt;/nowiki&gt; is converted to &lt;nowiki&gt;[[commons:Boston, Massachusetts|Boston]]&lt;/nowiki&gt;, which is rendered as [[commons:Boston, Massachusetts|Boston]].

===={{anchor|Relative link|Relative links|Subpage link}}Subpage links====
Subpages can be linked to with relative links, without giving the full page name. The following example shows how we link to various pages from the hypothetical &lt;code&gt;Snappy&amp;nbsp;Title/Logical&amp;nbsp;section&lt;/code&gt;. Note that that the full page name in the link title can be suppressed by appending another slash. For more flexibility, use a [[#Piped links|piped link]] as normal.

{| class=&quot;wikitable&quot;
! Full page name of the link target || Relative link || Displays as
|-
| &lt;code&gt;Snappy Title&lt;/code&gt; || &lt;code&gt;&lt;nowiki&gt;[[../]]&lt;/nowiki&gt;&lt;/code&gt;
| &lt;code&gt;Snappy Title&lt;/code&gt;
|-
| &lt;code&gt;Snappy Title/Sister page&lt;/code&gt; || &lt;code&gt;&lt;nowiki&gt;[[../Sister page]]&lt;/nowiki&gt;&lt;/code&gt;
| &lt;code&gt;Snappy Title/Sister page&lt;/code&gt;
|-
| &lt;code&gt;Snappy Title/Sister page&lt;/code&gt; || &lt;code&gt;&lt;nowiki&gt;[[../Sister page/]]&lt;/nowiki&gt;&lt;/code&gt;
| &lt;code&gt;Sister page&lt;/code&gt;
|-
| &lt;code&gt;Snappy Title/Logical section/interesting topic&lt;/code&gt; || &lt;code&gt;&lt;nowiki&gt;[[/interesting topic]]&lt;/nowiki&gt;&lt;/code&gt;
| &lt;code&gt;Snappy Title/Logical section/interesting topic&lt;/code&gt;
|-
| &lt;code&gt;Snappy Title/Logical section/interesting topic&lt;/code&gt; || &lt;code&gt;&lt;nowiki&gt;[[/interesting topic/]]&lt;/nowiki&gt;&lt;/code&gt;
| &lt;code&gt;interesting topic&lt;/code&gt;
|}

'''Note''' that the first character of sub-pages is case-sensitive.

===={{anchor|External link}}External links====
'''External links''' use absolute [[w:URL|URL]]s to link directly to any webpage. External links are in the form &lt;code&gt;&lt;nowiki&gt;[http://www.example.org link name]&lt;/nowiki&gt;&lt;/code&gt; (resulting in [http://www.example.org link name]), with the link name separated from the URL by a space. Links without link names appear numbered: &lt;code&gt;&lt;nowiki&gt;[http://www.example.org]&lt;/nowiki&gt;&lt;/code&gt; becomes [http://www.example.org]. Links with no square brackets display in their entirety: http://www.example.org .

[[Special:LinkSearch]] finds all pages linking to a given site.

The external link syntax can also be used to link to particular page versions within Wikibooks that are not accessible by wikilinks, such as page [[Help:Tracking changes#Page history|history]], edit view, an old version of a page, the [[Help:Tracking changes#Viewing diffs|diff]] between two versions, etc.

To display a link without the arrow icon, place the external link syntax between 
&lt;code&gt;&amp;lt;span class=&quot;plainlinks&quot;&gt;...&amp;lt;/span&gt;&lt;/code&gt; tags.

===={{anchor|Section link|Section links}}Section links (anchors)====
To link to a section in the same page you can use: &lt;code&gt;&lt;nowiki&gt;[[#Section name|displayed text]]&lt;/nowiki&gt;&lt;/code&gt;, and to link to a section in another page: &lt;code&gt;&lt;nowiki&gt;[[Page Name#Section name|displayed text]]&lt;/nowiki&gt;&lt;/code&gt;.

The section title in fact points to an &quot;anchor&quot; on the target page. It is possible to define anchors other than explicit section titles, using the [[Help:Templates|template]] {{tlx|anchor|anchor name}}. However &lt;code&gt;&lt;nowiki&gt;[[#top]]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;[[#toc]]&lt;/nowiki&gt;&lt;/code&gt; are reserved names that link to the top of a page and the table of contents, respectively.

Section links still work if the wikilink is a [[#Redirect|redirect]] (for example, if [[Help:About]] redirects to [[Wikibooks:Welcome]], then [[Help:About#General Information]] will link to the &quot;General Information&quot; section of [[Wikibooks:Welcome]]). It is also possible to put section links inside redirects. For example, [[WB:LINK]] redirects to [[Help:Editing#Links]]. Note that an explicit section link overrides any section link in a redirect, so [[WB:LINK#Interwiki links]] will go to the &quot;Interwiki links&quot; section of this page.  Anchor links can also be added to [[#External links|external links]] and to [[#Interwiki links|interwiki links]], again using the # syntax.

===={{anchor|Interlanguage link}}Interlanguage links====
'''Interlanguage links''' are links from any page at here at the English language Wikibooks to nearly equivalent or exactly equivalent pages in another language Wikibooks.

The interlanguage links take the following form:

:&lt;nowiki&gt;[[language code:Title]]&lt;/nowiki&gt;

where the language code is the two-letter code as per [[w:ISO 639-1|ISO 639-1]]. (See [[m:List of Wikibooks|Complete list of language Wikibooks available]]. English is &quot;en&quot;, Japanese is &quot;ja&quot;, etc.) So for example in the English language book on [[Calculus]], which is available on many other wikis, the interlanguage links might look like this:

:&lt;nowiki&gt;[[ja:解析学基礎]]&lt;/nowiki&gt;
:&lt;nowiki&gt;[[nl:Analyse]]&lt;/nowiki&gt;
:&lt;nowiki&gt;[[zh:微积分学]]&lt;/nowiki&gt;

Note: These links are treated specially, and don't show up in the body of the text, but rather in a special sidebar section &quot;in other languages&quot; listed by language name. Technically they can go anywhere in the page; placement does not alter the visual appearance of the links on the rendered page except for the order. However, the convention is to put them at the bottom of the wikitext.

===={{anchor|Interwiki link}}Interwiki links====
{| class=&quot;wikitable sortable&quot; style=&quot;margin-bottom:0; float:right;&quot;
! Project !! Long form !! Shortcut
|-
| [[w:Wikipedia|Wikipedia]]
| &lt;code&gt;[[[[wikipedia:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[w:]]]]&lt;/code&gt;
|-
| [[w:Wiktionary|Wiktionary]]
| &lt;code&gt;[[[[wiktionary:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[wikt:]]]]&lt;/code&gt;
|-
| [[w:Wikinews|Wikinews]]
| &lt;code&gt;[[[[wikinews:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[n:]]]]&lt;/code&gt;
|-
| [[w:Wikiquote|Wikiquote]]
| &lt;code&gt;[[[[wikiquote:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[q:]]]]&lt;/code&gt;
|-
| [[w:Wikisource|Wikisource]]
| &lt;code&gt;[[[[wikisource:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[s:]]]]&lt;/code&gt;
|-
| [[w:Wikispecies|Wikispecies]]
| &lt;code&gt;[[[[wikispecies:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[species:]]]]&lt;/code&gt;
|-
| [[w:Wikiversity|Wikiversity]]
| &lt;code&gt;[[[[wikiversity:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[v:]]]]&lt;/code&gt;
|-
| [[w:Wikivoyage|Wikivoyage]]
| &lt;code&gt;[[[[wikivoyage:]]]]&lt;/code&gt;
| &lt;code&gt;[[[[voy:]]]]&lt;/code&gt;
|}

An '''interwiki link''' links to a page on another Wikimedia project website, such as [[w:|Wikipedia]] or another language Wikibooks.  Other sites are listed in the [[m:Interwiki map|interwiki map]]. These links have the same &lt;nowiki&gt;[[...]]&lt;/nowiki&gt; syntax as [[#Wikilinks|wikilinks]] (see above), but take a prefix which specifies the target site. For example, &lt;nowiki&gt;[[w:Help:Contents]]&lt;/nowiki&gt; links to the &quot;Help:Contents&quot; page on Wikipedia. Links can be piped as with wikilinks. Remember that an [[#Interlanguage links|interlanguage link]] should be preceded by a colon if it is to be displayed where it appears in the text; otherwise it will be listed at the side of the page (which is appropriate only if it is the most closely corresponding page in the other language Wikibooks).

Interwiki links (like external links) are displayed in a slightly paler blue than ordinary wikilinks. MediaWiki does not detect whether these target pages exist, so they are never displayed red.  The interwiki links for the major Wikimedia projects are shown at right.

Some people prefer to use templates that wrap the above interwiki link syntax with some nice formatting --
{{tl|Wikipedia}}, {{tl|Wikipediapar}}, {{tl|Wikipedia-inline}}, {{tl|Wikiversity}}, {{tl|Wikisource}}, {{tl|Wikiquote}}, {{tl|Wikivoyage}}, etc.

{{clear}}

==={{anchor|Footnote|Footnotes|Reference}}References===
{{shortcut|WB:REFS}}
'''References''' present [[w:citation|citation]]s to reliable sources that support assertions. '''Footnotes''' add explanatory material and are useful if the added information would be distracting if written out in the main text.

====Inserting references====
{{anchor|Single citation of a reference or footnote}}'''Single citation of a reference or footnote'''

At the point of citation in the page, enter the footnote or reference like this:

:&lt;code&gt;&lt;nowiki&gt;&lt;ref&gt;Excel For Dummies, First Edition, Hungry Minds, Inc., 1980.&lt;/ref&gt;&lt;/nowiki&gt;&lt;/code&gt;

You can include formatting and links in the footnote or reference in the usual way.  The reference becomes visible in the &lt;nowiki&gt;&lt;references/&gt;&lt;/nowiki&gt; list at the bottom, if there is one.

{{anchor|Creating the list of references or footnotes}}'''Creating the list of references or footnotes'''

At the point where you want the text of the footnotes or references to appear (usually at the end of the page in a '''Notes''' or '''References''' section), insert the tag:

:&lt;code&gt;&lt;nowiki&gt;&lt;references/&gt;&lt;/nowiki&gt;&lt;/code&gt;

The template {{tl|reflist}} is an alternative, mostly used if there are many footnotes.

{{anchor|Multiple citations of the same reference or footnote}}'''Multiple citations of the same reference or footnote'''

To cite the same reference or footnote several times, identify it using the &lt;code&gt;name&lt;/code&gt; parameter of the &lt;code&gt;&lt;nowiki&gt;&lt;ref&gt;&lt;/nowiki&gt;&lt;/code&gt; tag.

At one of the citation points (it makes sense to choose the first), enter the reference like this:

:&lt;code&gt;&lt;nowiki&gt;&lt;ref name=&quot;Perry&quot;&gt;Perry's Handbook, Sixth Edition, McGraw-Hill Co., 1984.&lt;/ref&gt;&lt;/nowiki&gt;&lt;/code&gt;

Then at all the other citation points, just enter:

:&lt;code&gt;&lt;nowiki&gt;&lt;ref name=&quot;Perry&quot;/&gt;&lt;/nowiki&gt;&lt;/code&gt;

You are free to pick any footnote name, subject to a few rules. The footnote name is internal and will not be displayed anywhere when the page is viewed. Footnote names are case sensitive and may not be a numeric integer. Names and groups should be kept simple and restricted to the standard English alphabet and numerals.

{{anchor|Using templates to insert reference text}}'''Using templates to insert reference text'''

A number of [[Help:Templates|templates]], such as a generic {{tl|citation}}, or more specific {{tl|cite book}}, {{tl|cite web}}, etc., are available to format the text between &lt;code&gt;&lt;nowiki&gt;&lt;ref&gt;&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;/ref&gt;&lt;/code&gt; tags in a more structured way. These are listed at [[:Category:Citation templates]]. Their use is optional: they do aid with consistent formatting, but on the other hand they can make editing more cumbersome.

====Appearance of references====
The &lt;code&gt;&lt;nowiki&gt;&lt;ref&gt;&lt;/nowiki&gt;&lt;/code&gt; tags in the main text are converted to auto-numbered superscripts, like this:

{|class=&quot;wikitable&quot;
|
The only reference to Excel For Dummies.&lt;ref&gt;Excel For Dummies, First Edition, Hungry Minds, Inc., 1980.&lt;/ref&gt; The first reference to Perry's Handbook.&lt;ref name=&quot;Perry&quot;&gt;Perry's  Handbook, Sixth Edition, McGraw-Hill Co., 1984.&lt;/ref&gt; The second reference to Perry's Handbook and to another, related book.&lt;ref name=&quot;Perry&quot;/&gt;&lt;ref&gt;Nuclear Chemical Engineering (2nd Edition), McGraw-Hill Co., 1981.&lt;/ref&gt; A statement that requires a reference. The only reference to Linux in a Nutshell.&lt;ref&gt;Linux in a Nutshell, O'Reily Co., 2003.&lt;/ref&gt; And third reference to Perry's Handbook.&lt;ref name=&quot;Perry&quot;/&gt;
|}

Clicking on a numbered superscript takes you straight to the text of the corresponding footnote or reference.

The &lt;code&gt;&lt;nowiki&gt;&lt;references/&gt;&lt;/nowiki&gt;&lt;/code&gt; tag is expanded to show the text of the footnotes or references against their corresponding numbers, like this:

{| class=&quot;wikitable&quot;
|
&lt;references/&gt;
|}

For single citations, clicking on the arrow (&lt;span style=&quot;color:blue;&quot;&gt;'''↑'''&lt;/span&gt;) takes you to the point of citation in the main text. For multiple citations, the links back to the main text are distinguished by letter superscripts (&lt;span style=&quot;color:blue;&quot;&gt;'''''a'''''&lt;/span&gt;, &lt;span style=&quot;color:blue;&quot;&gt;'''''b'''''&lt;/span&gt;, &lt;span style=&quot;color:blue;&quot;&gt;'''''c'''''&lt;/span&gt; etc.). Clicking on a letter superscript takes you to the corresponding citation in the main text.

====Separate lists of references and footnotes====
Sometimes it is convenient to separate explanatory footnotes from references. This can be accomplished with the &quot;group&quot; parameter:

&lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;
This part of the text requires clarification,&lt;ref group=&quot;note&quot;&gt;Listed separately from the citation&lt;/ref&gt; whereas the entire text is cited.&lt;ref&gt;Citation.&lt;/ref&gt;

;Notes
&lt;references group=&quot;note&quot;/&gt;

;References
{{reflist|close=1}}
&lt;/syntaxhighlight&gt;

This part of the text requires clarification,&lt;ref group=&quot;note&quot;&gt;Listed separately from the citation&lt;/ref&gt; whereas the entire text is cited.&lt;ref&gt;Citation.&lt;/ref&gt;

;Notes
&lt;references group=&quot;note&quot;/&gt;

;References
{{Reflist|close=1}}

Note that, at present, such footnotes cannot themselves contain reference links.

Footnotes may also be listed at the ends of each section of text by closing the {{tl|reflist}} template with the &quot;close&quot; parameter, as shown in the box just above.

====List-defined references====
The software also allows named references to be defined within the reference list rather than in the main text.  This can make editing pages much easier, particularly on heavily cited sections.  For example:

&lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;The quick brown fox jumps over the lazy dog.&lt;ref name=&quot;LazyDog&quot;/&gt;

&lt;references&gt;
&lt;ref name=&quot;LazyDog&quot;&gt;This is the lazy dog reference.&lt;/ref&gt;
&lt;/references&gt;&lt;/syntaxhighlight&gt;

The quick brown fox jumps over the lazy dog.&lt;ref name=&quot;LazyDog&quot;/&gt;

&lt;references&gt;
&lt;ref name=&quot;LazyDog&quot;&gt;This is the lazy dog reference.&lt;/ref&gt;
&lt;/references&gt;

This can also be done using the {{tl|reflist}} template with a {{para|refs}} parameter.  If desired, the {{para|group}} parameter can be used to group references for the template:

&lt;syntaxhighlight lang=&quot;wikitext&quot;&gt;How razorback-jumping frogs&lt;ref name=&quot;Batteries&quot; group=&quot;note&quot;/&gt; can level six piqued gymnasts.&lt;ref name=&quot;JumpingFrogs&quot;/&gt;

;Notes
{{reflist|group=&quot;note&quot;|
refs=
&lt;ref name=&quot;Batteries&quot; group=&quot;note&quot;&gt;Batteries not included.&lt;/ref&gt;
}}
;References
{{reflist|
refs=
&lt;ref name=&quot;JumpingFrogs&quot;&gt;This is the jumping frogs reference.&lt;/ref&gt;
}}&lt;/syntaxhighlight&gt;

How razorback-jumping frogs&lt;ref name=&quot;Batteries&quot; group=&quot;note&quot;/&gt; can level six piqued gymnasts.&lt;ref name=&quot;JumpingFrogs&quot;/&gt;

;Notes
{{reflist|group=&quot;note&quot;|
refs=
&lt;ref name=&quot;Batteries&quot; group=&quot;note&quot;&gt;Batteries not included.&lt;/ref&gt;
}}
;References
{{reflist|
refs=
&lt;ref name=&quot;JumpingFrogs&quot;&gt;This is the jumping frogs reference.&lt;/ref&gt;
}}

==={{anchor|List}}Lists===
{{shortcut|WB:LIST}}

There are three types of lists:  '''unordered lists''', '''ordered lists''', and '''definition lists'''.

{|class=&quot;wikitable&quot; style=&quot;width:80%;&quot;
!wikitext!!rendering
|-
|
 * Unordered lists are easy to do:
 ** start every line
 * with a star
 ** more stars mean
 *** deeper levels
||
* Unordered lists are easy to do:
** start every line
* with a star
** more stars mean 
*** deeper levels
|-
|
 * A newline
 * in a list  
 marks the end of the list.
 Of course
 * you can
 * start again.
|
* A newline
* in a list  
marks the end of the list.
Of course
* you can
* start again.
|-
|
 # Numbered (ordered) lists are good
 ## very organized
 ## easy to follow
|
# Numbered (ordered) lists are good
## very organized
## easy to follow
|-
|
 * You can also
 ** break lines
 ** like this
|
* You can also
** break lines
** like this
|-
|
 ; Definition lists
 ; item : definition
 ; semicolon plus term
 : colon plus definition
|
; Definition lists
; item : definition
; semicolon plus term
: colon plus definition
|-
|
 * Or create mixed lists
 *# and nest them
 *#* like this
 *#*; definitions
 *#*: work:
 *#*; apple
 *#*; banana
 *#*: fruits
|
* Or create mixed lists
*# and nest them
*#* like this
*#*; definitions
*#*: work: 
*#*; apple
*#*; banana
*#*: fruits
|}

For simplicity, list items in wiki markup cannot be longer than a paragraph. A following blank line will end the list and reset the counter on ordered lists. Separating unordered list items with blank lines may look approximately normal on your screen, but it creates many separate one-item lists, which is a problem for people using [[w:screen readers|screen readers]], causing accessibility problems for people with disabilities.

===Other items===
* [[Help:Categories|Categories]]
* [[Help:Files|Files]]
* [[Help:Tables|Tables]]
* [[Help:Templates|Templates]]

==Common tasks==
==={{anchor|Revert}}Reverting===
{{shortcut|WB:REVERT}}
On Wikibooks, '''reverting''' means undoing the effects of one or more edits, which normally results in the page being restored to a version that existed sometime previously. More broadly, reverting may also refer to any action that in whole or in part reverses the actions of other editors.

This page contains technical information about making reverts. It should be borne in mind, however, that reverting good-faith actions of other editors (as opposed to [[Wikibooks:Vandalism|vandalism]]) is considered disruptive when done to excess, and can even lead to the reverter being [[Wikibooks:Blocking policy|blocked]] from editing.

====Manual reverting====
In some cases (for example, if a vandal added or removed text, and unrelated constructive edits have been made since), the easiest way to undo past edits may simply be to edit the current page, deleting wrongly added text or restoring wrongly deleted text (this can be copied and pasted from a past version of the page). However, it may be more convenient to restore a particular old version of the page from prior to the changes you wish to revert. To do this:
* Click the &quot;history&quot; tab at the top of the page to display the [[Help:Tracking changes#Page history|page history]].
* Click the time and date of the earlier version to which you wish to revert.  You will see a phrase similar to: &quot;This is an old revision of this page, as edited by ***.***.***.*** (talk) at 15:47, January 24, {{CURRENTYEAR}}. It may differ significantly from the current revision.&quot;
** '''Important:''' in the case of [[Wikibooks:Vandalism|vandalism]], take the time to make sure that you are reverting to the last version without the vandalism; there may be multiple consecutive vandal edits or they may be interspersed between constructive edits.
* Click the ''Edit'' tab as you normally would to edit a page. (Above the edit box, you will see a warning similar to: &quot;You are editing an old revision of this page. If you save it, any changes made since then will be removed.&quot;) If editing requires a registered account, log in first, or leave a note on the discussion page.
* Complete the [[#Edit summary|edit summary]] field (the abbreviation &quot;rv&quot; can be used to stand for &quot;revert&quot;; the edit summary &quot;rvv&quot; means &quot;reverting vandalism&quot;).
* Save the page.
* If constructive edits had been made after those that you wished to revert, return to the page history to find those edits, and redo them by hand if reasonably possible.

If reverting vandalism, check the [[Help:Tracking changes#User contributions|contribution history]] of the user who vandalized the page. If this user is vandalizing many pages,  [[Wikibooks:Reading room/Administrative Assistance|report them]].

====Undo====
{{shortcut|WB:UNDO}}
The MediaWiki software sometimes enables editors to easily revert (or &quot;undo&quot;) a single edit from the history of a page, without simultaneously undoing all constructive changes that have been made since. To do this, view the [[Help:Tracking changes#Page history|page history]] or the [[Help:Tracking changes#Viewing diffs|diff]] for the edit, then click on &quot;undo&quot; next to the edit in question. The software will attempt to create an edit page with a version of the page in which the undesirable edit has been removed, but all later edits are retained. There is a default edit summary, but this can be modified before saving.

It is also possible to undo several consecutive edits, even if they conflict among themselves: view the diff to be removed (by selecting the two extremal revisions in the history and clicking &quot;compare selected revisions&quot;), and click the &quot;undo&quot; link.

This feature removes the need to manually redo useful changes that were made after the edit which is being reverted. However, it will fail if undoing the edit would conflict with later edits. For example, if one edit adds a paragraph and a later edit modifies that paragraph, it will be impossible to automatically undo the earlier edit. In this case, you must determine how to resolve the problem manually.

====Rollback====
{{shortcut|WB:RBK|WB:ROLL|WB:ROLLBACK}}
[[Wikibooks:Administrators|Administrators]] and [[Wikibooks:Patrollers|patrollers]] who have been granted access to the rollback feature have additional links which:
* appear only next to the top edit
* revert ''all'' top consequent edits made by last editor
* work immediately, without the intermediate confirmation diff page
* add automatic [[#Edit summary|edit summary]] &quot;'''m''' Reverted edits by [[Special:Contributions/Example|Example]] ([[User talk:Example|talk]]) to last version by Example2&quot;, marking edit as minor

Rollback links appear on the [[Help:Tracking changes#User contributions|user contributions]] pages, [[Help:Tracking changes#Watching pages|user watchlists]], [[Help:Tracking changes#Page history|history pages]] and [[Help:Tracking changes#Viewing diffs|diff pages]]. Note that in the last case, rollback links can be misleading, since reversion is not necessarily to the old version shown (the diff page may show the combined result of edits, including some by other editors or only part of the edits the rollback button would revert). To see the changes the rollback button will revert, view the specific diff that compares the last version from the last editor with the last version from the previous editor.

Rollback works much quicker than undo, since it:
* allows reverting without even looking at the list of revisions or diff
* does not require loading an edit page and sending the wikitext back to the server
* does not require a click of the save button

On the other hand, it is not as versatile as undo, since it does not allow specification of which edits have to be undone. One may want to revert more or less edits than the rollback does or edits which do not include the last edit. It also does not allow adding an explanation to the automatic edit summary and it should only be used to revert obvious vandalism.

Rolling back a good-faith edit, without explanation, may be misinterpreted as &quot;I think your edit was no better than vandalism and reverting it doesn't need an explanation&quot;. Some editors are sensitive to such perceived slights; if you use the rollback feature other than for vandalism (for example, because undo is impractical due to the large page size), it is courteous to leave an explanation on the book's discussion page or on the talk page of the user, whose edit(s) you have reverted.

If someone else edited or rolled back the page before you clicked the &quot;rollback&quot; link, or if there was no previous editor, you will get an error message.

==== Bot rollback ====
In cases of flood vandalism, administrators and [[Wikibooks:Global rights policy#Global rollbackers|global rollbackers]] may choose to hide vandalism and reverts from [[Wikibooks:RC|recent changes]]. To do this, add &lt;kbd&gt;&amp;bot=1&lt;/kbd&gt; to the end of the URL used to access a user's contributions. For example: http://en.wikibooks.org/w/index.php?title=Special:Contributions&amp;target=SomePersistentVandal&amp;bot=1.

When the rollback links on the contributions list are clicked, the revert and the original edit that you are reverting will both be hidden from recent changes, unless you click the &quot;bots&quot; link in the Recent Changes to set &lt;kbd&gt;hidebots=0&lt;/kbd&gt;. The edits are not hidden from contributions lists, page histories or watchlists. The edits remain in the database and are not removed, but they no longer flood &quot;Recent changes&quot;. The aim of this feature is to reduce the annoyance factor of a flood vandal, with relatively little effort. This should '''not''' be used for reverting a change you just don't like, but is meant only for massive floods of simple vandalism.

==={{anchor|Redirect|Redirects}}Redirecting===
{{shortcut|WB:REDIRECT}}
'''Redirecting''' a page causes navigation to a given title to take the reader directly to a different page.  The page the reader visits first is called the '''redirect''' page.

====Syntax of redirects====
A page will be treated as a redirect page if its wikitext begins with &lt;code&gt;#REDIRECT&lt;/code&gt; followed by a valid [[#Wikilinks|wikilink]] or [[#Interwiki links|interwiki link]]. A space is usually left before the link. (Note that some alternative capitalizations of &quot;REDIRECT&quot; are possible.) The [[File:Vector toolbar redirect button.png|20px|link=]] button in the [[#Edit toolbar|edit toolbar]] can be used to produce this syntax.

Note that a redirect will only work as intended (i.e. take the reader directly to the target page) if the link is to an existing normal page (not a [[Special:SpecialPages|special page]]) on the same project (English Wikibooks). In other cases soft redirects are often used – see [[#Soft redirects|below]].

Examples:
*&lt;code&gt;&lt;nowiki&gt;#REDIRECT [[Help:Tracking changes]]&lt;/nowiki&gt;&lt;/code&gt; (redirects to the [[Help:Tracking changes]] page)
*&lt;code&gt;&lt;nowiki&gt;#REDIRECT [[Help:Tracking changes#Preferences]]&lt;/nowiki&gt;&lt;/code&gt; (redirects to the &quot;Preferences&quot; [[#Section|section]] of the [[Help:Tracking changes]] page)
*&lt;code&gt;&lt;nowiki&gt;#REDIRECT [[fr:Help:Tracking changes]]&lt;/nowiki&gt;&lt;/code&gt; (appears as a redirect to the [[Help:Tracking changes]] page on French Wikibooks, but will not work as a true redirect; this is called a &quot;soft redirect&quot;)

Any text appearing after the redirect link will be ignored in the display, but may be used to add categories, comments, etc.

Note that the redirect link must be explicit – it cannot contain [[Help:Variables|variables]], [[Help:Templates|templates]], etc.

When redirecting to a [[Help:Categories|category]] page, prefix the target pagename with a colon to prevent the redirect from showing up in the category. (Redirects from one category page to another should use soft redirects—see [[#Soft redirects|below]].) Redirects to [[Help:Files|file]] pages also require the colon.

====Appearance of redirects====
If the redirect target is an existing page on English Wikibooks, then if a reader navigates to the redirect page—by means of a [[#Wikilinks|wikilink]] or a [[w:URL|URL]]—they will be taken directly to the target page. However, the browser still shows the URL of the redirect page, and the target page shows a small notice below the top title to indicate that you arrived by means of a redirect. For example, if you click [[WB:RR]], you will be redirected to the [[Wikibooks:Reading room]] page, and the top of the page will look like:

&lt;blockquote style=&quot;background-color: white; color: black; border:1px solid black; padding: 1em;&quot;&gt;
&lt;div class=&quot;firstHeading&quot; style=&quot;color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 1.8em; font-family: 'Linux Libertine',Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;&quot;&gt;Wikibooks:Reading room&lt;/div&gt;
&lt;div id=&quot;contentSub&quot;&gt;(Redirected from &lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:WB:RR|redirect=no}}  Wikibooks:RR]&lt;/span&gt;)&lt;/div&gt;
&lt;/blockquote&gt;

To get the canonical URL of the target page in your browser's address bar, click the page's tab. To go to the redirect page itself (to edit it, view its history, etc.), click the link in the &quot;(Redirected from...)&quot; notice.

If the redirect target is a non-existing page ([[Help:Glossary#redlink|redlink]]), or a [[Special:SpecialPages|special page]], or a page in another project, then the redirect is not followed, and the reader sees the display of the redirect page (as illustrated below). If the target is a non-existent section of an existing page, then the redirect will take the reader to the top of the target page.

Note that chains of redirects are not followed. If title A redirects to B, and B is itself a redirect page, then a reader navigating to A will see the display of the redirect page B (as illustrated above).  This situation is called a [[Help:Glossary#double redirect|double redirect]]. ([[Wikibooks:Bots|Bots]] fix such chains so that each redirect points directly to the final target page.)

====Creation of redirects====
A redirect page can be created like any other page. Simply type in the wikitext &lt;syntaxhighlight lang=&quot;wikitext&quot; inline=yes&gt;#REDIRECT [[/xxx]]&lt;/syntaxhighlight&gt;, replacing &quot;xxx&quot; with the title of the target page (optionally followed by a &quot;#&quot; sign and the section title). The [[File:Vector toolbar redirect button.png|20px|link=]] button in the [[#Edit toolbar|edit toolbar]] above the edit window can be used to save typing (either click it and then insert the desired target, or else type the target, select it with the mouse, then click the button).  Make sure that there is no text ''before'' the #REDIRECT keyword, or the redirect will not work. There is not usually any reason to place any text after the link either, although sometimes categories (or categorizing templates) are added.

Similarly, any existing page can be edited to turn it into a redirect. If a new redirect page is created or an existing page turned into a redirect page, an [[#Edit summary|edit summary]] will be automatically generated stating that the page has been redirected to the given target. (This is overridden if the editor supplies an edit summary.)

When a page is [[WB:MOVE|moved]] (renamed), a redirect is automatically created from the old to the new name, and also one for the corresponding talk page (if that was moved as well). [[Wikibooks:Administrators|Administrators]] can choose to suppress creation of the redirect.

If the new page name is occupied by a redirect that has only one edit in its history and targeted to the old page name, it is replaced by the page being moved. If the redirect has more than one history entry, or has a different target page, then the move must be made by an administrator.

To edit a page which is already a redirect (or to view its history, talk page, etc.), follow the redirect to the target page, then click on the link in the &quot;(Redirected from ...)&quot; notice at the top of the page. This will take you to the redirect page itself. Another way to get to a redirect page is to go to the target page, and click &quot;[[WB:WLH|What links here]]&quot; (in the toolbox on the left of the page). This will show you all the back-links from that page, including redirects. Clicking on a redirect in this list will take you to the redirect page, not the target.

==== Soft redirects ====
As an alternative to the normal &quot;hard&quot; redirects (which take the reader directly to the target page), it is possible to create [[Help:Glossary#soft redirect|&quot;soft&quot; redirects]], which leave the reader on the redirect page, giving them the option of clicking the link to the target page. This is usually done in the following situations:
*When the target is on another project ([[w:|Wikipedia]], other language Wikibooks, etc.) or is a [[Special:SpecialPages|special page]]. (In these situations a hard redirect would behave as a soft one in any case.)
*For redirects between categories. (Hard redirects will work for category pages, but soft ones are preferred because of the software's inability to recategorize pages from redirected categories.)

Soft redirects are created using the templates {{tl|soft redirect}} and {{tl|category redirect}}.

==Potential problems==
==={{anchor|Protected page|Protected pages}}Page protection ===
{{see also|Wikibooks:Protection policy}}
[[Wikibooks:Administrators|Administrators]] are able to '''protect''' a page to restrict editing or moving of that page, and remove such '''protection'''. Protection can be indefinite, or expire after a specified time. 

*'''Full protection''' prevents editing by everyone except administrators. 
*'''Semi-protection''' prevents editing by unregistered contributors and contributors with accounts which are not autoconfirmed.
*'''Creation protection''' prevents a page (normally a previously [[Wikibooks:Deletion policy|deleted]] one) from being recreated.
*'''Move protection''' protects the page solely from [[WB:MOVE|moves]].

Any type of protection or unprotection may be requested at [[Wikibooks:Reading room/Administrative Assistance]]. Changes to a fully protected page should be proposed on the corresponding [[WB:DISCUSS|discussion page]].

==={{anchor|Edit conflict}}Edit conflicts ===
{{shortcut|WB:EC}}
If someone else makes an edit while you are making yours, the result is an edit conflict. Many conflicts can be automatically resolved by the Wiki. If it can't be resolved, however, you will need to resolve it yourself. 

To understand what an edit conflict is, consider the following situation:

* Alice clicks ''Edit'' on a page.
* Bob clicks ''Edit'' on the same page, while Alice is editing.
* Alice finishes her edits and clicks &quot;Save page&quot;. The page is saved with Alice's version while Bob is still editing.
* Bob finishes his edits and clicks &quot;Save page&quot;. Bob gets an &quot;edit conflict&quot; page, because the software can't automatically reconcile the differences between Bob's and Alice's versions of the page. The edit conflict page gives Bob a chance to reconcile the differences manually.

==== Layout ====
At the top of the edit conflict page is an editing box containing Alice's version of the whole page, even if Bob is doing section editing.

At the bottom of the edit conflict page is a second editing box containing the text Bob was going to submit. This will be Bob's version of the page or section he was editing.

Between the two editing boxes is a [[Help:Tracking changes#Viewing diffs|diff]] that shows the difference between Alice's and Bob's version of the page. For the section Bob is editing it shows Bob's changes and Alice's possible changes, except for sections where Bob and Alice have both made the same change. For the other sections it shows the full new text as if all that text was added.

Bob can edit in the upper editing box and press Save.

==== Resolution ====
If Bob only made small changes, and Alice made large changes, he may choose to work from Alice's version, and re-merge his changes in. Bob might choose to add some text like &quot;via edit conflict&quot; to the edit summary to warn Alice and others that he had to do this—Alice can then review his merging for accuracy.

If Bob made large changes, and Alice made small changes, he may choose to work from his version. One option is for Bob to copy the bottom text into the top text (or just copy over the one section of the top text, if Bob was section editing), with an appropriate [[#Edit summary|edit summary]] (e.g., &quot;via edit conflict, will remerge&quot;). Then Bob can view the page history, determine Alice's changes, and re-apply them to his version, in a separate edit.

If both Alice and Bob made large changes, matters become complicated, and Alice and Bob just have to do the best they can. For example, if both Alice and Bob simultaneously add a large section of text on the same subject, then it may be best for Bob to submit his changes, and then for Alice and Bob to both have a look at the two versions and decide between themselves which version is better.

Bob should not just post his changes over the top of Alice's. We [[Wikibooks:Assume good faith|assume good faith]]—mistakes are occasionally made, and newcomers may not understand the edit conflict window. However, Bob must not routinely ignore edit conflicts. It is absolutely not acceptable for Bob to overwrite Alice out of laziness. We encourage contributors to double-check their merges by using the [[Help:Tracking changes#Viewing diffs|diff]] feature.

==== Prevention ====
Because edit conflicts are irritating and time-consuming, you may choose to alter your editing habits so they happen less often. 

One of the easiest ways is to edit the smallest portion of the page necessary. If you are only going to be editing a single section in the page , then click the &quot;Edit&quot; link for that section, rather than the &quot;Edit&quot; link for the entire page. Two people can be working on different sections at the same time, and there will be no edit conflict.

To reduce the chance of edit conflicts, Wikibooks also has an &quot;In Use&quot; notice in its [[Help:Templates|Template]] namespace that people may use when editing a page over a long period of time.  Simply put {{tl|in use}} on a page before proceeding with a major edit, and remove the template when the editing is complete.

== See also ==
{{Meta|Help:Link}}
*[[Editing Wikitext]]
* [[Template:Color|text color]]

{{Wikibooks editor navigation}}
[[ja:Wikibooks:編集の仕方]]
[[ko:위키책:편집실]]</text>
      <sha1>m568nt9qsn6264sgmri5d0qasrl0639</sha1>
    </revision>
  </page>
  <page>
    <title>Video Game Design/Archetypes</title>
    <ns>0</ns>
    <id>65198</id>
    <revision>
      <id>4678644</id>
      <parentid>4635852</parentid>
      <timestamp>2026-10-28T00:07:23Z</timestamp>
      <contributor>
        <username>Panic2k4</username>
        <id>2865</id>
      </contributor>
      <comment>/* Scroll */ Asteroids game overview and introduction to scrolling games</comment>
      <origin>4678644</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="24678" sha1="nqzre8gz3kp9kbxe52hi5sp7h5qqqw1" xml:space="preserve">== Archetypes ==
There are many genres (type classification) of games, each one within its own defined domain, that commonly will have sub-domains (in a tree like form). All the games in a particular genre tend to share certain conventions, since they are the defining element. A game can also be classified in more than one genre, by layering (sectioning the game-play) or as a result of experimentation in an attempt to innovate or simply by a need to place very similar games in distinct categories.

For instance strategy games that are real time, will often share most common elements of turn base games, in fact '''RTS''' (Real time strategy) can be defined as a logical evolution of TBS games, due to the possibilities opened by the increase of computational power and graphics capabilities. In this example strategy games will then be the common root of TBS and RTS genres, and will include for instance the card game of Solitaire. Continuing with the example the Solitare game would be part of the simulator genre and its sub-domain of card games.

{{NOTE|A careful consideration should be given to the expectations of players, for instant it is not uncommon that RTS games will often include a turn base version of the game-play. Too much innovation can put players off. The same can be said by the need of normalization, but that will be discussed later on...}}

The game genre can also be defining in the type of people who would play it.

An '''archetype''' is a game that implements the purest set of conventions that is commonly accepted as defining a genre. A good example of an archetype would be any game that first implemented a genre or later implementations that strictly re-uses those conventions without any form of game-play innovation in terms of capabilities.

'''Classic Game Types'''

[[File:Donkey Kong arcade.jpg|thumb|256px|right|&lt;span style=&quot;color:white;&quot;&gt;Nintendo's Arcade version of &quot;Donkey Kong&quot; – this is one of the oldest video games.&lt;/span&gt;]]
'''Arcade Classics'''

Digdug – Pac-man – Asteroids – Space Invaders – Breakout – Pong – Pitfall

{{TODO|Add simple coverage to rise and downfall of the arcade games.}}

=== Maze ===

Example:
*Pacman

=== Platform ===
[[File:Celeste screenshot 02.png|thumb|''Celeste'', a 2D platformer.]]
A [[w:Platform game|platform game]] has the character(s) as anything from the protagonist to Arcadic Conventional and the player-character relationship being 1st or third person.

'''Platforms:'''The levels are designed as side scrollers (meaning that you see everything from the side almost like a cross-section. The character jumps between platforms to progress through the level and often times there are large 'bottomless-holes' in which the character dies.

'''Collectibles:''' Levels consist of collectibles such as coins, items, etc. which increase abilities and score. A subgenre of 3D platformer, the '''Collectathon''', makes gaining collectibles the primary goal.

Some platform games:
*[[w:Super Mario Bros|Super Mario Bros]]
*[[w:Mario 64|Super Mario 64]]

=== Scroll ===
The issue of defining a scroll game is complex, it starts by establishing what is constant (less movement and alteration) to what changes more (often the context) but this often diverges from the creator to the player, even as an intended illusion, that reverses the roles in the player's mind.

It is central to identify the definition as being centred on the players' perspective. From the old [[w:https://en.wikipedia.org/wiki/Asteroids_(video_game)|Asteroids game arcade]] into a myriad of reimplantations ([https://codingtrain.github.io/Asteroids/ Asteroids game] for the browse https://github.com/ggiraldo/Asteroids (Open Source) and evolutions of the concept, [https://osresearch.github.io/spacerocks2000/spacerocks2000/Spacerocks 2000] (https://osresearch.github.io/spacerocks2000) or even a more complex relativistic implementation [https://www.highdimensionalcoconuts.com/Work/RelativisticAsteroids/index.html Relativistic Asteroids] ) into a complex Rally simulator most of it is the same mechanic of scrolling and creating the illusion of a larger context for the player.

=== Puzzle ===
A [[:en:Puzzle game|Puzzle game]] usually uses both character and player-character relationship as an influence in the game. It uses concepts of score and level progression through logic and skill.

Some Puzzle games:

Myst – [[:en:Tetris|Tetris]] – Lumines

== Medium Qualifiers ==
The appearance of 3D environments in games that first started with vectorial simulations creates the need to distinguish 2D games from 3D, in arcades there was also attempts to create real 3D games, with minor successes and game studios attempted also a new type of system, the interactive video game that one day will probably make a come back. While not an archetype this type of qualifiers are often part of a game description.

=== 2D ===
{{TODO|Complete}}

=== 3D ===
{{TODO|Complete}}

=== Interactive ===
{{TODO|Complete}}

== Extended Game Types ==
The end of the arcade matches well with the increase of affordability of powerful game systems for home use. A time that sees the rise of the 3D environment over the older 2D. As the game specific arcade starts to become unprofitable new genres starts to appear, especially due to the home computer and long play models that wouldn't fit the arcade model.

=== Strategy ===

{{TODO|Cover Play by mail, and the need of reliable machines and the popularization of the PC so these type of game could be moved out of the main frames}}

==== Turn-base Strategy ====
The turn base strategy genre usually focus on tactics rather than superiority of arms such as in many RTS, the genre is therefore preferred by many gamers who desire long duration, complexity and greater tactical challenges instead of the hectic and repetitive game-play that is the basis of most recent RTS that is more focused in optimization of actions and returns.

The context were turn-base strategy can be applied is very vast, from military campaigns to businesses and fantasy all is opened to create the background.

*[[w:Lords of Magic|Lords of Magic]]

==== Real Time Strategy (RTS) ====
RTS, obviously stands for Real Time Strategy and as a game type it attempts to categorize any game system that permits strategizing over the game’s elements and actions in real time. This may include resource management, territorial control, unit coordination, and the ability to issue commands while the simulation continues to evolve. In many modern implementations the player may pause or slow the game to queue actions or set future behaviors, especially in more modern titles where hardware improvements allow increased complexity and the management of many interacting assets. In its more archaic form the game’s action and user interaction unfold without discrete turns that characterize classical board games or early computer strategy titles. This continuous flow of time is a mechanical constraint that shapes how players perceive the game world and how developers must structure interactions. In early implementations the player acted directly in real time, issuing commands as events unfolded, while modern hardware allows temporary pauses or slowdowns that let the player queue actions or define future behaviors. These differences reflect the evolution of computing power, memory, and interface design, all of which expanded the expressive range of RTS mechanics.

The conceptual roots of RTS design appeared long before the term existed. Early home computers such as the [[w:ZX Spectrum|ZX Spectrum]] and [[w:Commodore 64|Commodore 64]] hosted games that required players to react to unfolding situations, manage multiple agents, or control territory under time pressure. These titles did not yet form a coherent genre, but they introduced the essential idea that strategy could occur in real time. As hardware improved, developers gained the ability to simulate larger worlds, track more units, and update game states continuously. This shift from discrete to continuous simulation is central to understanding RTS design, because it forces players to think in terms of flow, timing, and prioritization rather than isolated decisions.

The emergence of RTS as a distinct type occurred on personal computers when higher resolutions, expanded memory, and mouse‑driven interfaces became standard. The mouse allowed rapid spatial commands, while the keyboard provided hotkeys and control groups that let players manage many units at once. These interface innovations were structural enablers of RTS complexity. Without them, the genre could not have developed its characteristic mechanics of base construction, resource economies, and multi‑unit coordination. The viewpoint used in these games, often top‑down or isometric, became equally important. It provided a clear representation of the battlefield, allowed rapid scanning of threats, and supported the mental mapping required for strategic planning. The open‑source project [[w:0 A.D. (video game)|0 A.D.]] illustrates how this visual language persists, with its isometric depiction of ancient cities demonstrating the clarity and readability that RTS design demands.&lt;br&gt; [[File:0 A.D. Seleukiden-Stadt Ken Wood 23.png|thumb|''0 A.D.'', an open source RTS.]]

As the genre matured, developers began exploring how terrain, physics, and environmental conditions could influence strategy. Games such as [[w:Command &amp; Conquer:_Tiberian_Sun|Tiberian Sun]] introduced height differences, destructible terrain, day‑night cycles, and weather systems that altered visibility and movement. These features encouraged players to consider elevation, cover, and environmental timing as strategic tools. The game also demonstrated how faction identity could be reinforced through mechanical asymmetry, with the GDI relying on heavy mechanized units and the Brotherhood of NOD emphasizing stealth, mobility, and unconventional tactics. Sound design played a crucial role in reinforcing these systems, with unit acknowledgments, construction cues, and musical pacing guiding the player’s attention across the battlefield.

{{YouTube link|2VwygGxTJH0|14 RTS Games are Still Memorable}} (Dark Reign is not mentioned but the topology and unit terrain effect was innovative)

Other developers focused on readability and empire‑scale clarity. [[w:Age of Empires II|Age of Empires II]] refined the classical RTS interface into a highly legible system where a single glance conveyed the state of the economy, the army, and the battlefield. Its emphasis on historical progression, resource balance, and clear visual language made it a model of strategic readability. The game demonstrated that clarity is not merely aesthetic but a mechanical requirement for large‑scale decision‑making.

The genre expanded further when developers began experimenting with three‑dimensional space. [[w:Homeworld|Homeworld]] introduced full 3D movement, requiring players to think in terms of volume rather than surface. This shift demanded new camera systems, new selection mechanics, and new spatial reasoning skills. Homeworld also pioneered persistent fleets, where surviving units carried over between missions, creating emotional investment and long‑term strategic consequences. Its ambient soundtrack and minimalist interface demonstrated how audio and visual design could support cognitive clarity in complex spatial environments.

Other titles explored stylistic experimentation and thematic extremes. KKND embraced exaggerated post‑apocalyptic aesthetics and fast‑paced combat, demonstrating how tone and visual identity could shape player expectations even when core mechanics remained familiar. In contrast, [[w:Total Annihilation|Total Annihilation]] pushed the technical boundaries of the genre with physics‑based projectiles, deformable terrain, and a streaming economy that reduced micromanagement. Its automation systems allowed units to behave intelligently without removing strategic agency, and its large‑scale battles demonstrated how hardware advances could support unprecedented simulation depth.

Some developers pursued scale as a defining feature. [[w:Cossacks:_European_Wars|Cossacks]] supported thousands of units simultaneously, emphasizing logistics, formations, and the industrial scale of early modern warfare. Its economy demanded constant attention, turning resource management into a strategic race that mirrored historical supply challenges. The game demonstrated that RTS design could model not only tactical engagements but also the logistical and organizational demands of large armies.

Other titles explored customization and community‑driven evolution. [[w:Warzone 2100|Warzone 2100]] introduced a modular unit design system where players combined chassis, propulsion, and weaponry to create bespoke forces. Its sensor‑driven artillery and automated counter‑battery systems showed how information flow could become a strategic resource. After the original studio closed, the game’s source code was released, and the community maintained it as an open‑source project, illustrating how player dedication can preserve and extend a game’s legacy.

The genre also produced titles that defined competitive play. [[w:StarCraft|StarCraft]] demonstrated how asymmetrical factions, tight control mechanics, and high mechanical skill ceilings could transform RTS into a competitive sport. Its emphasis on actions per minute, multitasking, and predictive play created a new form of strategic expression where physical speed became a resource. The game’s sound design, from unit barks to alert tones, reinforced the player’s cognitive map and supported rapid decision‑making under pressure.

Hybrid designs also emerged. Kingdom Under Fire blended RTS with action‑oriented hero control, requiring players to manage both large‑scale strategy and direct combat execution. Earth 2150 expanded the use of 3D terrain by allowing players to dig trenches, carve tunnels, and manipulate the environment as a tactical tool. Submarine Titans explored verticality in underwater environments, requiring players to manage depth as a strategic dimension and to maintain complex logistics in a hostile environment.

Not every experiment succeeded. Conquest Earth attempted to innovate with picture‑in‑picture views, fog generators, and direct unit control, but its interface complexity and lack of cohesion demonstrated that innovation must support, rather than obscure, the core strategic loop.

The foundational model of the genre remains [[w:Command &amp; Conquer|Command &amp; Conquer]], which established the basic loop of harvesting, building, training, and attacking. Its use of full‑motion video, asymmetrical factions, and accessible controls created a template that influenced nearly every RTS that followed. Licensed adaptations such as [[w:Star_Wars:_Galactic_Battlegrounds|Star Wars: Galactic Battlegrounds]] demonstrated how established engines could be repurposed to support new thematic settings while preserving mechanical clarity.

Within the broader Strategy category Real Time Strategy represents the lineage of games built around continuous decision‑making, simultaneous control, and evolving game states. It differs from turn‑based strategy through its uninterrupted flow of time and from tactical or simulation subtypes through its emphasis on the player’s influence over multiple agents and interconnected systems. RTS design continues to evolve, but its roots stretch back to the earliest experiments in real‑time control, and its modern form reflects the combined influence of hardware development, interface design, player psychology, sound design, and the visual languages that define how game worlds are perceived and controlled.

==== Tactical Combat Simulation ====
*[[w:Laser Squad|Laser Squad]], turn based.
*[[w:Jagged Alliance (series)|Jagged Alliance]], initially turn based, newer releases are mixed mode.

==== War Simulation ====
*[[w:Romance of the Three Kingdoms (video game series)|Romance of the Three Kingdoms]], turn based.

==== Business/Economy/Social simulation ====
[[File:Farhill Transport, 14th Mar 1939.png|thumb|''OpenTTD'' simulates the transportation business.]]
*[[w:OpenTTD|OpenTTD]], real time.
*Civilization, turn based.

==== Other with no specific niches ====
*Final Fantasy Tactics, turn based.
*[[w:Dawn of war| Warhammer 40,000: Dawn of War]], real time.
*[[w:Heroes of Might and Magic| Heroes of Might and Magic]], turn based.
*Black and White
*Imperium Galactica
*Real War

=== Role Playing ===
This defines any games wherein there the character(s) is/are the ''protagonist'' and the player either has a 3rd or 1st person interaction with it/them. Usually these games incorporate a personal view point of fantastic or futuristic settings, although others certainly exist.

==== Role Playing Game (RPG) ====
RPG or Role Playing Game should not to be simply confused with the more broad definition of role playing. The RPG genre evolved directly from complex table games.

The elements of an RPG generally include:

'''Battle:'''
Most RPGs have some form of battling in them. Historically they can occur in a resolution stage, based on a ''turn-based'' battle system, which shows players a new screen where the enemies are on one side of the 'field' and the characters are on the other. Each side must then wait till to gain enough ''energy'' to attack the other. The battle system often contains elements such as '''HP''' (health points), '''MP''' (Magic points), attack, speed, stamina, defense, and so forth.

A major portion of the battle system is '''EXP''' (experience) points. When the character(s) defeat an enemy it gain EXP and when it gains enough it will ''gain a level'', which increases some or all of its game statistics. This can be new or increased magic, spells, and special attacks.

recently however with more powerful processing power available, this static battle system have fallen in disuse, most RPGs today tend to be 3D and real-time combat is often the solution adopted.

'''Inventory:'''
A database of items, armor, weapons, and so forth the characters hold.

'''Story line:'''
Usually the player starts out with one or a few characters and the challenge is presented. Then as the game progresses members of the player's ''party'' leave and new ones enter. Games like this are generally divided into regions wherein the player must fight through and discover the problem then fight a ''boss''. At the end of the game the player usually fights the ''final boss'' which generally has 3 stages. RPGs have a lot of talking and usually have deeper storyline than other game types.

'''Character Progression:''
As an extension of the battle system mentioned above, most RPGs heavily emphasize the player developing their character(s) over the course of the game. Systems that increase the character's prowess in battle are most common, although others, such as crafting systems to create equipment for the character, are also relatively common.

Some RPGs:

[[w:Final Fantasy| Final Fantasy]]

Kingdom Hearts (Series)

Baldur's Gate – Dark Stone – Fallout – Ultima – Star Ocean – Dragon's Quest – Elder Scrolls – Icewind Dale

Hack n' Slash RPG Games:

Diablo I and II – Dynasty Warriors – Gauntlet Legends – Champions

These games are considered a variance of the RPG genre; however, they fall under the Hack n' Slash category. These games differ by the character's depth as well as the core game-play mechanics of how the game runs.

==== Action/Adventure ====
Action/Adventure Games usually have 3rd person (sometimes 1st person) player character relationship and the character is usually the protagonist. They may mix several other types but ultimately they are role playing games.

Examples:
*[[w:The Legend of Zelda series| Zelda]]
*Lost Planet
*Tomb Raider

=== First Person Shooters (FPS) ===
[[File:Xonotic 0.8.2 rocket.jpg|thumb|''Xontic'', an open source FPS.]]
First Person Shooters are games based on the so called 1st person perspective (although this very often puts your point of view in about chest height of the character) that places you behind the eyes of the protagonist.
The elements of an FPS are:

'''Weapons and artillery:''' The character is able to collect and use weapons and artillery with which they use to attack and destroy other characters/enemies.

'''Story line:''' Usually an FPS does not have a very deep story line and is more about staying alive than anything.

Some FPS's:

*[[w:Metroid Prime| Metroid Prime]]
*[[w:Quake|Quake]]
*[[w:Duke Nukem 3D|Duke Nukem 3D]]
*[[w:Doom| Doom]]
*[[w:Halo (video game series)|Halo]]
*[[w:Half-Life|Half-Life]]
*Goldeneye
*Perfect Dark
*Turok
*Bioshock

=== Racing ===
[[File:Supertuxkart-0.9-screenshot-7.jpg|thumb|''Super Tux Kart'', an open source racing game.]]
A racing game usually uses a 3rd (sometimes 1st) person player-character relationship where the character is an arcadic convention. Elements of Racing games are:

'''Vehicles:''' Usually there is some type of vehicle which the character drives, sometimes these vehicles are customizable and the game lets you choose a vehicle. Different vehicles usually have different stats such as faster speed but worse turning etc.

'''The Race:'''The race is separated in laps and judged by time and placing. Usually the game will have a 'time trial' mode wherein the player can try to beat a time. In the race the character will race against other characters (2+) the standard being 8.

Some Racing Games:
*[[w:Mario Kart| Mario Kart]]
*Ridge Racer
*Gran Turismo
*Forza
*Wave Race 64
*Need For Speed
*Project Gotham Racing
*Burnout

=== Simulation ===
[[File:Flightgear 2018.3 - Madrid, Spain at dawn with OSM2City output.jpg|thumb|''FlightGear'', an open source flight simulator.]]
A simulator is as it says a simulation of reality, even an imaginary reality will do. The differences on how that reality is reflected is not very significant in classifying a game as a simulator, it only suffices that a simulation is clear on the bounds it intends in replicating and the level of detail it provides. Most simulators will include several sub-genre but they are clearly in a class of their own.

Most simulator in 3D tend to have a hight degree of quality in regards to the simulated reality, that may indeed not satisfy the player beyond the specific purpose of the simulation. They are also mostly real time (or with real-time capability). This are often dedicated to things planes, helicopters, railroads, cars and tanks or even submarines in specific or generalized scenarios.

Isometric simulators are mostly relegating to economic simulation, management and construction, the need to reflect reality is not as important and modelization will suffice. They tend to be turn based or include very carefully designed pause events.

A simulation game can also have a variety of character and character relationships. Usually however, the player-character relationship is influence and the character are archaic and conventional.

Some Simulation Games:
*City-building and management simulator
**[[w:SimCity 4|Sim City]]
*Family simulation
**[[w:The sims|The Sims]]
*Flight simulator
*Management simulator
**[[w:Theme Hospital|Theme Hospital]]
*Trade simulation
**Space trade
***[[w:Elite (video game)|Elite]], [[w:Freelancer (video game)|Freelancer]] ...

=== Grow-like games ===
The Grow-like games can be considered a kind of puzzle game,
but the way the narrative emerges with little information about rules, boundaries, and outcomes causes some to consider them in a genre all their own.
&lt;ref&gt;[http://infocult.typepad.com/infocult/2006/11/the_grow_genre_.html &quot;The Grow genre continues&quot;];
[http://infocult.typepad.com/infocult/2006/05/a_new_grow_game.html &quot;A new Grow game&quot;]&lt;/ref&gt;

=== Rhythm games ===
[[File:Fretsonfire4.png|thumb|''Ferts on Fire'', an open source rhythm game.]]
Also a sub-genre of puzzle gaming, that specifically deals with the reproduction of actions and movements to replicate specific sequences of visual or audio queues.

=== Cross Genre Games ===

Hellgate: London – Rampart

==== MMO ====
MMO or Massively Multiplayer Online consists of all forms of all game genres where a nearly infinite number of players interact with each other via the Internet. MMO's usually consist of players killing monsters, doing quests, etc. to get to the highest level. MMO's are often PvP (Player vs. Player), where players from around the world will battle with each other with their custom-formed character.

== References ==
{{reflist}}

{{BookCat}}</text>
      <sha1>nqzre8gz3kp9kbxe52hi5sp7h5qqqw1</sha1>
    </revision>
  </page>
  <page>
    <title>Analog and Digital Conversion/The Ideal Sampler</title>
    <ns>0</ns>
    <id>85108</id>
    <revision>
      <id>4678507</id>
      <parentid>4504594</parentid>
      <timestamp>2026-10-27T15:52:28Z</timestamp>
      <contributor>
        <username>Iain marcuson</username>
        <id>3175980</id>
      </contributor>
      <comment>/* Ideal Sampler */  Add schematic of sample-and-hold.</comment>
      <origin>4678507</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4151" sha1="szlkw2geg35uew7ltrd7lo24u44zlx4" xml:space="preserve">{{ADC Page}}

== Ideal Sampler ==

{{info|The following few sections may rely heavily on [[Calculus]]. Sections not requiring calculus will appear at the end of this page}}

Let us say that we have a sampler device that operates as follows: [[File:Sample-hold-circuit.svg|thumb|right|alt=An input signal AI enters an amplifier.  The amplifier connects to a switch controlled by signal C.  The output of the switch connects to a capacitor, in turn connected to an amplifier whose output is AO|An ideal sample-and-hold, here referred to as a sampler.]]  
every T seconds, the sampler reads the current value of the input signal at that exact moment. The sampler then holds that value on the output for T seconds, before taking the next sample. We have a generic input to this system, f(t), and our sampled output will be denoted f*(t).  
We can then show the following relationship between the two signals:
:&lt;math&gt;f^*(t) = f(0)(u(0)-u(T)) + f(T)(u(T)-u(2T)) + ...&lt;/math&gt;

Note that the &lt;math&gt;f^*(nT+t)&lt;/math&gt; is constant for all &lt;math&gt;t\in[0,T)&lt;/math&gt;.  This applies for all integer &lt;math&gt;n \ge 0&lt;/math&gt;

== Star Transform ==

Taking the Laplace transform of this infinite sequence will yield us with a special result called the '''star transform'''. The star transform is also occasionally called the &quot;starred transform&quot; in some texts.

The star transform is defined as such:

:&lt;math&gt;F^*(s) = \mathcal{L}^*[f(t)] = \sum_{i = 0}^\infty f(iT)e^{-siT}&lt;/math&gt;

The star transform depends on the sampling time, T, and is different for a single signal, depending on the speed at which the signal is sampled.

== Sampler Block Diagram ==

{{info|Information below here will not require any previous knowledge of calculus}}

A sampler is usually denoted on a circuit diagram as being a switch that opens and closes at set intervals. These intervals represent the sampling time, T.

{{TextBox|
;Sampling Time:The amount of time between successive samples.
}}

Samplers work by reading in an analog waveform, and &quot;catching&quot; the value of that waveform at a particular point in time. This value is then fed into an ADC converter, and a digital sequence is produced.

The exact method by which the digital sequence is produced will be discussed later in the sections on quantization.

== Sampling Delays ==

Real samplers take a certain amount of time to read the sample, and convert it into a digital representation. This delay can usually be modeled as a delay unit in series with the sampler.

== Sampling Jitter ==

Samplers in real life don't always take a perfect sample exactly at time T, but instead sample &quot;around&quot; the right time. The difference between the ideal sampling time T, and the actual sample time is known as the &quot;Sampling Jitter&quot;, or simply the '''jitter'''.

== Periodicity ==

A signal is said to be periodic if there exists 
:&lt;math&gt;T\ne0 | f(t+T) = f(t) \forall t&lt;/math&gt;

A simple periodic function is
:&lt;math&gt;f(t) = \text{sin}(2\pi{}ft)&lt;/math&gt;

The above is a sine wave with frequency f and period &lt;math&gt;1\over{f}&lt;/math&gt;.  This sine wave will be sampled with sample frequency &lt;math&gt;f_s = {1\over{T'}}&lt;/math&gt;, or sample period &lt;math&gt;T'&lt;/math&gt;, meaning that we sample at &lt;math&gt;t=T'n&lt;/math&gt;.

=== Periodic After Sampling ===

Let &lt;math&gt;f=1&lt;/math&gt;.  Then

:&lt;math&gt;f(t) = \text{sin}(2\pi{}(1)t) = \text{sin}(2\pi{}t)&lt;/math&gt;

is periodic with period 1.

Let &lt;math&gt;T'=0.25&lt;/math&gt;  This yields

:&lt;math&gt;\begin{align}f^*(n) &amp; = f(nT), n\in\mathbb{Z} \\
&amp; = \text{sin}\left (2\pi{}(1)(nT')\right ) \\
&amp; = \text{sin}\left (2\pi{}n(0.25) \right ) \\
&amp; = \text{sin}\left ({\pi\over{2}}n \right )
\end{align}&lt;/math&gt; 

The sampled function is period if there is some &lt;math&gt;N \in \mathbb{N} | f^*(n+N) = f^*(n)&lt;/math&gt;

:&lt;math&gt;\begin{align}
f^*(n+N) &amp; = \text{sin}\left ({\pi\over{2}}(n+N) \right ) \\
&amp; = \text{sin}\left ({\pi\over{2}}n + {\pi\over{2}}N \right ) \\
\text{If N=4, then} \\
f*(n+N) &amp;= \text{sin}\left ({\pi\over{2}}n + {\pi\over{2}}(4) \right ) \\
&amp;= \text{sin}\left ({\pi\over{2}}n + 2\pi \right ) \\
&amp;= \text{sin}\left ({\pi\over{2}}n \right ) \\
&amp;= f^*(n)
\end{align}&lt;/math&gt;

This function is periodic in &lt;math&gt;n&lt;/math&gt; for &lt;math&gt;N=4&lt;/math&gt;.</text>
      <sha1>szlkw2geg35uew7ltrd7lo24u44zlx4</sha1>
    </revision>
  </page>
  <page>
    <title>User:Panic2k4/Sandbox/RapidEdit</title>
    <ns>2</ns>
    <id>99629</id>
    <revision>
      <id>4678622</id>
      <parentid>4643930</parentid>
      <timestamp>2026-10-27T21:50:28Z</timestamp>
      <contributor>
        <username>Panic2k4</username>
        <id>2865</id>
      </contributor>
      <minor />
      <origin>4678622</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="30012" sha1="6bgmdyf1q0y0y4k993z93dc6hj1kooo" xml:space="preserve">[[w:Help:Wikitext|Wikitext]] - [[Wikibooks:Boilerplate request for permission]]

== Welcome message ==
&lt;small&gt;&lt;small&gt;(This is not an automated message, I'll be watching during a time for any reply you make to it...)&lt;/small&gt;&lt;/small&gt;

Hello, and '''[[Wikibooks:Welcome, newcomers|welcome]]''' to [[Wikibooks]]!

Here are some tips to [[Help|help]] you get started:
* To learn the wiki-markup-language syntax, see [[Help:Editing]].
* Make sure to sign your posts and comments with four tildes, like this: &amp;#126;&amp;#126;&amp;#126;&amp;#126; 
**There is a box at the top of the edit window (if javascript is enabled on your browser) that will insert it too (looks like part of a signature). This will let others know who left it, and make it easy to reply back to you.
* Remember to conduct any editing experiments in the [[Wikibooks:Sandbox|sandbox]] (global to the system) or in a page on your own userspace.
* Remember to use [[Commons:Main Page|Commons]] project for image uploading.
* You can tell the community something about yourself in your userpage.
** You can get to this page by clicking the tab at the top of the page labeled with your registered username.
* Wikibooks are open-source textbooks. ([[WB:WIW|What is Wikibooks]]).
* If you are a '''Wikipedian''', see [[Wikibooks:Wikibooks for Wikipedians]] for a primer since things work a little different here.
** If you want to base your work here on materials from Wikipedia, please use [[WB:RFI]].
* If you're an '''instructor''' and plan on using Wikibooks for a class project, see [[Wikibooks:Guidelines for class projects]]
* Please say hello at the [[Wikibooks:Reading room|Reading Room]] with any questions or ideas.
* Eventually, you might want to read the [[Wikibooks:Manual of Style|Manual of Style]] and [[Wikibooks:Policies and guidelines|Policies and Guidelines]].
** Help us by participating in policy and guideline creation.
** Please take a look at [[Wikibooks:Naming policy]] before starting a new book.
* Remember to keep a [[Wikibooks:Neutral point of view|Neutral point of view]].
* Explore, [[Wikibooks:Be bold in updating pages|be bold in editing pages]], and have fun!

You will find more resources in [[Wikibooks:Community Portal|Community Portal]]. If you have questions, visit the [[Wikibooks:Study help desk|Study help desk]], the [[Wikibooks:Reading room|Reading Room]], [[Wikibooks:IRC channels|IRC channel]] or [[User_talk:Panic2k4|ask me personally on my talk page]]. For site news, see the [[WB:BB|Bulletin board]]. It might be a good idea to add that page to your &quot;[[Special:Watchlist|watchlist]]&quot; so that you can see when any new information is posted there. You can do that by clicking the tab labeled &quot;watch&quot; at the top of the page.


Good luck!

----

== Edit warning ==
&lt;nowiki&gt;
{{tmbox|type=notice|text='''Please help &lt;u&gt;''improve''&lt;/u&gt; Wikibooks'''.

Your [[Special:Contributions/EDIT|recent edits]] are considered unconstructive by fellow contributors. Please read [[WB:WIW|What is Wikibooks?]] for a description of what we allow. You can ask questions or ask for help in the [[WB:HELP|Assistance Reading Room]]. Please use the [[Wikibooks:Sandbox|sandbox]] for experimenting with the wiki software in the future. Thanks. --~~~~ }}

{{copypaste}}
&lt;/nowiki&gt;

== Get involved ==
&lt;nowiki&gt;
If you get interested in some of the politics of the system, most important if to keep the project evolving according to your needs, you could start by looking or participating in the common discussions forums, like [[WB:RFD]], and in any policy discussions as they are announced. This projects is very distinct from any other on Wikimedia. --~~~~
&lt;/nowiki&gt;

== Avoid copyright paranoia ==
You can avoid any copyright conflict in many ways, by using a different method, approach or structure one can avoid to direct copy word by word any copyright material, in any case we at wikibooks aren't cops nor is our duty to protect any copyright holders rights, but as any Wikibookian we should prevent copyright problems to the project.
Our copyright policy is in [[Wikibooks:Copyrights]] with some extensions added to media files in [[Wikibooks:Media]] and some more useful referential info is pointed out in the [[Wikibooks:Designated agent]] page.
If you are sure there will be no problem and until anyone proves a blatant copyright violation or the copyright holder requests a pull down you should be free to contribute in anyway you see as an improvement to the project. In the event there is a violation if not properly addressed per policy it will be deleted.  --[[User:Panic2k4|Panic]] ([[User talk:Panic2k4|talk]]) 02:41, 10 September 2008 (UTC)

==Welcome!==
[[Help:Welcome, newcomers|Welcome to Wikibooks]], a collection of open-content textbooks! You do not have to [[Special:Userlogin|log in]] to read or edit articles on Wikibooks. Creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
*The use of a username of your choice
*The ability to view all your contributions via a &quot;My contributions&quot; link 
*Your own [[w:Wikipedia:User_page|user page]] 
*Your talk page can, if you choose, allow users to send you messages without knowing your e-mail address
*Use a personal [[Special:Watchlist|watchlist]] so that you can add articles that interest you to monitor for changes.
*The ability to rename pages.
*The ability to [[Special:Upload|upload images]] 
*The ability to customize the appearance and behavior of the website
*The eligibility to become an [[Help:Administrators|administrator]] 
*The right to be heard in votes and elections
*Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibookian and '''[[Special:Userlogin|create an account]]'''. Feel free to ask me any questions you may have on my talk page. Make sure to sign your posts and comments with four tildes ('''&amp;#126;&amp;#126;&amp;#126;&amp;#126;'''), this will let others know who left it.

----
&lt;div style=&quot;text-align: center;&quot;&gt;&lt;big&gt;&lt;big&gt;&lt;big&gt;&lt;big&gt;&lt;big&gt;&lt;big&gt;&amp;#8617;&lt;/big&gt;&lt;/big&gt;&lt;/big&gt;&lt;/big&gt;&lt;/big&gt;&lt;/big&gt;&lt;/div&gt;

== VFD initiated... ==
&lt;nowiki&gt;
== VFD initiated... ==
{{mbox|type=warning|text=
'''[[Cookbook/Temp|Cookbook/Temp]] has been nominated for deletion. Please [[WB:VFD#Cookbook/Temp|share your thoughts]].'''&lt;br/&gt;You are being notified because you have created the page. If you haven't already, please see our [[WB:DP|deletion policy]].&lt;br&gt;  --~~~~}}
&lt;/nowiki&gt;

== Question ==
{|
|-
| style=&quot;vertical-align: top&quot; | [[Image:QW Question Mark.jpg]]
| style=&quot;border-left: 1px solid #000000; padding-left: 5px;&quot; |'''''Can I get a questions?'''''{{clr}}
|}
----

&lt;div style=&quot;clear: both;&quot;&gt;
&amp;nbsp; 
&lt;div style=&quot;float: left; vertical-align: top;&quot;&gt;
[[Image:Gnome-mime-text-x-readme.png|{{#if: {{{size|}}} | {{{size}}} | 25px}}]]
&lt;/div&gt;
&lt;div class=&quot;PrettyTextBox&quot; style=&quot;float: center; vertical-align:bottom; margin: 20px; padding: 0px 20px 0px 20px;&quot;&gt;
Text
&lt;/div&gt;
&lt;/div&gt;

----
Copyright 101  http://www.ascd.org/authors/ed_lead/el200112_simpson.html

&lt;!--
[[Programming:C plus plus/Cover|Test Cover]]

{{TotalAnnihilationTOC}}

http://en.wikibooks.org/wiki/Template:TotalAnnihilationTOC
--&gt;

[[Image:Graham's Hierarchy of Disagreement.jpg]]

{{[[Template:Displaytitle|Displaytitle]]}}

&lt;nowiki&gt;{{outdent|:::::::::::}}&lt;/nowiki&gt; = reset ident

&lt;nowiki&gt;
{{non-free software screenshot}}
{{non-free use rationale
|book       = Metasploit
|not free    = The written work describes or relates directly to the software that in displayed in the image.
|rationale   = It would reduce the usefulness of the written work not to provide an image.
|must use    = The image illustrates or helps to contextualize the textual information provided on the written work. 
}}
&lt;/nowiki&gt;

{{u|Panic2k4}}

== Structure changes ==
*Software maintenance
**Debugging
**Optimization
**Refactoring
**Rewrite

== WB:RFA posts (copy of post on WK talk page)==

My objection [[http://en.wikibooks.org/w/index.php?title=Wikibooks:Requests_for_adminship&amp;diff=prev&amp;oldid=696100 here]]

Your objection (recent) [[http://en.wikibooks.org/w/index.php?title=Wikibooks%3ARequests_for_adminship&amp;diff=746624&amp;oldid=745940 here]], I must point out that I selected the one that you state clearly the viewpoints that I find myself sharing with you.

You logic on the rejection of my objection (and to my view of the need of consensus but this is not the point we are addressing now, I will gladly engage you on that point on the discussion of the proposed decision policy ) is (older that the validation) [[http://en.wikibooks.org/w/index.php?title=Wikibooks%3ARequests_for_adminship&amp;diff=696974&amp;oldid=696798 here]], the flaw or opposing views, as I see it, is you converged on my points to validate an objection but on my objection you chose to ignore it (not the problem on the table now).  --[[User:Panic2k4|Panic]] 00:39, 15 March 2007 (UTC)

Call your attention also to the comments made by others regarding the validity of my objection. --[[User:Panic2k4|Panic]] 00:41, 15 March 2007 (UTC)

So and taking even you objection text like &quot;things have changed&quot; it is clear that the objectives or requirements to get the admin flag are mutable without necessarily affecting those that already have it and even you seem to evolve your personal requirements for an approval vote lets extrapolate this to a change in your views on the restrictiveness on granting an approval (or that a significant number of people that share your views are not present during a vote) it is easy to see that having the admin flag is not a certainty of trust or knowledge. (I could probably be more specific and point you situations were users were granted administrative flags under circumstances that bypassed those presets).  --[[User:Panic2k4|Panic]] 01:01, 15 March 2007 (UTC)

:There is a big difference between the two candidates. Az was particularly active, especially in fighting vandals and cleaning up vandalism. The other user was not active in any respect. I dont see these two issues being the same at all, and I didnt reverse myself. We can talk about the other issue about me promoting Az despite your objection if you want, but i am not likely to admit fault on that issue either. --[[User:Whiteknight|Whiteknight]] &lt;small&gt;([[User talk:Whiteknight|talk]]) ([[User:Whiteknight/Proposed Books|projects]])&lt;/small&gt; 01:13, 15 March 2007 (UTC)

::Well I can point one that you should clearly remember, the approval of Darklama (I also voted in opposition first and changed later but not because of trust or based on the users knowledge), but lets take that as example as you are particularly up-to-date on my still pending requests, the user performed several actions against stated policy (page moves, heavy structural changes), just before and after he was granted adminship (even you stated that on the call for comments), this is not to say he does not perform in general a good job or that I wish to have him lose his admin flag, it is just to demonstrate that there are a myriad of facets that should be considered when placing so much faith on a user just because he is an admin, it is incontestable that this specific user performed more good than wrong but admins shouldn't have a special hold on what is or not correct, as I said somewhere else admins are normal users on a specific task. (I'll go more deeply on this on the discussion of the revision for the specific policy)

::The consensus issue will be raised on the proper policy as I know you don't share my view on the strict use of it.

::I know that candidates aren't the same but was an opposition (you used the same logic to approve other users), I chose that because its use was similar in the value and content not the target, each user is different.

::Would you agree that an user can easily bypass the check and balances to get the admin flag then ? Any user could easily reproduce the valid work Az performed (with the same level of interaction with the rest of the community) and be granted the flag that doesn't provide any clue about the level of trust or knowledge or will to be involved on community matters in the long run, that is why I opposed at the time, your logic with the other user is even harder, the user already had the flag but lost it due to inertia (was he less trustworthy or with a lesser degree of knowledge, who can say), but I share your vote on that case (I must point out that I didn't particularly like how the removal of older admin flags was performed but I will also address that later). 

::Can we then agree that even if stated as a requirement trust and knowledge it shouldn't be blindly given to any user just because he has the admin flag ? or better yet only to users that have it ? That is what I was aiming to on that discussion a user should be only judged by performance and actions if he is or is not an admin is a lesser issue, I never wanted to be an administrator not because of the &quot;responsibility&quot; or anything like that just because I had no need to, if you place so much importance on that flag I will consider in 6 moths applying to it (that will be fun).  --[[User:Panic2k4|Panic]] 01:40, 15 March 2007 (UTC)

:::It is true that what AZ did (and still does a great deal) could be reproduced by other users. However, I think that it's difficult for someone to put that much work into things like vandal fighting and cleanup, etc, and not wanting to get involved with the community as a whole, especially since the point of doing that kind of stuff is to help protect the community from those that would harm it, and to improve it. However, I do understand your argument and to some degree I agree with you, that the newer admins may not have as much experience\community trust as older (not necessarily admin) contributors. 

:::That being said, I think that if a contributor can show that he or she really knows the ropes, has shown a true desire to get involved with the community, and would make good use of the admin priveleges, no matter how long the person's actually been around, he or she should be allowed to have it. There has to be some limit of course (that's what the 200 edit thing is for; people who are involved with the community will likely have relatively little difficulty reaching that due to all the different reasons there are for making posts) but I think it's not as clear-cut as you seem to be implying especially with your quoted objection to AZ's adminship nomination. Maybe it would make more sense to use as a guideline the number of edits in namespaces ''other'' than the main space, but I digress. &lt;small&gt;Revert me if you don't think it's appropriate for me to talk here but I wanted to keep it all on one page. &lt;/small&gt;[[User:Mattb112885|Mattb112885]] &lt;small&gt;([[User talk:Mattb112885|talk]]) &lt;/small&gt; 03:49, 15 March 2007 (UTC).

::::Well, you got more or less the jest of what I was attempting to reason with [[User:Whiteknight|Whiteknight]], note that I'm not in any way diminishing anyones work here, I was addressing the way, or if you will, the special consideration that [[User:Whiteknight|Whiteknight]] seems to attribute to the admin flag, nothing more (this is based on talks I have had with him and by several posts I have read here and there, I may be giving to much of attention to this point but it was on topic), administrators it is my view are here voluntarily and to provide a service to all not to archive any kind of special status, in a perfect world all would be granted adminiship or even checkuser rights, so, why not let anyone be an arbiter, if anything breaks no harm can be done to the community and the policy can be reworked later if we bar the access to people at the start without a clear justification we are only empowering the segmentation of what constitutes Wikibooks, the community.
::::As a side note and on the same topic, take for instance this page I had done some work and noticed the edit of Darklama and so did not fallow on what I will say next about this section [[Help:Administration_FAQ#Who_monitors_the_conduct_of_an_Administrator.3F]], this kind of information or concept is not only inaccurate but can provide to be dangerous it builds expectations of indeed getting above the others, humans are creatures that are in general driven by very basic instincts or formulate specific goal base decisions, one of the most damaging needs we have is to get above the crowd, known as the ego factor. It should be made clear that administrators aren't a special brotherhood with a secret sign, or right of decision to pass personal judgments, or have special powers, they are simple users like anyone else, granted that they should have some knowledge or have shown interest on the wellbeing of all but lets be fair and admit that this is probably hard to prove and very simple to simulate and ultimately people are people there will always be disagreements and attempts to engrandize oneself, we should attempt to perform above all this but we shouldn't be blind to the facts.
::::In specific to that section, I will let the time pass a little so not to offend or repeat the previous mistake in reverse, it is clear that Admins aren't monitored by the others admins only (Darklama solved only part of the problem), they are monitored by all users, any user can request the pulldown of the administrative flag and any user should (there are no clear policies yet) be able to request administrative  actions to be reaccessed or even reverted, by preventing an outside party or non administrators to participate in the decision process if the involved parties agree, is to me just wrong.  --[[User:Panic2k4|Panic]] 06:49, 15 March 2007 (UTC)

::::PS: Call you attention to consider expressing again your support  [[Wikibooks:Staff_lounge/Technical_Chat#Wikijunior_Namespace]], txs --[[User:Panic2k4|Panic]] 07:47, 15 March 2007 (UTC)

:Administrators must satisfy a vague set of requirements on activity, as well as satisfy vague requirements on their trust and knowledgability. Once those conditions are satisfied (and what it takes to satisfy them does change with time), that user is still subject to a vote of their peers as to whether or not to get adminship. Admins are just like ordinary users, and they are treated as ordinary in all discussions and votes. No special attention is paid to admins because of the flag. However, admins have been voted into a position of trust by the community, and that is a milestone that should not be ignored completely. I don't believe that people who aren't qualified to be admins should serve as arbiters, or bureaucrats, or checkusers. You may see these as all different issues, but I see them as the same: You must first prove that you are trusted (through an admin vote) before you can move on to higher levels of responsibility in the community. 
:In the USA, for instance, any person is entitled to run for president. In practice, however, the only people with a good chance of winning are state governors and US Senators. To the public, people who have already passed the hurdle to become a senator or govenor have less to prove of themselves then a non-politician does. I am not trying to draw a direct parallel, because adminship is not a position of power or control in the same way that presidency is. The point remains: Before moving to a higher rank (or a higher position of responsibility), you should first prove yourself by attaining a lower rank. In other words, you have to work your way up the ladder.
:In response to your comments about Darklama, you need to keep in mind that the [[Wikibooks:Decision making]] guideline is very vague about these kinds of points, and [[User_talk:Panic2k4/blocks_and_other_bits#Comment_by_User:Whiteknight|my comments on Darklama's additions]] served more as a personal interpretation of that guideline. In actuality, Darklama's edits were protected by the '''Be Bold'' directive, and it's only after your complaints are lodged that the decision making process begins. Should he likely have discussed changes with you before making them? Yes. Was he required to ask you before he made those changes? No. If you read the text of these policies and guidelines carefully, Darklama was perfectly in accordance with the edits that he made. --[[User:Whiteknight|Whiteknight]] &lt;small&gt;([[User talk:Whiteknight|talk]]) ([[User:Whiteknight/Proposed Books|projects]])&lt;/small&gt; 13:18, 15 March 2007 (UTC)

::Ok this is my last post on the subject with you because I can't believe you are seriously defending you point or that this will lead anywhere.
::How can you so adamantly defend the validity of the vote for adminiship if you consider the number of users we have on wikibooks (heck, consider only half or a third) and the average number of votes that can give one the flag (7 max) and on top of that there is no compliance with the consensus rule, you can only be joking about it or do you really believe that those votes represent the community ?
::I have proven several weaknesses to the identity of users, shown that a user can easily bypass the checks and balances, show that consensus is not fallowed, I believe if so inclined a few users that get admitted as administrators can remove the administrative flags of most of the older (a good enough proposal and good timing is all it's needed) and virtually control wikibooks, can't you see that if we start centralizing and empowering a segment of the community over the rest we risk such events or even if not started with that express intention such patterns of behavior can emerge.
::This is why I place so much importance on the strict use of consensus.
::I was not discussing Darklama I was commenting on past events and your own comments at the time, but again if we fallow consensus the status quo is maintained, that is all I was asking at the time and still require in several of the changes I initiated dialog and requested the user to give a validity to, the BEBOLD expressly states a limitation to that right and extends into how carefully it should be used, in that particular case Darklama was aware that I didn't agree with several changes he made when I was blocked. Move of pages go above simple edits, no policy, not even BEBOLD can be used to validate the moving of pages from an active book (where someone is working) without discussion.  --[[User:Panic2k4|Panic]] 17:46, 15 March 2007 (UTC)

::: I think you're not assuming the good faith of the administrators, Panic; I know you may have some bitterness towards them but most of them started with a clean plate before making their own decisions, they weren't trying to &quot;control wikibooks&quot;, and they're still not. It just so happens that most of the users on Wikibooks prefer to focus on content rather than doing things like voting on policy and on adminship, and that most of those users that are active in policy happen to be administrators (partly ''for'' that reason; as you pointed out, there have been failed rFas due to insufficient community involvement and knowledge of policy). No, the policy is not ''exact'' on what they mean by &quot;having enough involvement&quot;, this is left open for a reason and that's to allow flexibility for each new rFa that's out there.&lt;small&gt;—The preceding [[w:Wikipedia:Sign your posts on talk pages|unsigned]] comment was added by [[User:Mattb112285|Mattb112285]] ([[User talk:Mattb112285|talk]] • [[Special:Contributions/Mattb112285|contribs]]) {{{2|}}}.&lt;/small&gt;

::::I assume good faith dealing with any person as a rule, not only on wikibooks, but trust and respect is earned and can be lost and levels of both are not fixed or generalized, one has trust and respect for friends and parents but they are no equal, they depend on actions and perception, actions can be simulated and the last one can be fabricated.
::::Several events have indeed left a scar, reading things like this [[http://en.wikibooks.org/w/index.php?title=User_talk%3AChazz&amp;diff=765914&amp;oldid=765011 here]] (random example) and watching intentional misrepresentation of facts have indeed eroded my level of faith on some administrators and that &quot;group&quot; of users  in general. But as I have said people are people and each user is unique.  --[[User:Panic2k4|Panic]] 01:15, 16 March 2007 (UTC)

:::The community is small, and that's why a relatively large portion of the community appears to be admins, and also why admins can be elected with relatively few votes. You haven't &quot;proven&quot; any weaknesses in the identities of users, nor the falliability of admins, nor in the abuse of consensus. You have given your opinions on the matters, and I have disagreed. Also, there is plenty of accordance with the concensus rule. Concensus does not now and has not ever required 100% agreement. Furthermore, '''Be Bold''' enables users to act without gaining concensus (barring argument, of course), and [[Wikibooks:Decision making]] is only a ''guideline'', not a ''policy'' (I wanted it to be a policy, but the community decided to have more flexibility in the matter). 1 arbitrary disagreement among 7 strong support votes cannot and ''will not'' stop a measure from passing. I heard your objection, and I acknowledged it, but as the acting Bureaucrat I didn't believe that your objection was enough to stop Az's promotion. In that case, adequate consensus was achieved, and I stand by my decision 100%. --[[User:Whiteknight|Whiteknight]] &lt;small&gt;([[User talk:Whiteknight|talk]]) ([[User:Whiteknight/Proposed Books|projects]])&lt;/small&gt; 00:45, 16 March 2007 (UTC)

::::#weaknesses in the identities of users - If I was so inclined I would get a user approved as admin just to show that it can easily be done.
::::#falliability of admins - both SB Jhonny and Darklama have failed on admin taks, I don't intend to rehash the subject but you own words admited to errors, errors anyone can commit but should be strongly avoided by admins nonetheless.
::::#abuse of consensus - I don't agree with you definition of consensus nor how you have used the word, 7 to 1 is not consensus it's a vote by majority, I have addressed those on my essay.  --[[User:Panic2k4|Panic]] 01:15, 16 March 2007 (UTC)

:#You could certainly try to do this, I am highly doubtful that you would succeed. Plus, if you could &quot;pretend&quot; to be worthy of being an admin for a while, it would certainly raise questions as to why you have't been worthy of the honor on your primary account. At this point, additional sockpuppets, if they were discovered, would likely lead to you being blocked again. 
:#Your frequent insults of both SBJohnny and Darklama are annoying. In admin tasks, I dont believe that either have made any mistakes. Admins are empowered to use their best judgement, and both SBJohnny and Darklama have used their best judgement in handling situations. That you have an issue with either of these admins is to be expected, but it isn't proof of wrongdoing. If you dont like them, nominate them for removal. 
:#7 people with good reasons, and 1 person with bad reasons ''is concensus''. In concensus, the ''quality of the argument is more important then the quantity of the arguments''. Numerically, the vote could have been 3-5, but if the 3 had better arguments, the vote would have passed. I did not view your argument as being of particularly high quality, and I made a note of that. You would do well to read the full text of [[Wikibooks:Decision making]] so that you understand exactly what we mean by the word &quot;consensus&quot;. How we have defined that word may be different from the way your dictionary might define it. --[[User:Whiteknight|Whiteknight]] &lt;small&gt;([[User talk:Whiteknight|talk]]) ([[User:Whiteknight/Proposed Books|projects]])&lt;/small&gt; 01:23, 16 March 2007 (UTC)

:::#I never tried or worked with that as a target, even if I did perform regular admin tasks, fighting vandalization  of pages etc.., but will try it in 6 moths, and one of the points that we diverge is that I don't consider the task to be an honor but a vocation and a different way of contributing to the project nothing more.
:::#I don't regard it as insults, SBJohnny acknowledged as much and you own assessment of some actions of Darklama also address some failings (do you need the links to the relevant subjects?), I also have acknowledged my errors. I'm not ashamed of addressing them also. I state again that I don't want to nominate them for removal of the admin flag but I will use even my own errors to demonstrate some view points and try to make committing them again harder.
:::#Again, this point will not be solved as you are irredeemable on you view point, but you make a god point against your own definition, so you now have the sole hold on accessing the quality of votes or if they should count, funny that one, well this is why I stopped voting on the RFA. And will fight to show the community the fragility of using your definition.  --[[User:Panic2k4|Panic]] 01:50, 16 March 2007 (UTC)

::::We have 3 bureaucrats precisely so that I dont have unilateral control over RFA votes. According to the decision making guideline, &quot;votes&quot; (and that really is an inappropriate word) are measured by their quality. This is a necessary safeguard against sockpuppetry, and it also helps to distinguish between people who are non-committal, and people who are passionate about a particular option. As a final note, it isn't &quot;my definition&quot;, it is &quot;Everybody's definition except yours&quot;. You seem to be the only person who doesnt understand or doesnt agree with the decision making policy, so don't single me out as being some kind of evil perpetrator of a bad definition. Since this is my talk page, and since i am tired of these acusations, I am likely to delete any further references to that effect on sight. Read the guideline, all the details are spelled out. You are always welcome to propose a change to the guideline, I would be surprised if it got much support. --[[User:Whiteknight|Whiteknight]] &lt;small&gt;([[User talk:Whiteknight|talk]]) ([[User:Whiteknight/Proposed Books|projects]])&lt;/small&gt; 02:05, 16 March 2007 (UTC)</text>
      <sha1>6bgmdyf1q0y0y4k993z93dc6hj1kooo</sha1>
    </revision>
  </page>
  <page>
    <title>Template:Qr-twwp</title>
    <ns>10</ns>
    <id>101792</id>
    <redirect title="Template:Copypaste" />
    <revision>
      <id>4678632</id>
      <parentid>4484648</parentid>
      <timestamp>2026-10-27T23:43:55Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Per [[Wikibooks:Requests for deletion#Template:Qr-twwp]].</comment>
      <origin>4678632</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="32" sha1="1uh3izjf3cphgo55nxbmyk3a4i4llq9" xml:space="preserve">#REDIRECT [[Template:Copypaste]]</text>
      <sha1>1uh3izjf3cphgo55nxbmyk3a4i4llq9</sha1>
    </revision>
  </page>
  <page>
    <title>Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nf6/3. Nxe5</title>
    <ns>0</ns>
    <id>102584</id>
    <revision>
      <id>4678649</id>
      <parentid>4637155</parentid>
      <timestamp>2026-10-28T05:26:02Z</timestamp>
      <contributor>
        <username>DocJade</username>
        <id>3375871</id>
      </contributor>
      <minor />
      <comment>Add responses to infobox</comment>
      <origin>4678649</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2592" sha1="n49txh9qrqrya2dsjz0ndngkwf29tbf" xml:space="preserve">{{Chess Opening Theory/Position
|Russian game
|parent=[[../|Russian game]]
|responses=&lt;br&gt;
* [[/3...d6|3...d6 · Classical Variation]]
* [[/3...Nxe4|3...Nxe4 · Damiano variation]]
* [[/3...Nc6|3...Nc6 · Stafford gambit]]|eco=[[Chess/ECOC|C42]]
}}
== 3. Nxe5 ==
White picks up the undefended pawn. This is the classical continuation of Petrov's defence aka the Russian game. Before Black can recover the pawn, they must drive White's knight away, or else choose to gambit it.  

=== Recover the pawn ===

The natural move [[/3...Nxe4|'''3...Nxe4!?''']], the '''Damiano variation''', doesn't actually recover the pawn, as after 4. Qe2 Black runs into difficulties with pins on the open e-file. The classic beginner's trap is 4...Nf6?? 5. Nc6+, winning Black's queen. (Instead, Black can sacrifice the pawn in this line. See below.)

Therefore, in order to recover the pawn, Black has to drive White's knight away first. [[/3...d6|'''3...d6''']] 4. Nf3 Nxe4 is the '''main line'''. Without White's knight on the e-file, should White play 5. Qe2 Black may defuse it with 5...Qe7, defending and unpinning the knight.

=== Gambit the pawn ===

[[/3...Nc6|'''3...Nc6?!''']] is the most &quot;in vogue&quot; at amateur levels: the explosive '''Stafford gambit'''. After 4. Nxc6 dxc6, Black has sacrificed their pawn but opened the position, ready to play ...Bc5 and ...Ng4 for a swift attack on White's f2 square. 

Black may also give up the pawn with [[/3...Nxe4|'''3...Nxe4!?''']] 4. Qe2 Qe7, the Kholmov gambit. After 5. Qxe4 d6 6. d4 dxe5 7. dxe5 (trading knights) Nc6, it's often too perilous for White to hold onto the extra pawn.

[[/3...d5|'''3...d5?''']] is a gambit favoured by [[w:Baadur Jobava|Baadur Jobava]].

== Theory table ==
{{ChessTable}}

'''1. e4 e5 2. Nf3 Nf6 3. Nxe5'''
&lt;table border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot;&gt;
	&lt;tr&gt;
		&lt;th&gt;&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;3&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;4&lt;/th&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;right&quot;&gt;Classical Variation&lt;br&gt;(Main Line)&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;[[/3...d6|d6]]&lt;/td&gt;
		&lt;td&gt;[[/3...d6/4. Nf3|Nf3]]&lt;br&gt;[[/3...d6/4. Nf3/4...Nxe4|Nxe4]]&lt;/td&gt;
		&lt;td&gt;=&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;right&quot;&gt;Damiano Variation&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;[[/3...Nxe4|Nxe4]]&lt;/td&gt;
		&lt;td&gt;[[/3...Nxe4/4. Qe2|Qe2]]&lt;br&gt;[[/3...Nxe4/4. Qe2/4...Qe7|Qe7]]&lt;/td&gt;
		&lt;td&gt;+/-&lt;/td&gt;
	&lt;/tr&gt;
    &lt;tr&gt;
		&lt;th align=&quot;right&quot;&gt;Stafford Gambit&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;[[/3...Nc6|Nc6]]&lt;/td&gt;
		&lt;td&gt;[[/3...Nc6/4. Nxc6|Nxc6]]&lt;br&gt;[[/3...Nc6/4. Nxc6/4...dxc6|dxc6]]&lt;/td&gt;
		&lt;td&gt;+&lt;/td&gt;
	&lt;/tr&gt;
&lt;/table&gt;
{{ChessMid}}
== References ==
{{reflist}}
=== See also ===
{{wikipedia|Petrov Defence}}
{{BCO2}}
{{Chess Opening Theory/Footer}}</text>
      <sha1>n49txh9qrqrya2dsjz0ndngkwf29tbf</sha1>
    </revision>
  </page>
  <page>
    <title>Adventist Youth Honors Answer Book/Recreation/Drilling &amp; Marching</title>
    <ns>0</ns>
    <id>103035</id>
    <revision>
      <id>4678599</id>
      <parentid>4655685</parentid>
      <timestamp>2026-10-27T20:32:38Z</timestamp>
      <contributor>
        <username>Badygir</username>
        <id>3629551</id>
      </contributor>
      <comment>/* 1. Explain five or more objectives of drilling  . */</comment>
      <origin>4678599</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19503" sha1="p6ju7zp6qe2tz05jhotaekx7nwaimsh" xml:space="preserve">Short term  of the notes{{honor_header|1|1976|Recreation|General Conference}}
This chapter of the Adventist Youth Honors Answer book is intended to help you teach or learn the Drilling and Marching honor.  It is '''''not''''' to be considered the authoritative source or the final word on the Pathfinder way of drilling and marching.  For that, we refer you to the [http://www.adventsource.org/as20/product.aspx?ID=21350 Pathfinder Club Drill Manual] published by the NAD.

==1. Explain five or more objectives of drilling  .==
#'''Order:'''  It helps maintain an organized unit.
#'''Morale:''' Training discipline and group unity.
#'''Enjoyment:''' Fun activity, promotes use of imagination.
#'''Fellowship:''' Helps one learn to take orders, and follow them.
#'''Leadership:''' Helps one learn to give orders and build confidence.
#'''Self Control:''' Pay attention to the leader.
#'''Respect:''' Regard for the rights of others.
#'''Obedience:''' Learn to follow rules and regulations.

==2. Define the following==

===a. Formation===
Formation is the arrangement of the elements of a Pathfinder drill formation in any
prescribed manner.

===b. Line ===
Line is a formation in which the elements are side by side or abreast of each other. In a
club line the Pathfinders in each unit are abreast of each other with the units one behind the
other.

===c. Distance===
Distance is the space between people within a column (front to back).

===d. Rank ===
A rank is a line that is only one element in depth.

===e. Interval===
An interval is the distance between persons standing next to each other.

===f. Column ===
A column is formed when people stand one behind one another.

=== g. File===
A file is a single column.

===h. Distance===
Distance is the space between people within a column (front to back).

===i. Cover===
The cover command is used to align yourself with the person in front of you while maintaining correct distance.

=== j. Flank===
Flank is the right or left side of any formation from the point of view of someone within that formation.

===k. Cadence===
Cadence is the uniform rhythm in which a movement is executed, or the number of steps
or counts per minute at which the movement is executed.

- Cadence : 120 beats per minute 

==3. Explain the actions in each of the following groups==

===a. At Ease, Stand At Ease, and Parade Rest===
*'''Parade, REST''' is the most &quot;strict&quot; of these three commands.  It may be called only from the position of Attention. On preparatory commands, the position of Parade REST should be assumed when at STAND AT EASE, AT EASE, or REST. Pathfinders execute Parade REST by moving the left leg out (so feet are about 12 inches apart) and placing both hands in the small of the back, with the right hand on top of the left and thumbs locked together.  The head and eyes are to be kept looking straight ahead, because Parade REST is simply a more relaxed form of Attention.  STAND AT EASE, AT EASE, or REST and the directive for PRAYER ATTENTION may all be given from this position.
*'''STAND AT EASE''' is slightly more relaxed than Parade REST.  To do this command, execute parade rest as described above; however, the head and eyes are to follow the commander at all times.  Some clubs may allow the hands to relax during STAND AT EASE, but this is not permissible according to the NAD Drill Manual.  AT EASE and REST may be commanded from this position.
*'''AT EASE''' is more relaxed yet.  The right foot must stay &quot;glued&quot; in its place to the ground.  Pathfinders are allowed to move around (except for the right foot!), but you must remain silent and standing.  REST may be commanded from this position.

===b. Mark Time, Quick Time, and Double Time===
*'''MARK TIME''' is a command meaning to march in place.  When a unit is in Mark time, they should adjust and maintain their intervals and distances. To be proper, it should only be called from Quick time or Half step (Not Double time or from the Halt).  However, many clubs find it helpful to use this command from attention for the purpose of instruction. MARK TIME, MARCH can be called as either foot strikes the ground. When the command is given, take one more step after the command of execution (MARCH), plant the trailing foot alongside your stationary foot and march in place. Each foot should be alternately raised approximately 2 inches off the ground at the pace of Quick time. Allow your arms to swing naturally and adjust your alignment as necessary.
*'''QUICK TIME''' is marching to the cadence of 120 counts or steps per minute with appx. a 24-inch step. Your arms should swing naturally 9 inches straight to the front and 6 inches to the rear of the seams on your pants. The arms should not bend at the elbow and your fingers should be curled as in the position of attention. Head and eyes should be fixed to the front. Younger Pathfinders may find this hard to achieve at first, but with the help of an instructor, they should be able to master this very quickly.
*'''DOUBLE TIME''' is the cadence of 180 counts or steps per minute.  The length of the steps is also to be appx. 24 inches. The command DOUBLE TIME, MARCH is given either from a halt or as either foot strikes the ground while marching at Quick time. When given from the halt, at the command MARCH, raise your forearms up to a horizontal position with your fingers and thumb closed, knuckles out, and step off with your left foot. Continue to march at the 180 steps per minute cadence until further instructed. When marching at Quick time, at the command MARCH, take one more step at Quick time and step off with your trailing foot at Double time in the same manner as previously instructed. The only movements that can be executed at Double time are Halt, Quick time, Column Right/Left, and Column Half Right/Left.

===c. Hand Salute and Present Arms===
*'''PRESENT, ARMS''' is mostly used to salute the flag and is a one-count movement given only at the position of attention. To execute this command, raise the right arm and bend at the elbow.  The fingers of the right hand should touch the eyebrow, or if glasses are being worn, the rim of the glasses, or if a cap or hat is being worn, the brim of the hat (if both glasses and a cap are worn, touch the brim of the cap).  The upper arm should be parallel to the ground, and the forearm, wrist, and right hand/fingers should form a straight line (i.e. no bending at joints).  The elbow should be swung back so that it does not stick out in front of the body, but not so far that it is behind the body. To Order, ARMS (a one-count movement), simply lower the right arm smartly to your side and resume the position of Attention.  There should be no slapping sounds when executing this command.
*'''HAND SALUTE''' is exactly like Present, ARMS but without a command.  When reporting or when rendering courtesy, turn the head and eyes toward the person addressed as you salute. Upon acknowledgment, terminate the salute like Order, ARMS, but without a command.

===d. Right (Left) Flank and Column Right (Left)===
*'''RIGHT/LEFT FLANK, MARCH''' - Both the preparatory command (RIGHT/LEFT FLANK) and the command of execution (MARCH) are both given as the foot in the indicated direction strikes the ground (i.e. Left foot for Left Flank). The interval between the preparatory command and the command of execution is one step. At the command MARCH, each Pathfinder takes one more step, turns in the indicated direction on the ball of his leading foot, and steps off in the new direction with his trailing foot. Once marching in the new direction, glance out of the corner of your eye and dress to the right.
*'''COLUMN RIGHT/LEFT, MARCH''' - '''COLUMN RIGHT/LEFT, MARCH''' can be given from the halt or while marching. From the Halt, the command '''COLUMN RIGHT/LEFT, MARCH''' is given and the lead Pathfinder in the column nearest the direction given executes a 90-degree turn in the indicated direction and steps off with their left foot in the new direction taking one 24-inch step then continue at a Half step (12 inches) until the other columns catch up. The lead Pathfinders in the other columns execute a 45-degree turn in the given direction and step off with their left foot in the new direction taking 24-inch steps and continuing in an arc. As they come abreast of the other leaders they take up the Half Step. When all leaders are abreast, they step off with a 24-inch step without command. All other club members march forward on the command of execution and execute the column movement at approximately the same location as their unit leaders and in the same manner. While marching, both the preparatory command '''(COLUMN RIGHT/LEFT)''' and the command of execution '''(MARCH)''' are both given as the foot in the indicated direction strikes the ground (i.e. Left foot for Column Left). The interval between the preparatory command and the command of execution is one step. The execution of the command from here is the same as described above.

==4. Properly execute the following basic movements==

===a. Attention===
Standing at attention requires your feet to be together with your toes at a 45 degree angle. Your hands should be at your sides and curled as if you were holding a coin roll with the thumb over the first knuckle of your index finger. Your eyes should be always facing forward. You are not allowed to talk unless directed to do so. Most stationary commands, as well as the commands used to move a group forward, are called from this position.

===b. Parade Rest===
Like ATTENTION, your eyes should always be facing forward. When called to PARADE REST, your left foot moves away from your right foot and is set back down when your feet are about a shoulder width apart. Your hands are now behind you at the small of your back with the left hand behind the right hand. The command PARADE REST may only be given from ATTENTION.

===c. Stand At Ease ===
STAND AT EASE is exactly like PARADE REST except for two things. The first is that each person's eyes and head should follow the person instructing/addressing the group until the instructor has moved beyond a marcher's shoulder at which point the marcher's head should revert to looking forward until they can see the instructor again. The second is that a marcher's hands may be lower than that of PARADE REST, though the hands must still be in the same order (back of right hand against the left palm). STAND AT EASE may be called from ATTENTION or PARADE REST.

===d. At Ease ===
AT EASE is much like PARADE REST. Though you must be quiet and keep your right foot in place, you may otherwise move as needed. Your hands are also allowed to be lower than required for PARADE REST, just like STAND AT EASE. The command &quot;At Ease&quot; may be given from ATTENTION, PARADE REST, or STAND AT EASE.

===e. Dress Right Dress ===
When the command DRESS RIGHT DRESS is given, each person in the group (except for the group's left most file) extends their left arm. Each person in the group also (except for the group's right most file) turns their head to the right so that they may adjust themselves until they are just touching the fingertip(s) of the person on their right. The group's right most file never moves as everyone is to line up on them while executing DRESS RIGHT DRESS. Each member of the group continues to stay with their left arm up and their head turned to the right (unless they are part of the two files with exceptions) until the command READY FRONT (used to bring the group back to ATTENTION from DRESS RIGHT DRESS) is called. No command other than READY FRONT may be called from DRESS RIGHT DRESS.

===f. Prayer Attention ===
PRAYER ATTENTION is exactly like PARADE REST, but goes one step further. When a group is called to PRAYER ATTENTION, they must also bow their heads. '''Male Pathfinders &amp; Staff should take off and hold (behind their back) with their right hand, any headgear that they may have on.''' At the end of the prayer (without commands) each person is to return to PARADE REST (Men also put headgear back on). PRAYER ATTENTION may only be called from PARADE REST.

=== g. Present Arms===
When the command PRESENT ARMS is given, each person is to raise their right hand to just above their eyebrow. The upper arm should be out horizontal to the ground. The thumb and fingers should be fully extended and should only just touching above your eyebrow, glasses rims, or hat bill. This command can only be given from ATTENTION.

=== h. Order Arms===
The command ORDER ARMS is used to bring a person or persons back to ATTENTION from PRESENT ARMS. All a person must do is to bring their arm down to their side from PRESENT ARMS without slapping the arm against their leg.

===i. Right Face===
The command of RIGHT FACE is used to turn a person or persons to the (you guessed it) right. When the command is given, those who are to execute the command should lift their right toes and left heel and then pivot to the right on their right heel and left toes while turning to the right. The command is given only from ATTENTION and when completed, everyone should again be at ATTENTION.

===j. Left Face===
LEFT FACE is just like RIGHT FACE except that you lift your left toes and right heel and pivot on your left heel and right toes while turning to the left.

===k. About Face===
The command ABOUT FACE is used to turn a person or persons around 180 degrees. To do this, you put your right foot (toes pointed down) behind your left heel. Next, turn to your right (not too quickly or you will fall over) until you have turned completely around to face the opposite way that you were facing previously. This command is only issued from ATTENTION.

===l. Fall Out===
The command FALL OUT is one of the commands that dismisses a person or group of people. When the command FALL OUT is given, you are free to break from formation (Yes. One person can be a formation). Do not stray far from whoever is instructing you or your group though. FALL OUT does not give you permission to walk off where ever you feel like. Only when the command DISMISSED is given may you leave to wherever you want. The command FALL OUT can only be given from ATTENTION.

==5. Properly execute the following movements==
===a. Mark Time===
''Mark time, march'' can be called when the unit is at attention or marching.  The marchers will march in place when the command is called, and they should correct their intervals and distances as necessary.  If ''halt'' is called after ''mark time, march'', the unit should be able to ''dress right, dress'' and ''cover'' without having to move the feet.

===b. Forward March===
When ''forward march'' is called, the unit steps out with the left foot and begins to march forward.  If the unit is marching to music (in 4/4 time) or calling a cadence, the left foot will always land on the &quot;odd&quot; beat, and the right foot will always land on an &quot;even&quot; beat.  In 4/4 time, the &quot;count&quot; goes 1, 2, 3, 4 and then repeats:

:'''1:''' Left
:'''2:''' Right
:'''3:''' Left
:'''4:''' Right
:'''1:''' Left
:'''2:''' Right
:'''3:''' Left
:'''4:''' Right

If the unit is marching without music, the rightmost person in the front rank is by definition &quot;in step.&quot;  Everyone else must be in step with that person.

if the unit is already in motion (stationary marching) the command &quot;forward march&quot; should be on the left foot.

===c. Right Flank===
When ''right flank'' is called, every person in the unit simultaneously pivots to the right by 90 degrees and continues marching in the new direction. After this command is executed, the file that was right-most when it was called will become the front rank. The person who was last in that column will now be the ''marker'' - meaning he will be the right-most person in the front rank.

Right flank should be called on the right foot (that is, the command of execution should be spoken by the instructor when the right foot hits the ground). The unit then steps forward with the left, and everyone pivots to the right on their toes. Following this, the unit will step out with the left foot.

===d. Left Flank===
When ''left flank'' is called, every person in the unit simultaneously pivots to the left by 90 degrees and continues marching in the new direction. After this command is executed, the file that was left-most when it was called will become the front rank. The person who was first in that column will now be the ''marker'' - meaning he will be the right-most person in the front rank.

Left flank should be called on the left foot (that is, the command of execution should be spoken by the instructor when the left foot hits the ground). The unit then steps forward with the right foot, and everyone pivots to the left on their toes.  Following this, the unit will step out with the right foot.

===e. Column Right (with columns of three or four persons)===
When ''column right, march'' is called, the person in the front rank on the right makes a tight pivot turn to the right by 90 degrees.  As he turns, the other members in his rank also turn, but remain in a straight line side by side of one another.  When the entire rank is facing 90 degrees to the right, they continue marching forward in the new direction.

When the next rank reaches the same point at which the turn was made by the front rank, that rank turns in the same manner that the first ran did.  All ranks continue until the entire unit is marching in the same direction.

This command is called only when the unit is in motion.

Some groups find it useful to practice this maneuver while each rank holds onto a broom stick or pole.  This helps keep the rank in a straight line.

===f. Column Left (with columns of three or four persons)===
When ''column left, march'' is called, the person in the front rank on the left makes a tight pivot turn to the left by 90 degrees.  As he turns, the other members in his rank also turn, but remain in a straight line abreast of one another.  When the entire rank is facing 90 degrees to the left, they continue marching forward in the new direction.

When the next rank reaches the same point at which the turn was made by the front rank, that rank turns in the same manner that the first rank did.  All ranks continue until the entire unit is marching in the same direction.

This command is called only when the unit is in motion.

===g. Rear March===
This command is called on the &lt;u&gt;right&lt;/u&gt; foot.  When ''Rear, March'' is called, the marcher takes a step with the left foot, then swivels to the right on the toes of the left foot until facing the opposite direction, and then steps out again with the left foot (which should be at the rear after the marcher turns around).  This command should only be called when the unit is marching or marking time.

===h. Halt===
The command to halt should be called on the right foot.  The marchers will then take a step with the left foot as normal, and then take a half-step with the right foot, bringing it even with the left, and stop, remaining at attention.  giving it two counts only from the command of execution to full stop.

==6. Explain and demonstrate how to use, display, fold, and care for the national flag.==
===Flag Protocol===
{{:Adventist Youth Honors Answer Book/Flag protocol}}
On Memorial Day the flag should be flown half-staff till noon
;

*[http://www.adventsource.org/as20/product.aspx?ID=21350 Pathfinder Club Drill Manual]

[[{{BOOKCATEGORY|Adventist Youth Honors Answer Book}}/Completed Honors|{{SUBPAGENAME}}]]</text>
      <sha1>p6ju7zp6qe2tz05jhotaekx7nwaimsh</sha1>
    </revision>
  </page>
  <page>
    <title>Miskito/Lesson 1</title>
    <ns>0</ns>
    <id>109025</id>
    <revision>
      <id>4678502</id>
      <parentid>4662138</parentid>
      <timestamp>2026-10-27T15:11:01Z</timestamp>
      <contributor>
        <username>~2026-57357-62</username>
        <id>3629520</id>
      </contributor>
      <comment>/* The */</comment>
      <origin>4678502</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5271" sha1="2sro305ai8vwtph34wxovfnzjnfjgj0" xml:space="preserve">{{miskito_title|1|Nini Mary sa|My name is Mary|Pronunciation|Lesson 2}}

==''Is''==
{{miskito_model|
* Jan tara '''sa'''.
* Luis sirpi '''sa'''.
* Witin Pedro '''sa'''.
* Witin Susan '''sa'''.
* Witin tiara (female) '''sa'''.
* Witin umpira '''sa'''
* Nini Mary '''sa'''.
* Tuktiki sirpi '''sa'''.
|
* John '''is''' big.
* Luis '''is''' small.
* He '''is''' Pedro.
* She '''is''' Susan.
* She '''is''' young.
* She/He '''is''' poor.
* My name '''is''' Mary.
* My child '''is''' small.
}}
{{miskito_mini_exercise|
|
# ''Make a list of the words in these sentences and try to learn their meanings.''
# ''Hide the meanings of the model sentences and try to remember what they mean.''
# ''What do the following mean?''
* Witin sirpi sa.
* Tuktiki tiara sa.
* Nini Jan sa.
* Pedro umpira sa.
|
* She/He is small.
* My child is young.
* My name is John.
* Pedro is poor.
}}

{{miskito_comment|The verb usually comes at the end of a Miskito sentence. The first verb form you will learn is '''sa''' ''is''. The subject often comes first in the sentence.}}
{{miskito_note|Notice that Miskito grammar makes no gender distinctions. Both ''she'' and ''he'' are expressed by the same Miskito pronoun, '''witin'''.}}
{{miskito_note|Notice that '''nini''' and '''tuktiki''' both mean ''my...'' (something), and both end in '''-i'''.}}

&lt;br&gt;&lt;br&gt;&lt;br&gt;

==''This'' and ''that''==
{{miskito_model|
* '''Naha''' Jan sa.
* '''Naha''' tuktiki sa.
* '''Baha''' Lucia sa.
* '''Baha''' yaptiki sa.
|
* '''This''' is John.
* '''This''' is my child.
* '''That''' is Lucia.
* '''That''' is my mother.
}}
{{miskito_mini_exercise|
What do these sentences mean?
|
* Naha sirpi sa.
* Baha nini sa.
* Naha yaptiki sa.
|
* This is small.
* That is my name.
* This is my mother.
}}
 
{{miskito_comment|The demonstrative pronouns are '''naha''' ''this'' and '''baha''' ''that''.}}

&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;

==''The''==
{{miskito_model|
* Mairin '''ba''' tiara sa.
* Waitna '''ba''' sin tiara sa.
* Buk '''ba''' tara sa.
* Buk '''na''' sirpi sa.
|
* '''The''' woman is young.
* '''The''' man is young too.
* '''The''' book is big.
* '''This''' book is small.
}}
{{miskito_mini_exercise|
What do these sentences mean?
|
* Waitna ba umpira sa.
* Mairin ba sin umpira sa.
* Mairin na yaptiki sa.
|
* The man is poor.
* The woman is poor too.
* This woman is my mother.
}}

{{miskito_comment|The general definite article (&quot;the&quot;) is '''ba'''. The article follows the noun.}}
{{miskito_comment|There is another article '''na''' which denotes something near the speaker, and so is translated by &quot;this&quot;.}}.
{{miskito_note|Notice the parallellism between the demonstrative pronouns '''naha, baha''' and the articles '''na, ba'''!}}

&lt;br&gt;
==''A''==
{{miskito_model|
* Susan mairin '''kum''' sa.
* Yaptiki sin mairin '''kum''' sa.
* Aisiki waitna '''kum''' sa.
* Naha buk '''kum''' sa.
* Yul na daiwan '''kum''' sa.
|
* Susan is '''a''' woman.
* My mother is '''a''' woman too.
* My father is '''a''' man.
* This is '''a''' book.
* This dog is '''an''' animal.
}}
{{miskito_mini_exercise|
What do these sentences mean?
|
* Pedro waitna kum sa.
* Naha yul kum sa.
* Baha daiwan kum sa.
|
* Pedro is a man.
* This is a dog.
* That is an animal.
}}

{{miskito_comment|The indefinite definite article (&quot;a&quot; or &quot;an&quot;) is '''kum'''. This article follows the noun too.}}
{{miskito_note|'''Kum''' is also the number &quot;one&quot;.}}

&lt;br&gt;&lt;br&gt;&lt;br&gt;
==Vocabulary and review==
{| style=&quot;background-color:#DEE7F5;{{Text default color}};&quot; width:100%;&quot;
 | colspan=&quot;3&quot; | {{Miskito/Vocab head|click word to goto section / click arrow to &quot;show&quot; meaning}}
 |-
 | width=&quot;33%&quot; valign=&quot;top&quot; |
{{Miskito/Vocab|aisiki| |my father|1#A}}
{{Miskito/Vocab|ba|det|the|1#The}}
{{Miskito/Vocab|baha|pron|that|1#This and that}}
{{Miskito/Vocab|buk|n|book|1#The}}
{{Miskito/Vocab|daiwan|n|animal|1#A}}
{{Miskito/Vocab|kum|det|a, an|1#A}}
{{Miskito/Vocab|mairin|n|woman|1#The}}
 | width=&quot;33%&quot; valign=&quot;top&quot;|
{{Miskito/Vocab|na|det|this|1#The}}
{{Miskito/Vocab|naha|pron|this|1#This and that}}
{{Miskito/Vocab|nini| |my name|1#Is}}
{{Miskito/Vocab|sa| |is|1#Is}}
{{Miskito/Vocab|sin| |too, also|1#The}}
{{Miskito/Vocab|sirpi|adj|small|1#Is}}
{{Miskito/Vocab|tara|adj|big|1#Is}}
 | width=&quot;33%&quot; valign=&quot;top&quot;|
{{Miskito/Vocab|tiara|adj|young|1#Is}}
{{Miskito/Vocab|tuktiki| |my child|1#Is}}
{{Miskito/Vocab|umpira|adj|poor|1#Is}}
{{Miskito/Vocab|waitna|n|man|1#The}}
{{Miskito/Vocab|witin|pron|she, he|1#Is}}
{{Miskito/Vocab|yaptiki| |my mother|1#This and that}}
{{Miskito/Vocab|yul|n|dog|1#A}}
 |}


{| style=&quot;background:#DEE7F5;{{Text default color}}; width:100%&quot; cellpadding=&quot;2&quot; cellpadding=&quot;2&quot;
 | {{Miskito/Review head|Say in Miskito}}
{{Miskito/Review|My name is John.|Nini Jan sa.}}
{{Miskito/Review|My father is big.|Aisiki tara sa.}}
{{Miskito/Review|He is young.|Witin tiara sa.}}
{{Miskito/Review|My mother is young too.|Yaptiki sin tiara sa.}}
{{Miskito/Review|That is my child.|Baha tuktiki sa.}}
{{Miskito/Review|This is a book.|Naha buk kum sa.}}
{{Miskito/Review|The woman is my mother.|Mairin ba yaptiki sa.}}
{{Miskito/Review|The man is my father.|Waitna ba aisiki sa.}}
{{Miskito/Review|My father is a man.|Aisiki waitna kum sa.}}
{{Miskito/Review|This animal is a dog.|Daiwan na yul kum sa.}}
 |}

{{Miskito/Nav|Pronunciation|Lesson 2}}

{{BookCat}}</text>
      <sha1>2sro305ai8vwtph34wxovfnzjnfjgj0</sha1>
    </revision>
    <revision>
      <id>4678503</id>
      <parentid>4678502</parentid>
      <timestamp>2026-10-27T15:46:43Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>The period seems unnecessary.</comment>
      <origin>4678503</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5270" sha1="82m1ymuqjis8y7rhoyntf497hkqjf38" xml:space="preserve">{{miskito_title|1|Nini Mary sa|My name is Mary|Pronunciation|Lesson 2}}

==''Is''==
{{miskito_model|
* Jan tara '''sa'''.
* Luis sirpi '''sa'''.
* Witin Pedro '''sa'''.
* Witin Susan '''sa'''.
* Witin tiara (female) '''sa'''.
* Witin umpira '''sa'''
* Nini Mary '''sa'''.
* Tuktiki sirpi '''sa'''.
|
* John '''is''' big.
* Luis '''is''' small.
* He '''is''' Pedro.
* She '''is''' Susan.
* She '''is''' young.
* She/He '''is''' poor.
* My name '''is''' Mary.
* My child '''is''' small.
}}
{{miskito_mini_exercise|
|
# ''Make a list of the words in these sentences and try to learn their meanings.''
# ''Hide the meanings of the model sentences and try to remember what they mean.''
# ''What do the following mean?''
* Witin sirpi sa.
* Tuktiki tiara sa.
* Nini Jan sa.
* Pedro umpira sa.
|
* She/He is small.
* My child is young.
* My name is John.
* Pedro is poor.
}}

{{miskito_comment|The verb usually comes at the end of a Miskito sentence. The first verb form you will learn is '''sa''' ''is''. The subject often comes first in the sentence.}}
{{miskito_note|Notice that Miskito grammar makes no gender distinctions. Both ''she'' and ''he'' are expressed by the same Miskito pronoun, '''witin'''.}}
{{miskito_note|Notice that '''nini''' and '''tuktiki''' both mean ''my...'' (something), and both end in '''-i'''.}}

&lt;br&gt;&lt;br&gt;&lt;br&gt;

==''This'' and ''that''==
{{miskito_model|
* '''Naha''' Jan sa.
* '''Naha''' tuktiki sa.
* '''Baha''' Lucia sa.
* '''Baha''' yaptiki sa.
|
* '''This''' is John.
* '''This''' is my child.
* '''That''' is Lucia.
* '''That''' is my mother.
}}
{{miskito_mini_exercise|
What do these sentences mean?
|
* Naha sirpi sa.
* Baha nini sa.
* Naha yaptiki sa.
|
* This is small.
* That is my name.
* This is my mother.
}}
 
{{miskito_comment|The demonstrative pronouns are '''naha''' ''this'' and '''baha''' ''that''.}}

&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;

==''The''==
{{miskito_model|
* Mairin '''ba''' tiara sa.
* Waitna '''ba''' sin tiara sa.
* Buk '''ba''' tara sa.
* Buk '''na''' sirpi sa.
|
* '''The''' woman is young.
* '''The''' man is young too.
* '''The''' book is big.
* '''This''' book is small.
}}
{{miskito_mini_exercise|
What do these sentences mean?
|
* Waitna ba umpira sa.
* Mairin ba sin umpira sa.
* Mairin na yaptiki sa.
|
* The man is poor.
* The woman is poor too.
* This woman is my mother.
}}

{{miskito_comment|The general definite article (&quot;the&quot;) is '''ba'''. The article follows the noun.}}
{{miskito_comment|There is another article '''na''' which denotes something near the speaker, and so is translated by &quot;this&quot;.}}
{{miskito_note|Notice the parallellism between the demonstrative pronouns '''naha, baha''' and the articles '''na, ba'''!}}

&lt;br&gt;
==''A''==
{{miskito_model|
* Susan mairin '''kum''' sa.
* Yaptiki sin mairin '''kum''' sa.
* Aisiki waitna '''kum''' sa.
* Naha buk '''kum''' sa.
* Yul na daiwan '''kum''' sa.
|
* Susan is '''a''' woman.
* My mother is '''a''' woman too.
* My father is '''a''' man.
* This is '''a''' book.
* This dog is '''an''' animal.
}}
{{miskito_mini_exercise|
What do these sentences mean?
|
* Pedro waitna kum sa.
* Naha yul kum sa.
* Baha daiwan kum sa.
|
* Pedro is a man.
* This is a dog.
* That is an animal.
}}

{{miskito_comment|The indefinite definite article (&quot;a&quot; or &quot;an&quot;) is '''kum'''. This article follows the noun too.}}
{{miskito_note|'''Kum''' is also the number &quot;one&quot;.}}

&lt;br&gt;&lt;br&gt;&lt;br&gt;
==Vocabulary and review==
{| style=&quot;background-color:#DEE7F5;{{Text default color}};&quot; width:100%;&quot;
 | colspan=&quot;3&quot; | {{Miskito/Vocab head|click word to goto section / click arrow to &quot;show&quot; meaning}}
 |-
 | width=&quot;33%&quot; valign=&quot;top&quot; |
{{Miskito/Vocab|aisiki| |my father|1#A}}
{{Miskito/Vocab|ba|det|the|1#The}}
{{Miskito/Vocab|baha|pron|that|1#This and that}}
{{Miskito/Vocab|buk|n|book|1#The}}
{{Miskito/Vocab|daiwan|n|animal|1#A}}
{{Miskito/Vocab|kum|det|a, an|1#A}}
{{Miskito/Vocab|mairin|n|woman|1#The}}
 | width=&quot;33%&quot; valign=&quot;top&quot;|
{{Miskito/Vocab|na|det|this|1#The}}
{{Miskito/Vocab|naha|pron|this|1#This and that}}
{{Miskito/Vocab|nini| |my name|1#Is}}
{{Miskito/Vocab|sa| |is|1#Is}}
{{Miskito/Vocab|sin| |too, also|1#The}}
{{Miskito/Vocab|sirpi|adj|small|1#Is}}
{{Miskito/Vocab|tara|adj|big|1#Is}}
 | width=&quot;33%&quot; valign=&quot;top&quot;|
{{Miskito/Vocab|tiara|adj|young|1#Is}}
{{Miskito/Vocab|tuktiki| |my child|1#Is}}
{{Miskito/Vocab|umpira|adj|poor|1#Is}}
{{Miskito/Vocab|waitna|n|man|1#The}}
{{Miskito/Vocab|witin|pron|she, he|1#Is}}
{{Miskito/Vocab|yaptiki| |my mother|1#This and that}}
{{Miskito/Vocab|yul|n|dog|1#A}}
 |}


{| style=&quot;background:#DEE7F5;{{Text default color}}; width:100%&quot; cellpadding=&quot;2&quot; cellpadding=&quot;2&quot;
 | {{Miskito/Review head|Say in Miskito}}
{{Miskito/Review|My name is John.|Nini Jan sa.}}
{{Miskito/Review|My father is big.|Aisiki tara sa.}}
{{Miskito/Review|He is young.|Witin tiara sa.}}
{{Miskito/Review|My mother is young too.|Yaptiki sin tiara sa.}}
{{Miskito/Review|That is my child.|Baha tuktiki sa.}}
{{Miskito/Review|This is a book.|Naha buk kum sa.}}
{{Miskito/Review|The woman is my mother.|Mairin ba yaptiki sa.}}
{{Miskito/Review|The man is my father.|Waitna ba aisiki sa.}}
{{Miskito/Review|My father is a man.|Aisiki waitna kum sa.}}
{{Miskito/Review|This animal is a dog.|Daiwan na yul kum sa.}}
 |}

{{Miskito/Nav|Pronunciation|Lesson 2}}

{{BookCat}}</text>
      <sha1>82m1ymuqjis8y7rhoyntf497hkqjf38</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/General</title>
    <ns>4</ns>
    <id>112405</id>
    <revision>
      <id>4678500</id>
      <parentid>4677982</parentid>
      <timestamp>2026-10-27T15:04:40Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Call for new administrators */ new topic ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678500</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="26154" sha1="dt0kg0h9x0zg84apipehcp3kgqlv9pj" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:CHAT|WB:RR/G|WB:GENERAL}} {{TOC left|limit=3}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Archives/%(year)d/%(monthname)s
|algo = old(60d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
|key = 7a0ac23cf8049e4d9ff70cabb5649d1a
}}
Welcome to the '''General reading room'''. On this page, Wikibookians are free to talk about the Wikibooks project in general. For proposals for improving Wikibooks, see the [[../Proposals/]] reading room.
{{clear}}

[[Category:Reading room]]

== Call for administrators ==

Any experienced editor who has a good understanding of Wikibooks' policies should consider applying for administrator permissions at [[Wikibooks:Requests for permissions]]. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:10, 5 August 2026 (UTC)

:Is there a page here that describes what admins do? I am curious because I checked [https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=sysop&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 List of admins] and I see that there are already quite a few admins here and wonder which areas have a shortage.
:Just curious. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:56, 16 September 2026 (UTC)
::[[Wikibooks:Administrators]]. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 01:09, 16 September 2026 (UTC)

== Wikibooks project is not defined by goal ==

If it is for texbooks why is it called Wikibooks? It should be called Wikitextbooks! If it is for textbooks why does it contain cookbooks? For textbooks it's not supposed to have a [[Wikibooks:Featured books]]. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 09:20, 1 September 2026 (UTC)

:It's &quot;textbooks&quot; broadly construed: guides, manuals, how-tos, etc. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:15, 1 September 2026 (UTC)
::So we should change &quot;Wikibooks:Featured books&quot; to &quot;Wikibooks:Featured texts&quot;. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:17, 1 September 2026 (UTC)
:::I disagree and even if I agreed, it would be priority #49,389. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:20, 1 September 2026 (UTC)
::::It's according to community consensus that says this website contains textbooks not books. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:23, 1 September 2026 (UTC)
:::::&quot;[[wb:WIW|Simply, Wikibooks is a collection of open-content textbooks.]]&quot; [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:26, 1 September 2026 (UTC)
:Most textbooks are made by collaboration of some authors, co-authors and editors. Wikibooks help pages and guidelines remain silent when it comes to stages of writing a new texbooks. Even [[Using Wikibooks]] is not complete emough for enthusiasts. --[[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 18:13, 3 September 2026 (UTC)
:@[[User:Vivairan2|Vivairan2]], In my opinion this is a good question. I wish more users would chime in. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:10, 19 September 2026 (UTC)

== Wishlist 2027, invitation to share feedback ==

Hi, I’m [[m:User:SPerry-WMF|Sonja]] and I lead some of the [[mw:Contributors|teams]] at the Foundation who will be responsible for picking up wish work under the new wishlist process.

As you may know, the [[m:Community_Wishlist|Community Wishlist]] started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically.

In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver.

I would like to get community input specifically on these three stages of the Wishlist process:

* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#triage|'''triage stage''']], meaning how wishes are fleshed out, organized and filtered prior to voting
** We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#vote|'''voting stage''']], including who may vote and how votes are structured
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#postvote|'''post-vote stage''']], including how to bring equity into what work is prioritized
** One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and '''sister projects''', so that top-voted wishes from smaller projects also get attention

This message is an abstract of the full proposed process. As you [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027|read the proposed ideas on Meta]] (available in your language), please speak up about whether you think this will work well or if there are ways to make it stronger.

Regarding the timeline, this consultation is open for two weeks. You can post your feedback on Meta (in your preferred language) or in response below.

For this year’s cycle, [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#timeline|we plan]] to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together.

[[oldwikisource:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 13:52, 1 September 2026 (UTC)

:Thank you to everyone who engaged in the discussion around [[m:Talk:Community_Wishlist/Community_Wishlist_2027|the proposal from August 26]]. We've processed your feedback and [https://meta.wikimedia.org/w/index.php?title=Community_Wishlist/Community_Wishlist_2027&amp;diff=prev&amp;oldid=31041090 made changes] accordingly. Note that we weren’t able to implement all of it for this cycle, mostly for logistical reasons, but this is merely meant to be a first step and we will continue to improve this process with you all before we run through the next cycle. We plan to use [[m:Community_Wishlist/Community_Wishlist_2027#Updated_Community_Wishlist_Process_2027/2028|this updated version]] for the Wishlist 2027, and we look forward to hearing from you all during the submission and voting periods.
:[[:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 14:49, 17 September 2026 (UTC)
::@[[User:SPerry-WMF|User:SPerry-WMF]],@[[User:Trizek (WMF)|Trizek (WMF)]]: Thank you for posting info regarding the wishlist to the English Wikibooks. I am sure there are many new users here who can benefit.
::I used to participate in those discussions years ago and I know a lot of effort goes into making discussions useful not only for users of wikipedia, but also for the many language versions of the smaller wikimedia projects such as Wikibooks. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:28, 19 September 2026 (UTC)

== How Do I Get My Book On A Shelf? ==

Help, I don't know how shelves work. I don't know how to put my book on a shelf. Can anyone help?
The book is called''' Art And AI''' [[User:3MMPEYTON|3MMPEYTON]] ([[User talk:3MMPEYTON|discuss]] • [[Special:Contributions/3MMPEYTON|contribs]]) 23:00, 8 September 2026 (UTC)
: Which shelf are you referring? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:45, 10 September 2026 (UTC)

== Who is allowed to delete pages here? ==

On Aug 14, 2026 a user by the name of Max deleted a page I created in my user space. I don't see max in the list of admins here. Do they have the right to delete pages? Is there any documentation here I can consult?

Thanks in advance, [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 22:38, 15 September 2026 (UTC)

:We have local admins who have the technical ability to delete pages and virtually all material deleted here would be done by us (I'm one of them). A fairly small amount of users have global rights across all Wikimedia Foundation wikis and they will very rarely make deletions (e.g. if there are some kind of legal implications to material). [[User:Ottawahitech/American politics]] was deleted by [[User:Max]], who has [[Special:UserRights/Max|no special rights here]] but is one of the [[:m:Global sysops|global sysops]] I mentioned earlier. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:55, 15 September 2026 (UTC)
: Probably unrelated to the above, but Ottawahitech should do that with their account, unless if they are blocked. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:33, 15 September 2026 (UTC)
::Agreed and [[User:Ottawahitech]] is not blocked here, so no idea why he's using a temp account. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:43, 15 September 2026 (UTC)
:::There may be many reasons registered users are &quot;editing&quot; without logging in. Is it possible that they want to go about peacefully without attracting too much attention? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 15:01, 16 September 2026 (UTC)
:::: We neither have a policy nor a guideline about this, probably. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:12, 20 September 2026 (UTC)
::::Notwithstanding a claim that the temp account is actually User:Ottawahitech, we have no idea that they are the same person. If the temp account is the same person, and they want to have a user space page, they can create temp account ones. The registered user account pages are intended for that registered user account and not as a dumping ground for anyone to create pages. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 08:29, 13 October 2026 (UTC)

== Assistance to get page reviewed ==

My page is a translation page: [[Baiyi Zhuan]] 

It is a single page, it is translated according to my own ability and familiarity with the language with a disclosure on external tools. I would like it to get reviewed if possible as I do not have the rights.  [[User:Taitesena|Taitesena]] ([[User talk:Taitesena|discuss]] • [[Special:Contributions/Taitesena|contribs]]) 11:19, 18 September 2026 (UTC)

== Translation of books ==

Hello,
I would like to translate books from other Wikibooks into English. Are there any guidelines regarding how to do this? [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:34, 20 September 2026 (UTC)
: This has yet to be expanded, but you might want to take a look at [[Wikibooks:Content translation]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:13, 20 September 2026 (UTC)

== Feedback on Wikibooks redirect ==

I would like your feedback on my proposal to make [[Wikibooks:Username|this page]] redirect to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]? I would do it myself, but it is not possible due to the fact that [[Wikibooks:Username]] can only be made by admins. This is because [[Wikibooks:Username policy]] also links to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]. Regards, [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 04:37, 21 September 2026 (UTC)

:{{support}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 00:00, 22 September 2026 (UTC)
:This seems like a good idea to me. [[User:Alextejthompson|''Alextejthompson'']] (''Ping me or leave a message on my [[User talk:Alextejthompson|talk page]]'') 17:49, 21 September 2026 (UTC)
: {{done}}, I restored the redirect per consensus here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:03, 13 October 2026 (UTC)

== Pages created by [[User:Sisterian]] ==

I have checked with AI checkers (GPTZero, ZeroGPT) and they claim that these pages have been made with the use of GenAI. I do not know whether this is correct or not; because yes, AI checkers can and do make mistakes. I have tried reaching out to the person via talk page, to no response. I am asking for input just to see what the future of these pages are. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 12:00, 22 September 2026 (UTC)

:Thank you for flagging this @[[User:TechVindicator|TechVindicator]]. I have looked at these pages personally, and there is fairly conclusive evidence that this user has been using genAI/LLMs for their contributions. I have warned them accordingly. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:50, 22 September 2026 (UTC)

== I'm in the process of creating a separate page describing the removal of admin permissions ==

As the section title says, please see [[User:Codename Noreste/sandbox]] and feel free to make any adjustments. We might consider moving this to [[Wikibooks:Administrators/De-adminship]] someday. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:05, 24 September 2026 (UTC)

== Your feedback wanted: Remove ''(Language link added:) and similar'' edits from Special:RecentChanges ==

''(Apologies for posting in English. You can help by translating it)''

Hello, I’m Danny from [[:en:w:Wikimedia_Deutschland|Wikimedia Deutschland’s]] [[m:Wikidata_For_Wikimedia_Projects|Wikidata For Wikimedia Projects]] team.&lt;br/&gt;
We have been investigating and examining how Wikidata’s use in the [[Special:RecentChanges]] and [[Special:Watchlist]] pages can be made to be more useful, or less ‘noisy’ (fewer edits that have little value to the reader).

We are currently exploring to make a change in the volume and the type of Wikidata edits that appear in these pages, and '''we need your feedback''' to help us ensure this is a positive change for the Wikis and won’t disrupt your workflows.&lt;br/&gt;
Language links are also known as sitelinks or interlanguage links and describe when a Wikidata item is connected to a Wiki, adding it to the language dropdown tool for other connected Wikis.
[[File:Types of Lang Link changes.png|x350px|frame|A variety of &quot;Language Link&quot; edits as seen in the Recent Changes feed]]

The request for feedback is whether you support the removal of these language link edits from the Recent Changes and Watchlist feed, or would you oppose such a change and if so, why?
Please share you thoughts on the dedicated '''[[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|metawiki Talk page]]'''. 

Further information about this change: [[m:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|m:Wikidata_For_Wikimedia_Projects/Hide_Language_Link_edits]]

Thank you for any participation or feedback you give, -- [[m:User:Danny_Benjafield_(WMDE)|User:Danny Benjafield (WMDE)]] 11:46, 25 September 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31080832 --&gt;

== FlaggedRevs again ==

&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved to [[Wikibooks:Reading room/Proposals#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;

== Wikidata Sitelink changes in Recent Changes and Watchlist ==

''(Apologies for cross-posting in English, translating it will help spread the message)''

Editors on group 1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on [[Special:RecentChanges|Recent Changes]] and [[Special:Watchlist|Watchlist]] when a link to ''another'' language version of a page is added, removed, or changed in its Wikidata item. This change will begin on '''October 5 at 07:00 UTC''' as a two-week trial to reduce high-volume, low-value notifications and make higher-value changes easier to identify. Editors who rely on these notifications should be aware of the change and can share feedback or concerns on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project]] or [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]].&lt;br/&gt;Please reach out if you have any questions, thank you! -- [[User:Danny_Benjafield_(WMDE)|Danny Benjafield (WMDE)]] ([[User_talk:Danny_Benjafield_(WMDE)|talk]])  sent via [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:42, 1 October 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31106967 --&gt;

== Approved Revs extension ==

If we were to have this extension, we should only limit this to the Wikijunior namespace, since we will eventually stop using FlaggedRevs, unless if we want Approved Revs to work in another namespace.

Remember, this is not a vote, but an overall discussion. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 01:17, 11 October 2026 (UTC)

== An apology ==
Due to the removal of the &lt;code&gt;editor&lt;/code&gt; and &lt;code&gt;autoreview&lt;/code&gt; user groups and my failure to immediately correct the [https://github.com/JJPMaster/jjpmaster-bot-enwb-t1 code of  my bot], the markAdmins gadget data has not been updated for 39 hours. I apologize if anyone has been affected. [https://github.com/JJPMaster/jjpmaster-bot-enwb-t1/commit/65e615ef04d82500674a3711f2d99fe7cd8968d0 This commit] corrected the problem. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:05, 17 October 2026 (UTC)

== October 2026 Wikimedia Café: legal issues on Commons, and WMF Board selection process ==
&lt;div class=&quot;border-box&quot; style=&quot;background-color: var(--background-color-warning-subtle, #f8eaba); max-width: 875px; padding: 5px; border: 1px solid black; margin: 5px; color: var(--clr-dark)&quot;&gt;
&lt;div class=&quot;box&quot; style=&quot;float:left; padding-top: 10px; padding-right: 10px; padding-left: 10px; padding-bottom: 10px;&quot;&gt;[[File:Wikimedia Café logo in plain SVG format.svg|60px|alt=The logo for the Wikimedia Café]]&lt;/div&gt;
Hello! There will be two '''[https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Wikimedia Café]''' discussion opportunities in October. In a change from the usual Café practice, this month's sessions will have different topics. Anyone who meets the Café attendance criteria is welcome to attend either or both sessions.

Session A will happen on Saturday, 24 October 2026 at 15:00 UTC ([https://zonestamp.toolforge.org/1792854000 timestamp converter]), at a time friendly to the Americas, Africa, and Europe. This session will feature [https://meta.wikimedia.org/wiki/User:PBradley-WMF Wikimedia Foundation lawyer Phil Bradley-Schmieg]. We will discuss legal issues on Wikimedia Commons, including complexities of international law. (I am hoping that in a future month, a similar Café session will be offered at a time friendly to Asia and the Pacific.)

Session B will happen on Sunday, 25 October 2026 at 03:00 UTC ([https://zonestamp.toolforge.org/1792897200 timestamp converter]), at a time friendly to Asia and the Pacific, we will discuss [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2027/Proposed_eligibility_criteria proposed changes to how Wikimedia Foundation Board candidates are selected]. The latest proposals are much different from the earlier July 2026 proposals. The due date for feedback on current proposals is 27 October, and Wikimedians are welcome to participate on the [https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_elections/2027/Proposed_eligibility_criteria proposal talk page] regardless of Café attendance.

Please see the [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Café] page for more information, including [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#How_to_attend_the_session how to register]!

To subscribe or unsubscribe for Café notices on your talk page please [https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Wikimedia_Caf%C3%A9 go here].
&lt;br /&gt;
[[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]]&lt;/div&gt;
&lt;span style=&quot;white-space:nowrap;&quot;&gt;[[User:Pine|&lt;span style=&quot;color:#01796f; text-shadow:#00BFFF 0 0 1.0em&quot;&gt;༄ᨒ𖠰 Pine&lt;/span&gt;]] [[User talk:Pine|&lt;span style=&quot;color:DeepSkyBlue&quot;&gt;(&lt;b style=&quot;color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em&quot;&gt;✉&lt;/b&gt;)&lt;/span&gt;]]&lt;/span&gt; 06:22, 18 October 2026 (UTC)

== Speedy deletion and the deletion policy ==
Right now, I am trying to figure out how to split the speedy deletion and deletion policy, but the deletion policy has a meaningful content section which might either be moved to the speedy deletion page or not. Do abandoned pages also count as (not) meaningful content? Also, the spam, vandalism and nonsense, and test page reasons could probably be separate, instead of together. Otherwise, this seems to be confusing. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:28, 20 October 2026 (UTC)

== Proposal for the Wikibooks Magazine ==
Hello,
Just wanted to note that there is a proposal for the Wikibooks Magazine on [[Wikibooks:Reading room/Proposals#Wikibooks Magazine|this page]]. Please share your thoughts. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:34, 21 October 2026 (UTC)

== need help splitting a childrens book  ==
hi i am a newcomer and i really need some help  i am writing a childrens book  but it has turned into one GIANT piece of reading  i need help learning  how to break this book  up into  chapters ( note that i tried to do it thats how it became giant.)  or sub pages so it is easy to read thank you with peace,[[User:Phoenix3452|Phoenix3452]] ([[User talk:Phoenix3452|discuss]] • [[Special:Contributions/Phoenix3452|contribs]]) 15:32, 23 October 2026 (UTC)

:I posted a welcome message on your talk page that may be helpful. Let me know if you are still confused after taking a look. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 21:18, 23 October 2026 (UTC)

== Call for new administrators ==
Any experienced editors (especially patrollers) who have a good understanding of this project's policies and guidelines may put their name for administrator permissions at [[Wikibooks:Requests for permissions]]. We are looking for active administrators to better help with the maintenance of this project, thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 15:04, 27 October 2026 (UTC)</text>
      <sha1>dt0kg0h9x0zg84apipehcp3kgqlv9pj</sha1>
    </revision>
  </page>
  <page>
    <title>Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Bc4/3...Nf6/4. Ng5</title>
    <ns>0</ns>
    <id>133273</id>
    <revision>
      <id>4678667</id>
      <parentid>4633097</parentid>
      <timestamp>2026-10-28T08:39:18Z</timestamp>
      <contributor>
        <username>UnbreakablePromise</username>
        <id>3625823</id>
      </contributor>
      <comment>its not dubious, white gains a pawn for a bit less actvity, its 100% playable</comment>
      <origin>4678667</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="12208" sha1="7bo05xomdljt1js4cc0iqf8xaxvwkru" xml:space="preserve">{{Chess Opening Theory/Position
|name=Two knights defence
|eco=[[Chess/ECOC|C57]]
|parent=[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Bc4|Italian game]] → [[../|3...Nf6]]
}}

== 4. Ng5 ==
4. Ng5 is a sideline but the most common amateur move. This Romantic move is an attack on f7 with the bishop and knight, taking advantage of the fact that Black gave up control of g5 and cannot castle yet. However, it is unprincipled to attack before having finished development and Black equalises with best play. 

Black needs to defend f7: otherwise, as in the common beginner blunder, '''4...h6??''' 5. Nxf7 Qe7 6. Nxh8, Black gets the house. If Black thinks to counter-attack instead, [[/4...Nxe4|'''4...Nxe4?''']], the '''Ponziani-Steinitz gambit''', fails to 5. Bxf7+! Ke7 6. d4.

[[/4...d5|'''4...d5''']] is the best way to defend f7. This sacrifices a pawn to 5. exd5. Then there have been several moves tried:
* 5...Na5, the Polerio defence, is the most serious continuation and main line today. Black counterattacks the bishop, and the line continues 6. Bb5+ c6 7. dxc6 bxc6 8. Bd3 Nd5 9. Nf3 Bd6 10. O-O. White may be ahead a pawn, but Black is considered equal with more active pieces;
* 5...b5!?, the Ulvestad variation, to drive the bishop on c4 to somewhere less useful;
* 5...Nd4!?, the Fritz variation, gets the knight out from under the gun;
* 5...Nxd5?! is more common in amateur games, allowing 6. Nxf7, the audacious knight sacrifice known as the fried liver attack, or 6. d4, the Lolli attack. 

[[/4...Bc5|'''4...Bc5?''']] is the venomous but objectively dubious '''Traxler counterattack'''. Black can answer 5. Nxf7? Bxf2+! 6. Kxf2 Nxe4+{{chess/not}}, but instead 5. Bxf7+ is a free pawn. 

=== History ===

This move has been known since the 17th century, appearing in attributed to Italian chess masters [[w:Giulio Cesare Polerio|Giulio Cesare Polerio]]&lt;ref&gt;[https://www.chessgames.com/perl/chessgame?gid=1224683 Polerio v Domenico, 1610. Chessgames.com]&lt;/ref&gt; and [[w:Gioachino Greco|Gioachino Greco]].&lt;ref&gt;[https://www.chessgames.com/perl/chessgame?gid=1271138 Greco v NN, 1620]&lt;/ref&gt; Their games continued with the line 4...d5 5. exd5 Nxd5 6. Nxf7, the ''fegatello'', or in English, the &quot;fried liver&quot; attack. Colloquially, the position after 4. Ng5 may be called the &quot;fried liver&quot;, or that name is reserved specifically for the continuation with 5...Nxd5 and the sacrifice of the knight on f7. 

This is a sharp attack on Black's weakest square, f7. A generous critic might call 4. Ng5 &quot;forthright&quot;, though [[w:Siegbert Tarrasch|Siegbert Tarrasch]] called it  &quot;bungling&quot;.&lt;ref&gt;{{cite book |last=Tarrasch |first=Siegbert |translator-last1=Smith |translator-first1=G.E. |translator-last2=Bone |translator-first2=T.G. |title=The Game of Chess |year=1935 |location=London |publisher=Chatto &amp; Windus |url=https://archive.org/details/dli.ministry.13269/page/n5/mode/2up |via=Internet Archive |page=259}}&lt;/ref&gt; In general, chess masters find 4. d3 to be more sound, however 4. Ng5 demands Black play accurately and at worse the game is equal. 

A recent appearance of 4. Ng5 was in the 2026 Women's Candidates, played by [[w:Zhongyi Tan|Zhongyi Tan]].&lt;ref&gt;[https://www.chessgames.com/perl/chessgame?gid=3121156 Tan v Goryachkina, 2026. Chessgames.com]&lt;/ref&gt;

==Theory table==
{{ChessTable}}

'''1.e4 e5 2.Nf3 Nc6 3.Bc4 Nf6 4.Ng5'''

&lt;table border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot;&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;br&gt;4&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;br&gt;5&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;br&gt;6&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;br&gt;7&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;br&gt;8&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;br&gt;9&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;br&gt;10&lt;/th&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Traxler Counterattack, Bishop Sacrifice Line&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;1&lt;/th&gt;
		&lt;td&gt;Ng5&lt;br&gt;[[/4...Bc5|Bc5!?]]&lt;/td&gt;
		&lt;td&gt;[[/4...Bc5/5. Bxf7|Bxf7+]]&lt;br&gt;[[/4...Bc5/5. Bxf7/5...Ke7|Ke7]]&lt;/td&gt;
		&lt;td&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5|Bd5]]&lt;br&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8|Rf8]]&lt;/td&gt;
		&lt;td&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O|O-O]]&lt;br&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O/7...d6|d6]]&lt;/td&gt;
		&lt;td&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O/7...d6/8. c3|c3]]&lt;br&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O/7...d6/8. c3/8...Bg4|Bg4]]&lt;/td&gt;
		&lt;td&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O/7...d6/8. c3/8...Bg4/9.  Qb3|Qb3]]&lt;br&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O/7...d6/8. c3/8...Bg4/9. Qb3/9...Bb6|Bb6]]&lt;/td&gt;
		&lt;td&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O/7...d6/8. c3/8...Bg4/9. Qb3/9...Bb6/10. Bxc6|Bxc6]]&lt;br&gt;[[/4...Bc5/5. Bxf7/5...Ke7/6. Bd5/6...Rf8/7. O-O/7...d6/8. c3/8...Bg4/9. Qb3/9...Bb6/10. Bxc6/10...bxc6|bxc6]]&lt;/td&gt;
		&lt;td&gt;+/=&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Lolli Attack, Pincus Variation&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;2&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;[[/4...d5|d5]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5|exd5]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5|Nxd5!?]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4|d4]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4|Bb4+]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3|c3]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3/7...Be7|Be7]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3/7...Be7/8. Nxf7|Nxf7]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3/7...Be7/8. Nxf7/8...Kxf7|Kxf7]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3/7...Be7/8. Nxf7/8...Kxf7/9. Qf3|Qf3+]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3/7...Be7/8. Nxf7/8...Kxf7/9. Qf3/9...Ke6|Ke6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3/7...Be7/8. Nxf7/8...Kxf7/9. Qf3/9...Ke6/10. Qe4|Qe4]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. d4/6...Bb4/7. c3/7...Be7/8. Nxf7/8...Kxf7/9. Qf3/9...Ke6/10. Qe4/10...Rf8|Rf8]]&lt;/td&gt;
		&lt;td&gt;+/=&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Fried Liver Attack&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;3&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7|Nxf7!?]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7|Kxf7]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3|Qf3+]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6|Ke6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6/8. Nc3|Nc3]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6/8. Nc3/8...Ncb4|Ncb4]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6/8. Nc3/8...Ncb4/9. a3|a3]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6/8. Nc3/8...Ncb4/9. a3/9...Nxc2|Nxc2+]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6/8. Nc3/8...Ncb4/9. a3/9...Nxc2/10. Kd1|Kd1]]&lt;br&gt;[[/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6/8. Nc3/8...Ncb4/9. a3/9...Nxc2/10. Kd1/10...Nxa1|Nxa1]]&lt;/td&gt;
		&lt;td&gt;-+&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Polerio Defense, Kieseritzky, Yankovich Variation&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;4&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;[[/4...d5/5. exd5/5...Na5|Na5]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. d3|d3]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6|h6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3|Nf3]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3/7...e4|e4]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3/7...e4/8. Qe2|Qe2]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3/7...e4/8. Qe2/8...Nxc4|Nxc4]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3/7...e4/8. Qe2/8...Nxc4/9. dxc4|dxc4]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3/7...e4/8. Qe2/8...Nxc4/9. dxc4/9...Bc5|Bc5]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3/7...e4/8. Qe2/8...Nxc4/9. dxc4/9...Bc5/10. Nfd2|Nfd2]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. d3/6...h6/7. Nf3/7...e4/8. Qe2/8...Nxc4/9. dxc4/9...Bc5/10. Nfd2/10...O-O|O-O]]&lt;/td&gt;
		&lt;td&gt;=&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Polerio, Bishop Check Line, Suhle Defense&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;5&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5|Bb5+]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6|c6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6|dxc6]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6|bxc6]]&lt;/td&gt;
		&lt;td&gt;
[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2|Be2]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6|h6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9. Nf3|Nf3]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9. Nf3/9...e4|e4]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9. Nf3/9...e4/10. Ne5|Ne5]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9.  Nf3/9...e4/10. Ne5/10...Bc5|Bc5]]&lt;/td&gt;
		&lt;td&gt;∞&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Polerio, Bishop Check, Suhle, Steinitz Variation&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;6&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9. Nh3|Nh3]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9. Nh3/9...Bd6|Bd6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9. Nh3/9...Bd6/10. d3|d3]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Be2/8...h6/9. Nh3/9...Bd6/10. d3/10...O-O|O-O]]&lt;/td&gt;
		&lt;td&gt;∞&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Polerio, Bishop Check, Bogoljubov Variation&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;7&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Qf3|Qf3]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Qf3/8...Be7|Be7]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Qf3/8...Be7/9. Bxc6|Bxc6+]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Qf3/8...Be7/9. Bxc6/9...Nxc6|Nxc6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Qf3/8...Be7/9. Bxc6/9...Nxc6/10. Qxc6|Qxc6+]]&lt;br&gt;[[/4...d5/5. exd5/5...Na5/6. Bb5/6...c6/7. dxc6/7...bxc6/8. Qf3/8...Be7/9. Bxc6/9...Nxc6/10. Qxc6/10...Bd7|Bd7]]&lt;/td&gt;
		&lt;td&gt;∞&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Ulvestad Variation, Kurkin Gambit&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;8&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;[[/4...d5/5. exd5/5...b5|b5]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...b5/6. Bf1|Bf1]]&lt;br&gt;[[/4...d5/5. exd5/5...b5/6. Bf1/6...h6|h6]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...b5/6. Bf1/6...h6/7. Nxf7|Nxf7]]&lt;br&gt;[[/4...d5/5. exd5/5...b5/6. Bf1/6...h6/7. Nxf7/7...Kxf7|Kxf7]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...b5/6. Bf1/6...h6/7. Nxf7/7...Kxf7/8. dxc6|dxc6]]&lt;br&gt;[[/4...d5/5. exd5/5...b5/6. Bf1/6...h6/7. Nxf7/7...Kxf7/8. dxc6/8...Qd5|Qd5]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...b5/6. Bf1/6...h6/7. Nxf7/7...Kxf7/8. dxc6/8...Qd5/9. Qf3|Qf3]]&lt;br&gt;Qc5&lt;/td&gt;
		&lt;td&gt;b4&lt;br&gt;Qxb4&lt;/td&gt;
		&lt;td&gt;∞&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Fritz Variation, Gruber Variation, Berliner Variation&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;9&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;...&lt;/td&gt;
		&lt;td&gt;...&lt;br&gt;[[/4...d5/5. exd5/5...Nd4|Nd4]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nd4/6. c3|c3]]&lt;br&gt;[[/4...d5/5. exd5/5...Nd4/6. c3/6...b5|b5]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nd4/6. c3/6...b5/7. Bf1|Bf1]]&lt;br&gt;[[/4...d5/5. exd5/5...Nd4/6. c3/6...b5/7. Bf1/7...Nxd5|Nxd5]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nd4/6. c3/6...b5/7. Bf1/7...Nxd5/8. Ne4|Ne4]]&lt;br&gt;[[/4...d5/5. exd5/5...Nd4/6. c3/6...b5/7. Bf1/7...Nxd5/8. Ne4/8...Qh4|Qh4]]&lt;/td&gt;
		&lt;td&gt;[[/4...d5/5. exd5/5...Nd4/6. c3/6...b5/7. Bf1/7...Nxd5/8. Ne4/8...Qh4/9. Ng3|Ng3]]&lt;br&gt;[[/4...d5/5. exd5/5...Nd4/6. c3/6...b5/7. Bf1/7...Nxd5/8. Ne4/8...Qh4/9. Ng3/9...Bg4|Bg4]]&lt;/td&gt;
		&lt;td&gt;f3&lt;br&gt;e4&lt;/td&gt;
		&lt;td&gt;&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;Ponziani-Steinitz Gambit&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;10&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;[[/4...Nxe4|Nxe4?!]]&lt;/td&gt;
		&lt;td&gt;Bxf7+!&lt;br&gt;Ke7&lt;/td&gt;
		&lt;td&gt;d4&lt;br&gt;d5&lt;/td&gt;
		&lt;td&gt;Nc3

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;+=&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;left&quot;&gt;&lt;/th&gt;
		&lt;th align=&quot;right&quot;&gt;11&lt;/th&gt;
		&lt;td&gt;...&lt;br&gt;[[/4...Nd5|Nd5]]&lt;/td&gt;
		&lt;td&gt;d3

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;

&lt;/td&gt;
		&lt;td&gt;+=&lt;/td&gt;
	&lt;/tr&gt;
&lt;/table&gt;

{{ChessMid}}

==References==
{{Wikipedia|Two Knights Defence}}
{{reflist}}
{{BCO2}}
{{NCO}}
{{Chess Opening Theory/Footer}}</text>
      <sha1>7bo05xomdljt1js4cc0iqf8xaxvwkru</sha1>
    </revision>
  </page>
  <page>
    <title>Writing Adolescent Fiction/Character names</title>
    <ns>0</ns>
    <id>136055</id>
    <revision>
      <id>4678542</id>
      <parentid>4620106</parentid>
      <timestamp>2026-10-27T18:08:32Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Western Asia and North Africa */ Add saudi names section</comment>
      <origin>4678542</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5049" sha1="cmh4m6k4bk5ladywr38ifbtu830zmnw" xml:space="preserve">{{Ambox|type=style|text=Please do not change the names listed in each category, as your edit will be reverted. Instead, add it to the list for each category, or if you want to change it, leave a message in the talk page of the respective category.

Also please make sure that you add it in the correct sub category; don't assume that every name is so common to come in the 'Most common names' or similar.

Additionally, make sure that you add the name in such a way that they are in alphabetical order.}}
First names and surnames for characters of many different ethnic and religious groups. Here are many girls' names and boys' names, general, ethnic, and religious, and more than 48,000 surnames to choose from.
== General ==
*[[/Girls|A general list of girls' names]]
*[[/Boys|A general list of boys' names]]
*[[/Unisex|A general list of unisex names]]
*[[/Initial names|Initial names]]
*[[/Botanical|Botanical names]]
*[[/Precious stones|Precious stone names for girls]]

== Americas ==
*Names from Early Established Diaspora Communities in the Americas 
**[[/Popular names in the U.S. in different years|Popular names in the U.S. in different years]]
***[[/African-American|African-American]]
***[[/Southern/Southwestern double boys' names|Southern/Southwestern double boys' names]]
***[[/Southern girls' names|Southern girls' names]]
**[[/West Indian|West Indian]]
**Latin American Names 
***[[/Spanish|Spanish]]
***[[/Portuguese|Portuguese]]
***[[/French|French]]
*Names from Communities of Indigenous Peoples of the Americas  
**[[/Native American|Native American]]
**[[/Latin American Indian|Latin American Indian / Indigenous Latin American]]
**[[/Alaska Native|Alaska Native]]

== Europe ==
*[[/Albanian|Albanian]]
*[[/Basque|Basque]]
*[[/Belarusian|Belarusian]]
*[[/Bulgarian and Macedonian|Bulgarian and Macedonian]]
*[[/Carpatho-Rusyn|Carpatho-Rusyn]]
*[[/Celtic|Celtic]]
*[[/Cornish|Cornish]]
*[[/Czechoslovakian|Czechoslovakian]]
*[[/Danish|Danish]]
*[[/Dutch|Dutch]]
*[[/English|English]]
*[[/Estonian|Estonian]]
*[[/Finnish|Finnish]]
*[[/French|French]]
*[[/German|German]]
*[[/Greek|Greek]]
*[[/Hungarian|Hungarian]]
*[[/Italian|Italian]]
*[[/Latvian|Latvian]]
*[[/Lithuanian|Lithuanian]]
*[[/Maltese|Maltese]]
*[[/Manx|Manx]]
*[[/Polish|Polish]]
*[[/Portuguese|Portuguese]]
*[[/Romanian|Romanian]]
*[[/Russian|Russian]]
*[[/Scandinavian|Scandinavian]]
*[[/Scottish and Irish|Scottish and Irish]]
*[[/Spanish|Spanish]]
*[[/Swedish|Swedish]]
*[[/Ukrainian|Ukrainian]]
*[[/Welsh|Welsh]]
*[[/Yugoslavian|Yugoslavian]]

== Western Asia and North Africa ==
*[[/Ancient Egyptian|Ancient Egyptian]]
*[[/Arab|Arab]]
*[[/Berber|Berber]]
*[[/Kyrgyz|Kyrgyz]]
*[[/Maltese|Maltese]]
*[[/Persian|Persian]]
*[[/Turkish|Turkish]]
*[[/Armenian|Armenian]]
*[[/Azerbaijani|Azerbaijani]]
*[[/Georgian|Georgian]]
*[[Writing Adolescent Fiction/Character names/Western Asia and North Africa/saudi|Saudi]]

== South Asia ==
*[[/Bangladeshi|Bangladeshi]]
*[[/East Indian|Indian]]
*[[/Nepalese|Nepalese]]
*[[/Roma|Roma]]
*[[/Sri Lankan|Sri Lankan]]

== Subsaharan Africa ==
*[[/Congolese|Congolese]]
*[[Writing Adolescent Fiction/Character names/Horn of Africa (Ethiopian and Eritrean, Somali, Djiboutian)|Horn of Africa (Ethiopian and Eritrean, Somali, Djiboutian)]]
**[[Writing Adolescent Fiction/Character names/Horn of Africa (Ethiopian and Eritrean, Somali, Djiboutian)#Ethiopian and Eritrean|Ethiopian and Eritrean]]
**[[Writing Adolescent Fiction/Character names/Horn of Africa (Ethiopian and Eritrean, Somali, Djiboutian)#Somali|Somali]]
**[[Writing Adolescent Fiction/Character names/Horn of Africa (Ethiopian and Eritrean, Somali, Djiboutian)#Djiboutian|Djiboutian]] 
**Christian, Muslim, and Jewish names
*[[/Ghanaian|Ghanaian]]
*[[/Kenyan, Tanzanian and Ugandan|Kenyan, Tanzanian and Ugandan]] (including Swahili names)
*[[/Malawian|Malawian]]
*[[/Nigerian|Nigerian]]
*[[/Senegalese|Senegalese]]
*[[/Sesotho|Sesotho]]
*[[/Sierra Leonean|Sierra Leonean]]
*[[/Black South African|Black South African]]
*[[/Zimbabwean|Zimbabwean]]
*[[/African-American|African-American]]
*[[/West Indian|West Indian]]

== East and Southeast Asia ==
*[[/Burmese|Burmese]]
*[[/Cambodian|Cambodian]]
*[[/Chinese|Chinese]]
*[[/Filipino|Filipino]]
*[[/Himalayan|Himalayan]] (Tibetan, Bhutanese and Nepali)
*[[/Hmong|Hmong]]
*[[/Indonesian|Indonesian]] (and Malaysian)
*[[/Japanese|Japanese]]
*[[/Korean|Korean]]
*[[/Lahu|Lahu]]
*[[/Laotian|Laotian]]
*[[/Manchu|Manchu]]
*[[/Mien|Mien]]
*[[/Mongolian|Mongolian]]
*[[/Thai|Thai]]
*[[/Vietnamese|Vietnamese]]

== Oceania ==
*[[/Australian Aboriginal|Australian Aboriginal]]
*[[/Fijian|Fijian]]
*[[/Hawaiian|Hawaiian]]
*[[/Maori|Maori]]
*[[/Micronesian|Micronesian]] (Guamanian, Northern Mariana Islander, Marshallese, Palauan and FSM)
*[[/Papua New Guinean|Papua New Guinean]]
*[[/Samoan|Samoan]]
*[[/Tahitian|Tahitian]]
*[[/Tongan|Tongan]]

== Religion ==
*[[/Buddhist|Buddhist]]
*[[/Jewish|Jewish]]
*[[/Mennonite (European-origin)|Mennonite (European-origin)]]
*[[/Mormon|Mormon]]

{{Subject|Writing Adolescent Fiction}}</text>
      <sha1>cmh4m6k4bk5ladywr38ifbtu830zmnw</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Patrolling</title>
    <ns>4</ns>
    <id>145713</id>
    <revision>
      <id>4678515</id>
      <parentid>3821519</parentid>
      <timestamp>2026-10-27T17:16:26Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Updating, this is the basis.</comment>
      <origin>4678515</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1275" sha1="ly6f6k5mpjgipo8tjkvfcjm8dbejcjy" xml:space="preserve">{{shortcut|WB:PATROL}}
'''Patrolling''' is a feature used by [[Wikibooks:Administrators|administrators]] and [[Wikibooks:Patrollers|patrollers]] to mark [[Special:NewPages|newly created pages]] as patrolled. A log of recently patrolled pages can be found at [[Special:Log/patrol]].

== Patrolling new pages ==
Unpatrolled pages are shown up in [[Special:RecentChanges]] with a red exclamation mark (&lt;span style=&quot;font-weight: bold; color: red;&quot;&gt;&lt;abbr title=&quot;This edit has not yet been patrolled&quot;&gt;!&lt;/abbr&gt;&lt;/span&gt;), as well as being highlighted in yellow on [[Special:NewPages]]. In contrast, patrolled pages do not have an exclamation mark and is not highlighted in yellow.

A user with the appropriate  rights can click the button {{clickable button|2=Mark this page as patrolled|class=cdx-button cdx-button--action-progressive cdx-button--fake-button cdx-button--fake-button--enabled}}, which automatically marks the page as patrolled.

=== When not to mark a page as patrolled ===
A page should generally '''not''' be marked as patrolled if it contains the following:
* Obvious vandalism awaiting deletion or reversion
* Advertising or other inappropriate promotion
* Content which appears to be a copyright violation

==See also==
*[[Help:Tracking changes#Reviewing pages]]</text>
      <sha1>ly6f6k5mpjgipo8tjkvfcjm8dbejcjy</sha1>
    </revision>
    <revision>
      <id>4678517</id>
      <parentid>4678515</parentid>
      <timestamp>2026-10-27T17:17:08Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>Codename Noreste moved page [[Wikibooks:New page patrol]] to [[Wikibooks:Patrolling]]: New name.</comment>
      <origin>4678515</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1275" sha1="ly6f6k5mpjgipo8tjkvfcjm8dbejcjy" xml:space="preserve">{{shortcut|WB:PATROL}}
'''Patrolling''' is a feature used by [[Wikibooks:Administrators|administrators]] and [[Wikibooks:Patrollers|patrollers]] to mark [[Special:NewPages|newly created pages]] as patrolled. A log of recently patrolled pages can be found at [[Special:Log/patrol]].

== Patrolling new pages ==
Unpatrolled pages are shown up in [[Special:RecentChanges]] with a red exclamation mark (&lt;span style=&quot;font-weight: bold; color: red;&quot;&gt;&lt;abbr title=&quot;This edit has not yet been patrolled&quot;&gt;!&lt;/abbr&gt;&lt;/span&gt;), as well as being highlighted in yellow on [[Special:NewPages]]. In contrast, patrolled pages do not have an exclamation mark and is not highlighted in yellow.

A user with the appropriate  rights can click the button {{clickable button|2=Mark this page as patrolled|class=cdx-button cdx-button--action-progressive cdx-button--fake-button cdx-button--fake-button--enabled}}, which automatically marks the page as patrolled.

=== When not to mark a page as patrolled ===
A page should generally '''not''' be marked as patrolled if it contains the following:
* Obvious vandalism awaiting deletion or reversion
* Advertising or other inappropriate promotion
* Content which appears to be a copyright violation

==See also==
*[[Help:Tracking changes#Reviewing pages]]</text>
      <sha1>ly6f6k5mpjgipo8tjkvfcjm8dbejcjy</sha1>
    </revision>
    <revision>
      <id>4678523</id>
      <parentid>4678517</parentid>
      <timestamp>2026-10-27T17:18:06Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Patrolling new pages */ Shortcut.</comment>
      <origin>4678523</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1295" sha1="5liytowt6n3qz8vqy9reqy43og6argr" xml:space="preserve">{{shortcut|WB:PATROL}}
'''Patrolling''' is a feature used by [[Wikibooks:Administrators|administrators]] and [[Wikibooks:Patrollers|patrollers]] to mark [[Special:NewPages|newly created pages]] as patrolled. A log of recently patrolled pages can be found at [[Special:Log/patrol]].

== Patrolling new pages ==
{{shortcut|WB:NPP}}
Unpatrolled pages are shown up in [[Special:RecentChanges]] with a red exclamation mark (&lt;span style=&quot;font-weight: bold; color: red;&quot;&gt;&lt;abbr title=&quot;This edit has not yet been patrolled&quot;&gt;!&lt;/abbr&gt;&lt;/span&gt;), as well as being highlighted in yellow on [[Special:NewPages]]. In contrast, patrolled pages do not have an exclamation mark and is not highlighted in yellow.

A user with the appropriate  rights can click the button {{clickable button|2=Mark this page as patrolled|class=cdx-button cdx-button--action-progressive cdx-button--fake-button cdx-button--fake-button--enabled}}, which automatically marks the page as patrolled.

=== When not to mark a page as patrolled ===
A page should generally '''not''' be marked as patrolled if it contains the following:
* Obvious vandalism awaiting deletion or reversion
* Advertising or other inappropriate promotion
* Content which appears to be a copyright violation

==See also==
*[[Help:Tracking changes#Reviewing pages]]</text>
      <sha1>5liytowt6n3qz8vqy9reqy43og6argr</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:PATROL</title>
    <ns>4</ns>
    <id>146525</id>
    <redirect title="Wikibooks:Patrolling" />
    <revision>
      <id>4678516</id>
      <parentid>1087143</parentid>
      <timestamp>2026-10-27T17:16:49Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Changed redirect target from [[Wikibooks:New page patrol]] to [[Wikibooks:Patrolling]]</comment>
      <origin>4678516</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33" sha1="6jwvm8tfmukamf8mvvh2tve1kkgz0yl" xml:space="preserve">#REDIRECT[[Wikibooks:Patrolling]]</text>
      <sha1>6jwvm8tfmukamf8mvvh2tve1kkgz0yl</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:NPP</title>
    <ns>4</ns>
    <id>147190</id>
    <redirect title="Wikibooks:Patrolling" />
    <revision>
      <id>4678522</id>
      <parentid>1092866</parentid>
      <timestamp>2026-10-27T17:17:48Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Changed redirect target from [[Wikibooks:New page patrol]] to [[Wikibooks:Patrolling#Patrolling new pages]]</comment>
      <origin>4678522</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="54" sha1="0tosgychle8a978jobn0juh44ljgz4c" xml:space="preserve">#REDIRECT[[Wikibooks:Patrolling#Patrolling new pages]]</text>
      <sha1>0tosgychle8a978jobn0juh44ljgz4c</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/Proposals</title>
    <ns>4</ns>
    <id>155682</id>
    <revision>
      <id>4678525</id>
      <parentid>4678448</parentid>
      <timestamp>2026-10-27T17:39:09Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Enabling wgUseRCPatrol */ new topic ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678525</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="30825" sha1="5rp2akn5kyubyz8prmahhx3j50r0qdu" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing pages in the recent changes, not just new page creations. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>5rp2akn5kyubyz8prmahhx3j50r0qdu</sha1>
    </revision>
    <revision>
      <id>4678526</id>
      <parentid>4678525</parentid>
      <timestamp>2026-10-27T17:40:39Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>/* Enabling wgUseRCPatrol */ edit opening comment ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678526</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="30816" sha1="1mzjysjqs3k773afhz7rzct4fqx4iru" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>1mzjysjqs3k773afhz7rzct4fqx4iru</sha1>
    </revision>
    <revision>
      <id>4678527</id>
      <parentid>4678526</parentid>
      <timestamp>2026-10-27T17:45:57Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Approving Wikibooks:Outdated books as a policy */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678527</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31040" sha1="51w8wc0ku833de2hhgbldpi8n0991yb" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>51w8wc0ku833de2hhgbldpi8n0991yb</sha1>
    </revision>
    <revision>
      <id>4678528</id>
      <parentid>4678527</parentid>
      <timestamp>2026-10-27T17:48:42Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Discussion on whether to create an extended mover user group */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678528</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31261" sha1="d8g47pmfprjxsablwtcjwwss61gq8yo" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>d8g47pmfprjxsablwtcjwwss61gq8yo</sha1>
    </revision>
    <revision>
      <id>4678529</id>
      <parentid>4678528</parentid>
      <timestamp>2026-10-27T17:52:47Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* FlaggedRevs again */ Closed and done.</comment>
      <origin>4678529</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31502" sha1="89naar78fh9t45i00mgw4fbafc0tmwc" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
{{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}}
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)
{{end closed}}

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>89naar78fh9t45i00mgw4fbafc0tmwc</sha1>
    </revision>
    <revision>
      <id>4678531</id>
      <parentid>4678529</parentid>
      <timestamp>2026-10-27T17:55:10Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Disable (some) page creation by temporary accounts */ reply to ~2026-40500-29 ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678531</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31738" sha1="rz3xnbx3s864mksbs84xfe4ti8wjaag" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
{{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}}
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)
{{end closed}}

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>rz3xnbx3s864mksbs84xfe4ti8wjaag</sha1>
    </revision>
    <revision>
      <id>4678533</id>
      <parentid>4678531</parentid>
      <timestamp>2026-10-27T17:59:08Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Add inactivity policies for patrollers and uploaders? */ addition: CC to @TechVindicator. (-) ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678533</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31939" sha1="eu7p8pw1hsal7356tm1thum6hxwgeqg" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
{{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}}
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)
{{end closed}}

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
::: CC to @[[User:TechVindicator|TechVindicator]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:59, 27 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>eu7p8pw1hsal7356tm1thum6hxwgeqg</sha1>
    </revision>
    <revision>
      <id>4678534</id>
      <parentid>4678533</parentid>
      <timestamp>2026-10-27T18:00:16Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Wikibooks Magazine */ reply: We can do that with [[Wikibooks:Magazine]]. (-) ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678534</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="32135" sha1="2jzuswqmmpo0gc9ubtoud0cyqhjpnb9" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
{{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}}
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)
{{end closed}}

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
::: CC to @[[User:TechVindicator|TechVindicator]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:59, 27 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)
: We can do that with [[Wikibooks:Magazine]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:00, 27 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>2jzuswqmmpo0gc9ubtoud0cyqhjpnb9</sha1>
    </revision>
    <revision>
      <id>4678535</id>
      <parentid>4678534</parentid>
      <timestamp>2026-10-27T18:00:36Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Add inactivity policies for patrollers and uploaders? */ delete addition ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678535</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31934" sha1="nhwptboi9x6v1tzsxekjfu9195ggdeg" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
{{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}}
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)
{{end closed}}

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)
: We can do that with [[Wikibooks:Magazine]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:00, 27 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>nhwptboi9x6v1tzsxekjfu9195ggdeg</sha1>
    </revision>
    <revision>
      <id>4678536</id>
      <parentid>4678535</parentid>
      <timestamp>2026-10-27T18:01:05Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Add inactivity policies for patrollers and uploaders? */ addition ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4678536</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="32176" sha1="g0cbnri0rlfqkssg7103qtuutrssg5o" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
{{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}}
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)
{{end closed}}

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
::: CC to @[[User:MathsScienceNerd1|MathsScienceNerd1]], who was previously TechVindicator. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 27 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)
: We can do that with [[Wikibooks:Magazine]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:00, 27 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>g0cbnri0rlfqkssg7103qtuutrssg5o</sha1>
    </revision>
    <revision>
      <id>4678652</id>
      <parentid>4678536</parentid>
      <timestamp>2026-10-28T07:32:22Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>/* Wikibooks Magazine */</comment>
      <origin>4678652</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="32463" sha1="mtp5qc1qj0hu2d2kuhw2wf4i7vb1yr6" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks.

{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s
|algo = old(120d)
|counter = 1
|key = 1f2adc5eee951900b65c7b981b786191
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{clear}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
{{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}}
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)
{{end closed}}

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &lt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Add inactivity policies for patrollers and uploaders? ==
I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years.

I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence).

Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy.

Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC)
: {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC)
:: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC)
::: CC to @[[User:MathsScienceNerd1|MathsScienceNerd1]], who was previously TechVindicator. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 27 October 2026 (UTC)
:@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC)
:: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)

== Approving [[Wikibooks:Outdated books]] as a policy ==
I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below:
{{hidden archive top|Policy text}}

Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

;For books that aren't up to date, but can be reasonably updated
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

;For books that cannot be reasonably updated
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.

If the case is unambiguous:
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

If the case is ambiguous:

Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.
{{hidden archive bottom}} [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC)
: I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC)
::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC)
: {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC)

== Wikibooks Magazine ==
I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely).
&lt;br&gt;
If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think?
[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC)
:{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC)
:{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC)
:I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other &lt;abbr&gt;WMF&lt;/abbr&gt; wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:36, 21 October 2026 (UTC)
: Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC)
::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC)
: We can do that with [[Wikibooks:Magazine]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:00, 27 October 2026 (UTC)
::I will create a page about what the Wikibooks Magazine on the page provided, and the editions that will follow. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 07:32, 28 October 2026 (UTC)

== Discussion on whether to create an extended mover user group ==
Currently, patrollers (formerly reviewers) have the &lt;code&gt;suppressredirect&lt;/code&gt; user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we:
# Remove &lt;code&gt;suppressredirect&lt;/code&gt; from patrollers
# Add &lt;code&gt;suppressredirect&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; as well as include &lt;code&gt;delete-redirect&lt;/code&gt; (for deleting redirects with a single revision) and &lt;code&gt;move-subpages&lt;/code&gt; (to move all subpages of a book in a single action)
# Also include &lt;code&gt;noratelimit&lt;/code&gt; to &lt;code&gt;extendedmover&lt;/code&gt; instead of using a custom rate limit (optional), or increase the limit to 500
This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al.

This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC)

:@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC)
: Also, if this passes, we should create some guidelines for granting. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:48, 27 October 2026 (UTC)

== Enabling wgUseRCPatrol ==
Some of our sister projects have &lt;code&gt;&lt;nowiki&gt;wgUseRCPatrol&lt;/nowiki&gt;&lt;/code&gt; enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC)</text>
      <sha1>mtp5qc1qj0hu2d2kuhw2wf4i7vb1yr6</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks talk:Patrolling</title>
    <ns>5</ns>
    <id>160222</id>
    <revision>
      <id>4678519</id>
      <parentid>4651751</parentid>
      <timestamp>2026-10-27T17:17:08Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>Codename Noreste moved page [[Wikibooks talk:New page patrol]] to [[Wikibooks talk:Patrolling]]: New name.</comment>
      <origin>4651751</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="686" sha1="8jqmlqsgv678lbueaj6vxb6ub21mbg2" xml:space="preserve">Is this function active?  When I visit the new pages link (I'd never visited it before as RC is all that's really needed on WB) I don't see anything to indicate checked or unchecked pages. --[[User:Xania|ЗAНИA]] [[Image:Flag_of_Italy.svg|15px]][[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 21:34, 5 June 2008 (UTC)
:Yes, you can see that some pages are highlighted and some are not at [[Special:NewPages]]. Currently they are mostly not patrolled (ie yellow background). &amp;nbsp;'''&amp;ndash;&amp;nbsp;[[User:Mike.lifeguard|&lt;span style=&quot;color: Indigo;&quot;&gt;Mike.lifeguard&lt;/span&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color: Indigo;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 22:59, 5 June 2008 (UTC)</text>
      <sha1>8jqmlqsgv678lbueaj6vxb6ub21mbg2</sha1>
    </revision>
  </page>
  <page>
    <title>User:Moby-Dick4000</title>
    <ns>2</ns>
    <id>189868</id>
    <revision>
      <id>4678671</id>
      <parentid>4678058</parentid>
      <timestamp>2026-10-28T10:40:30Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Italian-American cuisine */</comment>
      <origin>4678671</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3973" sha1="s854vt51dox9wk6iajmnsmth0rzwhkg" xml:space="preserve">{{user|Moby-Dick4000}}

==Sandbox==
[[/Apollo 20 hoax]]

[[/paella alicantina]]

[[/Haggis]]

[[/Spaghetti allo Scoglio]]

[[/Spaghetti alla Chitarra]]

[[/Marinara sauce]]

[[/Valencian inspired paella]]

[[/Ragu with pasta]]

Singaporean chicken rice 
*http://allrecipes.com/Recipe/Singapore-Chicken-Rice/Detail.aspx

==Wikibooks==
[[wikibooks:templates|Templates]]
*{ { inuse } }

[[wikipedia:wp:merging and moving pages#performing the merger|How to perform mergers]]

[[wikipedia:wp:redirect|How to perform redirects]]

[[Special:UserList|Find all Wikibooks users]]

[[Cookbook:Policy|Cookbook Policy]]

===Procedure For Changing the Cookbook main page===
* Step 1: Edit [[Template:Featured recipe]] or [[Template:Featured ingredient]].
* Step 2: Purge the cache of the main cookbook page, by [http://en.wikibooks.org/w/wiki.phtml?title=Cookbook:Table_of_Contents&amp;action=purge clicking here]. This will allow non-logged in users to see the change.
* Step 3: Add [[:Category:Featured recipes]] or [[:Category:Featured ingredients]] to the featured item.

==Ingredients==
*[[cookbook:rice]]
*[[cookbook:pasta]]
*[[cookbook:potato]]
*[[cookbook:tomato]]
*[[cookbook:onion]]
*[[cookbook:Bell Pepper]]
*[[cookbook:Bivalve Preparation]]

==Recipes==
[[cookbook:Healthy, Traditional Recipes]]

===[[cookbook:Asian Cuisine]]===
[[cookbook:Duck fried rice]]

===Hispanic recipes===
#[[cookbook:Paella Cooking Techniques]] F
#[[cookbook:Paella Roja]] FC
#[[cookbook:Cuisine of Puerto Rico]] 
#[[cookbook:Mastering the Art of Cooking Paellas]] F
#[[cookbook:Cuisine of Spain]]
#[[cookbook:Gambas al Ajillo]] F
#[[cookbook:Fabes con Almejas]] FC
#[[cookbook:Arroz con Pollo]] F
#[[cookbook:Arroz Negro]] FC
#[[cookbook:Paella Valenciana]] FC
#[[cookbook:Paella de Marisco]] FC
#[[Cookbook:Ají de Gallina]] F
#[[cookbook:Arroz con Leche]]
#[[cookbook:Arroz con Frijoles Negros]] F
#[[cookbook:Black Beans and Rice]]
#[[cookbook:Arroz Tapado]] F
#[[cookbook:Sofrito]]
#[[Cookbook:Spanish Omelet]]
#[[Cookbook:Lechon asado]]
#[[Cookbook:Tortilla Canaria]] FC
#[[Cookbook:Valencian-Inspired Paella]] FC

===[[cookbook:Cuisine of Italy|Cuisine of Italy]]===
#[[cookbook:Baked Ziti]]
#[[cookbook:Cannoli]]
#[[cookbook:Caponata]]
#[[cookbook:Marinara Sauce]] FC
#[[cookbook:Ossobuco Alla Milanese]] F
#[[cookbook:Risotto]] F
#[[cookbook:Spaghetti alla Carbonara]] FC
#[[cookbook:Spaghetti alla Puttanesca]] FC
#[[cookbook:Spaghetti alle Vongole]] FC
#[[cookbook:Spaghetti with Bolognese meat sauce]]
#[[wikipedia:it:Spaghetti alle vongole]] (Italian Wikipedia)
#[[wikipedia:it:Spaghetti alla puttanesca]] (Italian Wikipedia)
#[[wikipedia:it:Pasta alla carbonara]] (Italian Wikipedia)

===[[cookbook:Cuisine of the United States|American cuisine]]===
#[[cookbook:Cuisine of the United States]]
#[[cookbook:Long Island Roast Duckling]] FC
#[[cookbook:New England Clam Chowder]]
#[[cookbook:Whole, Roasted Turkey with Stuffing]] F
#[[cookbook:Pumpkin Bread]] F
#[[cookbook:Pancake]]
#[[cookbook:Chocolate Chip Pancakes]]
#[[cookbook:Whole-Wheat Pancakes]] C
#[[cookbook:Succotash]]
====[[cookbook:Italian-American cuisine|Italian-American cuisine]]====
#[[cookbook:Cioppino]]
#[[cookbook:Spaghetti and Meatballs]]
#[[cookbook:Spaghetti with clams in white wine sauce]]
#[[cookbook:New York City-style pizza]]
#[[cookbook:American marinara sauce]]
#[[Cookbook:Meat and Sausage Ragu with Pasta]]

====[[cookbook:New York City cuisine|New York City cuisine]]====
#[[cookbook:Manhattan Clam Chowder]] F
#[[cookbook:New York Cheesecake]] F
#[[cookbook:New York City-style pizza]] F

====[[cookbook:Louisiana Creole cuisine|Louisiana Creole cuisine]]====
#[[cookbook:Jambalaya]] F
#[[cookbook:Seafood Gumbo]]
#[[cookbook:Gumbo]]
#[[cookbook:Cajun Red Beans and Rice]]

===French cuisine===
#[[cookbook:Boeuf Bourguignon]] FC
#[[cookbook:Bouillabaisse]] F
#[[cookbook:Duck à l'Orange]]
#[[cookbook:Duck Confit]]

==Non recipes==
*[[Modern Greek]]
*[[IB Computer Science]]
*[[Movie Making Manual]]</text>
      <sha1>s854vt51dox9wk6iajmnsmth0rzwhkg</sha1>
    </revision>
  </page>
  <page>
    <title>Canadian History/The People of the Lands/Cree</title>
    <ns>0</ns>
    <id>223906</id>
    <revision>
      <id>4678645</id>
      <parentid>3811649</parentid>
      <timestamp>2026-10-28T00:40:38Z</timestamp>
      <contributor>
        <username>~2026-57550-83</username>
        <id>3629565</id>
      </contributor>
      <origin>4678645</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2712" sha1="pbn4uhuv6rs06ju16yra2rpq5oe16gs" xml:space="preserve">The Cree were a First Nations people that mostly lived on the territory of modern Saskatchewan, Alberta, and Manitoba, though they spread as far east as Quebec. Their culture and lifestyle were that of the Plains people, a large group of tribes living in the Interior Plains. There were three general types of Cree-the Plains Cree, in Alberta and Saskatchewan, the Woods Cree, in Saskatchewan and Manitoba, the Swampy Cree, in Manitoba, Ontario, and Quebec.


== Plains Cree ==
The culture and lifestyle of the Cree depended largely on the bison. Bison made up a large part of their lives, including clothing, shelter, and food. Items such as clothing, cups, spoons, teepees/tipis, strings, and weapons were created using the various parts of the bison, among others. i like pp


==Cree Language ==
The Cree language was a language of the Algonquian family. Despite not developing a written syllabary until the early nineteenth century with contact with Europeans, by the beginning of the twentieth century the Cree had one of the highest literacy rates in the world.

== Spirituality ==
Cree spirituality was based on interactions with animals and other spirits that appeared in dreams, as was common among Native Americans. 

An event called the Thirsting Dance by the Cree, and the Sun Dance by other Plains Nations, was central to Plains spirituality. 
The Sun Dance was an annual event, taking place in the summer generally right before the big bison hunt, as that was when most members of a nation were present in one place. The sponsor of the event would often be either a much-admired woman or a man who had experienced success in a war raid.

A lodge would be built for the ceremony, and when it was completed, the dances would begin. The dancers were those who had made a vow to the tribe. Without food, drink or rest, they danced for the several days the ceremony took place. Staying on the spot, they danced with their eyes permanently focused on the top of the centre pole. To prove themselves, the young men of the tribe would have their chests pierced with skewers of bone, which were attached by a rope to the centre pole. While dancing, they would lean back until the skewers were ripped out.


== Cree in Modern Times ==
Today, the Cree is the largest First Nations group in (Canada), with 200,000 people members and 235 registered bands. A Cree band, the Lac La Ronge band, is the second largest in Canada.

== References ==
[http://www.mnsu.edu/emuseum/cultural/northamerica/cree.html|Cree, Minnesota State University]

[http://www.thecanadianencyclopedia.com/index.cfm?PgNm=TCE&amp;Params=A1ARTA0002005|Cree, Canadian Encyclopedia]

Michael Cranny,&quot;Crossroads: A Meeting of Nations&quot;

{{BookCat}}</text>
      <sha1>pbn4uhuv6rs06ju16yra2rpq5oe16gs</sha1>
    </revision>
    <revision>
      <id>4678669</id>
      <parentid>4678645</parentid>
      <timestamp>2026-10-28T09:58:57Z</timestamp>
      <contributor>
        <username>Wargo</username>
        <id>1009988</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-57550-83|~2026-57550-83]] ([[User talk:~2026-57550-83|talk]]) to last version by MarcGarver</comment>
      <origin>3811649</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2701" sha1="iqkwnsnxy7hi7f8yd9q3ma1kikixbvi" xml:space="preserve">The Cree were a First Nations people that mostly lived on the territory of modern Saskatchewan, Alberta, and Manitoba, though they spread as far east as Quebec. Their culture and lifestyle were that of the Plains people, a large group of tribes living in the Interior Plains. There were three general types of Cree-the Plains Cree, in Alberta and Saskatchewan, the Woods Cree, in Saskatchewan and Manitoba, the Swampy Cree, in Manitoba, Ontario, and Quebec.


== Plains Cree ==
The culture and lifestyle of the Cree depended largely on the bison. Bison made up a large part of their lives, including clothing, shelter, and food. Items such as clothing, cups, spoons, teepees/tipis, strings, and weapons were created using the various parts of the bison, among others.

==Cree Language ==
The Cree language was a language of the Algonquian family. Despite not developing a written syllabary until the early nineteenth century with contact with Europeans, by the beginning of the twentieth century the Cree had one of the highest literacy rates in the world.

== Spirituality ==
Cree spirituality was based on interactions with animals and other spirits that appeared in dreams, as was common among Native Americans. 

An event called the Thirsting Dance by the Cree, and the Sun Dance by other Plains Nations, was central to Plains spirituality. 
The Sun Dance was an annual event, taking place in the summer generally right before the big bison hunt, as that was when most members of a nation were present in one place. The sponsor of the event would often be either a much-admired woman or a man who had experienced success in a war raid.

A lodge would be built for the ceremony, and when it was completed, the dances would begin. The dancers were those who had made a vow to the tribe. Without food, drink or rest, they danced for the several days the ceremony took place. Staying on the spot, they danced with their eyes permanently focused on the top of the centre pole. To prove themselves, the young men of the tribe would have their chests pierced with skewers of bone, which were attached by a rope to the centre pole. While dancing, they would lean back until the skewers were ripped out.


== Cree in Modern Times ==
Today, the Cree is the largest First Nations group in (Canada), with 200,000 people members and 235 registered bands. A Cree band, the Lac La Ronge band, is the second largest in Canada.

== References ==
[http://www.mnsu.edu/emuseum/cultural/northamerica/cree.html|Cree, Minnesota State University]

[http://www.thecanadianencyclopedia.com/index.cfm?PgNm=TCE&amp;Params=A1ARTA0002005|Cree, Canadian Encyclopedia]

Michael Cranny,&quot;Crossroads: A Meeting of Nations&quot;

{{BookCat}}</text>
      <sha1>iqkwnsnxy7hi7f8yd9q3ma1kikixbvi</sha1>
    </revision>
  </page>
  <page>
    <title>Canadian History/The Whiskey Traders and the NWMP</title>
    <ns>0</ns>
    <id>224278</id>
    <revision>
      <id>4678558</id>
      <parentid>4621775</parentid>
      <timestamp>2026-10-27T19:17:02Z</timestamp>
      <contributor>
        <username>~2026-57285-77</username>
        <id>3629543</id>
      </contributor>
      <comment>v</comment>
      <origin>4678558</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1988" sha1="680r8ckkf8j8cpf59jii5y1i37b8cv8" xml:space="preserve">During the 1870's there were many independent companies trading whiskey to the Native peoples of the southwest part of the North-West Territories. This led to widespread alcoholism among the Native peoples, which eventually caused poverty, disease, malnutrition, and death. In 1873,Canadian government formed the North-West Mounted Police in an effort to reduce the use of alcohol as a trading currency. By 1874, the NWMP accomplished their task of removing the whiskey traders from Canada, forcing them to flee across the border to the 

Aboriginals of North-West Canada were eager to trade their furs for European tools, food, and weaponry. Trading between Native peoples and the Europeans became a large part of the history of Canada and the exploration and settlement of the country.

In the mid-1800's, American fur traders began to introduce Native peoples to liquor, which had a devastating effect on their way of life. The whiskey traders traded strong, cheap liquor to the Natives, and it benefited the traders greatly, allowing them to make better deals on trade. However, it caused malnutrition, poverty, and disease among the Natives.

Many forts, such as the infamous Fort Whoop-Up, were established around the southern Canadian plains, and the traders began to illegally trade whiskey to Native peoples. The Canadian government formed the North-West Mounted Police in an effort to prevent the use of whiskey in trading with Natives.

= The Formation of the NWMP =

In 1873, the North-West Mounted Police were formed and Assistant Commissioner James Macleod reached Fort Benton, and visited the fort to stock up on supplies. While visiting the fort, they were also introduced to Jerry Potts, whom they hired as a guide. 

With guidance from Potts, the group reached Fort Whoop-Up, which was searched and found to have no alcohol. After leaving the fort, they traveled further west, and established a permanent fort, Fort Macleod, on the Oldman River. 


{{BookCat}}</text>
      <sha1>680r8ckkf8j8cpf59jii5y1i37b8cv8</sha1>
    </revision>
    <revision>
      <id>4678567</id>
      <parentid>4678558</parentid>
      <timestamp>2026-10-27T19:49:19Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-57285-77|~2026-57285-77]] ([[User talk:~2026-57285-77|talk]]) to last version by ~2026-14420-45</comment>
      <origin>4621775</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2049" sha1="cw4ccdphdcr6bn15b7dpsvweguv9ga5" xml:space="preserve">During the 1870's there were many independent companies trading whiskey to the Native peoples of the southwest part of the North-West Territories. This led to widespread alcoholism among the Native peoples, which eventually caused poverty, disease, malnutrition, and death. In 1873, the Canadian government formed the North-West Mounted Police in an effort to reduce the use of alcohol as a trading currency. By 1874, the NWMP accomplished their task of removing the whiskey traders from Canada, forcing them to flee across the border to the United States. 

= The Arrival of the Whiskey Traders = 

Aboriginals of North-West Canada were eager to trade their furs for European tools, food, and weaponry. Trading between Native peoples and the Europeans became a large part of the history of Canada and the exploration and settlement of the country.

In the mid-1800's, American fur traders began to introduce Native peoples to liquor, which had a devastating effect on their way of life. The whiskey traders traded strong, cheap liquor to the Natives, and it benefited the traders greatly, allowing them to make better deals on trade. However, it caused malnutrition, poverty, and disease among the Natives.

Many forts, such as the infamous Fort Whoop-Up, were established around the southern Canadian plains, and the traders began to illegally trade whiskey to Native peoples. The Canadian government formed the North-West Mounted Police in an effort to prevent the use of whiskey in trading with Natives.

= The Formation of the NWMP =

In 1873, the North-West Mounted Police were formed and Assistant Commissioner James Macleod reached Fort Benton, and visited the fort to stock up on supplies. While visiting the fort, they were also introduced to Jerry Potts, whom they hired as a guide. 

With guidance from Potts, the group reached Fort Whoop-Up, which was searched and found to have no alcohol. After leaving the fort, they traveled further west, and established a permanent fort, Fort Macleod, on the Oldman River. 


{{BookCat}}</text>
      <sha1>cw4ccdphdcr6bn15b7dpsvweguv9ga5</sha1>
    </revision>
  </page>
  <page>
    <title>High School Earth Science/Sedimentary Rocks</title>
    <ns>0</ns>
    <id>226266</id>
    <revision>
      <id>4678553</id>
      <parentid>4242168</parentid>
      <timestamp>2026-10-27T18:49:56Z</timestamp>
      <contributor>
        <username>~2026-57358-90</username>
        <id>3629540</id>
      </contributor>
      <origin>4678553</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7907" sha1="4lb3yahkhsvylu5vahfta4gdhumbk60" xml:space="preserve">{{TOCright}}
You probably recognize the Figure 4.19 as the White House, the official home kplace of the President of the United States of America. Do you know why the White House is white? Its color has a lot to do with the stone materials that were used to construct it.

Construction for the White House began in 2032, and most of the work was carried out by people who had only recently come to the newly formed country of America. Its outside walls are made of a type of sedimentary rock called sandstone. The sandstone that was used to construct the White House is very porous, which means that rainwater can easily penetrate the sandstone. This made the White House susceptible to water damage in its early days of construction. To stop the water damage, workers had to cover the sandstone in a mixture of salt, rice, and glue, giving the White House its distinct white color.

[[File:White House Washington.JPG|center|500px|thumb|'''Figure 4.19''': The White House of the United States of America is made of a sedimentary rock called sandstone.]]
{{clear}}
==Lesson Objectives==
* Describe how sedimentary rocks are formed.
* Describe the properties of some common sedimentary rocks.
* Relate some common uses of sedimentary rocks.

==Sediments==
In this lesson, you will learn about sedimentary rocks like sandstone, how they form, how they are classified, and how people often use sedimentary rocks.

Recall from Lesson 4.1 that sedimentary rocks are formed by the compaction of sediments. '''Sediments''' may include:

* fragments of other rocks that have been worn down into small pieces, like sand,
* '''organic''' materials, or in other words, the remains of once-living organisms,
* or chemical '''precipitates''', which are materials that get left behind after the water evaporates from a solution.

Most sediments settle out of water (Figure 4.20). For example, running water in rivers carries huge amounts of sediments. The river dumps these sediments along its banks and at the end of its course. When sediments settle out of water, they form horizontal layers. One layer at a time is put down. Each new layer forms on top of the layers that were already there. Thus, each layer in a sedimentary rock is younger than the layer under it and older than the layer over it. When the sediments harden, the layers are preserved. In large '''outcrops''' of sedimentary rocks, you can often see layers that show the position and order in which the original sediment layers were deposited. Scientists can figure out the relative ages of layers by knowing that older ones are on the bottom and younger ones are on top.

[[File:HN999sRamon~SRP-tours6.jpg|center|500px|thumb|'''Figure 4.20''': Most sediments settle out of running water, such as in this river.]]

There are many different types of environments where sedimentary rocks form. Some places where you can see large deposits of sediments today include a beach and a desert. Sediments are also continuously depositing at the bottom of the ocean and in lakes, ponds, rivers, marshes and swamps. Avalanches produce large unsorted piles of sediment. The environment where the sediments are deposited determines the type of sedimentary rock that will form there.

==Sedimentary Rock Formation==
Sediments accumulate and over time may be hardened into rock. '''Lithification''' is the hardening of layers of loose sediment into rock (Figure 4.21). Lithification is made up of two processes: cementation and compaction. '''Cementation''' occurs when substances crystallize or fill in the spaces between the loose particles of sediment. These cementing substances come from the water that moves through the sediments. Sediments may also be hardened into rocks through '''compaction'''. This occurs when sediments are squeezed together by the
weight of layers on top of them. Sedimentary rocks made of cemented, non-organic sediments are called clastic rocks. Those that form from organic remains are called bioclastic rocks, and sedimentary rocks formed by the hardening of chemical precipitates are called chemical sedimentary rocks. Table 4.2 shows some common types of sedimentary rocks and the types of sediments that make them up.

[[File:Helgoland Lummenfelsen 22067.JPG|500px|center|thumb|'''Figure 4.21''': This cliff is made of a sedimentary rock called sandstone.  The bands of white and red represent different layers of sediment.  The layers of sediments were preserved during lithification.]]

{| class=&quot;wikitable&quot; style=&quot;width:500px; margin:0px auto 0px auto; text-align:center;&quot;
|+ Table 4.2: Common Sedimentary Rocks
! Picture || Rock Name || Type of Sedimentary Rock
|-
|[[File:Conglomerate Death Valley NP.jpg|200px]]
|Conglomerate
|Clastic (fragments of non-organic sediments)
|-
|[[File:UpperTriassicYorkCountyPA.jpg|200px]]
|Breccia
|Clastic
|-
|[[File:Sandstone(quartz)USGOV.jpg|200px]]
|Sandstone
|Clastic
|-
|[[File:SiltstoneUSGOV.jpg|200px]]
|Siltstone
|Clastic
|-
|[[File:ShaleUSGOV.jpg|200px]]
|Shale
|Clastic
|-
|[[File:Mongol rock salt Edit.jpg|200px]]
|Rock Salt
|Chemical precipitate
|-
|[[File:Baryte-247862.jpg|200px]]
|Rock Gypsum
|Chemical precipitate
|-
|[[File:Dolostone.jpg|200px]]
|Dolostone
|Chemical precipitate
|-
|[[File:DachsteinkalkBivalvia.jpg|200px]]
|Limestone
|Bioclastic (sediments from organic materials, or plant or animal remains)
|-
|[[File:Coal bituminous.jpg|200px]]
|Coal
|Organic
|}

Note from the pictures in the table that clastic sedimentary rocks vary in the size of their sediments. Both conglomerate and breccia are made of individual stones that have been cemented together. In conglomerate, the stones are rounded; in breccia, the stones are angular around the edges. Sandstone is made of smaller, mostly sand-sized particles cemented together. Siltstone is made mostly of silt, particles that are smaller than sand but larger than clay. Shales have the smallest grain size, being made mostly of clay-sized particles and hardened mud.

==Lesson Summary==
* Weathering and erosion produce sediments. Once these sediments are deposited, they can become sedimentary rocks.
* Sediments must be compacted and cemented to make sedimentary rock. This process is called lithification.

==Review Questions==
# What are three things that the sediments in sedimentary rocks may be made of?
# If you see a sedimentary rock outcrop and red layers of sand are on top of pale layers of sand, what do you know for sure about the ages of the two layers?
# Why do sedimentary rocks have layers of different colors sometimes?
# Describe the two processes necessary for sediments to harden into rock.
# What type of sedimentary rock is coal?
# Think back to the story at the start of the lesson about why the White House originally was white. Why do you think sandstone would be a particularly porous rock?

==Vocabulary==
; cementation
: Occurs when substances harden (crystallize) in the spaces between loose sediments.
; lithification
:  The hardening of layers of loose sediment into rock.
; organic
: Made from materials that were once living things.
; outcrop
: Large rock formation at the surface of the Earth.
; precipitate
: The solid materials left behind after a liquid evaporates.
; compaction
: Occurs when sediments are hardened by being squeezed together by the weight of layers on top of them.
; Weathering 
The process of wearing or being worn by long exposure to the atmosphere.
;Erosion
The geological process in which earthen materials are worn away and transported by natural forces such as wind or water

==Points to Consider==
* If you were interested in learning about Earth's history, which type of rocks would give you the most information?
* Could a younger layer of sedimentary rock ever be found under an older layer? How do you think this could happen?
* Could a sedimentary rock form only by compaction from intense pressure?


{{chapnav|Igneous Rocks|Metamorphic Rocks}}</text>
      <sha1>4lb3yahkhsvylu5vahfta4gdhumbk60</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/User/Applications</title>
    <ns>0</ns>
    <id>237399</id>
    <revision>
      <id>4678490</id>
      <parentid>4678384</parentid>
      <timestamp>2026-10-27T14:10:45Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4678490</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="244151" sha1="6bxp1ug5u7wng8jk3aosdf4momppz86" xml:space="preserve">
==Introduction==


[[#Graphical Image Editing Art]]
[[#Office Application]]
[[#Audio]]

[[#Misc Application]]
[[#Games &amp; Emulation]]

[[#Application Guides]]

[[#top|...to the top]]


[[#top|...to the top]]

Most apps can be opened on the Workbench (aka publicscreen pubscreen) which is the default display option but can offer a custom one set to your configurations (aka custom screen mode promotion). These custom ones tend to stack so the possible use of A-M/A-N method of switching between full screens and the ability to pull down screens as well 

If you are interested in creating or porting new software, see [http://en.wikibooks.org/wiki/Aros/Developer/Docs here]

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Internet Applications 
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Web Online Browser [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser Amelinium], Odyssey 2.0, [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1175&amp;highlight=odyssey&amp;rowstart=100 Odyssey 3.0], [], 
|&lt;!--Amiga OS--&gt;[https://juen.in/ Amelinium], [https://blog.alb42.de/programs/amifox/ amifox] with [https://github.com/alb42/wrp wrp server], IBrowse*, [https://github.com/zapek/Voyager Voyager], [https://github.com/reinauer/Voyager Voyager fork GCC] [https://github.com/amigazen/aweb3/ AWeb 3.6 src], [https://github.com/matjam/aweb AWeb Src], [http://aminet.net/package/comm/www/NetSurf-m68k-sources Netsurf], [], 
|&lt;!--AmigaOS4--&gt;[ Odyssey OWB], [ Timberwolf (Firefox port 2011)], [http://amigaworld.net/modules/newbb/viewtopic.php?forum=32&amp;topic_id=32847 OWB-mui], [http://strohmayer.org/owb/ OWB-Reaction], IBrowse*, [http://os4depot.net/index.php?function=showfile&amp;file=network/browser/aweb.lha AWeb], Voyager, [http://www.os4depot.net/index.php?function=browse&amp;cat=network/browser Netsurf], 
|&lt;!--MorphOS--&gt;Wayfarer, [http://fabportnawak.free.fr/owb/ Odyssey OWB], [ Netsurf], IBrowse*, AWeb, [], 
|-
|&lt;!--Sub Menu--&gt;Downloading videos and/or audio [https://github.com/yt-dlp/yt-dlp yt-dlp], [https://clipgrab.org/ clipgrab],  
|&lt;!--AROS--&gt;[], [https://blog.alb42.de/amitube/ Amitube], 
|&lt;!--Amiga OS--&gt;[https://blog.alb42.de/amitube/ Amitube], [ smtube], 
|&lt;!--AmigaOS4--&gt;[https://blog.alb42.de/amitube/ Amitube], getVideo, 
|&lt;!--MorphOS--&gt;[ ytsearch], [https://blog.alb42.de/amitube/ Amitube], [ getVideo], Tubexx 
|-
|&lt;!--Sub Menu--&gt;E-mailing SMTP POP3 IMAP based 
|&lt;!--AROS--&gt;Emailinium, [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/email SimpleMail], [http://sourceforge.net/projects/simplemail/files/ src], [https://github.com/jens-maus/yam YAM] 
|&lt;!--Amiga OS--&gt;Emailinium, [http://sourceforge.net/projects/simplemail/files/ SimpleMail], [https://github.com/jens-maus/yam YAM]
|&lt;!--AmigaOS4--&gt;SimpleMail, YAM, 
|&lt;!--MorphOS--&gt; SimpleMail, YAM, 
|-
|&lt;!--Sub Menu--&gt;Internet Chat IRC, ICB, 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat WookieChat], [https://sourceforge.net/projects/wookiechat/ Wookiechat src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat AiRcOS], Jabberwocky, 
|&lt;!--Amiga OS--&gt;[https://github.com/charabaruk/WookieChat Wookiechat], AmIRC 
|&lt;!--AmigaOS4--&gt;Wookiechat 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Wookiechat], [ AmIRC], 
|-
|&lt;!--Sub Menu--&gt;Instant Messaging IM like [https://github.com/BlitterStudio/amidon Hollywood lang based Mastodon client], BlueSky AT protocol, Facebook(TM), Twitter X (TM), Bitlbee IRC Gateway and others 
|&lt;!--AROS--&gt;[https://github.com/kaffeine1/telegram-amiga telegram-amiga], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat jabberwocky], 
|&lt;!--Amiga OS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], CLIMM, SabreMSN, [https://sourceforge.net/projects/ajabberwocky/ jabberwocky], 
|&lt;!--AmigaOS4--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], SabreMSN,
|&lt;!--MorphOS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 PolyglotNG], SabreMSN,
|-
|&lt;!--Sub Menu--&gt;Torrents 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/p2p ArTorr], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;CTorrent, Transmission 
|&lt;!--MorphOS--&gt;MLDonkey, Beehive, [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Transmission], CTorrent, 
|-
|&lt;!--Sub Menu--&gt;FTP 
|&lt;!--AROS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], MarranoFTP, [https://aminet.net/package/comm/tcp/wput-0.3.4c.i386-aros wput i386 c src]
|&lt;!--Amiga OS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://aminet.net/package/comm/tcp/AmiFTP AmiFTP], AmiTradeCenter, ncFTP, [https://aminet.net/package/comm/tcp/sana2-tftpclient sana2 tftpclient c src]
|&lt;!--AmigaOS4--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|&lt;!--MorphOS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Pftp], [http://aminet.net/package/comm/tcp/AmiFTP-1.935-OS4 AmiFTP], 
|-
|&lt;!--Sub Menu--&gt;WYSIWYG Web Site Editor
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Internet Radio Streaming Audio [http://www.gnu.org/software/gnump3d/ gnump3d], [http://www.icecast.org/ Icecast2] Server (Broadcast) and Client (Listen), [ mpd], [http://darkice.sourceforge.net/ DarkIce], [http://www.dyne.org/software/muse/ Muse], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc], Mplayer (Icecast Client only), 
|&lt;!--Amiga OS--&gt;[https://github.com/sandlbn/TuneFinder TuneFinder C Src], [https://github.com/sandlbn/TuneFinderMUI TuneFinderMUI], [http://amigazeux.net/anr/ AmiNetRadio], [https://github.com/boingball/MintAMP MintAMP], [], 
|&lt;!--AmigaOS4--&gt;[http://www.tunenet.co.uk/ Tunenet], 
|&lt;!--MorphOS--&gt;Mplayer, AmiNetRadio, 
|-
|&lt;!--Sub Menu--&gt;VoIP (Voice over IP) with SIP Client (Session Initiation Protocol) or Asterisk IAX2 Clients Softphone (skype like) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;AmiPhone with Speak Freely, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Weather Forecast 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ WeatherBar], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench AWeather], []
|&lt;!--Amiga OS--&gt;[http://amigazeux.net/wetter/ Wetter], [https://github.com/emartisoft/AmiWeatherForecasts AmiWeatherForecasts src], 
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/?function=showfile&amp;file=utility/workbench/flipclock.lha FlipClock], 
|&lt;!--MorphOS--&gt;[http://amigazeux.net/wetter/ Wetter], 
|-
|&lt;!--Sub Menu--&gt;Street Road Maps Route Planning GPS Tracking  
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/muimapparium/ MuiMapparium] [https://build.alb42.de/ Build of MuiMapp versions], 
|&lt;!--Amiga OS--&gt;AmiAtlas*, UKRoutePlus*, [http://blog.alb42.de/ AmOSM], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://blog.alb42.de/programs/mapparium/ Mapparium], 
|-
|&lt;!--Sub Menu--&gt;Clock and Date setting from the internet by network time protocol (NTP) [https://www.timeanddate.com/worldclock/ World Clock], [http://www.time.gov/ old standard NIST Internet Time Servers], 
|&lt;!--AROS--&gt;[https://github.com/bohunamiga/PiNTP PiNTP], [https://archives.arosworld.org/?function=showfile&amp;file=utility/workbench/amitimekeeper.i386-aros.lha amitimekeeper with c src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc ntpsync], [], 
|&lt;!--Amiga OS--&gt;ntpsync, [http://aminet.net/package/util/cdity/AmiTimeKeeper amitimekeeper], [http://aminet.net/comm/misc/netclock netclock], [https://aminet.net/package/comm/net/sntp sntp], [http://aminet.net/package/util/time/ScreenTime ScreenTime], [https://github.com/reinauer/SyncTime SyncTime], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Newsgroups
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[http://newscoaster.sourceforge.net/ Newscoaster], [https://github.com/jens-maus/newsrog NewsRog], [ WorldNews], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;RSS 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/Team-Boingo/AmiRSS AmiRSS src]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;AI
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/murinsel/AmigaAI Claude], [https://github.com/geekychris/amiga_mcp AI on host machine], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;BBS
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Graphical Image Editing Art==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Image Editing
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Pixel Raster Artwork [https://github.com/LibreSprite/LibreSprite LibreSprite based on GPL aseprite], [https://github.com/abetusk/hsvhero hsvhero], [], 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/ZunePaint/ ZunePaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit LunaPaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit GrafX2], [ LodePaint needs OpenGL], 
|&lt;!--Amiga OS--&gt;[http://www.amigaforever.com/classic/download.html PPaint], GrafX2, [https://github.com/grovdata/Amiga_Sources/blob/master/software.md DeluxePaint], [http://www.amiforce.de/perfectpaint/perfectpaint.php PerfectPaint], Zoetrope, Brilliance2*, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit LodePaint], GrafX2, 
|&lt;!--MorphOS--&gt;Sketch, Pixel*, GrafX2, [http://morphos.lukysoft.cz/en/vypis.php?kat=3 LunaPaint]
|-
|&lt;!--Sub Menu--&gt;Image viewing 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LookHere], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LoView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer PicShow] , [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--Amiga OS--&gt;PicShow, PicView, Photoalbum,
|&lt;!--AmigaOS4--&gt;WarpView, PicShow, flPhoto, Thumbs, [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album]
|-
|&lt;!--Sub Menu--&gt;Photography retouching / Image Manipulation like Photoshop(tm)  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOEffects], 
|&lt;!--Amiga OS--&gt;[ Tecsoft Video Paint aka TVPaint], Photogenics*, ArtEffect*, ImageFX*, XiPaint, fxPaint, ImageMasterRT, Opalpaint, 
|&lt;!--AmigaOS4--&gt;WarpView, flPhoto, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit Photocrop]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], ImageFX*, 
|-
|&lt;!--Sub Menu--&gt;Manage RAW picture folder galleries like Darktable, RAWtherapy, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Graphic Format Converter - ICC profile support sRGB, Adobe RGB, XYZ and linear RGB 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;GraphicsConverter, ImageStudio, [http://www.coplabs.org/artpro.html ArtPro]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Thumbnail Generator [], 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/shell Thumbnail Generator]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Icon Editor
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/iconedit Archives], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench Icon Toolbox], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/iconedit IconEditor]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Pixel Art Animation 
|&lt;!--AROS--&gt;Lunapaint
|&lt;!--Amiga OS--&gt;PPaint, AnimatED, Scala*, GoldDisk MovieSetter*, Walt Disney's Animation Studio*, ProDAD*, [https://github.com/historicalsource/DeluxePaint DeluxePaint src], Brilliance
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 Titler] 
|-
|&lt;!--Sub Menu--&gt;2D SVG based MovieSetter type [https://github.com/Flare-Animate/Flare Flare Animate] 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;MovieSetter*, Fantavision*
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Morphing 
|&lt;!--AROS--&gt;[ GLMorph]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Cad (qcad-&gt;LibreCAD, etc.) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Xcad, MaxonCAD
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Cad like FreeCad, BRL-CAD, OpenSCAD, AvoCADo, [https://github.com/ingelibre/ingetrazo ingetrazo] etc. using dxf, obj (vertices), blend, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;XCad3d*, DynaCADD*, [https://aminet.net/package/gfx/3d/Cycas178_EN Cycas]*, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Model Rendering of glft (json) gbl (png jpg), usdz (USD files with materials, textures, and animations), FBX Filmbox is a proprietary Autodesk format, 
|&lt;!--AROS--&gt;POV-Ray
|&lt;!--Amiga OS--&gt;[http://www.discreetfx.com./amigaproducts.html CINEMA 4D]*, POV-Ray, [https://eab.abime.net/showthread.php?t=123609 Lightwave3D RTG]*, Real3D*, Caligari24*, Reflections/Monzoom*, [https://github.com/privatosan/RayStorm Raystorm src], Tornado 3D, [https://github.com/AlphaPixel/Eric-Graham-1987-Juggler-Raytracer-1.0 Eric-Graham-1987-Juggler-Raytracer-1.0]
|&lt;!--AmigaOS4--&gt;Blender, POV-Ray, Yafray
|&lt;!--MorphOS--&gt;Blender, POV-Ray, Yafray
|-
|&lt;!--Sub Menu--&gt;3D Format Converter [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=graphics/convert/ 3doc.i386-aros], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=showfile&amp;file=graphics/convert/ivcon.lha IVCon]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen grabbing display 
|&lt;!--AROS--&gt;[ Screengrabber], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc snapit], [http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record screen recorder], []
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Grab graphics music from apps [https://github.com/Malvineous/ripper6 ripper6], [],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Manage metadata of images [https://github.com/exiv2/exiv2 exiv2], [ EXIF/IPTC/XMP metadata manipulation], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Office Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Office
!width:10%;|AROS (x86)
!width:10%;|[http://en.wikipedia.org/wiki/Amiga_software Commodore-Amiga OS 3.1] (68k)
!width:10%;|[http://en.wikipedia.org/wiki/AmigaOS_4 Hyperion OS4] (PPC)
!width:10%;|[http://en.wikipedia.org/wiki/MorphOS MorphOS] (PPC)
|-
|&lt;!--Sub Menu--&gt;Office Suite 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[ Softwood Final Office], [ Wordworth Office], [ Digita Office],  [ The Works!], [ Europress Mini Office], [], [ Papyrus Office Demo], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[ Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Word-processing 
|&lt;!--AROS--&gt;[https://finalwriter.godaddysites.com/ Final Writer 7*], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1995&amp;rowstart=20&amp;pid=12668#post_12668 Slovo], [https://github.com/sodero/MUI-Vim/releases MUI-Vim], [https://archives.arosworld.org/index.php?function=browse&amp;cat=office/wordprocessing Cinnamon Writer], [], 
|&lt;!--AmigaOS--&gt;[ Softwood FinalCopy II*], Haage AmigaWriter*, Digita WordWorth*, Softwood FinalWriter*, Micro-Systems Excellence 3*, Arnor Protext, Rashumon, [ InterWord], [ KindWords], [WordPerfect], [ New Horizons Flow], [ CygnusEd Pro], [ Micro-systems Scribble], 
|&lt;!--AmigaOS4--&gt;AbiWord, [ CinnamonWriter], 
|&lt;!--MorphOS--&gt;[ Cinnamon Writer], [http://www.meta-morphos.org/viewtopic.php?topic=1246&amp;forum=53 scriba], [http://morphos.lukysoft.cz/en/index.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Spreadsheets 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/leu/ Leu], [https://archives.arosworld.org/index.php?function=browse&amp;cat=office/spreadsheet ], 
|&lt;!--AmigaOS--&gt;[https://aminet.net/package/biz/spread/ignition-src Ignition Src 1.3], [MaxiPlan 500 Plus], [OXXI Plan/IT v2.0 Speadsheet], [ Superplan], [ Creative Developments TurboCalc], [ ProCalc], [ InterSpread], [Digita DGCalc], [ Gold Disk Advantage], [ Micro-systems Analyze!]
|&lt;!--AmigaOS4--&gt;Gnumeric, [https://ignition-amiga.sourceforge.net/ Ignition], 
|&lt;!--MorphOS--&gt;[ ignition], [http://morphos.lukysoft.cz/en/vypis.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Presentations
|&lt;!--AROS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, 
|&lt;!--Amiga OS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, [https://github.com/evaneykelen/mediapoint-amiga MediaPoint C and asm], PointRider, Scala*, 
|&lt;!--Amiga OS4--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider 
|&lt;!--MorphOS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider
|-
|&lt;!--Sub Menu--&gt;Databases 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=office/database BeeBase], 
|&lt;!--Amiga OS--&gt;Precision Superbase 4 Pro*, Arnor Prodata*, [https://sourceforge.net/projects/beebase/ BeeBase], Datastore, FinalData*, AmigaBase, Fiasco, Twist2*, [Digita DGBase], [], 
|&lt;!--AmigaOS4--&gt;BeeBase, SQLite, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=6 BeeBase], 
|-
|&lt;!--Sub Menu--&gt;PDF Viewing, editing and digital signatures 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/aros-foliopdf folio version of mupdf], [http://sourceforge.net/projects/arospdf/ ArosPDF via splash xpdf], [https://github.com/wattoc/AROS-vpdf vpdf], 
|&lt;!--Amiga OS--&gt;APDF 
|&lt;!--AmigaOS4--&gt;AmiPDF 
|&lt;!--MorphOS--&gt;APDF, vPDF, 
|-
|&lt;!--Sub Menu--&gt;Note Taking markdown support like Obsidian like, joplin, OneNote, EverNotes, xournalpp, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/text/edit/Kickdown c src with reaction gui], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Study and analyse, collect, organize, annotate, cite, and share
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PIM Personal Information Manager - Day Diary Planner Calendar App Filofax like 
|&lt;!--AROS--&gt;[ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;Digita Organiser*, On The Ball, Everyday Organiser, [ Contact Manager], 
|&lt;!--AmigaOS4--&gt;AOrganiser, 
|&lt;!--MorphOS--&gt;[http://polymere.free.fr/orga_en.html PolyOrga], 
|-
|&lt;!--Sub Menu--&gt;Accounting
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=office/misc ETB], LoanCalc, [ ], [ ], [ ], 
|[ Digita Home Accounts2], Accountant, Small Business Accounts, Account Master, [ Amigabok], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Project Management Research 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;SuperGantt, SuperPlan, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Desktop 
|&lt;!--AROS--&gt;Wanderer, Scalos, Workbook, DOpus5, 
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[https://github.com/zapek/Ambient Ambient Src]
|-
|&lt;!--Sub Menu--&gt;System Wide Search 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool Finder], [], [], 
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Dictionary - multilingual [http://sourceforge.net/projects/babiloo/ Babiloo], [http://code.google.com/p/stardict-3/ StarDict], 
|&lt;!--AROS--&gt;[ ],  
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System wide Thesaurus - multi lingual
|&lt;!--AROS--&gt;[ ], 
|Kuma K-Roget*, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Sticky Desktop Notes (post it type) 
|&lt;!--AROS--&gt;[http://aminet.net/package/util/wb/amimemos.i386-aros AmiMemos], [https://aminet.net/package/util/wb/amimemos.src-aros AmiMemos Src], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/util/wb/StickIt-2.00 StickIt v2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DTP Desktop Publishing 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOPublisher], 
|&lt;!--Amiga OS--&gt;[http://pagestream.org/ Pagestream]*, Professional Pro Page*, Saxon Publisher, Pagesetter, PenPal, 
|&lt;!--AmigaOS4--&gt;[http://pagestream.org/ Pagestream]* 
|&lt;!--MorphOS--&gt;[http://pagestream.org/ Pagestream]* 
|-
|&lt;!--Sub Menu--&gt;Printing 
|&lt;!--AROS--&gt;Postscript 3 laser printers, [https://github.com/bohunamiga/MintPRINT MintPRINT AirPrint IPP], [ Ghostscript], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/boingball/MintPRINT MintPRINT IPP], [https://github.com/Andiweli/AmiAirprint AmiAirprint], [http://www.irseesoft.de/tp_what.htm TurboPrint]*, [ GutenPrint], [https://aminet.net/package/comm/tcp/NetPrinter NetPrinter LPR], [], [], 
|&lt;!--AmigaOS4--&gt;(some native drivers), 
|&lt;!--MorphOS--&gt;early TurboPrint included, [https://aminet.net/package/comm/tcp/NetPrinter NetPrinter LPR], 
|-
|&lt;!--Sub Menu--&gt;Scanning 
|&lt;!--AROS--&gt;[ SCANdal], [], 
|&lt;!--Amiga OS--&gt;FxScan*, ScanQuix*, [https://github.com/boingball/MintSCAN MintSCAN], 
|&lt;!--AmigaOS4--&gt;SCANdal (Sane)
|&lt;!--MorphOS--&gt;SCANdal
|-
|&lt;!--Sub Menu--&gt;OCR
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/convert gOCR] 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos-files.net/categories/office/text Tesseract] 
|-
|&lt;!--Sub Menu--&gt;Text Editing
|&lt;!--AROS--&gt;Jano Editor (already installed as Editor), [http://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit EdiSyn], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit Annotate], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Vim], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd] [https://github.com/vidarh/FrexxEd src], [ NoWinEd], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/text/edit/TurboText20 TurboText20 ttx], Annotate, MicroGoldED/CubicIDE*, CygnusED*, Protext*, NoWinED, 
|&lt;!--AmigaOS4--&gt;Notepad, Annotate, CygnusED*, NoWinED, 
|&lt;!--MorphOS--&gt;MorphOS ED, NoWinED, GoldED/CubicIDE*, CygnusED*, Annotate, 
|-
|&lt;!--Sub Menu--&gt;Office Fonts [http://sourceforge.net/projects/fontforge/files/fontforge-source/ Font Designer] 
|&lt;!--AROS--&gt;[ ], [ ], 
|&lt;!--Amiga OS--&gt;TypeSmith*, SaxonScript (GetFont Adobe Type 1), 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Drawing Vector
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/amifig/ ZuneFIG previously AmiFIG], [https://github.com/serk118/designworks-aros designworks aros 64bit]
|&lt;!--Amiga OS--&gt;Drawstudio*, ProVector*, ArtExpression*, Professional Draw*, AmiFIG, MetaView, [https://gitlab.com/amigasourcecodepreservation/designworks Design Works Src], [], 
|&lt;!--AmigaOS4--&gt;MindSpace, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit amifig], 
|&lt;!--MorphOS--&gt;SteamDraw, [http://aminet.net/package/gfx/edit/amifig amiFIG], 
|-
|&lt;!--Sub Menu--&gt;video conferencing (jitsi) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;source code hosting
|&lt;!--AROS--&gt;Gitlab, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (server)
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/VNC_Server ArosVNCServer], 
|&lt;!--Amiga OS--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC], [http://dspach.free.fr/amiga/avnc/index.html AVNC]
|&lt;!--AmigaOS4--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC] 
|MorphVNC, vncserver
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (client) login and connect to another machine 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/VNC_Client/ ArosVNC], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc rdesktop], 
|&lt;!--Amiga OS--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://dspach.free.fr/amiga/vva/index.html VVA], [http://www.hd-zone.com/ RDesktop]
|&lt;!--AmigaOS4--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|-
|&lt;!--Sub Menu--&gt;notifications 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Ranchero 
|&lt;!--AmigaOS4--&gt;Ringhio 
|&lt;!--MorphOS--&gt;MagicBeacon 
|-
|&lt;!--Sub Menu--&gt;Biometric facial logins and fingerprint security features 
|&lt;!--AROS--&gt;Bebbossh, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Fido U2F (Universal 2nd Factor) and later FIDO2 (W3C WebAuthn with CTAP2) key authorization like Yubico YubiKey, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Audio==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Audio
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing playback Audio like MP3, [https://github.com/chrg127/gmplayer NSF], [https://github.com/kode54/lazyusf miniusf .usflib] [https://gitlab.com/kode54/psflib with pfslib], [], [], etc 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer], [ HarmonyPlayer hp], [http://www.a500.org/downloads/audio/index.xhtml playcdda] CDs, [ WildMidi Player], [https://bszili.morphos.me/ UADE mod player], [], [ RNOTunes], [ mp3Player], [], 
|&lt;!--Amiga OS--&gt;AmiNetRadio, AmigaAmp, playOGG, [https://codeberg.org/tygre/amimodradio amimodradio]
|&lt;!--AmigaOS4--&gt;TuneNet, SimplePlay, AmigaAmp, TKPlayer
|AmiNetRadio, Mplayer, Kaya, AmigaAmp
|-
|&lt;!--Sub Menu--&gt;Editing Audio 
|&lt;!--AROS--&gt;[ Audio Evolution 4] 
|&lt;!--Amiga OS--&gt;[https://sourceforge.net/projects/hd-rec/ HD-Rec Src], [http://www.sonicpulse.de/eng/news.html SoundFX], [ Samplitude], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/projects/hd-rec/ HD-Rec], AmiSoundED, [http://os4depot.net/?function=showfile&amp;file=audio/record/audioevolution4.lha Audio Evolution 4] 
|[http://www.hd-rec.de/HD-Rec/index.php?site=home HD-Rec], 
|-
|&lt;!--Sub Menu--&gt;Editing Tracker Music
|&lt;!--AROS--&gt;[https://github.com/hitchhikr/protrekkr Protrekkr], [ Schism Tracker], [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/tracker MilkyTracker], [http://www.hivelytracker.com/ HivelyTracker], [ Radium in AROS already],  [http://www.a500.org/downloads/development/index.xhtml libMikMod], 
|&lt;!--Amiga OS--&gt;MilkyTracker, HivelyTracker, DigiBooster, Octamed SoundStudio, [https://github.com/elindstrom/soundtracker soundtracker], 
|&lt;!--AmigaOS4--&gt;MilkyTracker, HivelyTracker, GoatTracker
|MilkyTracker, GoatTracker, DigiBooster, 
|-
|&lt;!--Sub Menu--&gt;Editing Music [], [https://github.com/kmatheussen/camd CAMD] and/or staves and musical notes on manuscript [https://github.com/ratchov/midish midish] midi sequencer 
|&lt;!--AROS--&gt;[http://bnp.hansfaust.de/ Bars and Pipes], [], [], 
|&lt;!--Amiga OS--&gt;[http://bnp.hansfaust.de/ Bars'n'Pipes], MusicX* David &quot;Talin&quot; Joiner &amp; Craig Weeks (for Notator-X), Deluxe Music Construction Set DMCS2*, [https://github.com/timoinutilis/midi-sequencer-amigaos Horny c Src] [https://github.com/kas1e/midi-sequencer-amigaos/tree/master/HornyGCC HornyGCC OS4 src] [https://github.com/capehill/midi-sequencer-amigaos Horny OS4 fork src] [https://www.amigans.net/modules/newbb/viewtopic.php?start=0&amp;topic_id=8143&amp;order=ASC&amp;status=&amp;mode=0 OS4 thread], HD-Rec, [https://aminet.net/package/mus/midi/dominatorV1_51 Dominator], [https://github.com/royaltm/Amiga-midiIn Amiga-midiIn], [ Aegis Sonix 2.0]
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Rockbeat, [http://bnp.hansfaust.de/download.html Bars'n'Pipes], [https://github.com/gooofy/freeaction Horny OS4 src fork], Audio Evolution 4, 
|&lt;!--MorphOS--&gt;Bars'n'Pipes, 
|-
|&lt;!--Sub Menu--&gt;Sound Sampling 
|&lt;!--AROS--&gt;[ Advanced AHI Recorder all], [https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/record Audio Evolution 4], [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;did=162 Quick Record], [https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc SOX to get AIFF 16bit files], [https://github.com/aros-development-team/AROS/tree/master/workbench/tools/AHIRecord AHIRecord], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/mus/edit/AudioEvolution3_src Audio Evolution 3 c src], [ Samplitude]*, Audiomaster IV*, 
|&lt;!--AmigaOS4--&gt;[https://github.com/timoinutilis/phonolith-amigaos phonolith c src], HD-Rec, Audio Evolution 4,
|&lt;!--MorphOS--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Audio Evolution 4,
|-
|&lt;!--Sub Menu--&gt;Audio Processing like easyeffects so having limiter, compressor, convolver, equalizer and auto volume and many other plugins 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Live Looping or Audio Misc - Groovebox like
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;CD/DVD burn
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=utility IsoTools], [https://code.google.com/p/amiga-fryingpan/ FryingPan], 
|&lt;!--Amiga OS--&gt;FryingPan, [ MakeCD], 
|&lt;!--AmigaOS4--&gt;FryingPan, AmiDVD, 
|&lt;!--MorphOS--&gt;[http://www.amiga.org/forums/printthread.php?t=58736 FryingPan], Jalopeano, 
|-
|&lt;!--Sub Menu--&gt;CD/DVD audio rip
|&lt;!--AROS--&gt;Lame, [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;cfid=0&amp;did=167 Quick CDrip],
|&lt;!--Amiga OS--&gt;Lame,  
|&lt;!--AmigaOS4--&gt;Lame, 
|&lt;!--MorphOS--&gt;Lame,  
|-
|&lt;!--Sub Menu--&gt;MP3 v1 and v2 Tagger
|&lt;!--AROS--&gt;id3ren (v1), [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/edit mp3info], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|
|-
|&lt;!--Sub Menu--&gt;Audio Convert
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc Sox], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/mus/misc/SoundBox SoundBox], [http://aminet.net/package/mus/misc/SoundBoxKey SoundBox Key], [http://aminet.net/package/mus/edit/SampleE SampleE], sox 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DJ mixing jamming 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/djh0ffman/PT1210 Hoffman PT1210 DJ tracker], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Radio Automation Software [http://www.rivendellaudio.org/ Rivendell], [http://code.campware.org/projects/livesupport/report/3 Campware LiveSupport], [http://www.sourcefabric.org/en/airtime/ SourceFabric AirTime], [http://www.ohloh.net/p/mediabox404 MediaBox404], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speakers Audio Sonos Mains AC networked wired controlled 
*2005 ZP100 with ZP80 
*2008 Zoneplayer ZP120 (multi-room wireless amp)  ZP90 receiver only with CR100 controller, 
*2009 ZonePlayer S5, 
*2010 BR100 wireless Bridge (no support),   
*2011 Play:3
*2013 Bridge (no support), Play:1,  
*2016 Arc,   Play:1,   
*Beam (Gen 2),   Playbar,  Ray,   Era 100,   Era 300,   Roam,   Move 2,   
*Sub (Gen 3),   Sub Mini,  Five,  Amp  S2 
|&lt;!--AROS--&gt;SonosController 
|&lt;!--Amiga OS--&gt;SonosController
|&lt;!--AmigaOS4--&gt;SonosController
|&lt;!--MorphOS--&gt;SonosController
|-
|&lt;!--Sub Menu--&gt;Smart Speakers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Video Creativity and Production==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Video
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing Video 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer], [ VAMP], [http://www.a500.org/downloads/video/index.xhtml CDXL player], [http://www.a500.org/downloads/video/index.xhtml IffAnimPlay], [], 
|&lt;!--Amiga OS--&gt;Frogger*, AMP2, MPlayer, RiVA*, MooViD*, 
|&lt;!--AmigaOS4--&gt;DvPlayer, MPlayer 
|&lt;!--MorphOS--&gt;MPlayer, Frogger, AMP2, VLC 
|-
|&lt;!--Sub Menu--&gt;Streaming Video and game streaming like OBS studio, Parsec, [https://github.com/lizardbyte/sunshine sunshine], [https://github.com/moonlight-stream/moonlight-qt moonlight], etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Playing DVD 
|&lt;!--AROS--&gt;[http://a-mc.biz/ AMC]*, Mplayer 
|&lt;!--Amiga OS--&gt;AMP2, Frogger 
|&lt;!--AmigaOS4--&gt;[http://a-mc.biz/ AMC]*, DvPlayer*, AMP2,  
|&lt;!--MorphOS--&gt;Mplayer 
|-
|&lt;!--Sub Menu--&gt;Screen Recording
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record Screenrecorder], [ ], [ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Screenrecorder, 
|-
|&lt;!--Sub Menu--&gt;Create Edit Individual Video - Amiga like OSs have no pro NLE 
|&lt;!--AROS--&gt;[ Mencoder], [ Quick Videos], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit AVIbuild], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc FrameBuild], FFMPEG, 
|&lt;!--Amiga OS--&gt;[ MainConcept Mainactor Broadcast*], [http://en.wikipedia.org/wiki/Video_Toaster Video Toaster*] with [https://discreetfx.com/openvideotoaster.html some c src], MacroSystem MovieShop 4.3*, proDAD Adorage*, [ IOSpirit VHI studio]*, [Gold Disk ShowMaker], [], 
|&lt;!--AmigaOS4--&gt;FFMpeg/GUI 
|&lt;!--MorphOS--&gt;Blender, Mencoder, FFmpeg
|-
|&lt;!--Sub Menu--&gt;Subtitle editor 
|&lt;!--AROS--&gt;[https://aminet.net/package/text/edit/Slarti_Arosx86ABIv0 Slarti_Arosx86ABIv0], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;IP-based video production workflows with High Dynamic Range (HDR), 10-bit color collaborative NDI, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Blogging like Lemmy or kbin
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR face recognition for Vtubers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting Live2D models with Cubism type editor or [https://github.com/AyagamiDev/ayagami ayagami] like with zipped moc3 with model metadata (model3, cdi3) 
&lt;pre&gt;
Model data (cmo3)
Basic motions (can3)
Background image (png)
Set of files for embedding (runtime folder)
• Model data (moc3)
• Motion data (motion3.json)
• Model settings file (model3.json)
• Physics settings file (physics3.json)
• Display auxiliary file (cdi3.json)
&lt;/pre&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting chatters .VRML models - standardized 3D file format for VR avatars 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;V-tubers V-tubing like Vseeface with Openseeface tracker or Vpuppr (virtual puppet project) for online live 2d / 3d art models rigging rigged LIV 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]


==Misc Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;File Management 
|&lt;!--AROS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 DOpus Magellan aka DOpus 5], [ Scalos], [ FileMaster], 
|&lt;!--Amiga OS--&gt;DOpus2, DOpus 4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], ClassAction, FileMaster, DirWork 2*, [https://github.com/RudolphRiedel/DiskMaster2 DiskMaster2 src], 
|&lt;!--AmigaOS4--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], Filer, AmiDisk 
|&lt;!--MorphOS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|-
|&lt;!--Sub Menu--&gt;Package Application Installer 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak?tab=repositories Pkg manager], [https://aros-pkg.azurewebsites.net/search?arch=x86_64 Pkg], [ InstallerNG], 
|&lt;!--Amiga OS--&gt;InstallerNG, Grunch, 
|&lt;!--AmigaOS4--&gt;Jack
|&lt;!--MorphOS--&gt;Jack 
|-
|&lt;!--Sub Menu--&gt;Compression archiver [https://github.com/FS-make-simple/paq9a paq9a], [], 
|&lt;!--AROS--&gt;XAD system is a toolkit designed for handling various file and disk archiver
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[https://aminet.net/package/util/pack/decrunchmania_os4 Crunchmania CrM2 depacker], 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Binary Hexadecimal Editor 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Zaphod], [],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Partition Editor formatter Disk Management
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1440&amp;highlight=partition&amp;pid=8821#post_8821 QuickPart], [ HDToolBox]
|&lt;!--Amiga OS--&gt;[https://github.com/stefanskotte/hdpart hdpart], [https://github.com/ChuckyGang/AmiPart AmiPart], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Repair and backups 
|&lt;!--AROS--&gt;ArSFSDoctor, 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/disk/bakup/quarterback_src Quarterback Tools C and asm src], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Disk check, integrity and history [https://github.com/smartmontools/smartmontools smart tools], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;File Verification / Repair 
|&lt;!--AROS--&gt;[https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=utility md5sum], [https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=utility/filetool asum], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool workpar2] (PAR2),  [http://zakalwe.fi/~shd/foss/cksfv/files/ compile cksfv from website], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Par2, 
|-
|&lt;!--Sub Menu--&gt;Multiple File renaming
|&lt;!--AROS--&gt;DOpus 4 or 5, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Anti Virus
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;VChecker, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Random Wallpaper Desktop changer [ DOpus5], [ Scalos],  
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Alarm Clock, Timer, Stopwatch, Countdown 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench DClock], [http://aminet.net/util/time/AlarmClockAROS.lha AlarmClock], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Edge snap window tool 
|&lt;!--AROS--&gt;[https://github.com/kaffeine1/edgesnap edgesnap]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}


==Misc Application 2==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;C/C++ IDE Integrated Development 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/aidea/ AIDEa], [ Murks], [],  
|&lt;!--Amiga OS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, [ StormC], [https://github.com/jens-maus/amide amide], [], 
|&lt;!--AmigaOS4--&gt;CodeBench , [https://gitlab.com/boemann/codecraft CodeCraft], 
|&lt;!--MorphOS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, 
|-
|&lt;!--Sub Menu--&gt;C/C++ Text Editors 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd], [https://github.com/vidarh/FrexxEd FrexxEd src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit Annotate] with [https://www.onyxsoft.se/files/annotate_src.lha src], 
|&lt;!--Amiga OS--&gt;[ Protext], [ CED], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[https://www.onyxsoft.se/annotate.html Annotate], 
|-
|&lt;!--Sub Menu--&gt;Repository
|&lt;!--AROS--&gt;[ Git]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Git
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;BASIC Computer Language 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Basic4SDL], [ Ace Basic], [ X-AMOS], [SDLBasic], [ Alvyn], 
|&lt;!--Amiga OS--&gt;[http://www.amiforce.de/main.php Amiblitz 3] with [https://github.com/AmiBlitz/AmiBlitz3 Asm src], [http://amos.condor.serverpro3.com/AmosProManual/contents/c1.html Amos Pro] with [https://github.com/AmiDARK/AmosProfessionalUnity-Official-Releases Asm src], [http://aminet.net/package/dev/basic/ace24dist ACE Basic], [https://github.com/gooofy/aqb aqb], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;sdlBasic
|-
|&lt;!--Sub Menu--&gt;Computer Languages Translation [https://tetracorp.github.io/guide/reverse-engineering-amiga.html], [https://amigasourcecodepreservation.gitlab.io/amiga-assembler-insider-guide/], [https://github.com/kermitfrog/Amiga-Re-Engineering Rust, Ghidra and FS-UAE], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://bitbucket.org/rhinoid/convert68000toc/src/main/ convert m68k seka asm-one to c], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Gui Creators
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/guitool MuiBuilder], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[ MuiBuilder],  
|-
|&lt;!--Sub Menu--&gt;Catalog .cd .ct Custom App Language Editors 
|&lt;!--AROS--&gt;FlexCat, [https://archives.arosworld.org/index.php?function=browse&amp;cat=utility Flexcat GUI], [], 
|&lt;!--Amiga OS--&gt;[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|&lt;!--AmigaOS4--&gt;[http://aminet.net/package/dev/misc/simplecat SimpleCat], FlexCat
|&lt;!--MorphOS--&gt;[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|-
|&lt;!--Sub Menu--&gt;Cross Development 
|&lt;!--AROS--&gt;[], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/geekychris/amiga_mcp amiga_mcp], [https://github.com/mbergmann-sh/AmigaED4-IDE AmigaED4-IDE], [https://lemonspawn.com/turbo-rascal-syntax-error-expected-but-begin/ Turbo Rascal], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Misc Application 3==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;System 
|&lt;!--AROS--&gt;[ SysExplorer], [ SysMon], [ Scout], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Terminals Shells CLIs 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/limpet limpet], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;OSK On Screen Keyboard
|&lt;!--AROS--&gt;[], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/util/wb/OSK.lha OSK]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Magnifier Magnifying Glass Magnification 
|&lt;!--AROS--&gt;[http://www.onyxsoft.se/files/zoomit.lha ZoomIT], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Comic Book CBR CBZ format reader viewer 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comics], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comicon], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Reader 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#legadon Legadon EPUB],[]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Converter 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Text to Speech tts [https://github.com/JonathanFly/bark-installer Bark], [], 
|&lt;!--AROS--&gt;[ Echo &quot; &quot; &gt;SPEAK:A1 inbuilt], [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc flite], 
|&lt;!--Amiga OS--&gt;[http://www.text2speech.com translator], [https://github.com/sidick/narrator.wyoming narrator.wyoming], [], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=search&amp;tool=simple FLite]
|&lt;!--MorphOS--&gt;[http://se.aminet.net/pub/aminet/mus/misc/ FLite]
|-
|&lt;!--Sub Menu--&gt;Speech Voice Recognition Dictation - [http://sourceforge.net/projects/cmusphinx/files/ CMU Sphinx], [http://julius.sourceforge.jp/en_index.php?q=en/index.html Julius], [http://www.isip.piconepress.com/projects/speech/index.html ISIP], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speech Voice Changer [], [], [], [], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Display Blanker screensaver 
|&lt;!--AROS--&gt;Blanker Commodity (built in), [https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/screenblanker GarshneBlanker], [http://sourceforge.net/projects/gblanker/ GBlanker Src], [], 
|&lt;!--Amiga OS--&gt;MultiCX, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;ModernArt Blanker, 
|-
|&lt;!--Sub Menu--&gt;Fortune Cookie Quotes Sayings 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc AFortune], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}


==Misc Application 4==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Fractals mandelbrot, etc 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc], 
|&lt;!--Amiga OS--&gt;ZoneXplorer, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Landscape Rendering 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/raytrace WCS World Construction Set], 
|&lt;!--Amiga OS--&gt;[ Vista Pro], [http://en.wikipedia.org/wiki/World_Construction_Set World Construction Set]
|&lt;!--AmigaOS4--&gt;[ WCS World Construction Set],
|&lt;!--MorphOS--&gt;[ WCS World Construction Set],
|-
|&lt;!--Sub Menu--&gt;Astronomy [https://sourceforge.net/projects/skychart/ skychart freepascal], [], [], 
|&lt;!--AROS--&gt;[ Digital Almanac (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/search?query=planetarium Aminet search], [http://aminet.net/misc/sci/DA3V56ISO.zip Digital Almanac], [https://aminet.net/package/misc/sci/da3sourceV58 Src c V58], [ Galileo renamed to Distant Suns]*, [], 
|&lt;!--AmigaOS4--&gt;[http://sourceforge.net/projects/digital-almanac/ Digital Almanac], Distant Suns*, [http://www.digitaluniverse.org.uk/ Digital Universe]*,
|&lt;!--MorphOS--&gt;[http://www.aminet.net/misc/sci/da3.lha Digital Almanac], [http://www.aminet.net/package/misc/sci/da3-mos-src Src c V56], 
|-
|&lt;!--Sub Menu--&gt;Astrology [https://sourceforge.net/projects/skylendar/ skylendar], [https://github.com/CruiserOne/Astrolog Astrolog], [https://www.astrolog.org/astrolog/astfile.htm Astrology alt site], [https://saravali.github.io/download.html Maitreya], [https://github.com/alamahant/Asteria Asteria], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Genealogy History Family Tree Ancestry Records (FreeBMD, FreeREG, and FreeCEN file formats or GEDCOM GenTree)
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; [ Origins], [ Your Family Tree], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Languages 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Fun School, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Mathematics ([http://www-fourier.ujf-grenoble.fr/~parisse/install_en.html Xcas], etc.), 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/scientific mathX] 
|&lt;!--Amiga OS--&gt;Maple V, mathX, Fun School, GCSE Maths, [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;Yacas 
|&lt;!--MorphOS--&gt;Yacas 
|-
|&lt;!--Sub Menu--&gt;Maths Graph Function Plotting
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#MUIPlot MUIPlot], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;App Utility Launcher Dock toolbar  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/docky BoingBar], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/adkennan/DockBot Dockbot],
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Printer [https://github.com/OrcaSlicer/OrcaSlicer OrcaSlicer]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;CNC control with laser and vinyl cutting 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PCB design
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Digital Signage
|&lt;!--AROS--&gt;Hollywood, Hollywood Designer 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;HAM radio, amateur radio, packet radio,  [], [], [], [https://cemaxecuter.com/ Dragon OS], [https://github.com/km4ack/73Linux with 73 link update], [https://www.youtube.com/watch?v=YAL5KNePRSg video for], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/punktniklas/NiKom NiKom], [https://www.amigarealm.com/amiga/amicomms/comm4.htm Comm4], [https://www.amigarealm.com/archives/comms/aarug/ TNC Terminal Node Controller with packets over serial connections on Yaesu or Woxum handheld], [https://aminet.net/comm/misc AmiCom], [ with 7Plus file encoder/decoder], [ mksstv], [ RTTYam], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;modern smart home network like Home Assistant Automation Yellow, Green, Mosquitto, EMQX, IFTTT (aka IF This Then That), 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/evil4dmin/ami2ha HA], [https://github.com/sidick/midge mtqq.lib], [https://aminet.net/package/comm/tcp/AmiHomeassist-0.7 AmiHomeassist], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Teaching classroom learning training [https://github.com/moodle/moodle moodle], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Games &amp; Emulation==

Some emulators/games require OpenGL to function and to adjust ahi prefs channels, frequency and unit0 and unit1 and 
[http://aros.sourceforge.net/documentation/users/shell/changetaskpri.php changetaskpri -1]

Rom patching  https://www.marcrobledo.com/RomPatcher.js/ https://www.romhacking.net/patch/ (ips, ups, bps, etc) and this other site supports the latter formats https://hack64.net/tools/patcher.php 

Free public domain roms for use with emulators can be found [http://www.pdroms.de/ here] as most of the rest are covered by copyright rules. If you like to read about old games see [http://retrogamingtimes.com/ here] and [http://www.armchairarcade.com/neo/ here] and a [http://www.vintagecomputing.com/ blog] about old computers. Possibly some of the [http://www.answers.com/topic/list-of-best-selling-computer-and-video-games best selling] of all time. [http://en.wikipedia.org/wiki/List_of_computer_system_emulators Wiki] with emulated systems list.

[https://archive.gamehistory.org/ Archive of VGHF], [https://library.gamehistory.org/ Video Game History Foundation Library search]


{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Emulation]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Games Emulation Amstrad CPC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [ Caprice32 (OpenGL &amp; pure SDL)], [ Arnold], [https://retroshowcase.gr/cpcbox-master/], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Apple2 and 2GS
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Arcade 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Mame], [ SI Emu (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;Mame, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem xmame], amiarcadia, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 Mame], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 2600 [], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Stella], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 5200 [https://github.com/wavemotion-dave/A5200DS A5200DS], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 7800
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 400 800 130XL [https://github.com/wavemotion-dave/A8DS A8DS], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Atari800], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Lynx
|&lt;!--AROS--&gt;[http://myfreefilehosting.com/f/6366e11bdf_1.93MB Handy (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Jaguar
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Bandai Wonderswan 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation BBC Micro and Acorn Electron [http://beehttps://bem-unix.bbcmicro.com/download.html BeebEm], [http://b-em.bbcmicro.com/ B-Em], [http://elkulator.acornelectron.co.uk/ Elkulator], [http://electrem.emuunlim.com/ ElectrEm], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Dragon 32 and Tandy CoCo [http://www.6809.org.uk/xroar/ xroar], [], 
|&lt;!--AROS--&gt;[], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C16 Plus4
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C64
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Vice (ABIv0 only)], [], 
|&lt;!--Amiga OS--&gt;Frodo, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem viceplus], 
|&lt;!--MorphOS--&gt;Vice, 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore Amiga
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Janus UAE], Emumiga, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer UAE], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 UAE], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Japanese MSX MSX2 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Intelivision
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Colecovision and Adam
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Milton Bradley (MB) Vectrex [ Vectrex OpenGL], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation PICO8 Pico-8 fantasy video game console [https://github.com/egordorichev/pemsa-sdl/ pemsa-sdl], [https://github.com/jtothebell/fake-08 fake-08], [https://github.com/Epicpkmn11/fake-08/tree/wip fake-08 fork], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo Gameboy
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem vba no sound], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem vba]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo NES
|&lt;!--AROS--&gt;[ EmiNES], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Fceu], [https://github.com/takahirox/nes-js?tab=readme-ov-file nes-js], [https://github.com/bfirsh/jsnes jsnes], [https://github.com/angelo-wf/NesJs NesJs], 
|&lt;!--Amiga OS--&gt;AmiNES, [http://www.dridus.com/~nyef/darcnes/ darcNES], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem amines]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo SNES
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Zsnes], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem warpsnes]
|&lt;!--MorphOS--&gt;[http://fabportnawak.free.fr/snes/ Snes9x], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo N64 
*HLE and plugins [ mupen64], [https://github.com/ares-emulator/ares ares], [https://github.com/N64Recomp/N64Recomp N64Recomp], [https://github.com/rt64/rt64 rt64], [https://github.com/simple64/simple64 Simple64], 
*LLE [], 
|&lt;!--AROS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+],
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+], [http://aminet.net/package/misc/emu/tr-981125_src TR64], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Gamecube Wii]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Wii U]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/yuzu-emu Nintendo Switch]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation NEC PC Engine 
|&lt;!--AROS--&gt;[], [], [https://github.com/yhzmr442/jspce js-pce], 
|[http://www.hugo.fr.fm/ Hugo], [http://mednafen.sourceforge.net/ Mednafen], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem tgemu]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Master System (SMS)
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Dega], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem sms], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem osmose]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Genesis/Megadrive
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem gp no sound], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem DGen], 
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/genplus-gx/ Genplus], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem genesisplus]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Saturn 
*HLE [https://mednafen.github.io/ mednafen], [http://yabause.org/ yabause], [], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;[http://yabause.org/ Yabause], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Dreamcast 
*HLE [https://github.com/flyinghead/flycast  flycast], [https://code.google.com/archive/p/nulldc/downloads NullDC], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair ZX80 and ZX81 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair Spectrum 
|[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Fuse (crackly sound)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer SimCoupe], [ FBZX slow], [https://jsspeccy.zxdemo.org/ jsspeccy], [http://torinak.com/qaop/games qaop], 
|&lt;!--Amiga OS--&gt;[http://www.zophar.net/sinclair.html Speculator], [http://www.worldofspectrum.org/x128/index.html X128], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair QL
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/misc/emu/QDOS4amiga1 QDOS4amiga]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation SNK NeoGeo Pocket
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem gngeo], NeoPop, 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sony PlayStation
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem FPSE], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem FPSE]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS2]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS3]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://vita3k.org/ Sony Vita]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/shadps4-emu/shadPS4 PS4]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation [http://en.wikipedia.org/wiki/Tangerine_Computer_Systems Tangerine] Oric and Atmos 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Oricutron]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem Oricutron]
|&lt;!--MorphOS--&gt;[http://aminet.net/package/misc/emu/oricutron Oricutron]
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 99/4 99/4A [https://github.com/wavemotion-dave/DS994a DS994a], [], [https://js99er.net/#/ js99er], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/misc/emu/TI4Amiga TI4Amiga], [http://aminet.net/package/misc/emu/TI4Amiga_src TI4Amiga src in c], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation HP 38G 40GS 48 49G/50G Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 58 83 84 85 86 - 89 92 Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games emulation Ms-Dos Dosbox type 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/aros-boxerapp Boxer]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [https://www.rockpapershotgun.com/ General]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Games [https://www.trackawesomelist.com/michelpereira/awesome-open-source-games/ Open Source and others] || AROS || Amiga OS || Amiga OS4 || Morphos 
|-
|&lt;!--Sub Menu--&gt;Games Action like [https://github.com/opentomb/OpenTomb opentomb], [https://github.com/LostArtefacts/TRX TRX formerly Tomb1Main], [https://github.com/TombEngine TombEngine], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Thrust], [https://github.com/fragglet/sdl-sopwith sdl sopwith], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action BOH], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/BSzili/OpenLara/tree/amiga/src source of openlara SDL2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Adventure like [http://dotg.sourceforge.net/ DMJ], [https://github.com/kromenak/gengine Gabriel Knight 3], [http://www.sarien.net/ Sierra Sarien], [https://github.com/klembot/twinejs twine js], [https://github.com/QSPFoundation/qspgui Quest Soft Player QSP], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/adventure dmagnetic], [https://archives.arosworld.org/?function=browse&amp;cat=emulation/misc ScummVM], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying frotz infocom], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Board like [https://github.com/aperture-software/colditz-escape escape from colditz], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/board], [http://amigan.1emu.net/releases Africa]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Cards 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/card], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12934#post_12934 Balatro], 
|&lt;!--AmigaOS--&gt;[http://home.arcor.de/amigasolitaire/e/welcome.html Reko], [https://github.com/samskivert/beschei-en beschei Src], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Misc [https://github.com/michelpereira/awesome-open-source-games Awesome open], [https://github.com/bobeff/open-source-games General Open Source], [https://github.com/SAT-R/sa2 Sonic Advance 2], [https://github.com/velorek1/cwordle Wordle type], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games FPS like [https://aminet.net/package/game/shoot/D1X_Rebirth_AGA Descent D1X src], [https://github.com/DescentDevelopers/Descent3 Descent 3], [https://github.com/Fewnity/Counter-Strike-Nintendo-DS Counter-Strike-Nintendo-DS], [https://github.com/Aleph-One-Marathon/alephone Bungie Marathon 1994], [https://zdoom.org/downloads UzDoom opengl 3.3], [https://github.com/ZDoom/gzdoom gzdoom opengl 3+], [https://zdoom.org/downloads LZDoom opengl 2.1], [https://github.com/OpenXRay/xray-16 S.T.A.L.K.E.R Xray], [https://staniks.github.io/articles/serious-engine-networking-analysis/ Serious Sam] [https://github.com/Croteam-official/Serious-Engine Serious Engine 1]
|&lt;!--AROS--&gt;Doom, Quake, [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Quake 3 Arena (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Assault Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube 2 Sauerbraten (OpenGL)], [http://fodquake.net/test/ FodQuake QuakeWorld], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Duke Nukem 3D], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Darkplaces Nexuiz Xonotic], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Doom 3 SDL (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Hexenworld and Hexen 2], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Aliens vs Predator Gold 2000 avp (openGL)], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Odamex (openGL doom)], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ zgloom], [], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ ab3dhd], [], 
|&lt;!--Amiga OS--&gt;Doom, Quake, AB3D, Fears, Breathless, Gloom, 
|&lt;!--AmigaOS4--&gt;Doom, Quake, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12 Doom], Quake, Quake 3 Arena, 
|-
|&lt;!--Sub Menu--&gt;Games MMORG like 
|&lt;!--AROS--&gt;[ Eternal Lands (OpenGL)],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Platform like 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform], [ Maze of Galious], [ Gish]*(openGL), [ Mega Mario], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ thextech SMBX], [http://www.gianas-return.de/ Giana's Return], [http://www.sqrxz.de/ Sqrxz], [www.sqrxz2.de/ Sqrxz 2], [http://www.sqrxz.de/sqrxz-3/ Sqrxz 3], [http://www.sqrxz.de/sqrxz-4/ Sqrxz 4], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform Cave Story], [https://bszili.morphos.me/ Frogatto], [https://bszili.morphos.me/ OpenJazz], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ pekkakana2], [ Aquaria], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ sonic CD], [], 
|&lt;!--Amiga OS--&gt;[ Giana Sisters], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Puzzle [https://github.com/mariopartyrd/marioparty4/tree/port Party], [https://github.com/mdodis/OpenSolomonsKey OpenSolomonsKey], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle], [ Cubosphere (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle Candy Crisis], [http://bszili.morphos.me/ TailTale], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Sports 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/aros-swos OpenSWOS], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Racing [ Trigger Rally], [ VDrift], [http://www.ultimatestunts.nl/index.php?page=2&amp;lang=en Ultimate Stunts], [http://maniadrive.raydium.org/ Mania Drive], [https://github.com/plowteam/donut Simpsons Hit and Run], [], 
|&lt;!--AROS--&gt;[ Super Tux Kart (OpenGL)], [http://www.dusabledanslherbe.eu/AROSPage/F1Spirit.30.html F1 Spirit (OpenGL)], [http://bszili.morphos.me/index.html MultiRacer], [https://bszili.morphos.me/ Speed Dreams], [https://archives.arosworld.org/?function=showfile&amp;file=game/driving/dethrace-0.10.1.x86_64-aros-v11.zip Carmageddon dethrace 64bit], [http://maniadrive.raydium.org/index.php?downloads=yes maniadrive like trackmania], 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://bszili.morphos.me/index.html Speed Dreams], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12], [http://bszili.morphos.me/index.html TORCS], 
|-
|&lt;!--Sub Menu--&gt;Games 1st first person DRPG [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/OpenEnroth/OpenEnroth OpenEnroth MM], []
|&lt;!--AROS--&gt;[https://github.com/BSzili/aros-stuff Arx Libertatis], [http://www.playfuljs.com/a-first-person-engine-in-265-lines/ js raycaster], [https://github.com/Dorthu/es6-crpg webgl], [https://github.com/sonountaleban/AmiShockolate System Shock], [], [], 
|&lt;!--AmigaOS--&gt;Phantasie, Faery Tale, Dungeon Master, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 3rd third person action CRPG  [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/alexbatalov/fallout1-ce fallout ce], [https://github.com/rwengine/openrw gta3], [https://github.com/gta-reversed/gta-reversed gta3 sa], [https://github.com/mrxenginner/reVC gta3 vc revc], [https://github.com/jakobharder/burntime/tree/main Burntime], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ fheroes2 homm2], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ breakhack], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ devilutionx diablo 1 hellfire], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ fallout 1], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ stratagus], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ hostile-takeover], [https://github.com/Kalamatee/ Openmw], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games isometric RPG [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/topics/dungeon?l=javascript Dungeon], [], [https://github.com/clintbellanger/heroine-dusk JS Dusk], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying nethack], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying GemRB], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games card based RPG [https://github.com/open-duelyst/duelyst Duelyst], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games turn based tactics RPG [], [], [], [], [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy UFO AI], [http://play.freeciv.org/ FreeCiv], [https://juen.in Aveterna online civ], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Strategy [http://rtsgus.org/ RTSgus], [http://stargus.sourceforge.net/ Stargus], [https://github.com/KD-lab-Open-Source/Perimeter Perimeter], [https://matty77.itch.io/conflict-3049 conflict-3049], [https://github.com/ZeroK-RTS/Zero-K Zero-K multi player rts lua], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy MegaGlest (OpenGL)], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ signus], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=140&amp;pid=12446#post_12446 Wargus warcraft 2 setup], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/game/strat/OpenDUNE_RTG OpenDUNE_RTG src]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Rhythm, Beat, Step [], [], [https://clonehero.net/ clonehero], [https://github.com/MatteoGodzilla/Dj-Engine Dj-Engine], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc Frets on Fire], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Shoot Em Ups [http://www.mhgames.org/oldies/formido/ Formido], [http://code.google.com/p/violetland/ Violetland], 
||&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Open Tyrian], [http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ Alien Blaster], [https://github.com/OpenFodder/openfodder OpenFodder], [https://archives.arosworld.org/?function=showfile&amp;file=game/action/ tbftss The Battle for the Solar System: the Pandora War]
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ The Battle for the Solar System: the Pandora War]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Simulations [http://scp.indiegames.us/ Freespace 2], [http://www.heptargon.de/gl-117/gl-117.html GL117], [http://code.google.com/p/corsix-th/ Theme Hospital], [http://code.google.com/p/freerct/ Rollercoaster Tycoon], [http://hedgewars.org/ Hedgewars], [https://github.com/raceintospace/raceintospace raceintospace], [https://github.com/Return-To-The-Roots RTTR Settlers 2], [https://github.com/OoliteProject/oolite oolite elite], [https://github.com/fesh0r/newkind newkind elite], [https://github.com/bohemiainteractive/cwr Arma Cold War Src], [https://github.com/endless-sky/endless-sky endless-sky], [https://github.com/pioneerspacesim/pioneer pioneer space command], 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/aros-micropolis micropolis]
|&lt;!--Amiga OS--&gt;SimCity, SimAnt, Sim Hospital, Theme Park, [https://github.com/angree/openttd_amiga_68k openttd amiga_68k], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Life Sim [https://github.com/ACreTeam/forest Animal Crossing], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Horror [https://github.com/Mikompilation/MikuPan Fatal Frame], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Sandbox Voxel Open World Exploration [https://github.com/ClassiCube/ Classicube],[http://www.michaelfogleman.com/craft/ Craft], [https://github.com/tothpaul/DelphiCraft DelphiCraft],[https://www.minetest.net/ Luanti formerly Minetest], [ infiniminer], 
|&lt;!--AROS--&gt;[https://github.com/Kalamatee/veloren veloren]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Battle Royale [https://bruh.io/ Play.Bruh.io], [https://www.coolmathgames.com/0-copter Copter Royale], [https://surviv.io/ Surviv.io], [https://nuggetroyale.io/#Ketchup Nugget Royale], [https://miniroyale2.io/ Miniroyale2.io], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Tower Defense [https://chriscourses.github.io/tower-defense/ HTML5], [https://github.com/SBardak/Tower-Defense-Game TD C++], [https://github.com/bdoms/love_defense LUA and LOVE], [https://github.com/HyOsori/Osori-WebGame HTML5], [https://github.com/PascalCorpsman/ConfigTD ConfigTD Pascal], [https://github.com/GloriousEggroll/wine-ge-custom Wine], []
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12871#post_12871 Plants vs Zombies PvZ], 
|&lt;!--Amiga OS--&gt;[https://github.com/boingball/miggy-tower-defense miggy-tower-defense], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Visual Novel Engines [https://github.com/diane1f0cd/VisualNovelTemplate Visual Novel Template], [https://github.com/Kirilllive/tuesday-js Tuesday JS], [https://github.com/tejasnayak25/vnsutra vnsutra], [https://github.com/weetabix-su/renpsp-dev RenPSP], [https://github.com/Galladite27/ONScripter-EN ONScripter-EN], [https://github.com/NathanGuilhot/VNES-Raylib https://github.com/NathanGuilhot/VNES VNES in Raylib], [https://www.renpy.org/latest.html renpy ren'py python based], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Reality VR [https://gitlab.com/madsbuvi/openmw openmw vr], [https://github.com/Team-Beef-Studios/BeefRaiderXR BeefRaiderXR], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Table Top VTT [ Roll20], [https://www.owlbear.rodeo/ owlbear rodeo], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Computer assisted TableTop TTRPG OSR [https://www.rpgsolo.com/play.php RPGSolo], [https://github.com/fpsvogel/solo-ttrpgs Solo TTRPG], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 2D 3D Engines [https://github.com/fegennari/3DWorld 3DWorld], [https://github.com/GarageGames/Torque3D Torque3D], [https://github.com/gameplay3d/GamePlay GamePlay 3D],  [https://www.babylonjs.com/ BabylonJS ], [ Godot], [ Ogre], [ Crystal Space], [https://github.com/JacobHess03/ Dragon-Quest like], [https://github.com/bjornbytes/lovr Lua LOVE for 2D LOVR for 3D], [], 
|&lt;!--AROS--&gt;[https://www.arkhamdev.net/wiki.htm?id=agx Arkham Development antiryadgx 8.9 lts with register], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/alpyre/Sevgi_Engine Sevgi Engine], [], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games C based game frameworks [https://github.com/orangeduck/Corange Corange], [https://github.com/scottcgi/Mojoc Mojoc], [https://orx-project.org/ Orx], [https://github.com/ioquake/ioq3 Quake 3], [https://www.mapeditor.org/ Tiled], [https://www.raylib.com/ 2d Raylib], [https://github.com/Rabios/awesome-raylib other raylib], [https://github.com/MrFrenik/gunslinger Gunslinger], [https://o3de.org/ o3d], [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/library GLFW], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/library Raylib 5], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games RPGMaker MV/MZ-compatible projects [https://github.com/Psychronic-Games/RPGReactor RPGReactor js],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Pinball [https://github.com/vpinball/vpinball vpinball], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games unpack unarc [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}


==Application Guides==

[[#top|...to the top]]

===Web Browser===

OWB is now at version 2.0 (which got an engine refresh, from July 2015 to February 2019) and 3.0.

This latest version has a good support for many/most web sites, even YouTube web page now works. [https://www.bilibili.tv/en/search untested] 

This improved compatibility comes at the expense of higher RAM usage (now 1GB RAM is the absolute minimum). 

Also, keep in mind that the lack of a JIT (Just-In-Time) JS compiler on the 32 bit version, makes the web surfing a bit slow. 

Only the 64 bit version of OWB 2.0 will have JIT enabled, thus benefitting of more speed. There are tooltypes that can be added to the icon to provide further features JIT, MSE etc 


Certificates from [https://curl.se/docs/caextract.html ca certs], 


DNS tracking blocking with [https://easylist.to/easylist/easylist.txt easylist.txt] in PROGDIR:Conf before starting browser with enabled AdBlock [https://github.com/easylist/easylist/tree/master easylist], [https://gitlab.com/eyeo anti abp], [https://firebog.net/ big blocklist], [https://github.com/StevenBlack/hosts Steves], [], [], 

This can be enabled with OWB Odyssey with Windows -&gt; Content Blocking and Windows -&gt; Messages and enter 

 https://www.youtube.com/api/stats/ads*
 https://www.youtube.com/pagead/adview*
 https://www.youtube.com#@##player-ads*

into your custom filters 


Element blocker browser extension might be needed for [https://github.com/easylist/easylist/wiki/Youtube-Issues youtube], [ mid roll], [ pre roll], [ ],  


OWB speed is much better when running from RAM Disk, the best way is to add the below into your S:User-Startup which copies OWB drawer from Extras:Internet/OWB to RAM Disk: 

So add this :
&lt;pre&gt;
copy Extras:Internet/OWB Ram:OWB/ ALL CLONE &gt;NIL:
copy Extras:Internet/OWB.info Ram: &gt;NIL:
&lt;/pre&gt;
Open RAM Disk and open OWB drawer and double click on OWB icon so that the above icon tooltypes are activated 

Problems are that the copy time is long (around 20 seconds added in the background), but we can make it faster if we delete useless files from the OWB drawer (docs, …)
If you don’t copy the drawer back onto the HD, you won’t save your cache, cookies, passwords… So you need a script for it.

 copy Extras:Internet/Amelinium/#? Ram:Amelinium/ ALL CLONE &gt;NIL: 

Error messages 

SSL error &quot;cant verify with ca-certificates&quot;, check bios clock time date is correct 

Error 6, try checking networking prefs settings and Save / Use preferences again or a '''few times''' otherwise the network chipset may not be compatible with Aros 


[https://www.google.com/search?q=%s&amp;udm=14 Google search without AI overview] 
[ DuckDuckGo]
[ Ecosia]
[ Qwant]
[ Swisscows]
[ Mojeek]
[ Brave Search]
[ PreSearch]
[ Startpage] 


===E-mail===

 Emailinium is now available for IMAP and POP3 based accounts 

YAM does not support SSL and most mail providers now switched to encrypted SMTP/POP3 connections


====SimpleMail====

SimpleMail supports IMAP and appears to work with GMail, but it's never been reliable enough, it can crash with large mailboxes.

Please read more on this [http://www.freelists.org/list/simplemail-usr User list]


 GMail

Be sure to activate the pop3 usage in your gmail account setup / configuration first.

pop3: 
pop.gmail.com
Use SSL: Yes
Port: 995

smtp:
smtp.gmail.com (with authentication)
Use Authentication: Yes
Use SSL: Yes
Port: 465 or 587


 Hotmail/MSN/outlook/Microsoft Mail mid-2017, all outlook.com accounts will be migrated to Office 365 / Exchange

Most users are currently on POP which does not allow showing folders and many other features (technical limitations of POP3). With Microsoft IMAP you will get folders, sync read/unread, and show flags. You still won't get push though, as Microsoft has not turned on the IMAP Idle command as at Sept 2013.

If you want to try it, you need to first remove (you can't edit) your pop account (long-press the account on the accounts screen, delete account). Then set it up this way:

1. Email/Password
2. Manual
3. IMAP
4.

* Incoming: imap-mail.outlook.com, port 993, SSL/TLS should be checked
* Outgoing: smtp-mail.outlook.com, port 587, SSL/TLS should be checked
* POP server name pop-mail.outlook.com, port 995, POP encryption method SSL

 Yahoo  Mail

On April 24, 2002 Yahoo ceased to offer POP access to its free mail service. Introducing instead a yearly payment feature, allowing users POP3 and IMAP server support, along with such benefits as larger file attachment sizes and no adverts.

Sorry to see Yahoo leaving its users to cough up for the privilege of accessing their mail. Understandable, when competing against rivals such as Gmail and Hotmail who hold a large majority of users and were hacked in 2014 as well.


Incoming Mail (IMAP) Server

* Server - imap.mail.yahoo.com
* Port - 993
* Requires SSL - Yes

Outgoing Mail (SMTP) Server

* Server - smtp.mail.yahoo.com
* Port - 465 or 587
* Requires SSL - Yes
* Requires authentication - Yes

Your login info

* Email address - Your full email address (name@domain.com)
* Password - Your account's password
* Requires authentication - Yes


Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a subscription subs fee to have access to SMTP and POP3

* Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
* “Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
* “Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
* “Password” – Your Yahoo Mail password.

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

* Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.


====YAM Yet Another Mailer====

 YAM does not support SSL and most mail providers have now switched to encrypted SMTP/POP3 connections

This email client is POP3 only if the SSL library is available [http://www.freelists.org/list/yam YAM Freelists]

One of the downsides of using a POP3 mailer unfortunately - you have to set an option not to delete the mail if you want it left on the server. IMAP keeps all the emails on the server.

Possible issues

Sending mail issues is probably a matter of using your ISP's SMTP server, though it could also be an SSL issue.


getting a &quot;Couldn't initialise TLSv1 / SSL error

Use of on-line e-mail accounts with this email client is not possible as it lacks the OpenSSL AmiSSl v3 compatible library

 GMail 
Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995

Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587

Account Name: your Gmail username (including '@gmail.com')
Email Address: your full Gmail email address (username@gmail.com)
Password: your Gmail password

Anyway, the SMTP is pop.gmail.com port 465 and it uses SSLLv3 Authentication. The POP3 settings are for the same server (pop.gmail.com), only on port 995 instead.


 Outlook.com access

&lt;pre &gt;
Outlook.com SMTP server address: smtp.live.com
Outlook.com SMTP user name: Your full Outlook.com email address (not an alias)
Outlook.com SMTP password: Your Outlook.com password
Outlook.com SMTP port: 587
Outlook.com SMTP TLS/SSL encryption required: yes 
&lt;/pre &gt;


 Yahoo  Mail

&lt;pre &gt;
“POP3 Server” – Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
“SMTP Server” – Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.
“Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
“Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
“Password” – Your Yahoo Mail password.
&lt;/pre &gt;

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a monthly fee to have access to SMTP and POP3


 Microsoft Outlook Express Mail 

1. Get the files to your PC.
By whatever method get the files off your Amiga onto your PC. In the YAM folder you have a number of different folders, one for each of your folders in YAM. Inside that is a file usually some numbers such as 332423.283. YAM created a new file for every single email you received.

2. Open up a brand new Outlook Express. Just configure the account to use 127.0.0.1 as mail servers. It doesn't really matter. You will need to manually create any subfolders you used in YAM.

3. You will need to do a mass rename on all your email files from YAM. Just add a .eml to the end of it. Amazing how PCs still rely mostly on the file name so it knows what sort of file it is rather than just looking at it! There are a number of multiple renamers online to download and free too.

4. Go into each of your folders, inbox, sent items etc. And do a select all then drag the files into Outlook Express (to the relevant folder obviously) Amazingly the file format that YAM used is very compatible with .eml standard and viola your emails appear. With correct dates and working attachments.

5. If you want your email into Microsoft Outlook. Open that up and create a new profile and a new blank PST file. Then go into File Import and choose to import from Outlook Express. And the mail will go into there. And viola.. you have your old email from your Amiga in a more modern day format.


===FTP===

Magellan has a great FTP module. It allows transferring files from/to a FTP server over the Internet or the local network and, even if FTP is perceived as a &quot;thing of the past&quot;, its usability is all inside the client. The FTP thing has a nice side effect too, since every Icaros machine can be a FTP server as well, and our files can be easily transferred from an Icaros machine to another with a little configuration effort.

First of all, we need to know the 'server' IP address. Server is the Icaros machine with the file we are about to download on another Icaros machine, that we're going to call 'client'. To do that, move on the server machine and 1) run Prefs/Services to be sure &quot;FTP file transfer&quot; is enabled (if not, enable it and restart Icaros); 2) run a shell and enter this command:

ifconfig -a

Make a note of the IP address for the network interface used by the local area network. For cabled devices, it usually is net0:. Now go on the client machine and run Magellan:

Perform these actions: 1) click on FTP; 2) click on ADDRESS BOOK; 3) click on &quot;New&quot;. 
You can now add a new entry for your Icaros server machine:

1) Choose a name for your server, in order to spot it immediately in the address book. Enter the IP address you got before.

2) click on Custom Options:


1) go to Miscellaneous in the left menu;

2) Ensure &quot;Passive Transfers&quot; is NOT selected;

3) click on Use. We need to deactivate Passive Transfers because YAFS, the FTP server included in Icaros, only allows active transfers at the current stage. Now, we can finally connect to our new file source:


1) Look into the address book for the newly introduced server, be sure that name and IP address are right, and

2) click on Connect. A new lister with server's &quot;MyWorkspace&quot; contents will appear. You can now transfer files over the network choosing a destination among your local (client's) volumes.

Can be adapted to any FTP client on any platform of your choice, just be sure your client allows Active Transfers as well.


===IRC Internet Relay Chat===

Jabberwocky is ideal for one-to-one social media communication, use IRC if you require one to many. 

Just type a message in ''lowercase''' letters and it will be posted to all in the [ AROS irc channel]. Please do not use UPPER CASE as it is a sign of SHOUTING which is annoying.

Other things to type in - replace &lt;message&gt; with a line of text and &lt;nick&gt; with a person's name

&lt;pre&gt;
/help

/list

/who
/whois &lt;nick&gt;

/msg &lt;nick&gt; &lt;message&gt;

/query &lt;nick&gt; 
&lt;message&gt;s
/query

/away &lt;message&gt;
/away

/quit &lt;going away message&gt; 
&lt;/pre&gt;


[http://irchelp.org/irchelp/new2irc.html#smiley Intro guide here]. IRC Primer can be found here in [http://www.irchelp.org/irchelp/ircprimer.html html], [http://www.irchelp.org/irchelp/text/ircprimer.txt TXT], [http://www.kei.com/irc/IRCprimer1.1.ps PostScript].


Issue the command /me &lt;text&gt; where &lt;text&gt; is the text that should follow your nickname.
Example: /me slaps ajk around a bit with a large trout

/nick &lt;newNick&gt;

/nickserv register &lt;password&gt; &lt;email address&gt;

/ns instead of /nickserv, while others might need /msg nickserv

/nickserv identify &lt;password&gt;

Alternatives:
/ns identify &lt;password&gt;
/msg nickserv identify &lt;password&gt;


==== IRC WookieChat ====

WookieChat is the most complete internet client for communication across the IRC Network. WookieChat allows you to swap ideas and communicate in real-time, you can also exchange Files, Documents, Images and everything else using the application's DCC capabilities.


add smilies drawer/directory

 run wookiechat from the shell and set stack to 1000000 e.g. wookiechat stack 1000000

select a server / server window

* nickname 
* user name 
* real name - optional

Once you configure the client with your preferred screen name, you'll want to find a channel to talk in.


servers

* New Server - click on this to add / add extra - change details in section below this click box 
* New Group
* Delete Entry
* Connect to server
* connect in new tab
* perform on connect

Change details

* Servername - change text in this box to one of the below Server: 
* Port number - no need to change
* Server password
* Channel - add #channel from below 
* auto join - can click this 
* nick registration password,

Click Connect to server button above


&lt;pre&gt;
Server: irc.freenode.net
Channel: #aros
&lt;/pre&gt;

irc://irc.freenode.net/aros

&lt;pre&gt;
Server: chat.amigaworld.net 
Channel: #amigaworld or #amigans 
&lt;/pre&gt;

&lt;pre&gt;
On Sunday evenings USA time usually starting around 3PM EDT (1900 UTC)
Server:irc.superhosts.net
Channel #team*amiga  
&lt;/pre&gt;

&lt;pre&gt;
BitlBee and Minbif are IRCd-like gateways to multiple IM networks
Server: im.bitlbee.org 
Port 6667 
Seems to be most useful on WookieChat as you can be connected to several servers at once. One for Bitlbee and any messages that might come through that. One for your normal IRC chat server. 
&lt;/pre&gt;

[http://www.bitlbee.org/main.php/servers.html Other servers],

&lt;pre&gt;
#Amiga.org - irc.synirc.net eu.synirc.net dissonance.nl.eu.synirc.net (IPv6: 2002:5511:1356:0:216:17ff:fe84:68a) 
twilight.de.eu.synirc.net zero.dk.eu.synirc.net us.synirc.net avarice.az.us.synirc.net envy.il.us.synirc.net harpy.mi.us.synirc.net 
liberty.nj.us.synirc.net snowball.mo.us.synirc.net - Ports 6660-6669 7001 (SSL)
&lt;/pre&gt;

&lt;pre&gt;
Multiple server support
&quot;Perform on connect&quot; scripts and channel auto-joins
Automatic Nickserv login
Tabs for channels and private conversations
CTCP PING, TIME, VERSION, SOUND
Incoming and Outgoing DCC SEND file transfers
Colours for different events
Logging and automatic reloading of logs
mIRC colour code filters
Configurable timestamps
GUI for changing channel modes easily
Configurable highlight keywords
URL Grabber window
Optional outgoing swear word filter
Event sounds for tabs opening, highlighted words, and private messages
DCC CHAT support
Doubleclickable URL's
Support for multiple languages using LOCALE
Clone detection
Auto reconnection to Servers upon disconnection
Command aliases
Chat display can be toggled between AmIRC and mIRC style
Counter for Unread messages
Graphical nicklist and graphical smileys with a popup chooser
&lt;/pre&gt;


====IRC Aircos ====

Double click on Aircos icon in Extras:Networking/Apps/Aircos. It has been set up with a guest account for trial purposes. Though ideally, choose a nickname and password for frequent use of irc. 


====IRC and XMPP Jabberwocky====
 Servers are setup and close down at random 
You sign up to a server that someone else has setup and access chat services through them. 

The two ways to access chat from jabberwocky
&lt;pre &gt;
Jabberwocky -&gt; Server -&gt; XMPP -&gt; open and ad-free 
Jabberwocky -&gt; Server -&gt; Transports (Gateways) -&gt; Proprietary closed systems 
&lt;/pre &gt;

The Jabber.org service connects with all IM services that use XMPP, the open standard for instant messaging and presence over the Internet. The services we connect with include Google Talk (closed), Live Journal Talk, Nimbuzz, Ovi, and thousands more. However, you can not connect from Jabber.org to proprietary services like AIM, ICQ, MSN, Skype, or Yahoo because they don’t yet use XMPP components (XEP-0114) '''but''' you can use Jabber.com's servers and IM gateways (MSN, ICQ, Yahoo etc.) instead.

The best way to use jabberwocky is in conjunction with a public jabber server with '''transports''' to your favorite services, like gtalk, Facebook, yahoo, ICQ, AIM, etc.


You have to register with one of the servers, [https://list.jabber.at/ this list] or [http://www.jabberes.org/servers/ another list], [http://xmpp.net/ this security XMPP list],

Unfortunately jabberwocky can only connect to one server at a time so it is best to check what services each server offers. If you set it up with separate Facebook and google talk accounts, for example, sometimes you'll only get one or the other.

Jabberwocky open a window where the Jabber server part is typed in as well as your Nickname and Password.

Jabber ID (JID) identifies you to the server and other users.

Once registered the next step is to goto Jabberwocky's &quot;Windows&quot; menu and select the &quot;Agents&quot; option. The &quot;Agents List&quot; window will open.

Roster (contacts list)

[http://search.wensley.org.uk/ Chatrooms] (MUC) are available

File Transfer - can send and receive files through the Jabber service but not with other services like IRC, ICQ, AIM or Yahoo. All you need is an installed webbrowser and OpenURL.

Clickable URLs - The message window uses Mailtext.mcc and you can set a URL action in the MUI mailtext prefs like SYS:Utils/OpenURL %s NEWWIN.

There is no consistent Skype like (H.323 VoIP) video conferencing available over Jabber. The move from xmpp to Jingle should help but no support on any amiga-like systems at the moment. [http://aminet.net/package/dev/src/AmiPhoneSrc192 AmiPhone] and [http://www.lysator.liu.se/%28frame,faq,nobg,useframes%29/ahi/v4-site/ Speak Freely] was an early attempt voice only contact. SIP and Asterisk are other PBX options.


 Facebook

If you're using the XMPP transport provided by Facebook themselves, chat.facebook.com, it looks like they're now requiring SSL transport. This means jabberwocky method below will no longer work. The best thing to do is to create an ID on a public jabber server which has a Facebook gateway.

&lt;pre &gt;
1. launch jabberwocky
2. if the login window doesn't appear on launch, select 'account' from the jabberwocky menu
3. your jabber ID will be user@chat.facebook.com where user is your user ID
4. your password is your normal facebook password
5. to save this for next time, click the popup gadget next to the ID field

6. click the 'add' button
7. click the 'close' button
8. click the 'connect' button
&lt;/pre &gt;

you're done. you can also click the 'save as default account' button if you want. jabberwocky configured to auto-connect when launching the program, but you can configure as you like. there is amigaguide documentation included with jabberwocky.

[http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=37085&amp;forum=32 Read more here]

for Facebook users, you can log-in directly to Facebook with jabberwocky. just sign in as @chat.facebook.com with your Facebook password as the password


 Twitter

For a few years, there has been added a twitter transport. Servers include [http://jabber.hot-chilli.net/ jabber.hot-chili.net],  and .

An [http://jabber.hot-chilli.net/tag/how-tos/ How-to]

:Read [http://jabber.hot-chilli.net/2010/05/09/twitter-transport-working/ more]

 Instagram 

no support at the moment best to use a web browser based client

 ICQ

The new version (beta) of StriCQ uses a newer ICQ protocol. Most of the ICQ Jabber Transports still use an older ICQ protocol. You can only talk one-way to StriCQ using the older Transports. Only the newer ICQv7 Transport lets you talk both ways to StriCQ. Look at the server lists in the first section to check.

Register on a Jabber server, e.g. this one works: http://www.jabber.de/
Then login into Jabberwocky with the following login data e.g. xxx@jabber.de / Password: xxx Now add your ICQ account under the window-&gt;Agents-&gt;&quot;Register&quot;. Now Jabberwocky connects via the Jabber.de server with your ICQ account.

 Yahoo Messenger

although yahoo! does not use xmpp protocol, you should be able to use the transport methods to gain access and post your replies

 MSN

early months of 2013 Microsoft will ditch MSN Messenger client and force everyone to use Skype...but MSN protocol and servers will keep working as usual for quite a long time....

Occasionally the Messenger servers have been experiencing problems signing in.  You may need to sign in at www.outlook.com and then try again.  It may also take multiple tries to sign in.  (This also affects you if you’re using Skype.)

You have to check each servers' Agents List to see what transports (MSN protocol, ICQ protocol, etc.) are supported or use the list address' provided in the section above. Then register with each transport (IRC, MSN, ICQ, etc.) to which you need access. After registering you can Connect to start chatting.

msn.jabber.com/registered should appear in the window.

From this [http://tech.dir.groups.yahoo.com/group/amiga-jabberwocky/message/1378 JW group] guide which  helps with this process in a clear, step by step procedure.

1. Sign up on MSN's site for a passport account. This typically involves getting a Hotmail address.

2. Log on to the Jabber server of your choice and do the following:

* Select the &quot;Windows/Agents&quot; menu option in Jabberwocky.
* Select the MSN Agent from the list presented by the server.
* Click the Register button to open a new window asking for:
**Username = passort account email address, typically your hotmail address.
**Nick = Screen name to be shown to anyone you add to your buddy list.
**Password = Password for your passport account/hotmail address.
* Click the Register button at the bottom of the new window.

3. If all goes well, you will see the MSN Gateway added to your buddy list. If not, repeat part 2 on another server. Some servers may show MSN in their list of available agents, but have not updated their software for the latest protocols used by MSN.

4. Once you are registered, you can now add people to your buddy list. Note that you need to include the '''msn.''' ahead of the servername so that it knows what gateway agent to use. Some servers may use a slight variation and require '''msg.gate.''' before the server name, so try both to see what works.

If my friend's msn was amiga@hotmail.co.uk and my jabber server was @jabber.meta.net.nz..
then amiga'''%'''hotmail.com@'''msn.'''jabber.meta.net.nz

or another the trick to import MSN contacts is that you don't type the hotmail URL but the passport URL... e.g. Instead of: goodvibe%hotmail.com@msn.jabber.com  You type: goodvibe%passport.com@msn.jabber.com 
And the thing about importing contacts I'm afraid you'll have to do it by hand, one at the time...

 Google Talk

any XMPP server will work, but you have to add your contacts manually. a google talk user is typically either @gmail.com or @talk.google.com. a true gtalk transport is nice because it brings your contacts to you and (can) also support file transfers to/from google talk users.

implement Jingle a set of extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP)

support ended early 2014 as Google moved to Google+ Hangouts which uses it own proprietary format


===Video Player MPlayer===

Many of the menu features (such as doubling) do not work with the current version of mplayer but using

4:3
 mplayer -vf scale=800:600 file.avi

16:9
 mplayer -vf scale=854:480 file.avi

if you want gui use;
 mplayer -gui 1 &lt;other params&gt; file.avi

&lt;pre &gt;
stack 1000000

; using AspireOS 1.xx 
; copy FROM SYS:Extras/Multimedia/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 1.x 
; copy FROM SYS:Tools/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 2.x 
; copy FROM SYS:Utilities/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

cd RAM:MPlayer
run MPlayer -gui &gt; Nil:
;run MPlayer -gui -ao ahi_dev -playlist http://www.radio-paralax.de/listen.pls &gt; Nil: 
&lt;/pre &gt;

$ mplayer rtsp://127.0.0.1:554/sample_300kbit.mp4


MPlayer supports multicast streaming, and rtp/rtsp protocols (it might require [http://www.live555.com/openRTSP/ live555 library] to work with some streams). But you might have to build it where it's disabled. Also, multicast won't work with some AmiTCP-likes. MIAMI supported it, though.

AROS supports IPv4 (old but works) and this includes the needed address space for RTP.

If you mean multicast via RTP - mplayer handles it. You can even force UDP over TCP

-rtsp-stream-over-tcp

If the rtsp Real Time Streaming Protocol  server needs authentification:

-user -passwd


MPlayer - Menu - Open Playlist and load already downloaded .pls or .m3u file - auto starts around 4 percent cache

MPlayer - Menu - Open Stream and copy one of the .pls lines below into space allowed, press OK and press play button on main gui interface


Old 8bit 16bit remixes chip tune game music 
 
http://www.radio-paralax.de/listen.pls 

http://scenesat.com/

http://www.shoutcast.com/radio/Amiga

http://www.theoldcomputer.com/retro_radio/RetroRadio_Main.htm

http://www.kohina.com/

http://www.remix64.com/

http://retrogamer.net/forum/

http://retroasylum.podomatic.com/rss2.xml

http://retrogamesquad.com/

http://www.retronauts.com/

http://monsterfeet.com/noquarter/

http://www.retrogamingradio.com/

http://www.radiofeeds.co.uk/mp3.asp


[[#top|...to the top]]

====ZunePaint==== 

simplified typical workflow

* importing and organizing and photo management
* making global and regional local correction(s) - recalculation is necessary after each adjustment as it is not in real-time 
* exporting your images in the best format available with the preservation of metadata


Whilst achieving 80% of a great photo with just a filter, the remaining 20% comes from a manual fine-tuning of specific image attributes.


For photojournalism, documentary, and event coverage, minimal touching is recommended. Stick to Camera Raw for such shots, and limit changes to level adjustment, sharpness, noise reduction, and white balance correction.

For fashion or portrait shoots, a large amount of adjustment is allowed and usually ends up far from the original. Skin smoothing, blemish removal, eye touch-ups, etc. are common.  Might alter the background a bit to emphasize the subject.

Product photography usually requires a lot of sharpening, spot removal, and focus stacking.

For landscape shots, best results are achieved by doing the maximum amount of preparation before/while taking the shot. No amount of processing can match timing, proper lighting, correct gear, optimal settings, etc. Excessive post-processing might give you a dramatic shot but best avoided in the long term.


* White Balance - Left Amiga or F12 and K and under &quot;Misc color effects&quot; tab with a pull down for White Balance - color temperature also known as AKA tint (movies) or tones (painting) - warm temp raise red reduce green blue - cool raise blue lower red green 
* Exposure - exposure compensation, highlight/shadow recovery
* Noise Reduction - during RAW development or using external software
* Lens Corrections - distortion, vignetting, chromatic aberrations
* Detail - capture sharpening and local contrast enhancement
* Contrast - black point, levels (sliders) and curves tools (F12 and K) 
* Framing - straighten () and crop (F12 and F) 
* Refinements - color adjustments and selective enhancements - Left Amiga or F12 and K for RGB and YUV histogram tabs - 
* Resizing - enlarge for a print or downsize for the web or email (F12 and D) 
* Output Sharpening - customized for your subject matter and print/screen size


White Balance - F12 and K

scan your image for a shade which was meant to be white (neutral with each RGB value being equal) like paper or plastic which is in the same light as the subject of the picture. Use the dropper tool to select this color, similar colours will shift and you will have selected the perfect white balance for your part of the image - for the whole picture make sure RAZ or CLR button at the bottom is pressed before applying to the image above.


Exposure correction

F12 and K - YUV Y luminosity - RGB extra red tint - move red curve slightly down and move blue green curves slightly up

Workflows in practice

* Undo - Right AROS key or F12 and Z 
* Redo - Right AROS key or F12 and R

First flatten your image (if necessary) and then do a rotation until the picture looks level. 
* Crop the picture. Click the selection button and drag a box over the area of the picture you want to keep. Press the crop button and the rest of the photo will be gone. 
* Adjust your saturation, exposure, hue levels, etc., (right AROS Key and K for color correction) until you are happy with the photo. Make sure you zoom in all of the way to 100% and look the photo over, zoom back out and move around. Look for obvious problems with the picture. 
* After coloring and exposure do a sharpen (Right AROS key and E for Convolution and select drop down option needed), e.g. set the matrix to 5x5 (roughly equivalent Amount to 60%) and set the Radius to 1.0. Click OK.


And save your picture


Implemented or would like to see for simplification and ease of use

basic filters (presets) like black and white, monochrome, edge detection (sobel), motion/gaussian blur, 
* negative, sepiatone, retro vintage, night vision, colour tint, color gradient, color temperature, glows, fire, lightning, lens flare, emboss, filmic, pixelate mezzotint, antialias, etc.

adjust / cosmetic tools such as crop, 
* reshaping tools, straighten, smear, smooth, perspective, liquify, bloat, pucker, push pixels in any direction, dispersion, transform like warp, blending with soft light, page-curl, whirl, ripple, fisheye, neon,  etc. 
* red eye fixing, blemish remover, skin smoothing, teeth whitener, make eyes look brighter, desaturate,

effects like oil paint, cartoon, pencil sketch, charcoal, noise/matrix like sharpen/unsharpen, (right AROS key with A for Artistic effects) 
* blend two image, gradient blend, masking blend, explode, implode, custom collage, surreal painting, comic book style, needlepoint, stained glass, watercolor, mosaic, stencil/outline, crayon, chalk, etc.

borders such as 
* dropshadow, rounded, blurred, color tint, picture frame, film strip polaroid, bevelled edge, etc.

brushes e.g.
* frost, smoke, etc.

and manual control of

fix lens issues including vignetting (darkening), color fringing and barrel distortion, and chromatic and geometric aberration -  lens and body profiles

perspective correction

levels - directly modify the levels of the tone-values of an image, by using sliders for highlights, midtones and shadows

curves -  Color Adjustment and Brightness/Contrast

color balance

one single color transparent (alpha channel (color information/selections) for masking and/or blending ) for backgrounds, etc.

Threshold indicates how much other colors will be considered mixture of the removed color and non-removed colors

decompose layer into a set of layers with each holding a different type of pattern that is visible within the image

any selection using any selecting tools like lasso tool, marquee tool etc. the selection will temporarily be save to alpha 
If you create your image without transparency then the Alpha channel is not present, but you can add later.

File formats like .psd (Photoshop file has layers, masks etc.  contains edited sensor data. The original sensor data is no longer available) .xcf .raw .hdr

Image Picture Formats
* low dynamic range (JPEG, PNG, TIFF 8-bit), 16-bit (PPM, TIFF), typically as a 16-bit TIFF in either ProPhoto or AdobeRGB colorspace -  TIFF files are also fairly universal – although, if they contain proprietary data, such as Photoshop Adjustment Layers or Smart Filters, making them proprietary.
* linear high dynamic range (HDR) images (PFM, [http://www.openexr.com/ ILM .EXR], jpg, [http://aminet.net/util/dtype cr2] (canon tiff based), hdr, NEF, CRW, ARW, MRW, ORF, RAF (Fuji), PEF, DCR, SRF, ERF, DNG files are RAW converted to an Adobe proprietary format - a container that can embed the raw file as well as the information needed to open it) 
An old version of [http://archives.aros-exec.org/index.php?function=browse&amp;cat=graphics/convert dcraw]

There is no single RAW file format. Each camera manufacturer has one or more unique RAW formats. RAW files contain the brightness levels data captured by the camera sensor. This data cannot be modified. A second smaller file, separate XML file, or within a database with instructions for the RAW processor to change exposure, saturation etc. The extra data can be changed but the original sensor data is still there. RAW is technically least compatible.

A raw file is high-bit (usually 12 or 14 bits of information) but a camera-generated TIFF file will be usually converted by the camera (compressed, downsampled) to 8 bits. The raw file has no embedded color balance or color space, but the TIFF has both. These three things (smaller bit depth, embedded color balance, and embedded color space) make it so that the TIFF will lose quality more quickly with image adjustments than the raw file. The camera-generated TIFF image is much more like a camera processed JPEG than a raw file. A strong advantage goes to the raw file. The power of RAW files, such as the ability to set any color temperature non-destructively and will contain more tonal values.

The principle of preserving the maximum amount of information to as late as possible in the process. The final conversion - which will always effectively represent a &quot;downsampling&quot; - should prevent as much loss as possible.

Once you save it as TIFF, you throw away some of that data irretrievably. When saving in the lossy JPEG format, you get tremendous file size savings, but you've irreversibly thrown away a lot of image data. As long as you have the RAW file, original or otherwise, you have access to all of the image data as captured.

Keyboard equivalence with Photoshop(tm) would help 

&lt;pre&gt;
File
PHOTOSHOP	SHORTCUT	GIMP
New	Ctrl+n	New
Open	Ctrl+o	Open
Close	Ctrl+w	Close
Save	Ctrl+s	Save
Save as	Shift+Ctrl+s	Save as
Revert	F12	Revert
Print	Ctrl+p	Print
Exit	Ctrl+q	Quit
 
Edit
PHOTOSHOP	SHORTCUT	GIMP
Undo/Redo (1 level)	Ctrl+z	Undo (Redo is Shift+Ctrl+z)
Cut	Ctrl+x	Cut
Copy	Ctrl+c	Copy
Paste	Ctrl+v	Paste
Paste Into	Shift+Ctrl+v	Paste Into
Fill with FG color	Alt+Backspace	Fill with FG color
Fill with BG color	Control+Backspace	Fill with BG color
 
Image/Colors
PHOTOSHOP	SHORTCUT	GIMP
Levels	Ctrl+l	Levels
Auto Contrast	Shift+Ctrl+Alt+l	Stretch Contrast (same?)
Curves	Ctrl+m	Curves
Color Balance	Ctrl+b	Color Balance
Hue/Saturation	Ctrl+u	Hue-Saturation
Desaturate	Shift+Ctrl+u	Desaturate
Invert	Ctrl+i	Invert
Default Colors	d	Default Colors
Switch Colors	x	Switch Colors
 
Layer
PHOTOSHOP	SHORTCUT	GIMP
New Layer	Shift+Ctrl+n	New Layer
Layer via Copy	Ctrl+j	Duplicate Layer
Bring (layer) to Front	Shift+Ctrl+]	Layer to Top
Send (layer) to Back	Shift+Ctrl+[	Layer to Bottom
Bring (layer) Forward	Ctrl+]	Raise Layer
Send (layer) Backward	Ctrl+[	Lower Layer
Select Top Layer	Shift+Alt+]	Select Top Layer
Select Bottom Layer	Shift+Alt+[	Select Bottom Layer
Select One Layer Forward	Alt+]	Select Previous Layer
Select One Layer Backward	Alt+[	Select Next Layer
Merge Down	Ctrl+e	Merge Down
Merge Visible	Shift+Ctrl+e	Merge Visible
Preserve Transparency	/	Keep Transparency
Cycle Modes Forwards	Shift+=	Next Layer Mode
Cycle Modes Backwards	Shift+-	Previous Layer Mode
 
Select
PHOTOSHOP	SHORTCUT	GIMP
Select All	Ctrl+a	Select All
Deselect	Ctrl+d	Select None
Inverse	Shift+Ctrl+i	Invert
Feather	Ctrl+Alt+d	Feather
 
View
PHOTOSHOP	SHORTCUT	GIMP
Zoom In	Ctrl+=	Zoom In
Zoom Out	Ctrl+-	Zoom Out
Fit on Screen	Ctrl+0	Zoom to Fit Window
Actual Pixels	Ctrl+Alt+0	Zoom 1:1
Show/Hide Extras	Ctrl+h	Toggle Show Selection (close enough?)
Show/Hide Guides	Ctrl+'	Toggle Show Guides
Show/Hide Grid	Ctrl+Alt+'	Toggle Show Grid
Show/Hide Rulers	Ctrl+r	Toggle Show Rulers
Snap	Ctrl+;	Snap to Guides
Scroll View Up	Page Up	Scroll Page Up
Scroll View Down	Page Down	Scroll Page Down
Scroll View Left	Ctrl+Page Up	Scroll Page Left
Scroll View Right	Ctrl+Page Down	Scroll Page Right
 
Window/Dialogs
PHOTOSHOP	SHORTCUT	GIMP
?	F5	Tools Dialog
Color Tab	F6	Colors Dialog
Layers Tab	F7	Layers Dialog
Info Tab	F8	Image Information
 
Tools
PHOTOSHOP         SHORTCUT     GIMP
Move Tool	v	Move Tool
Lasso Tool	l	Free Select Tool
Magic Wand Tool	w	Fuzzy Select Tool
Crop Tool	c	Crop &amp; Resize Tool
Airbrush Tool	j	Airbrush Tool
Paintbrush Tool	b	Paintbrush Tool
Clone Stamp Tool	s	Clone Stamp Tool
Eraser Tool	e	Eraser Tool
Blur Tool	r	Convolve Tool
Dodge Tool	o	DodgeBurn Tool
Type Tool	t	Text Tool
Pen Tool	p	Bezier Select Tool
Eye Dropper Tool	i	Color Picker Tool
Zoom Tool	z	Magnify Tool
Previous Brush	,	Previous Brush
Next Brush	.	Next Brush
First Brush	Shift+&lt;	First Brush
Last Brush	Shift+&gt;	Last Brush
Decrease Brush Size	[	Decrease Brush Size
Increase Brush Size	]	Increase Brush Size
Decrease Brush Hardness	{	Decrease Brush Hardness
Increase Brush Hardness	}	Increase Brush Hardness

Rectangular Marquee Tool	m	Rect Select Tool
Elliptical Marquee Tool	Shift+m	Ellipse Select Tool
Gradient Tool	g	Blend Tool
Paint Bucket Tool	Shift+g	Bucket Fill Tool 

Transform        Alt Cntrl T 


Help
PHOTOSHOP	SHORTCUT	GIMP
Help	F1	Help
Context Help	Shift+F1	Context Help
 
Misc.
PHOTOSHOP	SHORTCUT	GIMP
Last Filter	Ctrl+f	Repeat Last Filter
?	Shift+Ctrl+f	Reshow Last Filter
Preferences	Ctrl+k	Preferences
Liquify	Shift+Ctrl+x	IWarp (close enough?)
Toggle Quick Mask	q	Toggle Quick Mask
&lt;/pre&gt;


Spotlights - triangle of white opaque shape

Cutting out and/or replacing unwanted background or features - select large areas with the selection option like the Magic Wand tool (aka Color Range) or the Lasso (quick and fast) with feather 2 to soften edge or the pen tool which adds points/lines/Bézier curves (better control but slower), hold down the shift button as you click to add extra points/areas of the subject matter to remove. Increase the tolerance to cover more areas. To subtract from your selection hold down alt as you're clicking. 
* Layer masks are a better way of working than Erase they clip (black hides/hidden white visible/reveal). Clone Stamp can be simulated by   and brushes for other areas. 
* Leave the fine details like hair, fur, etc. to later with lasso and the shift key to draw a line all the way around your subject. Gradient Mapping - Inverse - Mask. i.e. Refine your selected image with edge detection and using the radius and edge options / adjuster (increase/decrease contrast) so that you will capture more fine detail from the background allowing easier removal. 
Remove fringe/halo

saving image as png rather than jpg/jpeg to keep transparency background intact.


Implemented [http://colorizer.org/ colour model representations] [http://paulbourke.net/texture_colour/colourspace/ Mathematical approach] - Photo stills are spatially 2d (h and w), but are colorimetrically 3d (r g and b, or H L S, or Y U V etc.) as well. 
* RGB - split cubed mapped color model for photos and computer graphics hardware using the light spectrum (adding and subtracting) 
* YUV - Y-Lightness U-blue/yellow V-red/cyan (similar to YPbPr and YCbCr) used in the PAL, NTSC, and SECAM composite digital TV color [http://crewofone.com/2012/chroma-subsampling-and-transcoding/#comment-7299 video]


Histograms

White balanced (neutral) if the spike happens in the same place in each channel of the RGB graphs. If not, you're not balanced. 
If you have sky you'll see the blue channel further off to the right.

RGB is best one to change colours. These elements RGB is a 3-channel format containing data for Red, Green, and Blue in your photo scale between 0 and 255. The area in a picture that appears to be brighter/whiter contains more red color as compared to the area which is relatively darker. Similarly in the green channel the area that appears to be darker contains less amount of green color as compared to the area that appears to be brighter.  Similarly in the blue channel the area appears to be darker contains less amount of blue color as compared to the area that appears to be brighter. Brightness luminance histogram also matches the green histogram more than any other color - human eye interprets green better e.g. RGB rough ratio 15/55/30%

RGBA (RGB+A, A means alpha channel) .  The alpha channel is used for &quot;alpha compositing&quot;, which can mostly be associated as &quot;opacity&quot;.  AROS deals in RGB with two digits for every color (red, green, blue), in ARGB you have two additional hex digits for the alpha channel.

The shadows are represented by the left third of the graph.  The highlights are represented by the right third.  And the midtones are, of course, in the middle.  The higher the black peaks in the graph, the more pixels are concentrated in that tonal range (total black area). 
By moving the black endpoint, which identifies the shadows (darkness) and a white light endpoint (brightness) up and down either sides of the graph, colors are adjusted based on these points. 
By dragging the central one, can increased the midtones and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .


RGB Curves

* Move left endpoint (black point) up or right endpoint (white point) up brightens 
* Move left endpoint down or right endpoint down darkens

Color Curves

* Dragging up on the Red Curve increases the intensity of the reds in the image but 
* Dragging down on the Red Curve decreases the intensity of the reds and thus increases the apparent intensity of its complimentary color, cyan. Green’s complimentary color is magenta, and blue’s is yellow.
&lt;pre&gt;
 Red &lt;-&gt; Cyan
 Green &lt;-&gt;Magenta
 Blue &lt;-&gt;Yellow 
&lt;/pre&gt;

YUV Best option to analyse and pull out statistical elements of any picture (i.e.  separate luminance data from color data). The line in Y luma tone box represents the brightness of the image with the point in the bottom left been black, and the point in the top right as white.  A low-contrast image has a concentrated clump of values nearer to the center of the graph. By comparison, a high-contrast image has a wider distribution of values across the entire width of the Histogram.   A histogram that is skewed to the right would indicate a picture that is a bit overexposed because most of the color data is on the lighter side (increase exposure with higher value F), while a histogram with the curve on the left shows a picture that is underexposed. This is good information to have when using post-processing software because it shows you not only where the color data exists for a given picture, but also where any data has been clipped (extremes on edges of either side): that is, it does not exist and, therefore, cannot be edited.  By dragging the endpoints of the line and as well as the central one, can increased the dark/shadows, midtones and light/bright parts and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .

The U and V chroma parts show color difference components of the image. It’s useful for checking whether or not the overall chroma is too high, and also whether it’s being limited too much
Can be used to create a negative image but also 
With U (Cb), the higher value you are, the more you're on the blue primary color. If you go to the low values then you're on blue complementary color, i.e. yellow.
With V (Cr), this is the same principle but with Red and Cyan.
e.g. If you push U full blue and V full red, you get magenta. If you push U full yellow and V full Cyan then you get green.

YUV simultaneously adds to one side of the color equation while subtracting from the other.  
using YUV to do color correction can be very problematic because each curve alters the result of each other: the mutual influence between U and V often makes things tricky. You may also be careful in what you do to avoid the raise of noise (which happens very easily). Best results are obtained with little adjustments

sunset that looks uninspiring and needs some color pop especially for the rays over the hill, a subtle contrast raise while setting luma values back to the legal range without hard clipping.


====Lunapaint====

Pixel based drawing app with onion-skin animation function

 Blocking, Shading, Coloring, adding detail 

&lt;pre&gt;
b BRUSH
e ERASER

alt eyedropper 
v layer tool 

z ZOOM / MAGNIFY &lt; &gt; n 
spc panning 
m  marque 
q lasso 
w same color selection / region 
&lt;/pre&gt;

&lt;pre&gt;
, LM RM
v 
V
f  filter 
F 
.  size 

p 
,  pick color 
[] last / next color 
&lt;/pre&gt;


There is not much missing in Lunapaint to be as good as FlipBook and then you have to take into account that Flipbook is considered to be amongst the best and easiest to use animation software out there. Ok to be honest Flipbook has some nice features that require more heavy work but those aren't so much needed right away, things like camera effects, sound, smart fill, export to different movie file formats etc.

Tried Flipbook with my tablet and compared it to Luna. The feeling is the same when sketching. LunaPaint is very responsive/fluent to draw with. Just as Flipbook is, and that responsiveness is something its users have mentioned as one of the positive sides of said software.

 author was learning MUI. Some parts just have to be rewritten with proper MUI classes before new features can be added.

* add [Frame Add] / [Frame Del]
* whole animation feature is impossible to use. If you draw 2 color maybe but if you start coloring your cells then you get in trouble
* pickup the entire image as a brush, not just a selection ? And consequently remove the brush from memory when one doesn't need it anymore. can pick up a brush and put it onto a new image but cropping isn't possible, nor to load/save brushes.
* Undo is something I longed for ages in Lunapaint.
* to import into the current layer, other types of images (e.g. JPEG) besides RAW64.
* implement graphic tablet features support


**GENERAL DRAWING**

Miss it very much:
UNDO
ERASER
COLORPICKER - has to show on palette too which color got picked.
BACKGROUND COLOR -Possibility to select from &quot;New project screen&quot;

Miss it somewhat:
ICON for UNDO
ICON for ERASER
ICON for CLEAR SCREEN ( What can I say? I start over from scratch very often )
BRUSH - possibility to cut out as brush not just copy off image to brush

**ANIMATING**

Miss it very much:
NUMBER OF CELLS - Possibity to change total no. of cells during project
ANIM BRUSH - Possibility to pick up a selected part of cells into an animbrush

Miss it somewhat:
ADD/REMOVE FRAMES: Add/remove single frame

In general LunaPaint is really well done and it feels like a new DeluxePaint version. It works with my tablet. Sure there's much missing of course but things can always be added over time. So there is great potential in LunaPaint that's for sure. Animations could be made in it and maybe put together in QuickVideo, saving in .gif or .mng etc some day.


LAYERS
-Layers names don't get saved globally in animation frames
-Layers order don't change globally in an animation (perhaps as default?).

EXPORTING IMAGES
-Exporting frames to JPG/PNG gives problems with colors. (wrong colors. See my animatiopn --&gt; My robot was blue now it's &quot;gold&quot; ) I think this only happens if you have layers.
-Trying to flatten the layers before export doesn't work if you have animation frames only the one you have visible will flatten properly all other frames are destroyed. (Only one of the layers are visible on them)
-Exporting images filenames should be for example e.g. file0001, file0002...file0010 instead as of now file1, file2...file10

LOAD/SAVE (Preferences)
-Make a setting for the default &quot;Work&quot; folder.

* Destroyed colors if exported image/frame has layers 
* mystic color cycling of the selected color while stepping frames back/forth (annoying)

&lt;pre&gt;
Deluxe Paint II enhanced key shortcuts 
    NOTE: @ denotes the ALT key

    [Technique]

    F1  - Paint
    F2  - Single Colour
    F3  - Replace
    F4  - Smear
    F5  - Shade
    F6  - Cycle
    F7  - Smooth
     M  - Colour Cycle

    [Brush]

     B  - Restore
     O  - Outline
     h  - Halve brush size
     H  - Double brush size
     x  - Flip brush on X axis
     X  - Double brush size on X axis only
     y  - Flip on Y 
     Y  - Double on Y
     z  - Rotate brush 90 degrees
     Z  - Stretch

    [Stencil]

     `  - Stencil On

    [Miscellaneous]

    F9  - Info Bar
    F10 - Selection Bar
    @o  - Co-Ordinates
    @a  - Anti-alias
    @r  - Colourise
    @t  - Translucent
    TAB - Colour Cycle

    [Picture]

     L  - Load
     S  - Save
     j  - Page to Spare(Flip)
     J  - Page to Spare(Copy)
     V  - View Page
     Q  - Quit

    [General Keys]

     m  - Magnify
     &lt;  - Zoom In
     &gt;  - Zoom Out
     [  - Palette Colour Up
     ]  - Palette Colour Down
     (  - Palette Colour Left
     )  - Palette Colour Right
     ,  - Eye Dropper
     .  - Pixel / Brush Toggle
     /  - Symmetry
     |  - Co-Ordinates
    INS - Perspective Control
    +/- - Brush Size (Fine Control)
     w  - Unfilled Polygon
     W  - Filled Polygon
     e  - Unfilled Ellipse
     E  - Filled Ellipse
     r  - Unfilled Rectangle
     R  - Filled Rectangle
     t  - Type/text tool
     a  - Select Font
    u/U - Undo
     d  - Brush
     D  - Filled Non-Uniform Polygon
    f/F - Fill Options
    g/G - Grid
    h/H - Brush Size (Coarse Control)
     K  - Clear
     c  - Unfilled Circle
     C  - Filled Circle
     v  - Line
     b  - Scissor Select and Toggle
     B  - Brush
    {,} - Toggle between two background colours
&lt;/pre&gt;

====Lodepaint====

Pixel based painting artwork app

====Grafx2====

Pixel based painting artwork app aesprite like 

[https://www.youtube.com/watch?v=59Y6OTzNrhk aesprite workflow keys and tablet use], [], 


====Vector Graphics ZuneFIG====

Vector Image Editing of files .svg .ps .eps


*Objects - raise lower rotate flip aligning snapping 
*Path - unify subtract intersect exclude divide 
*Colour - fill stroke 
*Stroke - size 
*Brushes - 
*Layers - 
*Effects - gaussian bevels glows shadows 
*Text    - 
*Transform - 


 AmiFIG ([http://epb.lbl.gov/xfig/frm_introduction.html xfig manual]) 

[[File:MyScreen.png|thumb|left|alt=Showing all Windows open in AmiFIG.|All windows available to AmiFIG.]]

for drawing simple to intermediate vector graphic images for scientific and technical uses and for illustration purposes for those with talent

;Menu options
* Load - fig format but import(s) SVG
* Save - fig format but export(s) eps, ps, pdf, svg and png
* PAN = Ctrl + Arrow keys 
* Deselect all points

There is no selected object until you apply the tool, and the selected object is not highlighted.

;Metrics - to set up page and styles - first window to open on new drawings

;Tools - Drawing Primitives - set Attributes window first before clicking any Tools button(s) 
* Shapes - circles, ellipses, arcs, splines, boxes,  polygon 
* Lines - polylines
* Text &quot;T&quot; button 
* Photos - bitmaps
* Compound - Glue, Break, Scale 
* POINTs - Move, Add, Remove 
* Objects - Move, Copy, Delete, Mirror, Rotate, Paste 
use right mouse button to stop extra lines, shapes being formed and the left mouse to select/deselect tools button(s)
* Rotate - moves in 90 degree turns centered on clicked POINT of a polygon or square

;Attributes which provide change(s) to the above primitives 
* Color
* Line Width
* Line Style
* arrowheads

;Modes 
Choose from freehand, charts, figures, magnet, etc.

;Library - allows .fig clip-art to be stored 
* compound tools to add .fig(s) together

;FIG 3.2 [http://epb.lbl.gov/xfig/fig-format.html Format] as produced by xfig version 3.2.5 
&lt;pre&gt;
Landscape
Center
Inches
Letter 
100.00
Single
-2
1200 2
4 0 0 50 -1 0 12 0.0000 4 135 1050 1050 2475 This is a test.01
&lt;/pre&gt;

# change the text alignment within the textbox. I can choose left, center, or right aligned by either changing the integer in the second column from 0 (left) to 1 or 2 (center, or right). 
# The third integer in the row specifies fontcolor. For instance, 0 is black, but blue is 1 and Green3 is 13.
# The sixth integer in the bottom row specifies fontface. 0 is Times-Roman, but 16 is Helvetica (a MATLAB default).
# The seventh number is fontsize. 12 represents a 12pt fontsize. Changing the fontsize of an item really is as easy as changing that number to 20.
# The next number is the counter-clockwise angle of the text. Notice that I have changed the angle to .7854 (pi/4 rounded to four digits=45 degrees).
# twelfth number is the position according to the standard “x-axis” in Xfig units from the left. Note that 1200 Xfig units is equivalent to once inch.
# thirteenth number is the “y-position” from the top using the same unit convention as before.

* The nested text string is what you entered into the textbox.
* The “01″ present at the end of that line in the .fig file is the closing tag. For instance, a change to \100 appends a @ symbol at the end of the period of that sentence.

; Just to note there are no layers, no 3d functions, no shading, no transparency, no animation


[[#top|...to the top]]

===Audio===


# AHI uses linear panning/balance, which means that in the center, you will get -6dB. If an app uses panning, this is what you will get. Note that apps like Audio Evolution need panning, so they will have this problem.

# When using AHI Hifi modes, mixing is done in 32-bit and sent as 32-bit data to the driver. The Envy24HT driver uses that to output at 24-bit (always).

# For the Envy24/Envy24HT, I've made 16-bit and 24-bit inputs (called Line-in 16-bit, Line-in 24-bit etc.). There is unfortunately no app that can handle 24-bit recording.


====Music Mods====

Digital module (mods) trackers are music creation software using samples and sometimes soundfonts, audio plugins (VST, AU or RTAS), MIDI.

Generally, MODs are similar to MIDI in that they contain note on/off and other sequence messages that control the mod player. Unlike (most) midi files, however, they also contain sound samples that the sequence information actually plays. MOD files can have many channels (classic amiga mods have 4, corresponding to the inbuilt sound channels), but unlike MIDI, each channel can typically play only one note at once. However, since that note might be a sample of a chord, a drumloop or other complex sound, this is not as limiting as it sounds.

Like MIDI, notes will play indefinitely if they're not instructed to end. Most trackers record this information automatically if you play your music in live. If you're using manual note entry, you can enter a note-off command with a keyboard shortcut - usually Caps Lock.

In fact when considering file size MOD is not always the best option. Even a dummy song wastes few kilobytes for nothing when a simple SID tune could be few hundreds bytes and not bigger than 64kB. AHX is another small format, AHX tunes are never larger than 64kB excluding comments.

[https://www.youtube.com/watch?v=rXXsZfwgil Protrekkr] (previously aka [w:Juan_Antonio_Arguelles_Rius|NoiseTrekkr])

If Protrekkr does not start, please check if the Unit 0 has been setup in the AHI prefs and still not, go to the directory utilities/protrekkr and double click on the Protrekkr icon

*Sample
*Note - Effect 
*Track (column) - Pattern - Order

It all starts with the Sample which is used to create Note(s) in a Track (column of a tracker) 
The Note can be changed with an Effect.  A Track of Note(s) can be collected into a Pattern (section of a song) and these can be given Order to create the whole song.

Patience (notes have to be entered one at a time) or playing the bassline on a midi controller (faster - see midi section above).  Best approach is to wait until a melody popped into your head.

*Up-tempo means the track should be reasonably fast, but not super-fast. 
*Groovy and funky imply the track should have some sort of &quot;swing&quot; feel, with plenty of syncopation or off beat emphasis and a recognizable, melodic bass line. 
*Sweet and happy mean upbeat melodies, a major key and avoiding harsh sounds.
*Moody - minor key

First, create a quick bass sound, which is basically a sine wave, but can be hand drawn for a little more variance. It could also work for the melody part, too.

This is usually a bass guitar or some kind of synthesizer bass. The bass line is often forgotten by inexperienced composers, but it plays an important role in a musical piece. Together with the rhythm section the bass line forms the groove of a song. It's the glue between the rhythm section and the melodic layer of a song.

The drums are just pink noise samples, played at different frequencies to get a slightly different sound for the kick, snare, and hihats.

Instruments that fall into the rhythm category are bass drums, snares, hi-hats, toms, cymbals, congas, tambourines, shakers, etc. Any percussive instrument can be used to form part of the rhythm section.

The lead is the instrument that plays the main melody, on top of the chords. There are many instruments that can play a lead section, like a guitar, a piano, a saxophone or a flute. The list is almost endless. There is a lot of overlap with instruments that play chords. Often in one piece an instrument serves both roles. The lead melody is often played at a higher pitch than the chords.

Listened back to what was produced so far, and a counter-melody can be imagined, which can be added with a triangle wave.

To give the ends of phrases some life, you can add a solo part with a crunchy synth. By hitting random notes in the key of G, then edited a few of them.

For the climax of the song, filled out the texture with a gentle high-pitch pad… …and a grungy bass synth.


The arrow at A points at the pattern order list. As you see, the patterns don't have to be in numerical order. This song starts with pattern &quot;00&quot;, then pattern &quot;02&quot;, then &quot;03&quot;, then &quot;01&quot;, etcetera. Patterns may be repeated throughout a song.

The B arrow points at the song title. Below it are the global BPM and speed parameters. These determine the tempo of the song, unless the tempo is altered through effect commands during the song.

The C arrow points at the list of instruments. An instrument may consist of multiple samples. Which sample will be played depends on the note. This can be set in the Instrument Editing screen. Most instruments will consist of just one sample, though. The sample list for the selected instrument can be found under arrow D.

Here's a part of the main editing screen. This is where you put in actual notes. Up to 32 channels can be used, meaning 32 sounds can play simultaneously. The first six channels of pattern &quot;03&quot; at order &quot;02&quot; are shown here. The arrow at A points at the row number. The B arrow points at the note to play, in this case a C4. The column pointed at by the C arrow tells us which instrument is associated with that note, in this case instrument #1 &quot;Kick&quot;.

The column at D is used (mainly) for volume commands. In this case it is left empty which means the instrument should play at its default volume. You can see the volume column being used in channel #6.

The E column tells us which effect to use and any parameters for that effect. In this case it holds the &quot;F&quot; effect, which is a tempo command. The &quot;04&quot; means it should play at tempo 4 (a smaller number means faster).

Base pattern

When I create a new track I start with what I call the base pattern. It is worthwhile to spend some time polishing it as a lot of the ideas in the base pattern will be copied and used in other patterns. At least, that's how I work. Every musician will have his own way of working. In &quot;Wild Bunnies&quot; the base pattern is pattern &quot;03&quot; at order &quot;02&quot;.

In the section about selecting samples I talked about the four different categories of instruments: drums, bass, chords and leads. That's also how I usually go about making the base pattern. I start by making a drum pattern, then add a bass line, place some chords and top it off with a lead. This forms the base pattern from which the rest of the song will grow.


Drums

Here's a screenshot of the first four rows of the base pattern. I usually reserve the first four channels or so for the drum instruments. Right away there are a couple of tricks shown here. In the first channel the kick, or bass drum, plays some notes. Note the alternating F04 and F02 commands. The &quot;F&quot; command alters the tempo of the song and by quickly alternating the tempo; the song will get some kind of &quot;swing&quot; feel.

In the second channel the closed hi-hat plays a fairly simple pattern. Further down in the channel, not shown here, some open hi-hat notes are added for a bit of variation.

In the third and fourth channel the snare sample plays. The &quot;8&quot; command is for panning. One note is panned hard to the left and the other hard to the right. One sample is played a semitone lower than the other. This results in a cool flanging effect. It makes the snare stand out a little more in the mix.


Bass line

There are two different instruments used for the bass line. Instrument #6 is a pretty standard synthesized bass sound. Instrument #A sounds a bit like a slap bass when used with a quick fade out. By using two different instruments the bass line sounds a bit more ”human”. The volume command is used to cut off the notes. However, it is never set to zero. Setting the volume to a very small value will result in a reverb-like effect. This makes the song sound more &quot;live&quot;.

The bass line hints at the chords that will be played and the key the song will be in. In this case the key of the song is D-major, a positive and happy key.


Chords

The D major chords that are being played here are chords stabs; short sounds with a quick decay (fade out). Two different instruments (#8 and #9) are used to form the chords. These instruments are quite similar, but have a slightly different sound, panning and volume decay. Again, the reason for this is to make the sound more human. The volume command is used on some chords to simulate a delay, to achieve more of a live feel. The chords are placed off-beat making for a funky rhythm.


Lead

Finally the lead melody is added. The other instruments are invaluable in holding the track together, but the lead melody is usually what catches people's attention.

A lot of notes and commands are used here, but it looks more complex than it is. A stepwise ascending melody plays in channel 13. Channel 14 and 15 copy this melody, but play it a few rows later at a lower volume. This creates an echo effect. A bit of panning is used on the notes to create some stereo depth. Like with the bass line, instead of cutting off notes the volume is set to low values for a reverb effect. The &quot;461&quot; effect adds a little vibrato to the note, which sounds nice on sustained notes.

Those paying close attention may notice the instrument used here for the lead melody is the same as the one used for the bass line (#6 &quot;Square&quot;), except played two or three octaves higher. This instrument is a looped square wave sample. Each type of wave has its own quirks, but the square wave (shown below) is a really versatile wave form.

Song structure

Good, catchy songs are often carefully structured into sections, some of which are repeated throughout the song with small variations.

A typical pop-song structure is: Intro - Verse - Chorus - Verse - Chorus - Bridge - Chorus.

Other single sectional song structures are

&lt;pre&gt;
Strophic or AAA Song Form - oldest story telling with refrain (often title of the song) repeated in every verse section melody 
AABA Song Form - early popular, jazz and gospel fading during the 1960s 
AB or Verse/Chorus Song Form - songwriting format of choice for modern popular music since the 1960s 
Verse/Chorus/Bridge Song Form
ABAB Song Form
ABAC Song Form
ABCD Song Form
AAB 12-Bar Song Form - three four-bar lines or sub-sections 
8-Bar Song Form
16-Bar Song Form
Hybrid / Compound Song Forms
&lt;/pre&gt;

The most common building blocks are:

#INTRODUCTION(INTRO)
#VERSE
#REFRAIN
#PRE-CHORUS / RISE / CLIMB
#CHORUS
#BRIDGE
#MIDDLE EIGHT
#SOLO / INSTRUMENTAL BREAK
#COLLISION
#CODA / OUTRO
#AD LIB (OFTEN IN CODA / OUTRO)

The chorus usually has more energy than the verse and often has a memorable melody line. As the chorus is repeated the most often during the song, it will be the part that people will remember.

The bridge often marks a change of direction in the song. It is not uncommon to change keys in the bridge, or at least to use a different chord sequence. The bridge is used to build up tension towards the big finale, the last repetition of chorus.


 Playing

RCTRL:                           Play song from row 0.

LSHIFT + RCTRL:                  Play song from current row.

RALT:                            Play pattern from row 0.

LSHIFT + RALT:                   Play pattern from current row.

Left mouse on '&gt;':               Play song from row 0.

Right mouse on '&gt;':              Play song from current row.

Left mouse on '|&gt;':              Play pattern from row 0.

Right mouse on '|&gt;':             Play pattern from current row.

Left mouse on 'Edit/Record':     Edit mode on/off.

Right mouse on 'Edit/Record':    Record mode on/off.


 Editing 


LSHIFT + ESCAPE:                 Switch large patterns view on/off

TAB:                    Go to next track

LSHIFT + TAB:                    Go to prev. track

LCTRL + TAB:                    Go to next note in track

LCTRL + LSHIFT + TAB:           Go to prev. note in track

SPACE:                           Toggle Edit mode On &amp; Off

(Also stop if the song is being played)

SHIFT SPACE:                     Toggle Record mode On &amp; Off

(Wait for a key note to be pressed

or a midi in message to be received)

DOWN ARROW:                      1 Line down

UP ARROW:                        1 Line up

LEFT ARROW:                      1 Row left

RIGHT ARROW:                     1 Row right

PREV. PAGE:                      16 Arrows Up

NEXT PAGE:                       16 Arrows Down

HOME / END:                      Top left / Bottom right of pattern

LCTRL + HOME / END:              First / last track

F5, F6, F7, F8, F9:              Jump to 0, 1/4, 2/4, 3/4, 4/4 lines of the patterns

+ - (Numeric keypad):           Next / Previous pattern

LCTRL + LEFT / RIGHT:           Next / Previous pattern

LCTRL + LALT + LEFT / RIGHT:    Next / Previous position

LALT + LEFT / RIGHT:           Next / Previous instrument

LSHIFT + M:                      Toggle mute state of the current channel

LCTRL + LSHIFT + M:             Solo the current track / Unmute all

LSHIFT + F1 to F11:              Select a tab/panel

LCTRL + 1 to 4:                 Select a copy buffer


 Tracking 

1st and 2nd keys rows:           Upper octave row

3rd and 4th keys rows:           Lower octave row

RSHIFT:                          Insert a note off

/ and * (Numeric keypad)

or F1 F2:                        -1 or +1 octave

INSERT / BACKSPACE:              Insert or Delete a line in current track

or current selected block.

LSHIFT + INSERT / BACKSPACE:     Insert or Delete a line in current pattern

DELETE (NOT BACKSPACE):          Empty a column or a selected block.


 Blocks

(Blocks can also be selected with the mouse by holding the right button and scrolling the pattern with the mouse wheel).


LCTRL + A:          Select entire current track

LCTRL + LSHIFT + A: Select entire current pattern

LALT + A:          Select entire column note in a track

LALT + LSHIFT + A: Select all notes of a track

LCTRL + X:          Cut the selected block and copy it into the block-buffer

LCTRL + C:          Copy the selected block into the block-buffer

LCTRL + V:          Paste the data from the block buffer into the pattern

LCTRL + I:          Interpolate selected data from the first to the last row of a selection

LSHIFT + ARROWS

PREV. PAGE

NEXT PAGE: Select a block

LCTRL + R:          Randomize the select columns of a selection, works similar to CTRL + I (interpolating them)

LCTRL + U:          Transpose the note of a selection to 1 seminote higher

LCTRL + D:          Transpose the note of a selection to 1 seminote lower

LCTRL + LSHIFT + U: Transpose the note of a selection to 1 seminote higher (only for the current instrument)

LCTRL + LSHIFT + D: Transpose the note of a selection to 1 seminote lower  (only for the current instrument)

LCTRL + H:          Transpose the note of a selection to 1 octave higher

LCTRL + L:          Transpose the note of a selection to 1 octave lower

LCTRL + LSHIFT + H: Transpose the note of a selection to 1 octave higher (only for the current instrument)

LCTRL + LSHIFT + L: Transpose the note of a selection to 1 octave lower (only for the current instrument)

LCTRL + W:          Save the current selection into a file


 Misc 


LALT + ENTER:     Switch between full screen / windowed mode

LALT + F4:        Exit program (Windows only)

LCTRL + S:         Save current module

LSHIFT + S:         Switch top right panel to synths list

LSHIFT + I:         Switch top right panel to instruments list


&lt;pre&gt;
C-x   xh xx xx hhhh             Volume 
B-x   xh xx xx hhhh             Jump to 
A#x  xh xx xx hhhh hhhh   Slide 
F-x    xh xx xx hhhh            Tempo 
D-x   xh xx xx hhhh             Pattern Break 
G#x  xh xx xx hhhh
&lt;/pre&gt;

h Hex 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13

d Dec 01 02 03 04 05 06 07 08 09 10  11 12 13 14 15 16 17 18 19

The Set Volume command: C. Input a note, then move the cursor to the effects command column and type a C. Play the pattern, and you shouldn't be able to hear the note you placed the C by. This is because the effect parameters are 00. Change the two zeros to a 40(Hex)/64(Dec), depending on what your tracker uses. Play back the pattern again, and the note should come in at full volume.

The Position Jump command next. This is just a B followed by the position in the playing list that you want to jump to. One thing to remember is that the playing list always starts at 0, not 1. This command is usually in Hex.

Onto the volume slide command: A. This is slightly more complex (much more if you're using a newer tracker, if you want to achieve the results here, then set slides to Amiga, not linear), due to the fact it depends on the secondary tempo. For now set a secondary tempo of 06 (you can play around later), load a long or looped sample and input a note or two. A few rows after a note type in the effect command A. For the parameters use 0F. Play back the pattern, and you should notice that when the effect kicks in, the sample drops to a very low volume very quickly. Change the effect parameters to F0, and use a low volume command on the note. Play back the pattern, and when the slide kicks in the volume of the note should increase very quickly.
This because each part of the effect parameters for command A does a different thing. The first number slides the volume up, and the second slides it down. It's not recommended that you use both a volume up and volume down at the same time, due to the fact the tracker only looks for the first number that isn't set to 0. If you specify parameters of 8F, the tracker will see the 8, ignore the F, and slide the volume up. Using a slide up and down at same time just makes you look stupid. Don't do it...

The Set Tempo command: F, is pretty easy to understand. You simply specify the BPM (in Hex) that you want to change to. One important thing to note is that values of lower than 20 (Hex) sets the secondary tempo rather than the primary.

Another useful command is the Pattern Break: D. This will stop the playing of the current pattern and skip to the next one in the playing list. By using parameters of more than 00 you can also specify which line to begin playing from.

Command 3 is Portamento to Note. This slides the currently playing note to another note, at a specified speed. The slide then stops when it reaches the desired note. 
&lt;pre&gt;
   C-2 1 000 - Starts the note playing
   ---      000
   C-3    330 - Starts the slide to C-3 at a speed of 30.
   ---     300 - Continues the slide
   ---     300 - Continues the slide
&lt;/pre&gt;
Once the parameters have been set, the command can be input again without any parameters, and it'll still perform the same function unless you change the parameters. This memory function allows certain commands to function correctly, such as command 5, which is the Portamento to Note and Volume Slide command. Once command 3 has been set up command 5 will simply take the parameters from that and perform a Portamento to Note. Any parameters set up for command 5 itself simply perform a Volume Slide identical to command A at the same time as the Portamento to Note.

This memory function will only operate in the same channel where the original parameters were set up.
There are various other commands which perform two functions at once. They will be described as we come across them.

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  00

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  02

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  05

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  08

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0A

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0D

C-3  04  ..  ..  09  10 ---&gt; C-3  04  ..  ..  09  10

(You can also switch on the Slider Rec to On, and perform parameter-live-recording, such as cutoff transitions, resonance or panning tweaking, etc..)  Note: this command only works for volume/panning and fx datas columns.


The next command we'll look at is the Portamento up/down: 1 and 2. Command 1 slides the pitch up at a specified speed, and 2 slides it down. This command works in a similar way to the volume slide, in that it is dependent on the secondary tempo. Both these commands have a memory dependent on each other, if you set the slide to a speed of 3 with the 1 command, a 2 command with no parameters will use the speed of 3 from the 1 command, and vice versa.

Command 4 is Vibrato. Vibrato is basically rapid changes in pitch, just try it, and you'll see what I mean. Parameters are in the format of xy, where x is the speed of the slide, and y is the depth of the slide. One important point to remember is to keep your vibratos subtle and natural so a depth of 3 or less and a reasonably fast speed, around 8, is usually used. Setting the depth too high can make the part sound out of tune from the rest.
Following on from command 4 is command 6. This is the Vibrato and Volume Slide command, and it has a memory like command 5, which you already know how to use.

Command 7 is Tremolo. This is similar to vibrato. Rather than changing the pitch it slides the volume. The effect parameters are in exactly the same format.   vibrato effect (0x1dxy) x = speed y = depth (can't be used if arpeggio (0x1b) is turned on) 

&lt;pre&gt;
 C-7 00 .. .. 1B37 &lt;-  Turn Arpeggio effect on
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B38 &lt;- Change datas
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B00 &lt;- Turn it off
&lt;/pre&gt;

Command 9 is Sample Offset. This starts the playback of the sample from a different place than the start. The effect parameters specify the sample offset, but only very roughly. Say you have a sample which is 8765(Hex) bytes long, and you wanted it to play from position 4321(Hex). The effect parameter could only be as accurate as the 43 part, and it would ignore the 21.

Command B is the Playing List/Order Jump command. The parameters specify the position in the Playing List/Order to jump to. When used in conjunction with command D you can specify the position and the line to play from.

Command E is pretty complex, as it is used for a lot of different things, depending on what the first parameter is. Let's take a trip through each effect in order.
Command E0 controls the hardware filter on an Amiga, which, as a low pass filter, cuts off the highest frequencies being played back. There are very few players and trackers on other system that simulate this function, not that you should need to use it. The second parameter, if set to 1, turns on the filter. If set to 0, the filter gets turned off.

Commands E1/E2 are Fine Portamento Up/Down. Exactly the same functions as commands 1/2, except that they only slide the pitch by a very small amount. These commands have a memory the same as 1/2 as well.

Command E3 sets the Glissando control. If parameters are set to 1 then when using command 3, any sliding will only use the notes in between the original note and the note being slid to. This produces a somewhat jumpier slide than usual. The best way to understand is to try it out for yourself. Produce a slow slide with command 3, listen to it, and then try using E31.

Command E4 is the Set Vibrato Waveform control. This command controls how the vibrato command slides the pitch. Parameters are 0 - Sine, 1 - Ramp Down (Saw), 2 - Square. By adding 4 to the parameters, the waveform will not be restarted when a new note is played e.g. 5 - Sine without restart.

Command E5 sets the Fine Tune of the instrument being played, but only for the particular note being played. It will override the default Fine Tune for the instrument. The parameters range from 0 to F, with 0 being -8 and F being +8 Fine Tune. A parameter of 8 gives no Fine Tune. If you're using a newer tracker that supports more than -8 to +8 e.g. -128 to +128, these parameters will give a rough Fine Tune, accurate to the nearest 16.

Command E6 is the Jump Loop command. You mark the beginning of the part of a pattern that you want to loop with E60, and then specify with E6x the end of the loop, where x is the number of times you want it to loop.

Command E7 is the Set Tremolo Waveform control. This has exactly the same parameters as command E4, except that it works for Tremolo rather than Vibrato.

Command E9 is for Retriggering the note quickly. The parameter specifies the interval between the retrigs. Use a value of less than the current secondary tempo, or else the note will not get retrigged.

Command EA/B are for Fine Volume Slide Up/Down. Much the same as the normal Volume Slides, except that these are easier to control since they don't depend on the secondary tempo. The parameters specify the amount to slide by e.g. if you have a sample playing at a volume of 08 (Hex) then the effect EA1 will slide this volume to 09 (Hex). A subsequent effect of EB4 would slide this volume down to 05 (Hex).

Command EC is the Note Cut. This sets the volume of the currently playing note to 0 at a specified tick. The parameters should be lower than the secondary tempo or else the effect won't work.

Command ED is the Note Delay. This should be used at the same time as a note is to be played, and the parameters will specify the number of ticks to delay playing the note. Again, keep the parameters lower than the secondary tempo, or the note won't get played!

Command EE is the Pattern Delay. This delays the pattern for the amount of time it would take to play a certain number of rows. The parameters specify how many rows to delay for.

Command EF is the Funk Repeat command. Set the sample loop to 0-1000. When EFx is used, the loop will be moved to 1000- 2000, then to 2000-3000 etc. After 9000-10000 the loop is set back to 0- 1000. The speed of the loop &quot;movement&quot; is defined by x. E is two times as slow as F, D is three times as slow as F etc. EF0 will turn the Funk Repeat off and reset the loop (to 0-1000).

effects 0x41 and 0x42 to control the volumes of the 2 303 units

There is a dedicated panel for synth parameter editing with coherent sections (osc, filter modulation, routing, so on) the interface is much nicer, much better to navigate with customizable colors, the reverb is now customizable (10 delay lines), It accepts newer types of Waves (higher bit rates, at least 24). Has a replay routine.

It's pretty much your basic VA synth. The problem isn't with the sampler being to high it's the synth is tuned two octaves too low, but if you want your samples tuned down just set the base note down 2 octaves (in the instrument panel).

so the synth is basically divided into 3 sections from left to right: oscillators/envelopes, then filter and LFO's, and in the right column you have mod routings and global settings.

for the oscillator section you have two normal oscillators (sine, saw, square, noise), the second of which is tunable, the first one tunes with the key pressed. Attached to OSC 1 is a sub-oscillator, which is a sawtooth wave tuned one octave down. The phase modulation controls the point in the duty cycle at which the oscillator starts. The ADSR envelope sliders (grouped with oscs) are for modulation envelope 1 and 2 respectively. you can use the synth as a sampler by choosing the instrument at the top.

In the filter column, the filter settings are: 1 = lowpass, 2 = highpass, 3 = off. cutoff and resonance. For the LFOs they are LFO 1 and LFO 2, the ADSR sliders in those are for the LFO itself.

For the modulation routings you have ENV 1, LFO 1 for the first slider and ENV 2, LFO 2 for the second, you can cycle through the individual routings there, and you can route each modulation source to multiple destinations of course, which is another big plus for this synth. Finally the glide time is for portamento and master volume, well, the master volume... it can go quite loud.

The sequencer is changed too, It's more like the one in AXS if you've used that, where you can mute tracks to re-use patterns with variation.


&lt;pre&gt;
Support for the following modules formats:
669 (Composer 669, Unis 669), 
AMF (DSMI Advanced Module Format), 
AMF (ASYLUM Music Format V1.0), 
APUN (APlayer), DSM (DSIK internal format), 
FAR (Farandole Composer), 
GDM (General DigiMusic), 
IT (Impulse Tracker), 
IMF (Imago Orpheus), 
MOD (15 and 31 instruments), 
MED (OctaMED), 
MTM (MultiTracker Module editor), 
OKT (Amiga Oktalyzer), 
S3M (Scream Tracker 3), 
STM (Scream Tracker), 
STX (Scream Tracker Music Interface Kit), 
ULT (UltraTracker), 
UNI (MikMod), 
XM (FastTracker 2),
Mid (midi format via timidity)
&lt;/pre&gt;


Possible plugin options include [http://lv2plug.in/ LV2],


====Midi - Musical Instrument Digital Interface====

A midi file typically contains music that plays on up to 16 channels (as per the midi standard), but many notes can simultaneously play on each channel (depending on the limit of the midi hardware playing it).

'''Timidity'''

Although usually already installed, you can uncompress the [http://www.libsdl.org/projects/SDL_mixer/ timidity.tar.gz (14MB)] into a suitable drawer like below's SYS:Extras/Audio/ 
 assign timidity: SYS:Extras/Audio/timidity
added to SYSːs/User-Startup

'''WildMidi playback'''


'''Audio Evolution 4 (2003) 4.0.23 (from 2012)'''


*Sync Menu    - CAMD Receive, Send checked 
*Options Menu - MIDI Machine Control - Midi Bar Display - Select CAMD MIDI in / out - Midi Remote Setup 


MCB Master Control Bus 
*Sending a MIDI start-command and a Song Position Pointer, you can synchronize audio with an external MIDI sequencer (like B&amp;P). 
*B&amp;P Receive, start AE, add AudioEvolution.ptool in Bars&amp;Pipes track, press play / record in AE then press play in Pipes 
*CAMD Receive, receive MIDI start or continue commands via camd.library sync to AE 


*MIDI Machine Control
*Midi Bar Display 
*Select CAMD MIDI in / out
*Midi Remote Setup - open requester for external MIDI controllers to control app mixer and transport controls cc remotely 
 Channel   - mixer(vol, pan, mute, solo), eq, aux, fx, 
 Subgroup  - Volume, Mute, Solo 
 Transport - Start, End, Play, Stop, Record, Rewind, Forward 
 Misc      - Master vol., Bank Down, Bank up 


&lt;pre&gt;
q        - quit 

First 3 already opened when AE started 
F1       - timeline window
F2       - mixer 
F3       - control 
F4       - subgroups 
F5       - aux returns 
F6       - sample list 

i        - Load sample to use 

space    - start/stop play 
b        - reset time 0:00


s        - split mode 
r        - open recording window 
a        - automation edit mode with p panning, m mute and v volume 


[ / ]    - zoom in / out 
:        - previous track
*        - next track 

x c v f  - cut copy paste cross-fade 
g        - snap grid 


&lt;/pre&gt;


 '''[http://bnp.hansfaust.de/ Bars n Pipes sequencer]'''

 BarsnPipes debug ... in shell 

Menu (right mouse)  
*Song        - Songs load and save in .song format but option here to load/save Midi_Files .mid in FORMAT0 or FORMAT1 
*Track       - 
*Edit        -
*Tool        - 
*Timing      - SMTPE Synchronizing 
*Windows     - 
*Preferences - Multiple MIDI-in option 

Windows (some of these are usually already opened when Bars n Pipes starts up for the first time) 
*Workflow -&gt; Tracks, .... Song Construction, Time-line Scoring, Media Madness, Mix Maestro, 
*Control  -&gt; Transport (or mini one), Windows (which collects all the Windows icons together-shortcut), .... Toolbox, Accessories, Metronome, 

Once you have your windows placed on the screen that suits your workflow, Song -&gt; Save as Default will save the positions, colors, icons, etc as you'd like them 

If you need a particular setup of Tracks, Tools, Tempos etc, you save them all as a new song you can load each time 

Right mouse menu -&gt; Preferences -&gt; Environment... -&gt; ScreenMode  - Linkages for Synch (to Slave) usbmidi.out.0 and Send (Master) usbmidi.in.0 - Clock MTC 


'''Tracks'''

#Double-click on B&amp;P's icon. B&amp;P will then open with an empty Song. You can also double-click on a song icon to open a song in B&amp;P.
#Choose a track. The B&amp;P screen will contain a Tracks Window with a number of tracks shown as pipelines (Track 1, Track 2, etc...). To choose a track, simply click on the gray box to show an arrow-icon to highlight it. This icon show whether a track is chosen or not. To the right of the arrow-icon, you can see the icon for the midi-input. If you double-click on this icon you can change the MIDI-in setup.
#Choose Record for the track. To the right of the MIDI-input channel icon you can see a pipe. This leads to another clickable icon with that shows either P, R or M. This stands for Play, Record or Merge. To change the icon, simply click on it. If you choose P, this track can only play the track (you can't record anything). If you choose R, you can record what you play and it overwrites old stuff in the track. If you choose M, you merge new records with old stuff in the track. Choose R now to be able to make a record.
#Chose MIDI-channel. On the most right part of the track you can see an icon with a number in it. This is the MIDI-channel selector. Here you must choose a MIDI-channel that is available on your synthesizer/keyboard. If you choose General MIDI channel 10, most synthesizer will play drum sounds. To the left of this icon is the MIDI-output icon. Double-click on this icon to change the MIDI-output configuration.
#Start recording. The next step is to start recording. You must then find the control buttons (they look like buttons on a CD-player). To be able to make a record. you must click on the R icon. You can simply now press the play button (after you have pressed the R button) and play something on you keyboard. To playback your composition, press the Play button on the control panel.
#Edit track. To edit a track, you simply double click in the middle part of a track. You will then get a new window containing the track, where you can change what you have recorded using tools provided. Take also a look in the drop-down menus for more features.


Videos to help understand [https://www.youtube.com/watch?v=A6gVTX-9900 small intro], [https://www.youtube.com/watch?v=abq_rUTiSA4&amp;t=3s Overview], [https://www.youtube.com/watch?v=ixOVutKsYQo Workplace Setup CC PC Sysex], [https://www.youtube.com/watch?v=dDnJLYPaZTs Import Song], [https://www.youtube.com/watch?v=BC3kkzPLkv4 Tempo Mapping], [https://www.youtube.com/watch?v=sd23kqMYPDs ptool Arpeggi-8], [https://www.youtube.com/watch?v=LDJq-YxgwQg  PlayMidi Song], [https://www.youtube.com/watch?v=DY9Pu5P9TaU Amiga Midi], [https://www.youtube.com/watch?v=abq_rUTiSA4 Learning Amiga bars and Pipes], 

Groups like [https://groups.io/g/barsnpipes/topics this] could help 


'''Tracks window'''

* blue &quot;1 2 3 4 5 6 7 8 Group&quot; and transport tape deck VCR-type controls
* Flags 
* [http://theproblem.alco-rhythm.com/org/bp.html Track 1, Track2, to Track 16, on each Track there are many options that can be activated] 

Each Track has a 

*Left LHS  - Click in grey box to select what Track to work on, Midi-In ptool icon should be here (5pin plug icon), and many more from the Toolbox on the Input Pipeline 
*Middle    - (P, R, M) Play, Record, Merge/Multi before the sequencer line and a blue/red/yellow (Thru Mute Play) Tap 
*Right RHS - Output pipeline, can have icons placed uopn it with the final ptool icon(s) being the 5pin icon symbol for Midi-OUT 

Clogged pipelines may need Esc pressed several times 


'''Toolbox (tools affect the chosen pipeline)'''

After opening the Toolbox window you can add extra Tools (.ptool) for the pipelines like keyboard(virtual), midimonitor, quick patch, transpose, triad, (un)quantize, feedback in/out, velocity etc
 right mouse -&gt; Toolbox menu option -&gt; Install Tool... and navigate to Tool drawer (folder) and select requried .ptool 

Accompany B tool to get some sort of rythmic accompaniment, Rythm Section and Groove Quantize are examples of other tools that make use of rythms
[https://aminet.net/search?query=bars Bars &amp; Pipes pattern format .ptrn] for drawer (folder). Load from the Menu as Track or Group 


'''Accessories (affect the whole app)''' 

Accessories -&gt; Install... and goto the Accessories drawer for .paccess like adding ARexx scripting support 


'''Song Construction'''
&lt;pre&gt;
F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Duplicator 
F5  Eraser 
F6  Toolpad 
F7  Bounding box 
F8  Lock to A-B-A 

A-B-A strip, section, edit flags, white boxes, 

&lt;/pre&gt;


Bars&amp;Pipes Professional offers three track formats; basic song tracks, linear tracks — which don't loop — and finally real‑time tracks. The difference between them is that both song and linear tracks respond to tempo changes, while real‑time tracks use absolute timing, always trigger at the same instant regardless of tempo alterations 

'''Tempo Map'''

F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Eraser 
F5  Curve 
F6  Toolpad 


Compositions

Lyrics, Key, Rhythm, Time Signature 

'''Master Parameters'''

Key, Scale/Mode

'''Track Parameters'''

Dynamics 


'''Time-line Scoring'''


'''Media Madness'''


'''Mix Maestro'''


*ACCESSORIES         Allows the importation of other packages and additional modules 
*CLIPBOARD           Full cut, copy and paste operations, enabling user‑definable clips to be shared between tracks.
*INFORMATION         A complete rundown on the state of the current production and your machine.
*MASTER PARAMETERS   Enables global definition of time signatures, lyrics, scales, chords, dynamics and rhythm changes.
*MEDIA MADNESS       A complete multimedia sequencer which allows samples, stills, animation, etc 
*METRONOME           Tempo feedback via MIDI, internal Amiga audio and colour cycling — all three can be mixed and matched as required.
*MIX MAESTRO         Completely automated mixdown with control for both volume and pan. All fader alterations are memorised by the software 
*RECORD ACTIVATION   Complete specification of the data to be recorded/merged. Allows overdubbing of pitch‑bend, program changes, modulation etc
*SET FLAGS           Numeric positioning of location and edit flags in either SMPTE or musical time 
*SONG CONSTRUCTION   Large‑scale cut and paste of individual measures, verses or chorus, by means of bounding box and drag‑n‑drop mouse selections
*TEMPO MAP           Tempo change using a variety of linear and non‑linear transition curves 
*TEMPO PALETTE       Instant tempo changes courtesy of four user‑definable settings.
*TIMELINE SCORING    Sequencing of a selection of songs over a defined period — ideal for planning an entire set for a live performance.
*TOOLBOX             Selection screen for the hundreds of signal‑processing tools available 
*TRACKS              Opens the main track window to enable recording, editing and the use of tools.
*TRANSPORT           Main playback control window, which also provides access to user‑ defined flags, loop and punch‑in record modes.


Bars and Pipes Pro 2.5 is using internal 4-Byte IDs, to check which kind of data are currently processed.
Especially in all its files the IDs play an important role. The IDs are stored into the file in the same order they are laid out in the memory.

In a Bars 'N' Pipes file (no matter which kind) the ID &quot;NAME&quot; (saved as its ANSI-values) is stored on a big endian system (68k-computer) as &quot;NAME&quot;. On a little endian system (x86 PC computer) as &quot;EMAN&quot;.  The target is to make the AROS-BnP compatible to songs, which were stored on a 68k computer (AMIGA).

If possible, setting MIDI channels for Local Control for your keyboard 

http://www.fromwithin.com/liquidmidi/archive.shtml


MIDI files are essentially a stream of event data. An event can be many things, but typically &quot;note on&quot;, &quot;note off&quot;, &quot;program change&quot;, &quot;controller change&quot;, or messages that instruct a MIDI compatible synth how to play a given bit of music.

* Channel     - 1 to 16 -
* Messages    - PC presets, CC effects like delays, reverbs,  etc 
* Sequencing  - MIDI instruments, Drums, Sound design, 
* Recording   - 
* GUI         - Piano roll or Tracker, Staves and Notes 

MIDI events/messages like step entry e.g. Note On, Note Off 

MIDI events/messages like PB, PC, CC, Mono and Poly After-Touch, Sysex, etc 

MIDI sync - Midi Clocks (SPS Measures), Midi Time Code (h, m, s and frames) SMPTE 

Individual track editing with audition edits so easier to test any changes. Possible to stop track playback, mix clips from the right edit flag and scroll the display using arrow keys. 

Step entry, to extend a selected note hit the space bar and the note grows accordingly. Ability to cancel mouse‑driven edits by simply clicking the right mouse button — at which point everything snaps back into its original form. Lyrics can now be put in with syllable dividers, even across an entire measure or section. Autoranging when you open a edit window, the notes are automatically displayed — working from the lowest upwards. 

Flag editing, shift‑click on a flag immediately open the bounds window, ready for numeric input. Ability to cancel edits using the right‑hand mouse button, plus much improved Bounding Box operations.

Icons other than the BarsnPipes icon -&gt; PUBSCREEN=BarsnPipes (cannot choose modes higher than 8bit 256 colors)

Preferences -&gt; Menu in Tracks window - Send MIDI defaults OFF 

Prefs -&gt; Environment -&gt; screenmode (saved to BarsnPipes.prefs binary file) 

Customization -&gt; pics in gui drawer (folder) - 


Can save as .song files and .mid General Midi 

SMF is a “Standard Midi File”  ([http://www.music.mcgill.ca/~ich/classes/mumt306/StandardMIDIfileformat.html SMF0, SMF1 and SMF2]), [https://github.com/stump/libsmf libsmf], [https://github.com/markc/midicomp MIDIcomp], [https://github.com/MajicDesigns/MD_MIDIFile C++ src], [], [https://github.com/newdigate/midi-smf-reader Midi player], 

* SMF0        All MIDI data is stored in one track only, separated exclusively by the MIDI channel.
* SMF1        The MIDI data is stored in separate tracks/channels.
* SMF2 (rarely used) The MIDI data is stored in separate tracks, which are additionally wrapped in containers, so it's possible to have e.g. several tracks using the same MIDI channels.


Would it be possible to enrich Bars N’Pipes with software synth and sample support along with audio recording and mastering tools like in the named MAC or PC music sequencers?
On the classic AMIGA-OS this is not possible because of missing CPU-power. The hardware of the classic AMIGA is not further developed. So we must say (unfortunately) that those dreams can’t become reality

BarsnPipes is best used with external MIDI-equipment. This can be a keyboard or synthesizer with MIDI-connectors. 

&lt;pre&gt;
MIDI can control 16 channels 
There are USB-MIDI-Interfaces on the market with 16 independent MIDI-lines (multi-port), which can handle 16 MIDI devices independently – 16×16 = 256 independent MIDI-channels or instruments 
handle up to 16 different USB-MIDI-Interfaces (multi-device). That is: 16X16X16 = 4096 independent MIDI-channels – theoretically 
&lt;/pre&gt;

&lt;pre&gt;
Librarian MIDI SYStem EXplorer (sysex) - PatchEditor and used to be supplied as a separate program like PatchMeister but currently not at present 
It should support MIDI.library (PD), BlueRibbon.library (B&amp;P), TriplePlayPlus, and CAMD.library (DeluxeMusic) and 
MIDI information from a device's user manual and configure a custom interface to access parameters for all MIDI products connected to the system 
Supports ALL MIDI events and the Patch/Librarian data is stored in MIDI standard format 
Annette M.Crowling, Missing Link Software, Inc.
&lt;/pre&gt;


Composers
&lt;pre&gt;
[https://x.com/hirasawa/status/1403686519899054086 Susumu Hirasawa] 

&lt;/pre&gt;


&lt;pre&gt;
1988 Todor Fay and his wife Melissa Jordan Gray, who founded the Blue Ribbon Inc
1992 Bars&amp;Pipes Pro published 
November 2000, Todor Fay announcement to release the sourcecode of Bars&amp;Pipes Pro 2.5c beta
end of May 2001, the source of the main program and the sources of some tools and accessories were in a complete and compileable state 
end of October 2009 stop further development of BarsnPipes New for now on all supported systems and made freeware 
2013 Alfred Faust diagnosed with incureable illness, called „Myastenia gravis“ (weak muscles) 
&lt;/pre&gt;


 Protrekkr

How to use Midi In/Out in Protrekkr ?

First of all, midi in &amp; out capabilities of this program are rather limited.

# Go to Misc. Setup section and select a midi in or out device to use (ptk only supports one device at a time).
# Go to instrument section, and select a MIDI PRG (the default is N/A, which means no midi program selected).
# Go to track section and here you can assign a midi channel to each track of ptk.
# Play notes :]. Note off works. F'x' note cut command also works too, and note-volume command (speed) is supported.

Also, you can change midicontrollers in the tracker, using '90' in the panning row:

&lt;pre&gt;
    C-3 02 .. .. 0000....


    --- .. .. 90 xxyy.... &lt;&lt; This will set the value 
    --- .. .. .. 0000....    of the controller n.'xx' to 'yy' (both in hex)
    --- .. .. .. 0000....
&lt;/pre&gt;

So &quot;--- .. .. 90 2040....&quot; will set the controller number $20(32) to $40(64).

You will need the midi implementation table of your gear to know what you can change with midi controller messages.

 N.B. Not all MIDI devices are created equal!

Although the MIDI specification defines a large range of MIDI messages of various kinds, not every MIDI device is required to work in exactly the same way and respond to all the available messages and ways of working. For example, we don't expect a wind synthesiser to work in the same way as a home keyboard.

Some devices, the older ones perhaps, are only able to respond to a single channel. With some of those devices that channel can be altered from the default of 1 (probably) to another channel of the 16 possible.

Other devices, for instance monophonic synthesisers, are capable of producing just one note at a time, on one MIDI channel. Others can produce many notes spread across many channels.

Further devices can respond to, and transmit, &quot;breath controller&quot; data (MIDI controller number 2 (CC#2)) others may respond to the reception of CC#2 but not be able to create and to send it.

A controller keyboard may be capable of sending &quot;expression pedal&quot; data, but another device may not be capable of responding to that message.

Some devices just have the basic GM sound set. The &quot;voice&quot; or &quot;instrument&quot; is selected using a &quot;Program Change&quot; message on its own.

Other devices have a greater selection of voices, usually arranged in &quot;banks&quot;, and the choice of instrument is made by responding to &quot;Bank Select MSB&quot; (MIDI controller 0 (CC#0)), others use &quot;Bank Select LSB&quot; (MIDI controller number 32 (CC#32)), yet others use both MSB and LSB sent one after the other, all followed by the Program Change message. The detailed information about all the different voices will usually be available in a published MIDI Data List.


 MIDI Implementation Chart

But in the User Manual there is sometimes a summary of how the device works, in terms of MIDI, in the chart at the back of the manual, the MIDI Implementation Chart.

If you require two devices to work together you can compare the two implementation charts to see if they are &quot;compatible&quot;. In order to do this we will need to interpret that chart.

The chart is divided into four columns headed &quot;Function&quot;, &quot;Transmitted&quot; (or &quot;Tx&quot;), &quot;Received&quot; (or &quot;Rx&quot;), or more correctly &quot;Recognised&quot;, and finally, &quot;Remarks&quot;.

&lt;pre&gt;
The left hand column defines which MIDI functions are being described.
The 2nd column defines what the device in question is capable of transmitting to another device.
The 3rd column defines what the device is capable of responding to.
The 4th column is for explanations of the values contained within these previous two columns.
&lt;/pre&gt;

There should then be twelve sections, with possibly a thirteenth containing extra &quot;Notes&quot;. Finally there should be an explanation of the four MIDI &quot;modes&quot; and what the &quot;X&quot; and the &quot;O&quot; mean.
&lt;pre&gt;
Mode 1: Omni On, Poly; 
Mode 2: Omni On, Mono; 
Mode 3: Omni Off, Poly; 
Mode 4: Omni Off, Mono.
&lt;/pre&gt;
O means &quot;yes&quot; (implemented), X means &quot;no&quot; (not implemented).

Sometimes you will find a row of asterisks &quot;**************&quot;, these seem to indicate that the data is not applicable in this case. Seen in the transmitted field only (unless you've seen otherwise).

Lastly you may find against some entries an asterisk followed by a number e.g. *1, these will refer you to further information, often on a following page, giving more detail.

Basic Channel
But the very first set of boxes will tell us the &quot;Basic Channel(s)&quot; that the device sends or receives on. 
&quot;Default&quot; is what happens when the device is first turned on, &quot;changed&quot; is what a switch of some kind may allow the device to be set to. 
For many devices e.g. a GM sound module or a home keyboard, this would be 1-16 for both. That is it can handle sending and receiving on all MIDI channels.

On other devices, for example a synthesiser, it may by default only work on channel 1. But the keyboard could be &quot;split&quot; with the lower notes e.g. on channel 2. If the synth has an arppegiator, this may be able to be set to transmit and or receive on yet another channel.
So we might see the default as &quot;1&quot; but the changed as &quot;1-16&quot;.

Modes.
We need to understand Omni On and Off, and Mono and Poly, then we can decipher the four modes.

But first we need to understand that any of these four Mode messages can be sent to any MIDI channel. They don't necessarily apply to the whole device.

If we send an &quot;Omni On&quot; message (CC#125) to a MIDI channel of a device, we are, in effect, asking it to respond to e.g. a Note On / Off message pair, received on any of the sixteen channels. Sound strange? Read it again. Still strange? It certainly is. We normally want a MIDI channel to respond only to Note On / Off messages sent on that channel, not any other. In other words, &quot;Omni Off&quot;.

So &quot;Omni Off&quot; (CC#124) tells a channel of our MIDI device to respond only to messages sent on that MIDI channel.

&quot;Poly&quot; (CC#127) is for e.g. a channel of a polyphonic sound module, or a home keyboard, to be able to respond to many simultaneous Note On / Off message pairs at once and produce musical chords.

&quot;Mono&quot; (CC#126) allows us to set a channel to respond as if it were e.g. a flute or a trumpet, playing just one note at a time. If the device is capable of it, then the overlapping of notes will produce legato playing, that is the attack portion of the second note of two overlapping notes will be removed resulting in a &quot;smoother&quot; transition.

So a channel with a piano voice assigned to it will have Omni Off, Poly On (Mode 3), a channel with a saxophone voice assigned could be Omni Off, Mono On (Mode 4).

We call these combinations the four modes, 1 to 4, as defined above. 
Most modern devices will have their channels set to Mode 3 (Omni Off, Poly) but be switchable, on a per channel basis, to Mode 4 (Omni Off, Mono).

This second section of data will include first its default value i.e. upon device switch on. Then what Mode messages are acceptable, or X if none.

Finally, in the &quot;Altered&quot; field, how a Mode message that can't be implemented will be interpreted. Usually there will just be a row of asterisks effectively meaning nothing will be done if you try to switch to an unimplemented mode.

Note Number
&lt;pre&gt;
The next row will tell us which MIDI notes the device can send or receive, normally 0-127.
The second line, &quot;True Voice&quot; has the following in the MIDI specification: 
&quot;Range of received note numbers falling within the range of true notes produced by the instrument.&quot;
My interpretation is that, for instance, a MIDI piano may be capable of sending all MIDI notes (0 to 127) by transposition, but only responding to the 88 notes (21 to 108) of a real piano. 
&lt;/pre&gt;

Velocity
This will tell us whether the device we're looking at will handle note velocity, and what range from 1-127, or maybe just 64, it transmits or will recognise. So usually &quot;O&quot; plus a range or &quot;X&quot; for not implemented.

After touch
This may have one or two lines two it.
If a one liner the either &quot;O&quot; or &quot;X&quot;, yes or no.
If a two liner then it may include &quot;Keys&quot; or &quot;Poly&quot; and &quot;Channel&quot;.
This will show whether the device will respond to Polyphonic after touch or channel after touch or neither.

Pitch Bend
Again &quot;O&quot; for implemented, &quot;X&quot; for not implemented.
(Many stage pianos will have no pitch bend capability.)
It may also, in the notes section, state whether it will respond to the full 14 bits, or not, as usually encoded by the pitch bend wheel.

Control Change
This is likely to be the largest section of the chart.
It will list all those controllers, starting from CC#0, Bank Select MSB, which the device is capable of sending, and those that it will respond to using &quot;O&quot; or &quot;X&quot; respectively.
You will, almost certainly, get some further explanation of functionality in the remarks column, or in more detail elsewhere in the documentation.

Of course you will need to know what all the various controller numbers do. Lots of the official technical specifications can be found at the [www.midi.org/techspecs/ MMA], with the table of messages and control change [www.midi.org/techspecs/midimessages.php message numbers]

Program Change
Again &quot;O&quot; or &quot;X&quot; in the Transmitted or Recognised column to indicate whether or not the feature is implemented. In addition a range of numbers is shown, typically 0-127, to show what is available.
True # (number): &quot;The range of the program change numbers which correspond to the actual number of patches selected.&quot;

System Exclusive
Used to indicate whether or not the device can send or recognise System Exclusive messages. A short description is often given in the Remarks field followed by a detailed explanation elsewhere in the documentation.

System Common - These include the following:
&lt;pre&gt;
MIDI Time Code Quarter Frame messages (device synchronisation).
Song Position Pointer
Song Select
Tune Request
&lt;/pre&gt;
The section will indicate whether or not the device can send or respond to any of these messages.

System Real Time
These include the following:
&lt;pre&gt;
Timing Clock - often just written as &quot;Clock&quot;
Start
Stop
Continue
&lt;/pre&gt;
These three are usually just referred to as &quot;Commands&quot; and listed.
Again the section will indicate which, if any, of these messages the device can send or respond to.
&lt;pre&gt;
Aux. Messages
Again &quot;O&quot; or &quot;X&quot; for implemented or not.
Aux. = Auxiliary.
Active Sense = Active Sensing.
&lt;/pre&gt;
Often with an explanation of the action of the device.

Notes
The &quot;Notes&quot; section can contain any additional comments to clarify the particular implementation.

Some of the explanations have been drawn directly from the MMA MIDI 1.0 Detailed Specification.
And the detailed explanation of some of the functions will be found there, or in the General MIDI System Level 1 or General MIDI System Level 2 documents also published by the MMA.


 OFFICIAL MIDI SPECIFICATIONS

SUMMARY OF MIDI MESSAGES
Table 1 - Summary of MIDI Messages

The following table lists the major MIDI messages in numerical (binary) order (adapted from &quot;MIDI by the Numbers&quot; by D. Valenti, Electronic Musician 2/88, and updated by the MIDI Manufacturers Association.). This table is intended as an overview of MIDI, and is by no means complete.

WARNING! Details about implementing these messages can dramatically impact compatibility with other products. We strongly recommend consulting the official MIDI Specifications for additional information.

MIDI 1.0 Specification

Message Summary Channel Voice Messages [nnnn = 0-15 (MIDI Channel Number 1-16)]

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1000nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note Off event. 
This message is sent when a note is released (ended). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1001nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note On event. 
This message is sent when a note is depressed (start). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1010nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Polyphonic Key Pressure (Aftertouch). 
This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. (kkkkkkk) is the key (note) number. (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Control Change. 
This message is sent when a controller value changes. Controllers include devices such as pedals and levers. Controller numbers 120-127 are reserved as &quot;Channel Mode Messages&quot; (below). (ccccccc) is the controller number (0-119). (vvvvvvv) is the controller value (0-127).
|-
|&lt;!--Status--&gt;1100nnnn || &lt;!--Data--&gt;0ppppppp || &lt;!--Description--&gt;Program Change. This message sent when the patch number changes. (ppppppp) is the new program number.
|-
|&lt;!--Status--&gt;1101nnnn || &lt;!--Data--&gt;0vvvvvvv || &lt;!--Description--&gt;Channel Pressure (After-touch). This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. This message is different from polyphonic after-touch. Use this message to send the single greatest pressure value (of all the current depressed keys). (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1110nnnn || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Pitch Bend Change. This message is sent to indicate a change in the pitch bender (wheel or lever, typically). The pitch bender is measured by a fourteen bit value. Center (no pitch change) is 2000H. Sensitivity is a function of the receiver, but may be set using RPN 0. (lllllll) are the least significant 7 bits. (mmmmmmm) are the most significant 7 bits.
|}

Channel Mode Messages (See also Control Change, above)

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Channel Mode Messages. 
This the same code as the Control Change (above), but implements Mode control and special message by using reserved controller numbers 120-127. The commands are:
*All Sound Off. When All Sound Off is received all oscillators will turn off, and their volume envelopes are set to zero as soon as possible c = 120, v = 0: All Sound Off
*Reset All Controllers. When Reset All Controllers is received, all controller values are reset to their default values. (See specific Recommended Practices for defaults) c = 121, v = x: Value must only be zero unless otherwise allowed in a specific Recommended Practice.
*Local Control. When Local Control is Off, all devices on a given channel will respond only to data received over MIDI. Played data, etc. will be ignored. Local Control On restores the functions of the normal controllers. 
c = 122, v = 0: Local Control Off
c = 122, v = 127: Local Control On
* All Notes Off. When an All Notes Off is received, all oscillators will turn off. 
c = 123, v = 0: All Notes Off (See text for description of actual mode commands.)
c = 124, v = 0: Omni Mode Off 
c = 125, v = 0: Omni Mode On 
c = 126, v = M: Mono Mode On (Poly Off) where M is the number of channels (Omni Off) or 0 (Omni On) 
c = 127, v = 0: Poly Mode On (Mono Off) (Note: These four messages also cause All Notes Off)
|}

System Common Messages

System Messages (0xF0)

The final status nybble is a “catch all” for data that doesn’t fit the other statuses. They all use the most significant nybble (4bits) of 0xF, with the least significant nybble indicating the specific category.

The messages are denoted when the MSB of the second nybble is 1. When that bit is a 0, the messages fall into two other subcategories.

System Common

If the MSB of the second second nybble (4 bits) is not set, this indicates a System Common message. Most of these are messages that include some additional data bytes.

System Common Messages
Type Status Byte   Number of Data Bytes      Usage 
&lt;pre&gt;
Time Code Quarter Frame	0xF1	1	Indicates timing using absolute time code, primarily for synthronization with video playback systems. A single location requires eight messages to send the location in an encoded hours:minutes:seconds:frames format*.
Song Position	0xF2	2	Instructs a sequencer to jump to a new position in the song. The data bytes form a 14-bit value that expresses the location as the number of sixteenth notes from the start of the song.
Song Select	0xF3	1	Instructs a sequencer to select a new song. The data byte indicates the song.
Undefined	0xF4	0	
Undefined	0xF5	0	
Tune Request	0xF6	0	Requests that the receiver retunes itself**.
&lt;/pre&gt;
*MIDI Time Code (MTC) is significantly complex. Please see the MIDI Specification
**While modern digital instruments are good at staying in tune, older analog synthesizers were prone to tuning drift. Some analog synthesizers had an automatic tuning operation that could be initiated with this command.


System Exclusive

If you’ve been keeping track, you’ll notice there are two status bytes not yet defined: 0xf0 and 0xf7. These are used by the System Exclusive message, often abbreviated at SysEx. SysEx provides a path to send arbitrary data over a MIDI connection. There is a group of predefined messages for complex data, like fine grained control of MIDI Time code machinery. SysEx is also used to send manufacturer defined data, such as patches, or even firmware updates.

System Exclusive messages are longer than other MIDI messages, and can be any length. The messages are of the following format:

0xF0, 0xID, 0xdd, ...... 0xF7
The message is bookended with distinct bytes.

It opens with the Start Of Exclusive (SOX) data byte, 0xF0.
The next one to three bytes after the start are an identifier.
Values from 0x01 to 0x7C are one-byte vendor IDs, assigned to manufacturers who were involved with MIDI at the beginning.
If the ID is 0x00, it’s a three-byte vendor ID - the next two bytes of the message are the value.
&lt;pre&gt;
ID 0x7D is a placeholder for non-commercial entities.
ID 0x7E indicates a predefined Non-realtime SysEx message.
ID 0x7F indicates a predefined Realtime SysEx message.
&lt;/pre&gt;
After the ID is the data payload, sent as a stream of bytes.
The transfer concludes with the End of Exclusive (EOX) byte, 0xF7.
The payload data must follow the guidelines for MIDI data bytes – the MSB must not be set, so only 7 bits per byte are actually usable. If the MSB is set, it falls into three possible scenarios.

An End of Exclusive byte marks the ordinary termination of the SysEx transfer.
System Real Time messages may occur within the transfer without interrupting it. The recipient should handle them independently of the SysEx transfer.
Other status bytes implicitly terminate the SysEx transfer and signal the start of new messages.
 Some inexpensive USB-to-MIDI interfaces aren’t capable of handling messages longer than four bytes.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11110000 || &lt;!--Data--&gt;0iiiiiii [0iiiiiii 0iiiiiii]  0ddddddd  --- --- 0ddddddd 11110111 || &lt;!--Description--&gt;System Exclusive. 
This message type allows manufacturers to create their own messages (such as bulk dumps, patch parameters, and other non-spec data) and provides a mechanism for creating additional MIDI Specification messages. The Manufacturer's ID code (assigned by MMA or AMEI) is either 1 byte (0iiiiiii) or 3 bytes (0iiiiiii 0iiiiiii 0iiiiiii). Two of the 1 Byte IDs are reserved for extensions called Universal Exclusive Messages, which are not manufacturer-specific. If a device recognizes the ID code as its own (or as a supported Universal message) it will listen to the rest of the message (0ddddddd). Otherwise, the message will be ignored. (Note: Only Real-Time messages may be interleaved with a System Exclusive.)
|-
|&lt;!--Status--&gt;11110001 || &lt;!--Data--&gt;0nnndddd || &lt;!--Description--&gt;MIDI Time Code Quarter Frame.
nnn = Message Type
dddd = Values
|-
|&lt;!--Status--&gt;11110010 || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Song Position Pointer. 
This is an internal 14 bit register that holds the number of MIDI beats (1 beat= six MIDI clocks) since the start of the song. l is the LSB, m the MSB.
|-
|&lt;!--Status--&gt;11110011 || &lt;!--Data--&gt;0sssssss || &lt;!--Description--&gt;Song Select. 
The Song Select specifies which sequence or song is to be played.
|-
|&lt;!--Status--&gt;11110100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Tune Request. Upon receiving a Tune Request, all analog synthesizers should tune their oscillators.
|-
|&lt;!--Status--&gt;11110111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;End of Exclusive. Used to terminate a System Exclusive dump. 
|}


System Real-Time Messages

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11111000 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Timing Clock. Sent 24 times per quarter note when synchronization is required.
|-
|&lt;!--Status--&gt;11111001 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111010 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Start. Start the current sequence playing. (This message will be followed with Timing Clocks).
|-
|&lt;!--Status--&gt;11111011 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Continue. Continue at the point the sequence was Stopped.
|-
|&lt;!--Status--&gt;11111100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Stop. Stop the current sequence.
|-
|&lt;!--Status--&gt;11111101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Active Sensing. This message is intended to be sent repeatedly to tell the receiver that a connection is alive. Use of this message is optional. When initially received, the receiver will expect to receive another Active Sensing message each 300ms (max), and if it does not then it will assume that the connection has been terminated. At termination, the receiver will turn off all voices and return to normal (non- active sensing) operation. 
|-
|&lt;!--Status--&gt;11111111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Reset. Reset all receivers in the system to power-up status. This should be used sparingly, preferably under manual control. In particular, it should not be sent on power-up.
|}


Advanced Messages

Polyphonic Pressure (0xA0) and Channel Pressure (0xD0)

Some MIDI controllers include a feature known as Aftertouch. While a key is being held down, the player can press harder on the key. The controller measures this, and converts it into MIDI messages.

Aftertouch comes in two flavors, with two different status messages.

The first flavor is polyphonic aftertouch, where every key on the controller is capable of sending its own independent pressure information. The messages are of the following format:
&lt;pre&gt;
0xnc, 0xkk, 0xpp
n is the status (0xA)
c is the channel nybble
kk is the key number (0 to 127)
pp is the pressure value (0 to 127)
&lt;/pre&gt;
Polyphonic aftertouch is an uncommon feature, usually found on premium quality instruments, because every key requires a separate pressure sensor, plus the circuitry to read them all.

Much more commonly found is channel aftertouch. Instead of needing a discrete sensor per key, it uses a single, larger sensor to measure pressure on all of the keys as a group. The messages omit the key number, leaving a two-byte format
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xD)
c is the channel number
pp is the pressure value (0 to 127)
&lt;/pre&gt;

Pitch Bend (0xE0)

Many keyboards have a wheel or lever towards the left of the keys for pitch bend control. This control is usually spring-loaded, so it snaps back to the center of its range when released. This allows for both upward and downward bends.

Pitch Bend Wheel

The wheel sends pitch bend messages, of the format
&lt;pre&gt;
0xnc, 0xLL, 0xMM
n is the status (0xE)
c is the channel number
LL is the 7 least-significant bits of the value
MM is the 7 most-significant bits of the value
&lt;/pre&gt;
You’ll notice that the bender data is actually 14 bits long, transmitted as two 7-bit data bytes. This means that the recipient needs to reassemble those bytes using binary manipulation. 14 bits results in an overall range of 214, or 0 to 16,383. Because it defaults to the center of the range, the default value for the bender is halfway through that range, at 8192 (0x2000).

Control Change (0xB0)

In addition to pitch bend, MIDI has provisions for a wider range of expressive controls, sometimes known as continuous controllers, often abbreviated CC. These are transmitted by the remaining knobs and sliders on the keyboard controller shown below.


Continuous Controllers

These controls send the following message format:
&lt;pre&gt;
0xnc, 0xcc, 0xvv
n is the status (0xB)
c is the MIDI channel
cc is the controller number (0-127)
vv is the controller value (0-127)
&lt;/pre&gt;

Typically, the wheel next to the bender sends controller number one, assigned to modulation (or vibrato) depth. It is implemented by most instruments.

The remaining controller number assignments are another point of confusion. The MIDI specification was revised in version 2.0 to assign uses for many of the controllers. However, this implementation is not universal, and there are ranges of unassigned controllers.

On many modern MIDI devices, the controllers are assignable. On the controller keyboard shown in the photos, the various controls can be configured to transmit different controller numbers. Controller numbers can be mapped to particular parameters. Virtual synthesizers frequently allow the user to assign CCs to the on-screen controls. This is very flexible, but it might require configuration on both ends of the link and completely bypasses the assignments in the standard.


Program Change (0xC0)

Most synthesizers have patch storage memory, and can be told to change patches using the following command:
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xc)
c is the channel
pp is the patch number (0-127)
&lt;/pre&gt;
This allows for 128 sounds to be selected, but modern instruments contain many more than 128 patches. Controller #0 is used as an additional layer of addressing, interpreted as a “bank select” command. Selecting a sound on such an instrument might involve two messages: a bank select controller message, then a program change.

Audio &amp; Midi are not synchronized, what I can do ?
Buy a commercial software package but there is a nasty trick to synchronize both. It's a bit hardcore but works for me:

 Simply put one line down to all midi notes on your pattern (use Insert key)
 and go to 'Misc. Setup', adjust the latency and just search a value
 that will make sound sync both audio/midi.

The stock Sin/Saw/Pulse and Rnd waveforms are too simple/common, is there a way to use something more complex/rich ?
You have to ability to redirect the waveforms of the instruments through the synth pipe by selecting the &quot;wav&quot; option for the oscillator you're using for this synth instrument, samples can be used as wavetables to replace the stock signals.


Sound banks like soundfont (sf2) or Kontakt2 are not supported at the moment


====DAW Audio Evolution 4====

Audio Evolution 4 gives you unsurpassed power for digital audio recording and editing on the Amiga. The latest release focusses on time-saving non-linear and non-destructive editing, as seen on other platforms. Besides editing, Audio Evolution 4 offers a wide range of realtime effects, including compression, noise gate, delays, reverb, chorus and 3-band EQ.

Whether you put them as inserts on a channel or use them as auxillaries, the effect parameters are realtime adjustable and can be fully automated. Together with all other mixing parameters, they can even be controlled remotely, using more ergonomic MIDI hardware.

Non-linear editing on the time line, including cut, copy, paste, move, split, trim and crossfade actions

The number of tracks per project(s) is unlimited .... AHI limits you to recording only two at a time. i.e. not on 8 track sound cards like the Juli@ or Phase 88.

sample file import is limited to 16bit AIFF (not AIFC, important distinction as some files from other sources can be AIFC with aiff file extension). and 16bit WAV (pcm only)


Most apps use the Music Unit only but a few apps also use Unit (0-3) instead or as well. 
* Set up AHI prefs so that microphone is available. (Input option near the bottom)


stereo++ allows the audio piece to be placed anywhere and the left-right adjusted to sound positionally right

hifi best for music playback if driver supports this option


Load 16bit .aif .aiff only sample(s) to use not AIFC which can have the same ending. AIFF stands for Audio Interchange File Format 

 sox recital.wav recital.aiff

 sox recital.wav −b 16 recital.aiff channels 1 rate 16k fade 3 norm
 sox input.wav        output.aiff bass −b 16 rate 48k

performs the same format translation, but also applies four effects (down-mix to one channel, sample rate change, fade-in, nomalize), and stores the result at a bit-depth of 16.

 rec −c 2 radio.aiff trim 0 30:00

records half an hour of stereo audio 

 play existing-file.wav


24bit PCM WAV or AIFF do not work 

*No stream format handling. So no way to pass on an AC3 encoded stream unmodified to the digital outputs through AHI.
*No master volume handling. Each application has to set its own volume. So each driver implements its own custom driver-mixer interface for handling master volumes, mute and preamps.
*Only one output stream. So all input gets mixed into one output.
*No automatic handling of output direction based on connected cables.
*No monitor input selection. Only monitor volume control. 


select the correct input (Don't mistake enabled sound for the correct input.)
The monitor will feedback audio to the lineout and hp out no matter if you have selected the correct input to the ADC. The monitor will provide sound for any valid input. This will result in free mixing when recording from the monitor input instead of mic/line because the monitor itself will provide the hardware mixing for you. Be aware that MIC inputs will give two channel mono. Only Linein will give real stereo.

Now for the not working part. Attempt to record from linein in the AE4 record window, the right channel is noise and the left channel is distorted. Even with the recommended HIFI 16bit Stereo++ mode at 48kHz.


Channels

Monitor

Gain

Inout

Output

Advanced settings - Debugging via serial port


* Options -&gt; Soundcard In/Out
* Options -&gt; SampleRate
* Options -&gt; Preferences

F6 for Sample File List

Setting a grid is easy as is measuring the BPM by marking a section of the sample. Is your kick drum track &quot;not in time&quot; ? If so, you're stumped in AE4 as it has no fancy variable time signatures and definitely no 'track this dodgy rhythm' function like software of the nature of Logic has. So if your drum beat is freeform you will need to work in freeform mode. (Real music is free form anyway).

If the drum *is* accurate and you are just having trouble measuring the time, I usually measure over a range of bars and set the number of beats in range to say 16 as this is more accurate, Then you will need to shift the drum track to match your grid *before* applying the grid. (probably an iterative process as when the grid is active samples snap to it, and when inactive you cannot see it).

AE4 does have ARexx but the functions are more for adding samples at set offsets and starting playback / recording.


These are the usual features found in DAWs...

* Recording digital audio, midi sequencer and mixer 
* virtual VST instruments and plug-ins 
* automation, group channels, MIDI channels, FX sends and returns, audio and MIDI editors and music notation editor


* different track views 
* mixer and track layout (but not the same as below) 
* traditional two windows (track and mixer)


Mixing - mixdown

Could not figure out how to select what part I wanted to send to the aux, set it to echo and return. Pretty much the whole echo effect. Or any effect.

Take look at page17 of the manual.

When you open the EQ / Aux send popup window you will see 4 sends. Now from the menu choose the windows menu.

Menus-&gt;Windows-&gt; Aux Returns Window

or press F5

You will see a small window with 4 volume controls and an effects button for each. Click a button and add an effects to that aux channel, then set it up as desired (note the reverb effect has a special AUX setting that improves its use with the aux channel, not compulsory but highly useful). You set the amount of 'return' on the main mix in the Aux Return window, and the amount sent from each main mixer channel in the popup for that channel. Again the aux sends are &quot;prefade&quot; so the volume faders on each channel do not affect them.


Tracking


Effects - fade in

To add some echoes to some vocals, tried to add an effect on a track but did not come out. This is made more complicated as I wanted to mute a vocal but then make it echo at the muting point. Want to have one word of a vocal heard and then echoed off. But when the track is mute the echo is cancelled out.

To correctly understand what is happening here you need to study the figure at the bottom of page 15 on the manual. You will see from that that the effects are applied 'prefade' So the automation you applied will naturally mute the entire signal.

There would be a number of ways to achieve the goal,

You have three real time effects slots, one for smoothing like so

Sample -&gt; Amplify -&gt; Delay

Then automate the gain of the amplify block so that it effectively mutes the sample just before the delay at the appropriate moment, the echo effect should then be heard.

Getting the effects in the right order will require experimentation as they can only be added top down and it's not obvious which order they are applied to the signal, but there only two possibilities, so it wont take long to find out.

Using MUTE can cause clicks to the Amplify can be used to mute more smoothly so that's a secondary advantage.

Signal Processing -


Overdub

[[#top|...to the top]]

===Office===

====Spreadsheet Leu====

Support for some xlsx, and ods functions 


====Spreadsheet Ignition====

; Needs ABIv1 to be completed before more can be done

File formats supported 
* ascii #?.txt and #?.csv (single sheets with data only). 
* igs and TurboCalc(WIP) #?.tc for all sheets with data, formats and formulas.

There is '''no''' support for xls, xlsx, ods or uos ([http://en.wikipedia.org/wiki/Uniform_Office_Format Uniform Unified Office Format]) at the moment.

* Always use Esc key after editing Spreadsheet cells.
* copy/paste seems to copy the first instance only so go to Edit -&gt; Clipboard to manage the list of remembered actions. 
* Right mouse click on row (1 or 2 or 3) or column header (a or b or c)  to access optimal height or width of the row or column respectively 
* Edit -&gt; Insert -&gt; Row  seems to clear the spreadsheet or clears the rows after the inserted row until undo restores as it should be...

Change Sheet name by  Object -&gt; Sheet -&gt; Properties

Click in the cell which will contain the result, and click '''down arrow button''' to the right of the formula box at the bottom of the spreadsheet and choose the function required from the list provided. Then click on the start cell and click on the bottom right corner, a '''very''' small blob, which allows stretching a bounding box (thick grey outlines) across many cells This grey bounding box can be used to '''copy a formula''' to other cells.

Object -&gt; Cell -&gt; Properties to change cell format - Currency only covers DM and not $, Euro, Renminbi, Yen or Pound etc. 
Shift key and arrow keys selects a range of cells, so that '''formatting can be done to all highlighted cells'''. 
View -&gt; Overview then select ALL with one click (in empty cell in the top left hand corner of the sheet).

Default mode is relative cell referencing e.g. a1+a2 but absolute e.g. $a$1+$a$2 can be entered.

* #sheet-name to '''absolute''' reference another sheet-name cell unless reference() function used.

;Graphs

use shift key and arrow keys to select a bunch of cells to be graph'ed making sure that x axes represents and y axes represents

* value() - 0 value, 1 percent, 2 date, 3 time, 4 unit ...


;Dates 
* Excel starts a running count from the 1st Jan 1900 and Ignition starts from 1st Jan 1AD '''(maybe this needs to change)'''
Set formatting Object -&gt; Cell -&gt; Properties and put date in days


;Time 
Set formatting Object -&gt; Cell -&gt; Properties and put time in seconds taken


;Database (to be done by someone else)

type - standard, reference (bezug), search criterion (suchkriterium), 
* select a bunch of cells and Object -&gt; Database -&gt; Define to set Datenbank (database) and Felder (fields not sure how?) 
* Neu (new) or loschen (delete) to add/remove database headings e.g. Personal, Start Date, Finish Date (one per row?)
* Object -&gt; Database -&gt; Index to add fields (felder) like Surname, First Name, Employee ID, etc. to ?

Filtering done with dbfilter(), dbproduct() and dbposition().

Activities with dbsum(), dbaverage(), dbmin() and dbmax().

Table sorting -


;Scripts (Arexx)

;Excel(TM) to Ignition - commas ''',''' replaced by semi-colons ''';''' to separate values within functions 
*SUM(), 
*AVERAGE(), MAX(), MIN(), INT(), PRODUCT(), MEDIAN(), VAR() becomes Variance(), Percentile(),
*IF(), AND, OR, NOT 
*LEFT(), RIGHT(), MID() becomes MIDDLE(), LEN() becomes LENGTH(), 
*LOWER() becomes LOWERCASE(), UPPER() becomes UPPERCASE(),
* DATE(yyyy,mm,dd) becomes COMPUTEDATE(dd;mm;yyyy), 
*TODAY(), DAY(),WEEK(), MONTH(),=YEAR(TODAY()), 
*EOMONTH() becomes MONTHLENGTH(), 
*NOW() should be date and time becomes time only, SECOND(), MINUTE(), HOUR(),
*DBSUM() becomes DSUM(),


;Missing and possibly useful features/functions needed for ignition to have better support of Excel files 
There is no Merge and Join Text over many cells, no protect and/or freeze row or columns or books but can LOCK sheets, no define bunch of cells as a name, Macros (Arexx?), conditional formatting, no Solver, no Goal Seek, no Format Painter, no AutoFill, no AutoSum function button, no pivot tables, (30 argument limit applies to Excel)

*HLOOKUP(), VLOOKUP(), [http://production-scheduling.com/excel-index-function-most-useful/ INDEX(), MATCH()], CHOOSE(), TEXT(), 
*TRIM(), FIND(), SUBSTITUTE(), CONCATENATE() or &amp;, PROPER(), REPT(), 
*[https://acingexcel.com/excel-sumproduct-function/ SUMPRODUCT()], ROUND(), ROUNDUP(), *ROUNDDOWN(), COUNT(), COUNTA(), SUMIF(), COUNTIF(), COUNTBLANK(), TRUNC(), 
*PMT(), PV(), FV(), POWER(), SQRT(), MODE(), TRUE, FALSE, 
*MODE(), LARGE(), SMALL(), RANK(), STDEV(), 
*DCOUNT(), DCOUNTA(), WEEKDAY(),


;Excel Keyboard [http://dmcritchie.mvps.org/excel/shortx2k.htm shortcuts needed to aid usability in Ignition] 
&lt;pre&gt;
Ctrl Z - Undo

Ctrl D - Fill Down
Ctrl R - Fill right

Ctrl F - Find
Ctrl H - Replace

Ctrl 1 - Formatting of Cells
CTRL SHIFT ~ Apply General Formatting ie a number 
Ctrl ; - Todays Date 

F2 - Edit cell
F4 - toggle cell absolute / relative cell references

&lt;/pre&gt;


====Document Scanning - Scandal====

Scanner usually needs to be connected via a USB port and not via a hub or extension lead.

Check in Trident Prefs -&gt; Devices that the USB Scanner is not bound to anything (e.g. Bindings None)
If not found then reboot the computer and recheck.

Start Scandal, choose Settings from Menu strip at top of screen and in Scanner Driver choose the ?#.device of the scanner (e.g. epson2.device).

The next two boxes - leave empty as they are for morphos SCSI use only
 or put ata.device (use the selection option in bigger box below) and Unit as 0 this is needed for gt68xx

* gt68xx - no editing needed in s/gt68xx.conf but needs a firmware file that corresponds to the scanner [http://www.meier-geinitz.de/sane/gt68xx-backend/ gt68xx firmwares] in sys:s/gt68xx.
* epson2 - Need to edit the file epson2.conf in sys/s that corresponds to the scanner being used

'''Save''' the settings but do not press the Use button (aros freezes)

Back to the Picture Scan window and the right-hand sections.

Click on the '''Information''' tab and press Connect button and the scanner should now be detected.

Go next to the '''Scanner''' tab next to Information Tab should have Color, Black and White, etc. and dpi settings now. Selecting an option Color, B/W etc. can cause dpi settings corruption (especially if the settings are in one line) so set '''dpi first'''. Make sure if Preview is set or not.

In the '''Scan''' Tab, press Scan and the scanner will do its duty. 
Be aware that nothing is saved to disk yet.

In the Save tab, change format JPEG, PNG or IFF DEEP. Tick incremental and base filename if necessary and then click the Save button. The image will now be saved to permanent storage.


The driver ignores a device if it is already bond to another USB class, rejects it from being usable. However, open Trident prefs, select your device and use the right mouse button to open. Select &quot;NONE&quot; to prevent poseidon from touching the device. Now save settings. It should always work now.

[[#top|...to the top]]

===Emulators===

==== Amiberry ====


==== Amiga Emu - Janus UAE ====

With Amibridge, AROS attempts to make the UAE emulator seem embedded within but it still is acting as an app 

There is no dynarec m68k for each hardware that Aros supports or direct patching of motorola calls to AROS hardware accelerated ones unless the emulator has that included 

Try starting Janus with a priority of -1 like this little script:
&lt;pre&gt;
cd sys:system/AmiBridge/emulator
changetaskpri -1
run janus-uae -f my_uaerc.config &gt;nil:
cd sys:prefs
endcli
&lt;/pre&gt;
This stops Janus hogging all the CPU time.


===Miscellaneous===

====Screensaver Blanker====

Most blankers on the amiga (i.e. aros) run as commodities (they are in the tools/commodities drawer). Double click on blanker.

Control is with an app called Exchange, which you need to run first (double click on app) or  run QUIET sys:tools/commodities/Exchange &gt;NIL: but subsequently can use (Cntrl Alt h).

Icon tool types (may be broken) or command line options 
&lt;pre&gt;
seconds=number 
&lt;/pre&gt;

Once the timing is right then add the following to s:icaros-sequence or s:user-startup

e.g. for 5 minutes

 run QUIET sys:tools/commodities/Blanker seconds=300 &gt;NIL:


*[http://archives.aros-exec.org/index.php?function=showfile&amp;file=graphics/screenblanker/gblanker.i386-aros.zip Garshneblanker] can make Aros unstable or slow. Certain blankers crashes in Icaros 2.0.x like Dragon, Executor.


*[ Acuario AROS version], the aquarium screen saver.

Startup: extras:acuariofv-aros/acuario

Kill: c:break name=extras:acuariofv-aros/acuario

Managed to start Acuario by the Executor blanker.

&lt;pre&gt;
cx_priority=
cx_popkey=    ie CX_POPKEY=&quot;Shift F1&quot; 
cx_popup=Yes or No

&lt;/pre&gt;


&lt;pre&gt;
 Qualifier String    Input Event Class
   ----------------    -----------------
    &quot;lshift&quot;           IEQUALIFIER_LSHIFT
    &quot;rshift&quot;           IEQUALIFIER_RSHIFT
    &quot;capslock&quot;         IEQUALIFIER_CAPSLOCK
    &quot;control&quot;          IEQUALIFIER_CONTROL
    &quot;lalt&quot;             IEQUALIFIER_LALT
    &quot;ralt&quot;             IEQUALIFIER_RALT
    &quot;lcommand&quot;         IEQUALIFIER_LCOMMAND
    &quot;rcommand&quot;         IEQUALIFIER_RCOMMAND
    &quot;numericpad&quot;       IEQUALIFIER_NUMERICPAD
    &quot;repeat&quot;           IEQUALIFIER_REPEAT
    &quot;midbutton&quot;        IEQUALIFIER_MIDBUTTON
    &quot;rbutton&quot;          IEQUALIFIER_RBUTTON
    &quot;leftbutton&quot;       IEQUALIFIER_LEFTBUTTON
    &quot;relativemouse&quot;    IEQUALIFIER_RELATIVEMOUSE
&lt;/pre&gt;


&lt;pre&gt;
    Synonym     Synonym
    String     Identifier
    -------    ----------
    &quot;shift&quot;    IXSYM_SHIFT    /* look for either shift key */
    &quot;caps&quot;     IXSYM_CAPS     /* look for either shift key or capslock */
    &quot;alt&quot;      IXSYM_ALT      /* look for either alt key */

Highmap is one of the following strings:
    &quot;space&quot;, &quot;backspace&quot;, &quot;tab&quot;, &quot;enter&quot;, &quot;return&quot;, &quot;esc&quot;, &quot;del&quot;,
    &quot;up&quot;, &quot;down&quot;, &quot;right&quot;, &quot;left&quot;, &quot;f1&quot;, &quot;f2&quot;, &quot;f3&quot;, &quot;f4&quot;, &quot;f5&quot;,
    &quot;f6&quot;, &quot;f7&quot;, &quot;f8&quot;, &quot;f9&quot;, &quot;f10&quot;, &quot;help&quot;.


&lt;/pre&gt;


[[#top|...to the top]]

==== World Construction Set WCS (Version 2.031) ====

WCS is a fractal landscape software such as Scenery Animator, Vista Pro and Panorama. Open sourced February 2022, World Construction Set [https://3dnature.com/downloads/legacy-software/ legally and for free] and [https://github.com/AlphaPixel/3DNature c source]. 

Announced August 1994 this version dates from April 1996 developed by Gary R. Huber and Chris &quot;Xenon&quot; Hanson&quot; from Questar 

&lt;pre&gt;
Assign &quot;WCSProjects:&quot; &quot;Volume:Dir/Dir/WCSProjects&quot; 
Assign &quot;WCSFrames:&quot;   &quot;Volume:Dir/Dir/WCSFrames&quot; 
&lt;/pre&gt;

&lt;pre&gt;
Load projects .proj by accessing pull down menu Project -&gt; Open then click on CanyonSunset.proj
OK to changing .par file and enlarge Status Log window to show what is happening 
Render by pull down menu Modules -&gt; Render with End equal 1 not 300 then click bottom middle button Render 
&lt;/pre&gt;

[https://www.youtube.com/watch?v=CxQDmf1ZWG0 Youtube walkthrough of above], [], [], 

Also try working with the already built file ColoDemo - Then open with the drop-down menu: Project/Open, then WCSProject:ColoDemo.proj
Which allows you to use altimetric DEM files already included and Loading scene parameters from ColoDemo.par
Once this is done, save everything with a new name to start working exclusively on your project. 
Then drop-down menu and select Save As (&quot;NewName&quot;.proj name), then drop-down menu to open parameter and select Save All ( .par name)


After launching the software, there is a the Module Control Panel composed of five icons. 
It is a dock type shortcut of the first few functions of the drop-down menu 

*Database   - Load (#?.proj), Append, Create, Edit, Save, Dir List (of WCSProject drawer), 
*Data Ops   - Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats  
*Map View   - Database file Loader leading to Map View Control with option to the Database Editor 
*Parameters - Editor for Motion, Color, Ecosystem, Clouds, Waves, management of altimeter files DEM, sclock settings etc 
*Render     - rendering terrain 

These are more in the pull down menu but not in the dock 
*Motion Editor
*Color Editor
*Ecosys Editor 


Simple minimal workflow 
*Load database (1st icon - 1st)
*Set parameters and save .par file (4th icon)
*Render scene (5th icon) 

[https://www.youtube.com/watch?v=ZbTwwR2qcc4 Youtube], [], 

&lt;pre&gt;
.proj new project name which creates a drawer of additional files 

.binary array, ascii array .xyz , z buffer, DTED .dt0, vista 1990s dem, iff  conversion 
.Obj with .elev, .frd with .hdr maps, - digital elevation model (DEM) is a 3D representation of elevation data in various formats 
USGS 7.5MinDEM, 

.par 


&lt;/pre&gt;


Since for the time being no project is loaded, a query window indicates a procedural error when clicking on the rendering icon (right end of the bar). The menu is quite traditional; it varies according to the activity of the windows. To display any altimetric file in the &quot;Mapview&quot; (third icon of the panel), There are three possibilities:

* Loading of a demonstration project.
* The import of a DEM file, followed by texturing and packaging from the &quot;Database-Editor&quot; and the &quot;Color-Editor&quot;.
* The creation of an altimetric file in WCS format, then texturing.


The altimeter file editing (display in the menu) is only made possible if the &quot;Mapview&quot; window is active.

The software is made up of many windows and won't be able to describe them all. Know that &quot;Color-Editor&quot; and the &quot;Data-Editor&quot; comprise sufficient functions for obtaining an almost real rendering quality. You have the possibility of inserting vector objects in the &quot;Data-Editor&quot; (creation of roads, railways, etc.) 


The Map View (MapView) window

*Database - Objects and Topos
*View     - Align, Center, Zoom, Pan, Move 
*Draw     - Maps and distance 
*Object   - Find, highlight, add points, conform topo, duplicate 
*Motion   - Camera, Focus, path, elevation 
*Windows  - DEM designer, Cloud (.cld) and wave (.wve) editor, 


You will notice that by selecting this window and simply moving the pointer to various points on the map you will see latitude and longitude values ​​change, along with the height.
Drop-down menu and Modules, then select MapView and change the width of the window with the map to arrange it in the best way on the screen. With the Auto button the center. Window that then displays the contents of my DEM file, in this case the Grand Canyon. MapView allows you to observe the shape of the landscape from above
 

ZOOM button

Press the Zoom button and then with the pointer position on a point on the map, press the left mouse button and then move to the opposite corner to circumscribe the chosen area and press the left mouse button again, then we will see the enlarged area selected on the map.
Would add that there is a box next to the Zoom button that allows the direct insertion of a value which, the larger it is, the smaller the magnification and the smaller the value, the stronger the magnification. At each numerical change you will need to press the DRAW button to update the view.

PAN button

Under Zoom you will find the PAN button which allows you to move the map at will in all directions by the amount you want. This is done by drawing a line in one direction, then press PAN and point to an area on the map with the pointer and press the left mouse button. At this point, leave it and move the pointer in one direction by drawing a line and press the left mouse button again to trigger the movement of the map on the screen (origin and end points). Do some experiments and then use the Auto button immediately below to recenter everything.
There are parameters such as TOPO, VEC to be left checked and immediately below one that allows different views of the map with the Style command (Single, Multi, Surface, Emboss, Slope, Contour), each with its own particularities to highlight different details.

Now you have the first basics to manage your project visually on the map. Close the MapView window and go further...


Let's start working on ECOSYSTEMS
If we select Emboss from the MapView Style command we will have a clear idea of ​​how the landscape appears, realizing that it is a predominantly desert region of our planet. Therefore we will begin to act on any vegetation present and the appearance of the landscape.
With WCS we will begin to break down the elements of the landscape by assigning defined characteristics. It will be necessary to determine the classes of the ecosystem (Class) with parameters of Elevation Line (maximum altitude), Relative Elevation (arrangement on basins or convexities with respectively positive or negative parameters), Min Slope and Max Slope (slope). WCS offers the possibility of making ecosystems coexist on the same terrain with the UnderEco function, by setting a Density value.


Ecosys Ecosystem Editor

Let's open it from Modules, then Ecosys Editor. In the left pane you will find the list of ecosystems referring to the files present in our project. It will be necessary to clean up that box to leave only the Water and Snow landscapes and a few other predefined ones. We can do this by selecting the items and pressing the Remove button (be careful not for all elements the button is activated, therefore they cannot all be eliminated).
Once this is done we can start adding new ecosystems. Scroll through the various Unused and as soon as the Name item at the top is activated allowing you to write, type the name of your ecosystem, adding the necessary parameters.
&lt;pre&gt;
Ecosystem1: Name: RockBase Class: Rock Density: 80 MinSlope: 15 UnderEco: Terrain
Ecosystem2: Name: RockIncl Clss: Rock Density: 80 MinSlope: 30 UnderEco: Terrain
Ecosystem3: Name: Grass Class Low Veg Density: 50 Height: 1 Elev Line : 1500 Rel El Eff: 5
Max Slope: 10 – Min Slope: 0 UnderEco: Terrain
Ecosistema4: Name: Shrubs Class: Low Veg Density: 40 Height: 8 Elev Line: 3000
Rel El Eff: -2 Max Slope: 20 Min Slope : 5 UnderEco: Terrain
Ecosistema5: Name: Terrain Class: Ground Density: 100 UnderEco: Terrain
&lt;/pre&gt;

Now we need to identify an intermediate ecosystem that guarantees a smooth transition between all, therefore we select as Understory Ecosystem the one called Terrain in all ecosystems, except Snow and Water .
Now we need to 'emerge' the Colorado River in the Canyon and we can do this by raising the sea level to 900 (Sea Level) in the Ecosystem called Water.
Please note that the order of the ecosystem list gives priority to those that come after. So our list must have the following order: Water, Snow, Shrubs, RockIncl, RockBase, Terrain. It is possible to carry out all movements with the Swap button at the bottom. To put order you can also press Short List. Press Keep to confirm all the work done so far with Ecosystem Editor.
Remember every now and then to save both the Project 'Modules/Save' and 'Parameter/Save All'

EcoModels are made up of .etp .fgp .iff8 for each model 


Color Editor

Now it's time to define the colors of our scene and we can do this by going to Modules and then Color Editor. In the list we focus on our ecosystems, created first.
Let's go to the bottom of the list and select the first white space, assigning the name 'empty1', with a color we like and then we will find this element again in other environments... It could serve as an example for other situations!
So we move to 'grass' which already exists and assign the following colors: R 60 G 70 B50
&lt;pre&gt;
'shrubs': R 60 G 80 B 30
'RockIncl' R 110 G 65 B 60
'RockBase' R 110 G 80 B 80
' Terrain' R 150 G 30 B 30
&lt;pre&gt;
Now we can work on pre-existing colors
&lt;pre&gt;
'SunLight' R 150 G 130 B 130
'Haze and Fog' R 190 G 170 B 170
'Horizon' R 209 G 185 B 190
'Zenith' R 140 G 150 B 200
'Water' R 90 G 125 B 170
&lt;/pre&gt;

Ambient R 0 G 0 B 0

So don't forget to close Color Editor by pressing Keep.
Go once again to Ecosystem Editor and assign the corresponding color to each environment by selecting it using the Ecosystem Color button. Press it several times until the correct one appears. Then save the project and parameters again, as done previously.


Motion Editor

Now it's time to take care of the framing, so let's go to Modules and then to Motion Editor. An extremely feature-rich window will open. Following is the list of parameters regarding the Camera, position and other characteristics:
&lt;pre&gt;
-Camera Altitude: 7.0
-Camera Latitude: 36.075
-Camera Longitude: 112.133
-Focus Attitude: -2.0
-Focus Latitude: 36.275
-Focus Longitude: 112.386
-Camera : 512 → rendering window
-Camera Y: 384 → rendering window
-View Arc: 80 → View width in degrees
-Sun Longitude: 172
-Sun Latitude: -0.9
-Haze Start: 3.8
-Haze Range: 78, 5
&lt;/pre&gt;
As soon as the values ​​shown in the relevant sliders have been modified, we will be ready to open the CamView window to observe the wireframe preview. Let's not consider all the controls that will appear.
Well from the Motion Editor if you have selected Camera Altitude and open the CamView panel, you can change the height of the camera by holding down the right mouse button and moving the mouse up and down. To update the view, press the Terrain button in the adjacent window. As soon as you are convinced of the position, confirm again with Keep. You can carry out the same work with the other functions of the camera, such as Focus Altitude...
Let's now see the next positioning step on the Camera map, but let's leave the CamView preview window open while we go to Modules to open the window at the same time MapView. We will thus be able to take advantage of the view from the other together with a subjective one.


From the MapView window, select with the left mouse button and while it is pressed, move the Camera as desired. To update the subjective preview, always click on Terrain.
While with the same procedure you can intervene on the direction of the camera lens, by selecting the cross and with the left button pressed you can choose the desired view. So with the pressure of Terrain I update the Preview. Possibly can enlarge or reduce the Map View using the Zoom button, for greater precision.
Also write that the circle around the cameras indicates the beginning of the haze, there are two types (haze and fog) linked to the altitude. Would also add that the camera height is editable through the Motion Editor panel.


The sun

Let's see that changing the position of the sun from the Motion Editor. Press the SUN button at the bottom right and set the time and the date. Longitude and latitude are automatically obtained by the program. Always open the View Arc command from the Motion Editor panel, an item present in the Parameter List box.

Once again confirm everything with Keep and then save again.


Animation

The animation part is not left-back and also occupies a window. The settings possibilities are enormous. A time line with dragging functions (&quot;slide&quot;, &quot;drag&quot;...) comparable to that of LightWave completes this window. 


A small window is available for positioning the stars as a function of a date, in order to vary the seasons and their various events (and yes...).

At the bottom of the &quot;Motion-Editor&quot;, a &quot;cam-view&quot; function will give you access to a control panel. Different preview modes are possible. The rendering is also accessible through a window. No less than nine pages compose it. At this level, you will be able to determine the backup name of your images (&quot;path&quot;), the type of texture to be calculated, the resolution of the images, activate or deactivate functions such as the depth buffer (&quot;zbuffer&quot;), the blur, the background image, etc.


Once all these parameters have been set, all you have to do is click on the &quot;Render&quot; button.

For rendering go to Modules and then Render. Select the resolution, then under IMA select the name of the image. Move to FRA and indicate the level of fractal detail which of 4 is quite good. Then Keep to confirm and then reopen the window, pressing Render you will see the result. The image will be opened with any viewing program.


Strengths:

* Multi-window.
* Quality of rendering.
* Accuracy.
* Opening, preview and rendering on CyberGraphX screen.
* Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats 
* The &quot;zbuffer&quot; function.

Weaknesses:

* No OpenGL management 
* Calculation time.
* No network computing tool.


====Writing CD / DVD - Frying Pan====

Can be backup DVDs (4GB ISO size limit due to use of FileInfoBlock), create audio cds from mp3's, and put .iso files on discs

If using for the first time - click Drive button and Device set to ata.device and unit to 0 (zero)

Click Tracks Button - Drive 1 - Create New Disc or Import Existing Disc Image (iso bin/cue etc.) - Session File open cue file

If you're making a data cd, with files and drawers from your hard drive, you should be using the ISO Builder.. which is the MUI page on the left. (&quot;Data/Audio Tracks&quot; is on the right).

You should use the &quot;Data/Audio tracks&quot; page if you want to create music cds with AIFF/WAV/MP3 files, or if you download an .iso file, and you want to put it on a cd.

Click WRITE Button - set write speed - click on long Write button

Examples

Easiest way would be to burn a DATA CD, simply go to &quot;Tracks&quot; page &quot;ISO Builder&quot; and &quot;ADD&quot; everything you need to burn.

On the &quot;Write&quot; page i have &quot;Masterize Disc (DAO)&quot;, &quot;Close Disc&quot; and &quot;Eject after Write&quot; set.

One must not &quot;Blank disc before write&quot; if one uses a CDR


AUDIO CD from MP3's are as easy but tricky to deal with. FP only understands one MP3 format, Layer II, everything else will just create empty tracks

Burning bootable CD's works only with .iso files. Go to &quot;Tracks&quot; page and &quot;Data/Audio Tracks&quot; and add the .iso


====odf====

Every ODF file is a collection of several subdocuments within a package (ZIP file), each of which stores part of the complete document.

* content.xml – Document content and automatic styles used in the content.
* styles.xml – Styles used in the document content and automatic styles used in the styles themselves.
* meta.xml – Document meta information, such as the author or the time of the last save action.
* settings.xml – Application-specific settings, such as the window size or printer information.


To read document follow these steps:

* Extracting .ods file.
* Getting content.xml file (which contains sheets data).
* Creating XmlDocument object from content.xml file.
* Creating DataSet (that represent Spreadsheet file).
* With XmlDocument select “table:table” elements, and then create adequate DataTables.
* Parse child’s of “table:table” element and fill DataTables with those data.
* At the end, return DataSet and show it in application’s interface.


To write document follow these steps:

* Extracting template.ods file (.ods file that we use as template).
* Getting content.xml file.
* Creating XmlDocument object from content.xml file.
* Erasing all “table:table” elements from the content.xml file.
* Reading data from our DataSet and composing adequate “table:table” elements.
* Adding “table:table” elements to content.xml file.
* Zipping that file as new .ods file.

XLS file format

The XLS file format contains streams, substreams, and records.

These sheet substreams include worksheets, macro sheets, chart sheets, dialog sheets, and VBA module sheets. 
All the records in an XLS document start with a 2-byte unsigned integer to specify Record Type (rt), and another for Count of Bytes (cb). A record cannot exceed 8224 bytes. If larger than the rest is stored in one or more continue records.

* Workbook stream 
**Globals substream
***BoundSheet8 record - info for Worksheet substream i.e. name, location, type, and visibility. (4bytes the lbPlyPos FilePointer, specifies the position in the Workbook stream where the sheet substream starts) 
**Worksheet substream (sheet) - Cell Table - Row record - Cells (2byte=row 2byte=column 2byte=XF format)
***Blank cell record
***RK cell record 32-bit number. 
***BoolErr cell record (2-byte Bes structure that may be either a Boolean value or an error code)
***Number cell record (64-bit floating-point number)
***LabelSst cell record (4-byte integer that specifies a string in the Shared Strings Table (SST). Specifically, the integer corresponds to the array index in the RGB field of the SST)
***Formula cell record (FormulaValue structure in the 8 bytes that follow the cell structure. The next 6 bytes can be ignored, and the rest of the record is a CellParsedFormula structure that contains the formula itself)
***MulBlank record (first 2 bytes give the row, and the next 2 bytes give the column that the series of blanks starts at. Next, a variable length array of cell structures follows to store formatting information, and the last 2 bytes show what column the series of blanks ends on)
***MulRK record 
***Shared String Table (SST) contains all of the string values in the workbook.

ACCRINT(), ACCRINTM(), AMORDEGRC(), AMORLINC(), 
COUPDAYBS(), COUPDAYS(), COUPDAYSNC(), COUPNCD(), COUPNUM(), COUPPCD(), 
CUMIPMT(), CUMPRINC(), 
DB(), DDB(), DISC(), 
DOLLARDE(), DOLLARFR(), 
DURATION(), EFFECT(), FV(), FVSCHEDULE(), 
INTRATE(), IPMT(), IRR(), ISPMT(), MDURATION(), MIRR(), NOMINAL(), NPER(), NPV(), 
ODDFPRICE(), ODDFYIELD(), ODDLPRICE(), ODDLYIELD(), 
PMT(), PPMT(), PRICE(), PRICEDISC(), PRICEMAT(), PV(), RATE(), 
RECEIVED(), SLN(), SYD(), TBILLEQ(), TBILLPRICE(), TBILLYIELD(), 
VDB(), XIRR(), XNPV(), YIELD(), YIELDDISC(), YIELDMAT(),


&lt;pre&gt;
&lt;/pre&gt;


&lt;pre&gt;
&lt;/pre&gt;

&lt;pre&gt;
&lt;/pre&gt;

{{BookCat}}</text>
      <sha1>6bxp1ug5u7wng8jk3aosdf4momppz86</sha1>
    </revision>
  </page>
  <page>
    <title>How to Type/Introduction to Typing</title>
    <ns>0</ns>
    <id>253820</id>
    <revision>
      <id>4678514</id>
      <parentid>4441203</parentid>
      <timestamp>2026-10-27T17:05:38Z</timestamp>
      <contributor>
        <username>Weisongyang</username>
        <id>3629511</id>
      </contributor>
      <minor />
      <comment>Made the gramatical mistake correct with suitable collection of words, and made the content easy to understand by people. Secondly i had added sources to learn online typing.</comment>
      <origin>4678514</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1574" sha1="pqniiuzbolas1lylmkqaj5us578i7j6" xml:space="preserve">In the good old days of mechanical typewriter, typing used to be a skill possessed by very few. But with computers becoming accessible for masses, typing has become an everyday activity. While pressing keys to input text is simple, doing it accurately and at fast speeds without looking at the keyboard is what is necessary.

This book will help you:

* Learn how to type efficiently.
* Type at faster speeds.

Typing efficiently is crucial for '''preventing common frustrations''' such as:

* Making frequent mistakes while typing.
* Accidentally deleting text.

Typing at faster speeds can be a significant advantage, especially when meeting a tight deadline. When your fingers are trained to hit the right keys as soon as a word comes to mind, typing becomes much faster compared to the &quot;hunt-and-peck&lt;ref&gt;{{Cite web |title=Free Online Typing Speed Test &amp; Keyboarding |url=https://www.typingbattles.com/blog/touch-typing-vs-hunt-and-peck |access-date=2026-10-27 |website=TypingBattles |language=en}}&lt;/ref&gt;&quot; method. The skill of typing can prove to be of immense help at home, at school, in the office, and in virtually any environment.

Learning how to type is becoming a fundamental life skill. Typing doesn't take much time to learn—just a few focused hours if you are ready. If you are looking for additional free resources to practice typing, you can explore typing.com, monkeytype.com or typingbattles.com for supplementary typing exercises.

==Finding a good program for typing==
Any text editor can be used to learn typing as described in this book.

{{BookCat}}</text>
      <sha1>pqniiuzbolas1lylmkqaj5us578i7j6</sha1>
    </revision>
  </page>
  <page>
    <title>C programming/Index</title>
    <ns>0</ns>
    <id>266906</id>
    <revision>
      <id>4678623</id>
      <parentid>4666412</parentid>
      <timestamp>2026-10-27T22:47:59Z</timestamp>
      <contributor>
        <username>Alexey Vazhnov</username>
        <id>120729</id>
      </contributor>
      <comment>/* F */ fix internal link to [[../Program flow control#for_loops]]</comment>
      <origin>4678623</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5399" sha1="09hy6r3oxowo8bpe11kzzeuod57sk2t" xml:space="preserve">{{Nav}}

This is an alphabetical index of the book.

{{CompactTOC}}

==A==
* &lt;code&gt;argv&lt;/code&gt; - poorly treated
** [[../Pointers and arrays/#sizeof]]
* [[../Arrays/]]
* Assignment
** [[../Variables/#Declaring, Initializing, and Assigning Variables]]
** [[../Simple math/#Assignment operators]]
* [[../Variables#auto|&lt;code&gt;auto&lt;/code&gt;]]

==B==
* Boolean
** [[../Control#Conditionals]]
* [[../Control#Loops|&lt;code&gt;break&lt;/code&gt;]]

==C==
* [[../Memory management#The calloc function|&lt;code&gt;calloc&lt;/code&gt;]]
* [[../Control#The_Switch-Case_statement|&lt;code&gt;case&lt;/code&gt;]]
* [[../Simple_math#Cast_operators|Cast operators]]
* &lt;code&gt;char&lt;/code&gt;
** [[../Variables/#The char type]]
* [[../Structure_and_style#Comments|Comments]]
* [[../Control#Relational_and_Equivalence_Expressions|Comparison]]
* [[../Compiling/]]
* [[../Variables#const_qualifier|&lt;code&gt;const&lt;/code&gt;]]
* [[../Control#Loops|&lt;code&gt;continue&lt;/code&gt;]]
* [[../Control#Conditionals|Conditionals]]
* [[../Control|Control structures]]

==D==
* Data types
** [[../Variables/]]
** [[../Complex types/]]
* [[../Control#The_Switch-Case_statement|&lt;code&gt;default&lt;/code&gt;]]
* [[../Control#Do-While_loops|&lt;code&gt;do&lt;/code&gt;]]
* [[../Preprocessor#.23define|&lt;code&gt;#define&lt;/code&gt;]]
* &lt;code&gt;double&lt;/code&gt;
** [[../Variables/#The double type]]

==E==
* [[../Control#Conditionals|&lt;code&gt;else&lt;/code&gt;]]
* [[../Preprocessor#.23if,.23else,.23elif,.23endif (conditionals)|&lt;code&gt;#else&lt;/code&gt;]]
* [[../Preprocessor#.23if,.23else,.23elif,.23endif (conditionals)|&lt;code&gt;#elif&lt;/code&gt;]]
* [[../Preprocessor#.23if,.23else,.23elif,.23endif (conditionals)|&lt;code&gt;#endif&lt;/code&gt;]]
* [[../Preprocessor#.23error|&lt;code&gt;#error&lt;/code&gt;]]
* [[../Variables#extern|&lt;code&gt;extern&lt;/code&gt;]]

==F==
* [[../File_IO|Files]]
* &lt;code&gt;float&lt;/code&gt;
** [[../Variables#The float type]]
* [[../Program flow control#for_loops|&lt;code&gt;for&lt;/code&gt;]]
* [[../Memory management#The free function|&lt;code&gt;free&lt;/code&gt;]]
* [[../Procedures_and_functions|Functions]]
* [[../Procedures_and_functions#Variable-length argument lists|Variadic functions]]

==G==
* [[../Control#One_last_thing:_goto|&lt;code&gt;goto&lt;/code&gt;]]

==I==
* [[../Control#Conditionals|&lt;code&gt;if&lt;/code&gt;]]
* [[../Preprocessor#.23if,.23else,.23elif,.23endif (conditionals)|&lt;code&gt;#if&lt;/code&gt;]]
* [[../Preprocessor#.23ifdef,.23ifndef|&lt;code&gt;#ifdef&lt;/code&gt;]]
* [[../Preprocessor#.23ifdef,.23ifndef|&lt;code&gt;#ifndef&lt;/code&gt;]]
* [[../Preprocessor#.23include|&lt;code&gt;#include&lt;/code&gt;]]
* Input and output
** [[../Simple input and output/]]
** [[../File IO/]]
* &lt;code&gt;int&lt;/code&gt;
** [[../Variables/#The int type]]

==L==
* Logical operators
** [[../Simple math/#Logical operators]]
** [[../Control#Logical Expressions]]
* &lt;code&gt;long&lt;/code&gt;
** [[../Variables/#Data type modifiers]]
* [[../Control#Loops|Loops]]

==M==
* [[../Preprocessor|Macros]]
* &lt;code&gt;main&lt;/code&gt; - poorly treated
** [[../Pointers and arrays/#sizeof]]
* [[../Memory management#Malloc|&lt;code&gt;malloc&lt;/code&gt;]]
* Math
** [[../Simple math/]] - addition, subtraction, multiplication, division, and modulus
** [[../Further math/]] - functions from &lt;code&gt;math.h&lt;/code&gt; library
* [[../Memory management/]]
* Multidimensional arrays
** [[../Common practices/#Dynamic multidimensional arrays]]

==O==
* Operator
** [[../Simple math/]]
** [[../Reference tables/#Table of Operators]]

==P==
* [[../Preprocessor#.23pragma|&lt;code&gt;#pragma&lt;/code&gt;]]
* [[../Preprocessor/]]
* &lt;code&gt;printf&lt;/code&gt;
** [[../Simple input and output/#Output using printf()]]
** [[../C reference/stdio.h/printf/]]
** [[../Procedures and functions/printf/]]
* Pointers
** [[../Pointers and arrays/]]
** [[../Complex types/#Pointers]]
* [[../Procedures_and_functions|Procedures]]

==R==
* [[../Memory management#The realloc function|&lt;code&gt;ralloc&lt;/code&gt;]]
* [[../Variables#register|&lt;code&gt;register&lt;/code&gt;]]
* [[../Procedures_and_functions|&lt;code&gt;return&lt;/code&gt;]]

==S==
* &lt;code&gt;short&lt;/code&gt;
** [[../Variables/#Data type modifiers]]
* &lt;code&gt;signed&lt;/code&gt;
** [[../Variables/#Data type modifiers]]
* [[../Variables#sizeof|&lt;code&gt;sizeof&lt;/code&gt;]]
* Standard libraries
** [[../Standard libraries]]
** [[../Procedures and functions#Functions from the C Standard Library]]
** [[../assert.h]]
** [[../complex.h]]
** [[../ctype.h]]
** [[../errno.h]]
** [[../fenv.h]]
** [[../float.h]]
** [[../inttypes.h]]
** [[../iso646.h]]
** [[../limits.h]]
** [[../locale.h]]
** [[../math.h]]
** [[../setjmp.h]]
** [[../signal.h]]
** [[../stdarg.h]]
** [[../stdbool.h]]
** [[../stddef.h]]
** [[../stdint.h]]
** [[../stdio.h]]
** [[../stdlib.h]]
** [[../string.h]]
** [[../tgmath.h]]
** [[../time.h]]
** [[../wchar.h]]
** [[../wctype.h]]
* [[../Variables#static|&lt;code&gt;static&lt;/code&gt;]]
* [[../Procedures_and_functions#Static Functions|Static functions]]
* [[../Strings/]]
* [[../Complex types|&lt;code&gt;struct&lt;/code&gt;]]
* [[../Procedures_and_functions|Subprograms]]
* [[../Control#The_Switch-Case_statement|&lt;code&gt;switch&lt;/code&gt;]]

==T==
* [[../Complex_types|&lt;code&gt;typedef&lt;/code&gt;]] - seems poorly treated

==U==
* [[../Preprocessor#.23undef|&lt;code&gt;#undef&lt;/code&gt;]]
* [[../Complex_types#Unions|&lt;code&gt;union&lt;/code&gt;]]
* &lt;code&gt;unsigned&lt;/code&gt;
** [[../Variables/#Data type modifiers]]

==V==
* [[../Procedures_and_functions#Variable-length argument lists|Variable-length argument lists]]
* [[../Procedures_and_functions#Variable-length argument lists|Variadic functions]]
* [[../Variables#volatile|&lt;code&gt;volatile&lt;/code&gt;]]

==W==
* [[../Control#Loops|&lt;code&gt;while&lt;/code&gt;]]

==Variables==
* [[../Variables/]]

{{Nav}}</text>
      <sha1>09hy6r3oxowo8bpe11kzzeuod57sk2t</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Koavf</title>
    <ns>3</ns>
    <id>269776</id>
    <revision>
      <id>4678658</id>
      <parentid>4674949</parentid>
      <timestamp>2026-10-28T08:01:50Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <comment>/* Ideas for next Wikibooks Magazine */ new section</comment>
      <origin>4678658</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="29750" sha1="527h60767l7u0d2dkawj75o8qpu26cq" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Koavf!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks. [[User:QuiteUnusual|&lt;span style=&quot;color:#E66C2C&quot;&gt;'''QU'''&lt;/span&gt;]] &lt;sup&gt;[[User talk:QuiteUnusual|&lt;span style=&quot;color:#306754&quot;&gt;TalkQu&lt;/span&gt;]]&lt;/sup&gt; 08:04, 19 April 2012 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;

I see you've been editing for years but nobody has said Hi, so Hi! [[User:QuiteUnusual|&lt;span style=&quot;color:#E66C2C&quot;&gt;'''QU'''&lt;/span&gt;]] &lt;sup&gt;[[User talk:QuiteUnusual|&lt;span style=&quot;color:#306754&quot;&gt;TalkQu&lt;/span&gt;]]&lt;/sup&gt; 08:04, 19 April 2012 (UTC)

== Our confusing subject/category hierarchy ==

The way we've got things set up is less than ideal; it's grown up over the years as we've tried to make do with the wiki software we've been given.  I can try to fix up a Subject:Anarchism for you later today (anywhere from a few minutes to a few hours from now).  Here's an attempt to explain generally how it all works:
* Each book has a ''book category'', which contains all the pages in that book (and also any templates specific to that book).
* Each subject has a ''subject category'', which contains the main pages of all the books that explicitly name that subject.
* Each subject has an associated ''allbooks category'', which contains the main pages of all the books that explicitly name either that subject, or any of its subsections.
There are a series of pages that (unfortunately) have to be set up just right in order to make all that happen; it's a bit tricky.  We really ''should'' have a full-blown interactive wizard for managing it all, but while we're waiting for that (I'm working on tools for building wizards, over at [[n:Help:Dialog|English Wikinews]]), it can be confusing.
* '''''If''''' template {{tl|subjects}}, on the main page of a book,is given the name of a subject that has been set up just the way expected by our semi-automation, the template automatically lists the book under the named subject and all the ancestors of that subject.  For example, I've now set up a [[Subject:Christianity]], so putting {{tlx|subjects|Christianity}} on a book's main page will now cause it to be listed in that subject, and also in [[Subject:Abrahamic religions]], [[Subject:Religion]], and [[Subject:Humanities]].
* Creating a category for a topic, such as [[:Category:Anarchism]], doesn't automatically set up an associated subject.
* There ''is'' a way to get assistance with setting up a category, though it sure would be nice to have more assistance than it gives.  I used this assistance to set up [[Subject:Christianity]] a few minutes ago, and, as I say, I'll try to do [[Subject:Anarchism]] soon.  The trick is to edit the book's main page, add parameter &quot;{{!}}diagnose=true&quot; to the {{tl|subjects}} template, and preview the page; there's no need to save the page.  If there's a &quot;subject&quot; page there that hasn't been set up properly, the preview presents you with a bunch of buttons for setting up the needed infrastructure pages.
--[[User:Pi zero|Pi zero]] ([[User talk:Pi zero|discuss]] • [[Special:Contributions/Pi zero|contribs]]) 15:09, 12 September 2014 (UTC)
:{{Ping|Pi zero}} I figured out how ''some'' of that was working by tinkering myself. Thanks. My only concern was that there were existing categories which are more refined and better for navigation which you were emptying it out of. If you think a category is ''too'' refined and should be upmerged (and you may not think this), then discussion would be better. Thanks. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:12, 12 September 2014 (UTC)

:: Yeah, it can be awkward to decide when something is worth creating a child subject for, and when it's better to simply list it in the parent subject.  I suppose it depends on how well-defined the child subject is, and how naturally it fits into the existing hierarchy.  It ''usually'' wouldn't make sense, for instance, to create a subject just so that a single book could be put in it.

:: When a non-subject category is passed to {{tl|subjects}}, so that the template is unable to list the book in subjects as it's supposed to, the template puts out a call for help by adding the book to [[:Category:Attention needed (allbooks)]].  Every once in a while I remember to go look there, and fix all the problems it reports.  Usually this consists of changing parameters to the template, to put the book in subjects that have been set up rather than ones that haven't been set up.  However, sometimes the subject really ''should'' be set up.  As, for example, [[Subject:Christianity]].  I got partway into shifting listings to [[Subject:Abrahamic religions]] before my higher reasoning caught up with me and said, wait a minute, there are already child subjects for Islam and Judaism, why on Earth wouldn't there be one for Christianity?  (This is my laughing at myself.)  --[[User:Pi zero|Pi zero]] ([[User talk:Pi zero|discuss]] • [[Special:Contributions/Pi zero|contribs]]) 15:32, 12 September 2014 (UTC)
:::{{Ping|Pi zero}} Exactly: there is and will be enough material to warrant a division but maybe not for Rastafarianism (at least not now or soon). By the way, thanks for all the work you do wb and wn--they don't get enough attention as WMF projects. I can tell that you really want to improve them. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:34, 12 September 2014 (UTC)

== Fonts ==

@PeterEasthope: Can you show me the page that you are editing?
: Justin, the problem is now solved with module [[Oberon/A2/Oberon.MediaWiki.Mod]].  The module pages in Oberon are produced by that module.  Regards, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 15:29, 15 January 2018 (UTC)

== Color gradient ==

Hi. What means square bracket in : &quot;[S]eparate the calculation phase from the colouring phase&quot;—Claude Heiland-Allen  ? --[[User:Adam majewski|Adam majewski]] ([[User talk:Adam majewski|discuss]] • [[Special:Contributions/Adam majewski|contribs]]) 16:13, 2 March 2020 (UTC)
:{{Ping|Adam majewski}} I don't know; I didn't add the quote. :/ It does seem unhelpful. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:14, 2 March 2020 (UTC)
:: Yes, but you have add bracket : &quot;Latest revision as of 18:04, 1 March 2020 (edit) (undo) (thank) Koavf (discuss | contribs)    rollback 1 edit&quot; --[[User:Adam majewski|Adam majewski]] ([[User talk:Adam majewski|discuss]] • [[Special:Contributions/Adam majewski|contribs]]) 16:50, 2 March 2020 (UTC)
:::{{Ping|Adam majewski}} Oh, you are just asking about the bracket? Sorry. I added that because in English, it is common to add brackets at the beginning of lines where you only have part of a quotation. The quotation here has no punctuation and doesn't seem to be a complete thought, so I just assumed that it's a quotation from mid-sentence. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:53, 2 March 2020 (UTC)

== Mathematics(about lines ,areas and volumes) ==

Let's start with the notion of a point that is considered as the most fundamental thing of Eucledian geometry .what is a point? You heard that point has position but it has no length ,neither breadth nor width.
Now let's discuss a little about unit(because it is must for further discussion).

Now, what is unit ? You heard that when we measure a physical quantity, we have to a convenient part of the same quantity as documentary and this part is called unit. When measuring the quantity we only concern with the number of unit and specify the unit as letters or another symbols(say, a length of 3cm ,here 3 is the number of unit presented in the measurement and cm is the particular part that we take as unit).Remember this passage as it is helpful for further discussion.

Now ,let's talk about lines . You heard that line is the combination of infinite points.But is this statement true?
Hitherto we discussed about units ,there we take a unit as a convenient part of the same quantity. So ,is the property of line and point same? 
If we take the definition of line ,we heard line has length ,neither breadth nor width but a point has nothing but a position.so from definition their properties  are not same ,the are different with their properties.
Then ,how can a line be made of points?
Now one can say,
&quot; One can find infinite points on line,then why shouldn't we take line as the combination of points?&quot;
It is also documentay.
But we should think that from definition the point has no lenth then how can we form a length by combining points ?as one point has no length then how a few points can form a length? 
You will understand better by an example, take the shadow of an object ,will this shadow be thicker if we place the shadow of another object on it? No!!
Then what is true ,a line is made of points or not?
And if the line is not made of points then what is the connection between line and point? As we can find infinite points on a line.

You should remember the whole discussion and relate this while compairing the line and area.in this also somebody say that area is made of infinite lines.This statement is controversial, too.As line has no breadth how lines make an area?
And same controversy for volumes.
You can think a point as a property of line at a position.And you should concern about this controversy.

Thank you, for reading!! [[User:Debdut Guha|Debdut Guha]] ([[User talk:Debdut Guha|discuss]] • [[Special:Contributions/Debdut Guha|contribs]]) 03:20, 15 July 2020 (UTC)
:Oh, okay. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:20, 15 July 2020 (UTC)

==A new proposal==
[[File:Internet-group-chat.svg|link=|alt=|left|48x48px]]Hi {{BASEPAGENAME}}, there is currently a proposal at [[: Wikibooks:Reading room/Proposals]] for non-admins to be given the ability of  &lt;code&gt; Suppress redirect&lt;/code&gt; and &lt;code&gt; Move subpages&lt;/code&gt;. Since you’ve been an active user on Wikibooks for the last thirty day, I thought you might join in by giving feedback/opinion or amendments. Thank you so much for your time [[User:Synoman Barris|Synoman Barris]] ([[User talk:Synoman Barris|discuss]] • [[Special:Contributions/Synoman Barris|contribs]]) 14:18, 14 September 2020 (UTC)

== You should become an en.wiki admin. ==

Just curious why you are not. [[User:Tgregtregretgtr|T. Gregtregretgtr]] ([[User talk:Tgregtregretgtr|discuss]] • [[Special:Contributions/Tgregtregretgtr|contribs]]) 23:28, 17 January 2022 (UTC)
:{{ping|Tgregtregretgtr}} I haven't been dedicated to this wiki in the past. No particular reason: it's a great idea and resource. There are just 24 hours in a day. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:42, 17 January 2022 (UTC)
:: Koavf,I meant the English Wikipedia. [[User:Tgregtregretgtr|T. Gregtregretgtr]] ([[User talk:Tgregtregretgtr|discuss]] • [[Special:Contributions/Tgregtregretgtr|contribs]]) 23:42, 17 January 2022 (UTC)
:::Oh, well I had been nominated by others but displayed incompetence in the nominations. I also am blocked there at present for edit-warring. I'm hoping the community sees the value in me contributing in the future, but that's predicated on me having a clear plan for constructive editing that builds trust in other editors that I will act appropriately. Edit-warring is unacceptable, so I will have to show that I won't engage in it on en.wp and I haven't proven that to a sufficient amount yet. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:51, 17 January 2022 (UTC)
:::: On April 1st,Wikipedia will not make vandalism allowed. OK? [[User:Tgregtregretgtr|T. Gregtregretgtr]] ([[User talk:Tgregtregretgtr|discuss]] • [[Special:Contributions/Tgregtregretgtr|contribs]]) 23:57, 25 January 2022 (UTC)
:::::It's never allowed. Were it allowed, it wouldn't be vandalism. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 00:06, 26 January 2022 (UTC)

== Welcoming users ==

Hi, I see you left the welcome message in my user page back when I joined this wikimedia project. I’m interested in welcoming new users here. How do I go along doing that? Thanks in advance, -[[User:Gifnk dlm 2020|Gifnk dlm 2020]] &lt;span style=&quot;color:purple;&quot;&gt;From Middle English Wikipedia&lt;/span&gt; 📜📖💻  ([[User talk:Gifnk dlm 2020|talk]]) 15:09, 18 January 2022 (UTC)
:{{Ping|Gifnk dlm 2020}} I have only ever welcomed users as I've happened to find them, e.g. if a new user edits a page on my watchlist. If you want to make it a point to welcome new users, you can check [[Special:RecentChanges]] with [https://en.wikibooks.org/wiki/Special:RecentChanges?userExpLevel=newcomer&amp;hidebots=1&amp;hideWikibase=1&amp;limit=1000&amp;days=30&amp;urlversion=2 these filters]. I generally only welcome someone who has actually made edits and not just anyone who creates an account, but you could do either. The {{tl|welcome}} template is helpful and particularly if you add some kind of personal message below substituting it. I'm glad you want to do outreach to others. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 18:18, 18 January 2022 (UTC)

::Thank you very much! I will start welcoming users. -[[User:Gifnk dlm 2020|Gifnk dlm 2020]] &lt;span style=&quot;color:purple;&quot;&gt;From Middle English Wikipedia&lt;/span&gt; 📜📖💻  ([[User talk:Gifnk dlm 2020|talk]]) 18:22, 18 January 2022 (UTC)

== Recipe style guidelines ==

Hello! Your feedback would be welcome and appreciated at [[Cookbook_talk:Policy/Recipe_template#Style_guidelines]]. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:20, 24 November 2022 (UTC)

== Hello ==

Hello to koavf.I read your comment and you suggested a few things.

These were:

&lt;nowiki&gt;*&lt;/nowiki&gt;Craigslist, Fiver, Upwork, etc.*

what are these [[User:Germany Poul Ah|Germany Poul Ah]] ([[User talk:Germany Poul Ah|discuss]] • [[Special:Contributions/Germany Poul Ah|contribs]]) 05:14, 2 September 2023 (UTC)

:These are websites where you can list [[:w:en:want ads|want ads]]. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 05:19, 2 September 2023 (UTC)
::How to do it? [[User:Germany Poul Ah|Germany Poul Ah]] ([[User talk:Germany Poul Ah|discuss]] • [[Special:Contributions/Germany Poul Ah|contribs]]) 04:40, 3 September 2023 (UTC)
:::The easiest to make a post on is https://craigslist.org/ I can't promise you will get any responses there either, but it's a little more likely than here at least. Good luck. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 04:44, 3 September 2023 (UTC)
::::Thank you,I really can't write my six books. [[User:Germany Poul Ah|Germany Poul Ah]] ([[User talk:Germany Poul Ah|discuss]] • [[Special:Contributions/Germany Poul Ah|contribs]]) 13:11, 3 September 2023 (UTC)

== [[Special:Diff/4322625]] ==

Hi @[[User:Koavf|Koavf]]! Sorry about that! I didn't realize that non-breaking spaces were important. I'm in the habit of removing odd/out of place characters. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:37, 6 September 2023 (UTC)

:They're certainly helpful. Thanks for all you do, KC. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 04:50, 6 September 2023 (UTC)

== Help bring a book over from the French wikibooks ==

Hi {{PAGENAME}},

Since you contribute to many wmf-wikis as a functionary, I wonder if you can tell me what is the easiest way to bring the book [[The Wikimedia movement]] over here from the French wikibooks. This book was written by [[User:Lionel Scheepmans]] who 
: &quot;holds a doctorate in political and social sciences, is a free-culture activist and is a lecturer in anthropology at UCLouvain University. He holds several administrative positions within the Wikimedia movement, which he has been observing in a participatory way since 2011. Before writing his doctoral thesis on the Wikimedia movement, he was the author of a master's thesis entitled [[Wikiversity:Fr:Culture fr Wikipedia|Culture fr Wikipedia]], in which he describes the organization of the free encyclopedia in French.&quot;

Any help you can offer would be greatly appreciated. Thanks in advance,
Also @[[User:MathXplore|MathXplore]], @[[User:Kittycataclysm|Kittycataclysm]], @[[User:SHB2000|SHB2000]], @[[User:MarcGarver|MarcGarver]], @[[User:Leaderboard|Leaderboard]], @[[User:Xania|Xania]], @[[User:Atcovi|Atcovi]] [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 19:12, 12 March 2024 (UTC)

:Hi {{re|Ottawahitech}}, it needs to be imported and then translated. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 20:19, 12 March 2024 (UTC)
:Mind if I take a look at it in a few days time? Sorry for the delay – uni exams rn are killing me. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 20:29, 12 March 2024 (UTC)
::It will need to be exported then imported using importupload (an XML file upload). It's not difficult, but you can find the session timing out if the file is particularly large. All admins have importupload rights here. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 22:40, 12 March 2024 (UTC)
:Always happy to help, but I don't have advanced permissions here. :/ —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 01:05, 13 March 2024 (UTC)
: I guess others have answered the question. I would like to note that translation can also be done in userspace (By starting things at userspace or moving to there after import). Feel free to move to mainspace from userspace after translation is complete. Please also note that Wikibooks reviewers and admins can move pages without redirects (Please see [[special:UserGroupRights]] for details). [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 01:28, 13 March 2024 (UTC)
::Thanks to all for contributing here. I am still fuzzy about the procedure for bringing the book [[The Wikimedia movement]] over from the French wikibooks and translating it into English. 
::I looked up [[Wikibooks:Requests for import]], is this where non-admin users are supposed to request help from an Admin (I guess importers cannot import books that are not written in English)? According to [[Help:Importing]], pages are imported to the ''Transwiki namespace'', but I am not sure what happens then, and where the translation from French to English is supposed to take place before the translated text can get merged into the existing skeleton set up by [[User:Lionel Scheepmans]]. 
::Thanks in advance, [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 17:26, 16 March 2024 (UTC)
:::{{re|Ottawahitech}}, the process is as follows:
:::* An admin or importer imports the book from fr.wikibooks (this must be done using external import aka importupload); users can request at [[WB:RFI]] among other venues.
:::* the book now lives in the Transwiki namespace. This is an opportunity for the translation to take place.
:::* Once the translation has taken place, the book is simply moved to namespace (or wherever the book is to be moved).
:::[[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 04:36, 17 March 2024 (UTC)

== Re:Cats ==

Hi @[[User:Koavf|Koavf]]! Just touching base re: [[Special:Diff/4480484]]—I didn't notice that you had just added that category when I removed it, so I hope it didn't come off as rude. The primary reason that page shouldn't have that category is because it's not a recipe page—it's an ingredient page. I'm also overhauling a bunch of cookbook categories in general to resolve several persistent issues that have cropped up over the years. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:35, 8 March 2025 (UTC)

:Not at all, KC. I saw that you were clearly removing entries from the category for deletion. I could never judge you. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:37, 8 March 2025 (UTC)

== I have a little problem :Linear Algebra and the C Language ==

I have a small problem with my book, can you help me? Thank you.

https://en.wikibooks.org/wiki/Linear_Algebra_and_the_C_Language

[[User:Xhungab|Xhungab]] ([[User talk:Xhungab|discuss]] • [[Special:Contributions/Xhungab|contribs]]) 08:38, 18 October 2025 (UTC)

== Email ==

I sent you an email, feel free to take a look. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:34, 3 July 2026 (UTC)

== The Elements Wikijunior book ==

I closed a discussion that there is no consensus–there was one in favor and one against, but there is no clear consensus to feature The Elements on the main page. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:20, 11 July 2026 (UTC)
: However, since you implemented the functions to feature the book, I wouldn't try to reverse or fight against it since it's done. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:25, 11 July 2026 (UTC)
::Oh boy, yeesh. What a screw up. Let me fix that immediately. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 18:52, 11 July 2026 (UTC)
:::Yikes. This is what happens when I decide as soon as I wake up, &quot;I'll help!&quot;. Reading comprehension is important. Thanks/sorry. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 18:54, 11 July 2026 (UTC)

== Redirect of [[Wikibooks:Username]] ==
Hello Koavf,
Could you perhaps create a redirect of [[Wikibooks:Username|this page]] to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]? I would create the redirect myself, however only sysops can make it. Is that alright?
Regards, [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:04, 20 September 2026 (UTC)

:I'm a little reluctant to make a cross-namespace redirect without some other feedback. Can you make the request somewhere that will give it more feedback? Thanks. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 14:24, 20 September 2026 (UTC)

== Ideas for next Wikibooks Magazine ==
Hi Koavf,
I have created the discussion page to discuss ideas for the next Wikibooks Magazine [[Wikibooks talk:Magazine/1|here]]. Please feel free to contribute your ideas. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:01, 28 October 2026 (UTC)</text>
      <sha1>527h60767l7u0d2dkawj75o8qpu26cq</sha1>
    </revision>
  </page>
  <page>
    <title>Yoga/Basic Yoga Series</title>
    <ns>0</ns>
    <id>278237</id>
    <revision>
      <id>4678501</id>
      <parentid>4676067</parentid>
      <timestamp>2026-10-27T15:06:45Z</timestamp>
      <contributor>
        <username>CommonsDelinker</username>
        <id>49843</id>
      </contributor>
      <comment>Removing [[:c:File:Yoga_teacher_adjusting_student_in_Halasana_plow_pose_at_Om_Setu_Yogashala_Rishikesh.jpg|Yoga_teacher_adjusting_student_in_Halasana_plow_pose_at_Om_Setu_Yogashala_Rishikesh.jpg]], it has been deleted from Commons by [[:c:User:Herbythyme|</comment>
      <origin>4678501</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="41479" sha1="b7le9f22lgl5zhfurtjf06m41ifnopn" xml:space="preserve">[[File:CrescentMoon2.JPG|thumb|400px]][[File:Basic Yoga Series.ogv|thumb|Basic Yoga Series (15 min.)]]
Yoga provides a variety of techniques ([[w:List of asanas|List of asanas]]). It has techniques for the body and the mind. We should practice each yoga exercise so, that it works well for us. What hurts us, we omit it. What is good, that we do. We can vary all yoga exercises creative. We ask ourselves constantly: “What do I need now? What’s good for me? What triggers best my tensions?” Find your individual rhythm and your priorities. Do the breaks at the right moment and in the right track. If you do not want to spend much time for yoga, just do a little break at the end. Through the exercises you will gain experience with yoga. You learn the key techniques. You get a lot of exercise tips. After a while you'll know what is good for you. You'll find out what yoga exercises you need personally. You'll find your personal way to practice yoga. Yoga is an ongoing experiment. On the way to self-realization, you will need many different yoga practices. There are specific techniques for each stage of development. If you know the basic exercises presented here, you will find quickly in any situation the right technique.

== Basic Yoga Series ==
[[File:Basic Yoga Series.png|thumb]]
The Basic [[w:Yoga series|Yoga Series]] takes about 10 to 20 minutes. Decide how much time you want to invest every day in your path of yoga. Practice the Basic Yoga Series so that it is good for you. Make small relaxation breaks between the exercises, if it is helpful for you. In a yoga group, there is basically after each exercise a short break. At home you can relax at the end of the series. The relaxation at the end is important because most of the tensions resolve there and we get into a good mood. 

1. Cycling = We lie on our back on the yoga mat (blanket). We are raising the head, arms and legs. We move the arms and legs like riding a bicycle. We think the mantra &quot;Cycling&quot;. We move to the left and right side. 

2. Pelvic rotation = We lie down outstreched on the floor. The arms surround the head. We rotate the pelvis to the left and head to the right. And vice versa. We focus on the spine. We do this gently several times, so that we solve well the tensions in the spine.

3. Candle = From the supine position, we stretch the legs to the sky and prop up us on the back with our hands. We move the legs, such as cycling and think the mantra &quot;Candle&quot;. 

4. Swing =  We roll gently from the candle in the supine position and pull our knees toward our chest. We embrace our legs and relax rocking from side to side. It is as if we swing lovingly a little kid.

5. Arm-leg raising = We turn around and lie on our stomach. We lift the right arm and the left leg stretched as far as possible. We then lift the left arm and right leg. We do this several times and count the numbers from 1 to 20 in the body.

6. Pelvic rotation =  In the prone position we lie our head on the hands and turn with our breath   several times the pelvis relaxed to the left and right. We focus on the spine and twist as much as possible.

7. Feet = We stay relaxed in the prone position and move softly our feet. The head rests on the hands. We focus on the feet and move it relaxed and gently on our way.

8. Meditation = We rise up in a sitting position (heel seat or cross-legged) and put the hands in our lap (or on the legs). The back is straight and the belly relaxed. We think the mantra &quot;Om Shanti&quot; until our mind comes to rest.

9. Blessing = We move our hand and think, &quot;I send light to (name). May all people be happy. May the world be happy.&quot;

10. Relaxation = We lie down comfortably and relax. First we stop one minute every thought, focus on the feet and move it gently. Then we relax for a few minutes completely.

---&gt; [http://www.wikihow.com/Do-Yoga-for-Absolute-Beginners-%28Basic-Yoga-Series%29 Basic Yoga Series with pictures]

== Dynamic Mantra Yoga ==
[[File:Dynamic Mantra Yoga (20 min.).ogv|thumb|Dynamic Mantra Yoga (20 min.)]]
The dynamic Mantra Yoga is a quick way to relaxation, health and happiness. We connect dynamic yoga exercises with mantras (positive words). We resolve systematically the tensions in all parts of the body. By this we get health and happiness. We become happy out of ourselves.  Learn it in an easy way with the video. It is good for beginners and advanced. This yoga series lasts 20 minutes. The first ten minutes we make the dynamic exercises and the second 10 minutes we meditate. Do yoga as it is good for you. 

1. Cycling = We lie on our back on the yoga mat (blanket). We raise the head, arms and legs. We move the arms and legs like riding a bicycle. We think the mantra &quot;Cycling&quot;. We move to the left and right side.

2. Butt knocking = We turn onto the back, put our feet on the ground near the butt and knock a minute dynamic with the butt up and down on the ground. We work all our stress and aggressions out. We focus on our body. We lift the butt while knocking so much in the air, that we resolve the tensions in the upper body.

3. Feet and fist stomping = Move all your anger out and think the mantra &quot;Anger&quot;.

4. Candle = We go into the candle, straighten both legs to the sky and support us with our hands at the back. We think the mantra &quot;Candle&quot;. 

5. Spine rotation = Lie down on your back. Move your pelvis to the left and your head to the right side. Both to the other side. Twist on this way several times your spine. Feel the spine. Move your feet and rotate the spine. Resolve all tension in your spine. 

6. Arm-leg raising = We turn around and lie on our stomach. We lift the right arm and the left leg stretched as far as possible. We then lift the left arm and right leg. We do this several times and count the numbers from 1 to 20 in the body. 

7. Up and down = Sit in the heel seat, raise your hands up to the sky, visualize a beautiful sun and think the mantra &quot;Light&quot;. Bow forward in the heel seat, bring the light to the earth and think &quot;Light&quot;. Do this several times. Finally put your hands behind your back and bring it together with your arms extended upward. This relaxes the chest. 

8. Meditation seat = We rise up in a sitting position (heel seat or cross-legged).
a) Move a hand in blessing: &quot;I send light to (name). May all people be happy. May the world be happy.&quot;
b) Think a minute the mantra &quot;Om Shanti&quot;. 

9. Meditation in lying = 
a) Count the nummers 1 to 20 in the head, chest, belly, legs and feet.
b) Tense and relax twice all muscles.
c) Move your feet.
d) Relax some minutes completely.

10. Get up and think the mantra: &quot;Om all enlightened Masters. Om inner wisdom. Please guide and help me on my way.&quot;

==Computer Yoga==
[[File:Computer Yoga with Yogi Nils.ogv|thumb|Computer Yoga (sitting, 9 min.)]]
Don´t work too much. Don´t rest too much. Find your personal balance. Stay healthy and happy. Do every day some spiritual exercises. Do Computer Yoga every day. It is very easy. Relax in a few minutes. Go positiv through your life. 

1. Move your head and '''think the mantra 5 to 10 times &quot;Om&quot; in your head.''' Turn your head left and right. Forward and backward. 

2. Move your shoulders, so that all tensions resolve. What is the best way for you? Move forward, and another way round. '''Move with your elbows and think &quot;Om, Om, Om...&quot;''' And another way round. Om..

3. Move your spine to the right and left side. The head also. '''Think &quot;Om , Om, Om.. &quot; in your spine.''' 

4. Move your feet on the ground. '''Say &quot;Om&quot; in your belly, in your legs, in your feet and in the earth. Concentrate on the whole earth and think the mantra &quot;Earth&quot;.''' 

5. Massage your body from head to feet. Put your hands over your head together, rub the palms, visualize the sky above you and '''say the mantra &quot;Heaven&quot;. The light comes down and you massage the light into your face, your eyes, your ears, your whole body and think &quot;Light, Light...&quot; Fill yourself with light. Move your feet, fill light into the earth and think, &quot;Light ...&quot;'''

6. Move your hand and send light so your people, '''&quot;I send light to ... May all people be happy. May all the world be happy.&quot;'''

7. Rub your palm together, think on the enlightened masters and say, '''&quot;Om all enlightened masters, please help me on my way.&quot;''' Now you can ask a question. Think about your life. What are your goals? What is your way? Hear the answer within you. Feel the answer inside. What is the answer? 

8. Put your hands on your legs or your belly. '''Make your mind calm and think the mantra &quot;Om&quot; in your head, your thorax, your belly, your legs, feet, in the earth and in the whole cosmos. &quot;Om Om Om Shanti Om Peace Om Peace Om Shanti Om Peace ...&quot;'''

9. Stop one minute all your thinking. '''Sit only there. Don´t think.''' 

10. What do you have to take in your life? Take it. What is your positive sentence now? What helps you to go positive through your day and your life? '''&quot;My positive sentence is: I am optimistic. I go my way optimistic.&quot;''' 

*[http://www.youtube.com/watch?v=69ctHFfR3I8 Computer Yoga for Advanced (video, 9 min.)]
*[http://www.youtube.com/watch?v=XJrp2W77sIg Computer Meditation (video, 5 min.)]

== Creative Hatha Yoga ==
[[File:Creativ Hatha Yoga.jpg|thumb|200px]]
In the Western world we have relaxation yoga, power yoga, stretch yoga, meditation yoga and different kinds of spiritual yoga. Creative Hatha Yoga works with all of these techniques. Most western yogis first learn one special yoga way and then they practice creative yoga. Whatever you choose to do, the main point is to follow your own wisdom, to feel what you need and to find your personal yoga practice. The Creative Hatha Yoga is a way of spontaneously and creatively develop the currently useful yoga exercises. Listen to the voice of your inner wisdom and feel in your body. What exercises do you need right now? How you must practice it, so that your inner tensions dissolve, that your Kundalini energy awakes and you get in a state of happiness and well-being? Try different yoga exercises. Feel what is good for you. Developed your personal yoga series. 

Watch the [http://www.youtube.com/watch?v=66nn6QE-J1w video (Creative Hatha Yoga)]. The video is in german language, but you can understand it, when you read the following text.

1. Circle = We start with the shaking. We run on tiptoe on the spot and shake the body. We turn around. We massage light in the whole body and think the mantra  ”Light, Light, Light … “

2. Cobra = We slowly bow forward. We lay on the ground. We base our head on the hands. We highlight the knees slightly and swing the feet back and forth. We count in the kidneys the numbers 1 to 20.

3. Pelvic rotation = We lay with our head on the hands and relax. We rotate the basin far to the left and right, back and forth. We focus on the spine. 

4. Feet = We move the feet and toes slightly. We circle the feet over the ground. We feel the feet. Relax.

5. Massage = We come up and kneel down on the heels. We turn in the spine to the right. The head is also turning. We turn to the left. The head is also turning. We massage the body from top to bottom. We rub all the stress and tension out.

6. Earth rubbing = We bend forward in the heel seat. We rub the ground with our hands and think the mantra “Earth”. We draw with our hands a circle of light on the earth around us. We sit in the circle of light. What color has the circle of light? Yellow, orange, blue, gold? 

7. Cycling = We turn around and lay on our backs. We move with the feet a bike ride. We lay our hands on the belly, lift the head, the legs turn to the right and left. The head always shows in the opposite direction.

8. Shoulder stand (Sarvangasana) = We go into the candle. The feet points to the sky. We base with our hands up at the back. We go on riding a bike with our feet, see the light around us, thinking the mantra “Light” and turn our head slightly to the left and right.

9. Plow Pose (Halasana) = From Sarvangasana, gently lower both straight legs over the head until the toes touch the floor behind you. Support the spine with the hands or interlace fingers on the ground. Halasana stretches the entire spine, calms the nervous system, and stimulates the thyroid gland before transition.

10. Blessing = We gently roll down from the posture into our meditation seat (cross legged). We move a hand in blessing and think, “I send light to (name). May all people be happy. May the world be happy.”

11. Meditation (Shavasana) = We lie down on the back. We lay our hands on the belly. We move the feet and toes. We think “Om” in the body, legs and feet, “Om, Om, Om ..” We send all people over the world our “Om”. We feel the cosmos. We feel one with our world. Everything is fine the way it is. We do not have to be perfect. We rest until we feel well. Then we slowly come back. We stretch and loll us. We are back and in a positive mood.

* [http://commons.wikimedia.org/wiki/File:Creative_Hatha_Yoga.ogv Video Creative Hatha Yoga (germ., 6 min.)]

== Fitness Yoga ==
[[File:Fitness Yoga.ogv|thumb|Fitness Yoga (10 min.)]][[File:Fitness Yoga.jpg|thumb|200px]]
Fitness Yoga is a dynamic form of yoga. We can eliminate our stress after work and recharge us with positive energy. In 10 minutes we are fit again.

1. Shake Meditation = We make five minutes the  [[Yoga_oracle#Shake_Meditation|Shake Meditation]] and move out all the accumulated stress: Dissolve your anger (think the mantra, &quot;anger&quot;). Dissolve your grief (&quot;I'm sad because ...&quot;). Circle your shoulders. Twist your spine. Massage your body. Rub the earth with your feet. 

2. Windmill = In triangle stand (feet apart) we bow forwards with a straight spine. We extend our arms out to the sides and turn ten times in the spine backwards and forwards. The hand points to the opposite foot. We think the numbers 1 to 20 in our body.

3. Pushups = We do ten pushups. We count as a mantra in the body the numbers 1 to 20.

4. Arm-leg raising = We turn around and lie on our stomach. We lift the right arm and the left leg stretched as far as possible. We then lift the left arm and right leg. We do this several times and count the numbers from 1 to 20 in the body.

5. Pelvic rotation = We lie our head on the hands and turn with our breath several times the pelvis relaxed to the left and right. We focus on the spine and twist as much as possible.

6. Butt knocking = We turn onto the back, put our feet on the ground near the butt and knock a minute dynamic with the butt up and down on the ground. We work all our stress and aggressions out. We focus on our body. We lift the butt while knocking so much in the air, that we resolve the tensions in the upper body.

7. Abdominal muscle training = We put our hands together behind your head and pull thirty times the head to the knees. The knees are bent and move to the head. We move our upper body 10 times in the middle high, 10 times  to the right and 10 times to the left side. We count in the body of the numbers 1 to 30.

8. Candle = We go into the candle, straighten both legs to the sky and support us with our hands at the back. We breathe one minute relaxed into the body.

9. Meditation = We rise up in a sitting position (heel seat or cross-legged) and put the hands in our lap (or on the legs). The back is straight and the belly relaxed. We think the mantra &quot;Om Shanti&quot; until our mind comes to rest. We move our hand and think, &quot;I send light to (name). May all people be happy. May the world be happy.&quot;

10. Relaxation = We lie down comfortably and relax. First we stop one minute every thought, focus on the feet and move it gently. Then we relax for a few minutes completely.

== Kids Yoga ==

The greatest gift we can give our children is a spiritual education. If we teach our children positive values​​, they will be able to lead a happy and successful life. If we bring them close to inner happiness as the center of life, one day they will find their own way to get there.

1. Sun = We stand in a circle and put our hands together in front of the heart chakra. We bow to each other and think, &quot;We welcome the sun.&quot;

2. Sky = We raise our arms to the sky and stand on the tip toe. &quot;We welcome the sky.&quot;

3. Moon = We stand like a moon, bow to the left and then to the right side in the hips, and move the outer arm over our head. &quot;We welcome the moon.&quot;

4. Stars = We make big circles with our arms, visualize the entire cosmos full of stars and think, &quot;We welcome the stars.&quot;

5. All children = We're turn ourselves with outstretched arms in the spine left and right, see the children around us and say, &quot;We welcome all children.&quot; 

6. Grass = We bow the upper body forwards and rub with our hands in circles the earth, &quot;We welcome the grass.&quot;

7. Fun = We stand again up straight, put one foot on the opposite knee, standing on one leg like a yogi and shout: &quot;This is fun.&quot; For this we applaud vigorously with the hands, until we have all the good mood.

== Yoga Series against Anxiety ==
[[File:Yoga against Anxiety.jpg|thumb|200px]]
Fears are part of our time. Many people have fears. Anxiety is caused by work pressure, violence and movies on TV. Yoga can help to overcome fears by relieving inner tensions, calming the mind and generate positive thoughts. Yoga gives us the strength to overcome anxiety provoking situations. Yoga makes us inwardly and outwardly strong. If you get enlightened, all fears vanish. Face it.

1.  Anger = We lie on our back and put our feet on the bottom near the butt. Our knees are upright. The head is on the earth. We pound our fists on the ground and stomp our anger alternately with our feet in the ground. We solve all the pent-up anger. To whom or what are you angry today?

2.  Butt Knocking = We knock a minute dynamic with the butt up and down on the ground. We work all our stress and aggressions out. We focus on our body. We lift the butt while knocking so much in the air, that we resolve the tensions in the upper body.

3. Bridge = We put in the supine position our arms around the head and press the pelvis as much as possible upwards. The shoulders and the head rest on the floor. We make large circles with our pelvis in the air. First ten times left and then ten times right around. We visualize water and think the mantra &quot;Water&quot;.

4. Candle = We go into the candle, straighten both legs to the sky and support us with our hands at the back. We breathe one minute relaxed into the body.

5. Meditation Posture = We're rolling out of the candle into the heel seat (or cross legged). We stretch our arms to the sky. We breathe in. Then we bow before us and put the hands on the floor. We breathe out. This exercise we do several times and count the numbers 1 to 20 in the body. 

6. Blessing =  In our meditation seat we move a hand in blessing and think, &quot;I send light to (name). May all people be happy. May the world be happy.&quot; We then think the mantra &quot;Light&quot; and send light a) to our friends b) to our enemies c) to ourselves.  We massage the light into our body.

7. Meditation = We sit in the meditation position (cross-legged or heel seat) and put the hands in the lap. The back is straight and the belly relaxed. We stop one minute every thought. Then we remain in meditation, thoughts can come and go as they please. All feelings of anger, fear and grief appear and dissolve by themselves.

8. Forward = Forward with optimism.

* See also: [https://www.youtube.com/watch?v=c8dDFlVMfiw Video Yoga for Anxiety from Sue], [https://www.youtube.com/watch?v=SP_pn8QEjsw Video Yoga for Anxiety Ekhart Yoga], [https://www.youtube.com/watch?v=IsSQx5GIwEw Yoga for Anxiety (Video from Amy)], [http://yoga.wonderhowto.com/how-to/reduce-anxiety-using-yoga-with-tara-stiles-289271/ Video Tara Stiles]

*  [http://www.livestrong.com/article/102423-yoga-poses-anxiety-depression/ yoga-poses-anxiety-depression], [http://www.yogajournal.com/for_teachers/2390 Yoga for Anxiety and Panic Attacks], [http://vitailluminata.com/yoga-therapy-anxiety/ Yoga Therapy for Anxiety]

== Yoga Stretching ==
[[File:Fb1.jpg|thumb|100px]]
Yoga stretching strengthens the agility of the body. By stretching, combined with a relaxed concentration on the body, the tensions in the muscles is released. See also the video [http://www.youtube.com/watch?v=C639ArXu1iw BEGINNING YOGA FOR STRETCH AND STRENGTH (10 min.)].

1. Plier =  In standing or sitting. We stretch our legs forward. The hands grasp the feet. We pull the head as far as possible to the feet. We move the feet gently back and forth. We send light from the head  to our feet and think: &quot;Light, light, light.&quot;

2. Butterfly = In sitting. We pull the feet to the body, put the soles of our feet together, grasp the feet and stretch the knee sideways to the ground. The back is straight. We move the knee like a butterfly gently up and down. We think the numbers from 1 to 20 in the legs.

3. Spine = We sit cross-legged. The spine is straight. We rotate several times in the spine. The head spins also. The eyes look left and right to the horizon. What do we see there?

4. Blessing = We move a hand in blessing and think: &quot;I send light to ... (name). May all people be happy. May the world be happy.&quot;

5. Meditation = The back is straight and the head upright. The hands lie in the lap. We stop one minute every thougt. We relax.

==Yoga with Meditation ==
[[File:Yoga with Meditation.png|thumb|200px]] 
101. Yoga with meditation is slowly and quietly. The various yoga postures activate our chakras (inner energy channels) and load us with good energy. Meditation while the yoga exercises brings our minds to rest. We  meditate on each yoga posture 1 to 3 minutes. We feel how each yoga posture forms a specific energy field (aura field) around the body. Through the creation of certain energy fields, we clean our body and mind of tensions. It is helpful, if we can feel the spiritual energy. But it is not necessary. It is enough to concentrate relaxed on our body and the postures.  We take breaks as needed between the yoga exercises.

1. Leg raising = We lie on our back and lift a minute the stretched right leg. We meditate on the right leg. The toes point to the head. The head rests on the ground. We set off and lift the stretched left leg as far as possible. The toes point to the head. We meditate for one minute on the left leg. The arms lie relaxed at the sides.

2. Two-leg raising = In the supine position we lift up both legs. The toes point to the head. We raise our head towards the feet. We send a light beam from the toes to the head and think the mantra &quot;Light&quot;. We breathe in the stomach. We meditate one minute on the posture.

3. Candle = We go into the candle, straighten both legs to the sky and support us with our hands from the back. We breathe one minutes relaxed into the body.

4. Feet = We roll from the candle again in the supine position, stretch our legs, put our hands on the belly and move gently our feet. We stop our mind and focus a minute on our belly.

5. Cobra = We turn on our stomach and lift as far as possible a minute the upper body with our back muscles. The head is in the back, the hands are placed laterally from the body on the floor. We breathe relaxed into the cobra. We send a beam of light from the head down the back and think &quot;Light&quot;.

6. Locust = We set off the head and lift the right leg stretched as far as possible in the air. We meditate one minute on the leg. We lift the left leg for a minute and concentrate relaxed on it.

7. Cobra with feet to head = We raise like in the cobra the upper body and head. The hands are placed laterally from the body on the floor. In addition, we now lift both legs and bring the feet as close as possible to the head. We breathe relaxed in the stomach and hold the position for a minute. We send a beam of light from the feet to the head and think the mantra &quot;Light&quot;.

8. Pelvic rotation = In the prone position we lie our head on the hands and turn with our breath several times the pelvis relaxed to the left and right. We focus on the spine and twist as much as possible.

9. Meditation = The back is straight, the head upright, and we relax the belly. The hands lie in the lap. We circulate light in the head, in the whole body, in the legs, feet, arms and hands. At the same time we think the mantra &quot;light, light, light&quot;. We visualize in the earth a small star (dot of light). The star circulate in the earth and we think, &quot;Earth&quot;. Then we let the star circulate in the sky above us, around our body and in our body. Thereby we think the mantra &quot;Star, Star, Star.&quot; We rub in circles with one hand our stomach and the star comes to rest.

10. Relaxation = We lie down or sit in a comfortable position and move gently our feet. We stop one minute all thoughts. Then we relax completely. Go your way positive. Take things as they are. Concentrate on your goals. Work for a world of love, peace and happiness. Move a hand, send all people light and think, &quot;I send light to (name). May all people be happy. May the world be happy.&quot;

==Yoga with Positive Thinking==
[[File:Yoga and positive thinking.ogv|thumb|Yoga with Positive Thinking, Video 10 min.]]
[[File:Yoga with positive thinking.jpg|thumb]]
Yoga with positive thinking is very helpful for many people. It allows one to quickly overcome negative tendencies and reach a happy and healthy life. Positive thinking and daily meditation are the two basic techniques of enlightenment. All the negative characteristics are ultimately based on attachment (to external pleasures, other people, to his ego) or rejection (of suffering situations, pain). If we accept the suffering in our lifes and let go of our worldly desires and longings, the tensions in our minds resolve. Our inner happiness creates a positiv feeling of life. We get into a life in the light (in a paradise view of life). The main way to overcome the negative qualities is to focus on the positive qualities of wisdom, self-discipline, peace, love and happiness.

1. Go = Jog on the spot, with your arms moving by your side. Visualize light, turn around and think, '''&quot;I go the positive way.&quot;''' 

2. Windmill = Straddle your legs apart, bow forward, turn like a windmill into the spinal column and think: '''&quot;My goal is ...&quot;.''' 

3. Frog = Bring your feet together. Bow your upper body forward. Push yourself up with your hands on the floor and move your buttocks down in a crouch and back up in the air. The head goes up to the sky and down to the earth. Practice the frog several times and think: '''&quot;I have strength and endurance.&quot;'''

4. Arm-leg raising = Lie down on your stomach. Raise your left arm and right leg. Bring both back to the earth and lift the right arm and the left leg. Do this several times. Think, '''&quot;I take things the way they are.&quot;''' 

5. Upper body raising = Lie in the prone position, with your hands on the floor and repeatedly press the upper body up and down. The head goes to the neck and forward. While breathing in and out, think, '''&quot;I let go of my false desires.&quot;''' 

6. Pelvic rotation = In the prone position, turn your pelvis to the right and then to the left. Your head must lie on your hands. Think, '''&quot;I am sad because ...&quot;.''' 

7. Feet = Get your feet moving in the prone position. The head lies relaxed on your hands. Think, '''&quot;I forgive... (my partner / parents / the cosmos / God), that he/she...&quot;.''' Whom do you want to forgive today? Think these words until a feeling of sadness arises in you, of letting go and forgiveness.

8. Cycling =  Turn on your back, lift your head and move your arms and legs. Think, '''&quot;My positive thought today is....&quot;.'''

9. Candle = Stretch your legs to the sky. Your hands support you at the back. Visualize the sky, move your feet and think many times the mantra '''&quot;Optimism&quot;.'''

10. Meditation = Roll from the candle into your meditation seat (cross-legged or heel seat). Put your hands in your lap. The back is straight and the stomach is relaxed. Move one hand and wrap them and think, '''&quot;I send light to ... May all people be happy. May the world be happy.&quot;''' Stop all your thoughts for a minute. Relax.

==Office Yoga==
[[File:Schultz in Italy.jpg|thumb|400px]]
Today's professional life is marked by a lot of stress and strain. The Office Yoga helps us to preserve our health and inner happiness.

1. Stretch =  We put our hands together, turn up the palms outside and stretch our hands pleasurably over the head. We keep our hands above the head and breathe several times deeply in and out.

2.  Right and left stretch = We stretch the right and left side of the body. We continue to hold the hands over the head and breathe several times in the stretched side of our body.

3. Spine rotation = We continue to hold the outstretched hands above our head. We turn the spine several times to the right and to the left side. 

4. Elbow circles = We lay the hands on the shoulders and make dynamic circles with the elbows. We resolve the tension in the shoulders and neck. We feel that movement we need and what is good for us. We make small and large circles.

5. Head moving =  We lay our hands on the legs. We stretch the head backwards,  to the right side,  to the left side and let him hang forward. Each time we breathe relaxed in and out.

6. Massage =  We rub the eyes and face, so that we can see clearly again. We visualize a color of healing and massage it from head to foot on our body. What is your healing color today? We think the name of our color as a mantra: &quot;orange, blue, gold, pink ...&quot;. We  bow down and rub also the ground. 

7. Meditation = We put the hands in our lap, thinking the mantra: &quot;I am a Buddha (Shiva, Goddess) of the rest. I live in the rest.  I go the way of rest.&quot; Then we move a hand in blessing and think: &quot;I send light to (name). May all people be happy. May the world be happy.&quot;

8. Little Bird = We rub our feet on the ground, visualize ourselves as a tree with  roots, trunk, leaves and crown. Thereby we think as mantra: &quot;Tree.&quot; We let the roots grow deep into the earth and think our mantra until we are well rooted in the earth. A little bird comes flying, sits on the tree and gives us a positive sentence. What is your bird? What does he say to you?

== Three Abdominal Exercises ==
  
We lay our hands on the legs. The back is straight. The belly is relaxed.

1. Pelvic floor = We tense the pelvic muscles, stop our breath, think the numbers 1 to 20 in the pelvis and move the toes. Then we relax the pelvis.

2.  Belly = We move the abdominal muscels to the spine, exhale, stop the breath, think in the belly 1 to 20 and move the toes. We relax.

3. Chest = We draw the belly in the chest, exhale, hold our breath, think in the chest the numbers 1 to 20 and move the toes. We relax.

4. Spine = We tense again the pelvic muscles, pull our stomach in the chest, hold our breath and turn us several times in the spine to the right and left. We also rotate the head. We think the numbers 1-20 in the body. We relax.

5. Healing = We rub our hands in front of the heart chakra and ask the enlightened Masters (God) for help. &quot;Om all enlightened Masters. Om inner wisdom. Please guide and help me on my way.&quot; We now can make a question of healing. We hear the answer inside. What is your problem? What is your healing question? What is the answer of your inner wisdom? What solves the problem?

6. Healing salve = We visualize a healing salve in our hands, think her color as a mantra and rub it into our whole body. We massage the ointment especially on our sick body areas. What is your color of healing? Rub it for so long in the diseased area of ​​the body, until it has absorbed all the healing energy.

7. Blessing = We rub with our feet the earth, move a hand in blessing and think: &quot;I send light to (name). May all people be happy. May the world be happy.&quot; We relax. Feel into your body. How do you feel now? Feel the relaxation and well-being in you.

== Bones Meditation ==

This meditation strengthens our life force. It heals our internal organs, we center us in our body and get the power to act positively.

1. Moving = We make faces, move our head, shoulders, arms, hands, legs and feet. We turn in the spine backwards and forwards. We relax.

2. Internal organs = We visualize our brain and think several times the mantra &quot;brain.&quot; We think the mantra &quot;brain&quot; until we feel that our brain is well filled with healing energy. We also visualize successively all other internal organs and think their name as mantra: &quot;Lungs, stomach, intestines, bladder, kidneys (right and left  at the back), liver (front right), spleen (front left), solar plexus, heart.&quot; In conclusion, we visualize all the organs at once and think several times: &quot;All internal organs&quot;.

3. Bones = We visualize one after another all bones and think at least twice: &quot;Skull, spine, chest bones, arm bones, hand bones, pelvis, leg bones, feet bones, skeleton.&quot; So that we can feel the individual bones better, we move them easily. Finally, we visualize all the bones together and revolve light around us. We think the mantra &quot;light.&quot;

4. Sun = We see a beautiful sun in our belly. We think the mantra &quot;Sun&quot; and thereby radiate light in our body. The sunlight becomes stronger and fills the entire universe around us with light. We move our arms and think the mantra &quot;Stars&quot;. We see the whole universe full of stars and light.

5. Stop = We stop all thoughts. We bring our mind to rest. We relax. If we have meditated enough, we return slowly. How do you feel now? Feel the relaxation and well-being in you.

== Switch Breathing ==
 
Alternate nostril breathing is an important yoga technique. It brings us into the inner balance. In the body there are three main energy channels: the left (Ida, moon, peace), the right (pingala, sun, activity) and the central energy channel (sushumna, Kundalini channel). If we have filled the left and the right channels with [[w:Prana|prana]], increases the Kundalini energy by its own in the central channel. Then appears peace, happiness and inner strength. 

1. Bellows breathing = We place one hand on your stomach and practice a minute bellows breathing. We breathe at a higher speed with the abdominal muscles and fill our body with spiritual energy (prana, light).

2. Switch breathing = We press our thumb on the right nostril and breathe with the bellows breathing through the left nostril, move the left toes and count from 1 to 20 in the body. We press with your index finger (middle finger, ring finger) on the left nostril and breathe with the bellows breathing through the right nostril, move the right toes and count 1-20 in the body. Then we switch back and forth between the left and right nostril and forth, count the numbers, until a feeling of inner peace and harmony is created.

3. Pelvic Floor = We tense the pelvic floor, count there are the numbers 1 to 20 and move the toes of both feet. We relax.

4. Circles with the upper body  = We put the hands on our knees and circle with a straight upper body several times to the left. We tense the pelvic floor and visualize a large sea around us. We think the mantra &quot;Water&quot;. Then we revolve several times in the other direction and think again the mantra &quot;Water&quot;. We relax the pelvic floor.

5. &quot;Om&quot; in the belly = We put our hands together in her lap, think a minute the mantra &quot;Om&quot; in our belly, breathe into the belly and move the toes. We stop a minute every thought. We relax.

==Goddess Yoga== 
[[File:Rautenstrauch-Joest-Museum - Durga-Altar-2451.jpg|thumb|500px|Karttikeya (peace, unity consciousness), Lakshmi (love, wealth), Durga (power), Sarasvati (wisdom, creativity), Ganesha (happiness, joy)]] 
Goddess Yoga means to pray to the Goddess, visualize the Goddess, identify with the Goddess and realize the Goddess within oneself. To visualize and to meditate on the Goddess awakes the energy of healing, happiness and enlightenment (kundalini energy). The four main Goddesses in Yoga are Durga (the Goddess of power on a tiger), Kali (the black Goddess with a sword), Sarasvati (the white Goddess with a book) and Lakshmi (the Goddess of luck with giver hands). They embody the four properties strength, peace, wisdom and love. If we want to be happy in our lives, we need all these four properties. The Goddess Yoga is the highest form of Yoga. With him we can awaken the kundalini energy (the inner happiness). We can quickly get into the light. Important in Goddess Yoga is, that we are always in touch with ourselves and our inner wisdom. We should never practice formally (without internal involvement). We should find creativity in our personal form of Goddess Yoga.

1. Durga Durga is the Goddess of power. She rides on a tiger (or lion). She has the force of a tiger within herself. What she decides to be her goal, she reaches it. She is a winner. She has many weapons around her, meaning, that she uses creative methods to reach her goals. We shake both fists near our head and think the word &quot;power&quot;, until we feel the power of Durga in us. What are the goals in your life? In which way you can reach them? '''&quot;My goal is ... My way to be victorious is ...&quot;'''

2. The black Goddess Kali has a sword. She is able to sacrifice her ego and thus to get peace in her mind. We put our hands in the lap. We rub the earth with the feet, we feel the ground and think: '''&quot;I let go of my false desires. I take the things as they are.&quot;'''

3. Sarasvati is the Goddess of wisdom and creativity. She holds a book and a rosary in her hands. She roots herself in the holy books and in her own wisdom. What is your wisdom today? Track the index finger beside the head to the sky, move it a little and think, '''&quot;Wisdom is ... Unwisdom is ...&quot;'''

4. Lakshmi is the Goddess of luck and happiness. Beside her head are two flowers. She sees the beauty in her live. She recognizes her world as a paradise. She is enlightened and has a paradise view of the cosmos. In her lap she holds a pitcher full of gold pieces. She has inner and outer wealth and spend it to her followers. What is your wealth? Recognize yourself as the Goddess of wealth. Rub your hands on your belly and think the mantra: '''&quot;The wealth in my life is... I am grateful for ... &quot;'''

5. Be a mother of the earth. Consider all beings as your children. Identify yourself with them. Wish them luck and happiness. You are now Lakshmi with the giver hands. Move your hands and think, '''&quot;I send light to ... May all people be happy. May the world be happy .&quot;'''

== Kundalini Yoga ==

We activate with the star circling the Kundalini energy and then meditate with the Shambhavi Mudra on the light within us. We thus get quickly inner peace and happiness. Sitting in the Shambhavi meditation the light flows more and more into us. The bliss grows more and more. The Shambhavi Mudra is Shivas main meditation. It is the easiest way to stay in the light (in Sat-Chid-Anananda). 

1. Earth = We visualize a bright star. We imagine the earth beneath us and circle with a star in the globe. We think the word &quot;Earth&quot; as a mantra. We circle as long with our star in the earth, until the whole earth among us is full of light. We rub the ground with the feet.

2. Sun = We see a beautiful sun in the sky. She sends her rays down on us. We let the light flow into us. We fill our entire body with light and think often the mantra &quot;Sun&quot;. We move the feet and toes.

3. Body = We circle with the star around our body and think the mantra &quot;body&quot;. We clean all the tensions around our body. We wrap us with light. We massage our body.

4. Inside =  We circle with the star in the body. We clean all areas of the body sequentially from their tensions and fill it with light. We think the mantra &quot;Light.&quot; We circle with the star particularly in our head, chest, abdomen, legs and feet. We massage the special part of the body.

5. Blessing = We move a hand in blessing and think, &quot;I send light to (name). May all people be happy. May the world be happy.&quot;

6. Om Shanti = The hands are in the belly. We tense the muscles in the pelvis, in the abdomen and chest. We keep the tension. We relax. We do that once again. Then we breathe deeply several times in the belly. We think by inhalation &quot;Om&quot; and by exhalation &quot;Shanti&quot;. We come with the mantra &quot;Om - Shanti&quot; more and more toward inner peace. Our thoughts become quiet.

7. Shambhavi mudra = By the star circling, our energy has turned inwardly. The back is straight, the head upright, and the belly relaxed. We open half or whole our eyes and focus on the energy in us (the light, a chakra, or the Kundalini channel in the middle of our body). Thus the energy of the eyes flows inwardly and stabilizes our meditation. We stop all thoughts. We concentrate on the Kundalini channel, a chakra (heart or sacral chakra) or the light within us. We spend some time in quiet meditation. Then we come back slowly.

*[http://www.youtube.com/watch?v=zsEZylK8sDA&amp;feature=fvwrel Video  of Fire Kundalini Yoga Breathing Exercise]
*[http://www.youtube.com/watch?v=OsSWWLo9g7s&amp;feature=relmfu Video Kundalini Yoga Exercises]
*[http://www.youtube.com/watch?v=xUP-imkHFfY&amp;feature=relmfu Video Chakra Meditation Technique for Kundalini Awakening]
*[http://www.youtube.com/watch?feature=player_embedded&amp;v=yMzitUCItVM Video High Kundalini Yoga Meditation Technique (Sa Ta Na Ma)]
*[http://www.youtube.com/watch?v=Jy9UBHtRhOI&amp;feature=related Video Kirtan Kriya Woman (Sa Ta Na Ma)]

{{BookCat}}</text>
      <sha1>b7le9f22lgl5zhfurtjf06m41ifnopn</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Platforms/Arm Raspberry Pi support</title>
    <ns>0</ns>
    <id>286123</id>
    <revision>
      <id>4678670</id>
      <parentid>4678063</parentid>
      <timestamp>2026-10-28T10:40:11Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4678670</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106664" sha1="gxsa8zi7eo8zh5syjnwr4li0kory2hh" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. [https://aros.sourceforge.io/nightly1.html raspi-aarch64-smp-system multicore is available] [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT). 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect up to 480p (wifi) and up to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

If no separate audio stream error - set settings -&gt; Video quality to 360p or lower as Youtube has a fallback mode at that level 

https://t.me/s/channel_name for Telegram public messages from [https://t.me/s/AROS_official AROS_official] [https://t.me/s/vamped_amiga vamped_amiga] [https://t.me/s/demoscenecracktros demoscenecracktros] 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but that has changed recently [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 

[https://www.youtube.com/watch?v=nHt_k_QkHe0 AmiWest 2026 Day 1], [https://www.youtube.com/watch?v=nA2fnaOt1Ik Amiwest 2026 Day 2],
 

[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] 
*weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], 


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2], [https://github.com/Joshua-Riek/armbian-build Linux Armbian builds for old mobile devices], [], 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>gxsa8zi7eo8zh5syjnwr4li0kory2hh</sha1>
    </revision>
    <revision>
      <id>4678672</id>
      <parentid>4678670</parentid>
      <timestamp>2026-10-28T10:46:24Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4678672</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106892" sha1="8gf9x9w2zv3ic752ufp0pzcbw8kqxdh" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. [https://aros.sourceforge.io/nightly1.html raspi-aarch64-smp-system multicore is available] [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT). 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect up to 480p (wifi) and up to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

If no separate audio stream error - set settings -&gt; Video quality to 360p or lower as Youtube has a fallback mode at that level 

https://t.me/s/channel_name for Telegram public messages from [https://t.me/s/AROS_official AROS_official] [https://t.me/s/vamped_amiga vamped_amiga] [https://t.me/s/demoscenecracktros demoscenecracktros] 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but that has changed recently [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 

[https://www.youtube.com/watch?v=nHt_k_QkHe0 AmiWest 2026 Day 1], [https://www.youtube.com/watch?v=nA2fnaOt1Ik Amiwest 2026 Day 2],
 

[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon Macs] [https://github.com/jonx/Macaros early alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] with [https://github.com/pomaros pomaros]. There is a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2076&amp;highlight=jonx&amp;pid=14193#post_14193 work in progress native Mac Apple silicon M1 M2 M3 version] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] 
*weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], 


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2], [https://github.com/Joshua-Riek/armbian-build Linux Armbian builds for old mobile devices], [], 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>8gf9x9w2zv3ic752ufp0pzcbw8kqxdh</sha1>
    </revision>
  </page>
  <page>
    <title>Introduction to Inorganic Chemistry/Review of Chemical Bonding</title>
    <ns>0</ns>
    <id>293959</id>
    <revision>
      <id>4678484</id>
      <parentid>4677992</parentid>
      <timestamp>2026-10-27T13:07:24Z</timestamp>
      <contributor>
        <username>Tem5psu</username>
        <id>1013978</id>
      </contributor>
      <minor />
      <origin>4678484</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="77763" sha1="4zyoy61r0vlar119zicnm93prek7rdj" xml:space="preserve">
== Chapter 1:  Review of Chemical Bonding==
[[File:Phosphorus-pentoxide-3D-balls.png|thumb|right|Ball-and-stick representation of chemical bonding in the molecules P&lt;sub&gt;4&lt;/sub&gt;O&lt;sub&gt;10&lt;/sub&gt; and P&lt;sub&gt;4&lt;/sub&gt;S&lt;sub&gt;10&lt;/sub&gt;.]]Molecules (and extended solids) are built from atoms that form chemical bonds.  Theories of bonding seek to explain why molecules and solids form, what their structures are, why some are more stable than others, and how they react.  As we will learn in Chapter 2, quantum mechanics gives us the most realistic picture of chemical bonding via molecular orbital (MO) theory.  However, the MO description of bonding is conceptually difficult and mathematically intensive.  This chapter will review less rigorous (but still useful) models such as Lewis dot structures and valence shell electron-pair repulsion (VSEPR) theory.  When combined with a qualitative quantum mechanical description of bonding through the concepts of orbital hybridization and resonance, these simple models can help us understand a great deal about the structures, stabilities, and reactions of inorganic molecules.

The theory of chemical bonding has a long history, dating back to ancient Greece and the atomists [[w:Democritus|Democritus]], [[w:Leucippus|Leucippus]], and the [[w:Epicureanism|Epicureans]].  They postulated the existence of immutable atoms moving through the void, and envisioned the physical properties of materials as arising from the kinds and shapes of atoms.  In his epic poem ''[[w:de_rerum_natura|De rerum natura]]'' (On the Nature of Things), the Roman poet [[w:Lucretius|Lucretius]] (c. 99 BC – c. 50 BC), drawing on his Epicurean beliefs, describes some atoms and chemical bonding in the following way:

''What seems to us the hardened and condensed''&lt;br&gt;
''Must be of atoms among themselves more hooked,''&lt;br&gt;
''Be held compacted deep within, as 'twere''&lt;br&gt;
''By branch-like atoms -- of which sort the chief''&lt;br&gt;
''Are diamond stones, despisers of all blows''&lt;br&gt;
''And stalwart flint and strength of solid iron''&lt;br&gt;
''And brazen bars, which, budging hard in locks,''&lt;br&gt;
''Do grate and scream.  But what are liquid, formed''&lt;br&gt;
''Of fluid body, they indeed must be''&lt;br&gt;
''Of elements more smooth and round -- because''&lt;br&gt;
''Their globules severally will not cohere.''

Lucretius' [https://www.gutenberg.org/files/785/785-h/785-h.htm poem] is enjoyable reading and contains some remarkable insights into the microscopic world, given the tools available at the time.  Modern analytical methods show that he was off base with his ideas about hooks and spheres, however.  We will revisit the nature of chemical bonding in the substances Lucretius mentions (diamond, quartz, iron, brass, and water) in the context of modern chemical theories to understand why they have the special properties they do.


'''Learning goals for Chapter 1:'''

*Be able to draw Lewis dot structures, assign formal charges, predict molecular geometries (including bond angles), and calculate bond orders for molecules, including hypervalent molecules and ions.
*Describe hypervalent molecules using no-bond resonance.
*Understand and articulate how predictions of molecular structure and bonding can be experimentally verified.
*Learn to construct hybrid orbitals from s and p atomic orbitals.
*Use the isoelectronic principle to design new molecules and solids.
*Rationalize bond strength and chemical reactivity using bond polarity arguments.
*Interrelate bond length and bond strength.

==1.1 Valence bond theory: Lewis dot structures, the octet rule, formal charge, resonance, and the isoelectronic principle==
[[File:electron dot.svg|350px|thumb|right|Fig. 1.1.1.  Examples of Lewis dot diagrams showing chemical bonds between carbon, hydrogen, and oxygen, and non-bonding electron pairs.]]
'''Atoms and Molecules'''&lt;br&gt;
[[w:Atomism|Atomism]], because it was dismissed by [[w:Aristotle|Aristotle]], enjoyed a long sleep in scientific discourse until it was reconsidered by  [[w:Galileo_Galilei|Galileo]], [[w:René_Descartes|Decartes]], and [[w:Pierre_Gassendi|Gassendi]] in the 1600s.  [[w:John_Dalton|Dalton]] postulated the modern atomic theory in 1808 based on his observation that elements such as hydrogen and oxygen combined in specific ratios (the Law of Definite Proportions), but the atomic theory remained contentious throughout most of the 19th century.  [[w:JJ_Thompson|Thompson]], [[w:Ernest_Rutherford|Rutherford]], [[w:Nils_Bohr|Bohr]], and others around the turn of the 20th century established that matter was indeed composed of atoms that contained heavy nuclei and light electrons, and that atoms could exist in excited states that could be interpreted as excitations of their electrons to different energy levels.  However the atomic theory did not provide a ready explanation for the bonded states of atoms in molecules.

In 1916, still more than a decade before modern quantum theory would adequately describe the shapes of [[w:Atomic_orbitals|atomic orbitals]], [[w:Gilbert_N._Lewis|Lewis]] proposed the octet theory based on the empirically observed rules of valence, i.e., the combining ratios of atoms in molecules.&lt;ref&gt;G. N. Lewis, &quot;The atom and the molecule,&quot; J. Am. Chem. Soc. 1916, 38, 762-785&lt;/ref&gt;  This theory, in hindsight, can be rationalized for s- and p-block elements by observing that main-group atoms can use their four valence orbitals (s, p&lt;sub&gt;x&lt;/sub&gt;, p&lt;sub&gt;y&lt;/sub&gt;, and p&lt;sub&gt;z&lt;/sub&gt;) to accommodate up to eight electrons, some or all of which may be shared with other atoms. In Lewis' model, the valence electrons of an atom were situated at the corners of a cube, and the cubes could share edges or faces to complete their octets.  Lewis developed a shorthand notation for these structures based on dots that represented the valence electrons, as illustrated in Fig. 1.1.1. A pair of electrons shared between atoms constitutes a chemical bond, and can also be represented as a line joining the atoms.  Four electrons shared between atoms, represented by two lines, is a double bond, and so forth.  Any pairs of electrons not involved in bonding form &quot;lone pairs&quot; that belong to one atom only and are thus not involved in bonding.

The Lewis picture is powerful in its simplicity.  It can be readily used to rationalize or predict the combining ratios of atoms, to sort plausible and unlikely structures for molecules (including large ones), and to rationalize the acid-base properties of many molecules.  It is important to remember that the model is built on a shaky, pre-quantum mechanical description of atoms and so with it, we will make mistakes.  Nevertheless it is useful to see how far we can go with the Lewis model.
&lt;br /&gt;
&lt;br /&gt;

'''Constructing the octet valence bond picture for a molecule'''&lt;br /&gt;&lt;br/&gt;
We can construct an octet picture for any molecule using the '''N-V method:'''&lt;br /&gt;

:Number of electrons ''needed'' to make separate octets around all atoms = '''N'''&lt;br /&gt;

:(N = 8 for non-H atoms, N = 2 for H)&lt;br /&gt;

:Number of ''valence'' electrons = '''V'''  (add up using group numbers; don't forget to add or subtract for charges on ions)&lt;br /&gt;

:Number of ''shared'' electrons = '''S''' = N-V; and therefore the number of bonds = S/2&lt;br /&gt;

:Fill in lone pairs everywhere else to complete octets&lt;br /&gt;


Example:  nitrate anion, NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;&lt;br /&gt;

:N = 4 atoms x 8 electrons = 32&lt;br /&gt;
:V = 5 + 6 + 6 + 6 + 1 = 24  	(N + O + O + O + charge)&lt;br /&gt;
:S = 32-24 = 8 shared electrons = '''4 bonds'''&lt;br /&gt;

:The number of lone pairs is obtained by difference: (V-S)/2 = (24-8)/2 = 8&lt;br /&gt;

:Now draw the molecule, starting with the four bonds and adding eight lone pairs to complete the octets:
&lt;br /&gt;

::[[File:Nitrate Lewis dot structure.svg|100px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:Count the shared and unshared electrons around each atom in the nitrate ion and you will see that all atoms are '''octet''' and that the total number of valence electrons (V) is 24.  If you do the N-V calculation according to the rules above, you should always get an octet structure.
&lt;br /&gt;
[[File:System2.gif|right|400px|thumb|The charges on atoms in a molecule (or an extended solid such as SiO&lt;sub&gt;2&lt;/sub&gt;) can be estimated from X-ray photoelectron spectra (XPS).  Energetic X-rays ionize atoms by kicking out electrons from their core orbitals.  By conservation of energy, the kinetic energy (KE) of an emitted electron is related to its binding energy (BE) and the energy of the incoming X-ray photon (hν) by BE = hν - KE. Electrons are harder to remove from positively charged atoms (higher BE), and easier to remove from negatively charged atoms (lower BE), relative to the neutral element.]] 
The '''formal charge''' distribution is assigned by dividing the shared (bonding) electrons equally between atoms.  Thus, the singly bonded O atoms each possess 7 electrons, and because O is in group 6, their formal charge is -1.  The doubly bonded O has a formal charge of zero.  The N atom has a formal charge of +1 because it &quot;owns&quot; 4 valence electrons and is in group 5.  

Note that the '''formal charge''' is '''not''' the same thing as the '''oxidation number''' (or '''oxidation state''').  In the nitrate ion, the oxidation state of nitrogen is +5 and the oxidation state of oxygen is -2.  The formal charge is typically closer to the &quot;real&quot; charge on the atom (as measured, e.g., by [[w:X-ray_photoelectron_spectroscopy|X-ray photoelectron spectroscopy]]).  Oxidation states are a useful bookkeeping device for keeping track of oxidation-reduction reactions, as we will discuss in Chapter 4.  Like oxidation states, the formal charges on the atoms in a molecule or ion must ''add up to its overall charge''. 

We can similarly draw the Lewis structure for ammonia as shown below:
&lt;br /&gt;

::[[File:ammonia Lewis structure.svg|200px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

&lt;br /&gt;
When we divide the shared electrons equally between the atoms, we see that the N atom has five electrons and each H atom has one. These are the same as their group numbers, and thus, all the formal charges in the ammonia molecule are zero.

Octet structures of the Lewis acid-base adduct NH&lt;sub&gt;3&lt;/sub&gt;BF&lt;sub&gt;3&lt;/sub&gt;, the hydronium ion H&lt;sub&gt;3&lt;/sub&gt;O&lt;sup&gt;+&lt;/sup&gt;, and the sulfate anion SO&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;2-&lt;/sup&gt; are shown below.  In this case (and in many Lewis structures we will draw), we leave off the implied lone pairs around the peripheral atoms.  Try calculating the number of bonds in each of these molecules using the N-V method, and fill in the lone pairs that are not explicitly drawn in.
::[[File:octet structures.jpg|400px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In cases where more than one valence bond structure is possible, we can use formal charges to decide which structures should be more or less stable.  The rules are:&lt;br /&gt;

*The formal charges on atoms are minimized in stable structures, zero being the best case.
*Negative formal charges should be placed on the most electronegative atom(s).
*Positive formal charges should be placed on the least electronegative atom(s).
*It is unfavorable to place like charges (++ or --) on neighboring atoms in a molecule.
&lt;br /&gt;

Examples of these rules are shown below for alternative structures of BF&lt;sub&gt;3&lt;/sub&gt; and ONF.  

::[[File:Boron trifluoride resonance.svg|300px|left]][[File:Atmospheric ozone.svg|400px|right|thumb|Life outside of the ocean owes its existence to the presence of ozone (O&lt;sub&gt;3&lt;/sub&gt;) in the stratosphere.  Ozone absorbs the ultraviolet light in the solar spectrum, which otherwise would cause catastrophic damage to DNA and other biological molecules.  Because ozone is produced photochemically from O&lt;sub&gt;2&lt;/sub&gt;, which is itself generated by photosynthesis, the spectroscopic signature of ozone in the atmosphere of distant planets is one possible way to look for extraterrestrial life.]][[File:Susan Solomon-Desk With Globe.jpg|right|400px|thumb|[[w:Susan_Solomon|Susan Solomon]] discovered the heterogeneous catalytic mechanism whereby ozone is decomposed by chlorofluorocarbons (freons), creating the Antarctic ozone hole.  Her work formed the basis of the [[w:Montreal_Protocol|U.N. Montreal Protocol]], an international agreement to protect the ozone layer by regulating damaging chemicals.]] 

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;br /&gt;

In the BF&lt;sub&gt;3&lt;/sub&gt; case, the structure on the left is non-octet, because there are only six electrons (three bonds) in the valence shell of B.  Such structures are said to be ''electron deficient.''  An octet structure (right) can be drawn, but it places a positive formal charge on F, the most electronegative atom in the molecule.  Thus, neither structure is completely &quot;happy,&quot; but the formal charge rules tell us that the electron-deficient structure on the left is more stable.  The electron deficiency of BF&lt;sub&gt;3&lt;/sub&gt; makes it a powerful Lewis acid.


In the case of ONF, the structure on the left is unfavorable for two reasons.  First, it places a positive formal charge on F, the most electronegative atom.  Second, there is another possible structure (right) that has zero formal charge, which is preferable to one with non-zero charge.  This means that the structure on the right, with a double bond between N and O, is more reasonable.
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::[[File:ONF resonance structures.jpg|225px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

'''Resonance structures'''&lt;/br&gt;
The ozone (O&lt;sub&gt;3&lt;/sub&gt;) molecule has two equivalent octet structures, shown below:
&lt;br /&gt;
&lt;br /&gt;

::[[File:ozone resonance structures.jpg|225px|left]]

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In both cases, the Lewis dot diagram suggests that there are three kinds of oxygen atoms in the molecule, with +1, 0, and -1 formal charges.  These structures also suggest that ozone should have one single and one double bond.  Experimentally (by [[w:Electron_diffraction|electron diffraction]]), however, we find that the molecule is symmetric, with both O-O bond lengths the same. The real (instantaneous) structure is the average of the two forms, as shown below.  In the classical Lewis picture of the molecule, we can rationalize resonance by observing that electrons, being thousands of times lighter than the nuclei of atoms, move very fast on the timescale of molecular vibrations.  Thus, in the time it takes for the oxygen atoms to adjust their positions, the electrons can move back and forth many times.  In the quantum mechanical MO picture (Chapter 2), we will see that resonance involves electrons that are fully delocalized over the atoms in the molecule. We represent resonance structures with a double-headed arrow to signify that the only difference between the Lewis structures is the distribution of electrons.

In the instantaneous structure of ozone, the formal (-) charge is shared between the two terminal oxygen atoms and therefore each one has a formal charge of -1/2.  The O-O bonds are the average of a single and a double bond, i.e., each O-O bond order is 1.5.
[[File:ozone avg structure.jpg|150px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Similarly, the nitrate anion has three resonance structures, and experimentally (by X-ray crystallography of nitrate salts) we find that all the N-O bonds in the ion are the same.  In this case, in the averaged structure, each O atom has a formal charge of -2/3 and the N-O bond order is 4/3 (=1.33...).


[[File:Nitrate ion resonance structures.png|300px|left]] = [[File:Nitrate-ion-resonance-hybrid-2D.png|119x119px]]
&lt;br/&gt;
&lt;br/&gt;
'''Inequivalent resonance structures'''&lt;br&gt;
The rules of resonance also apply to inequivalent structures, which in general will have different energies from each other.  In this case the structure of the molecule represents a weighted average of the low energy structures.  A good example is the cyanate ion, OCN&lt;sup&gt;-&lt;/sup&gt;. We can write three inequivalent octet structures for the molecule:

:&lt;math chem&gt;\ce{~^{-}O-C\equiv N  &lt;-&gt;  O=C=N^- &lt;-&gt;  ^+  O\equiv C-N^{2-}}&lt;/math&gt;

The first two are reasonable resonance structures, although we suspect the one on the left is the best because it puts the negative formal charge on the most electronegative atom.  The last one is clearly a bad resonance structure, because the formal charges are high and there is a positive charge on the oxygen atom.  The real structure is thus a weighted average of the first two.&lt;br&gt;
&lt;br /&gt;

'''No-bond resonance'''&lt;br&gt;
An interesting and useful kind of inequivalent resonance structure is one in which there is a bond order of ''zero'' between two of the atoms.  This concept of '''no-bond resonance''' is important in understanding the bonding in many halogen- and hydrogen-containing compounds. The idea is illustrated below for the generic molecule X-Y-Z, where Z might be an electronegative halogen atom such as F.  By moving the bonding electrons from the Y-Z bond onto the Z atom, and moving a lone pair from X into the X-Y bond, we generate the resonance structure shown on the right in which all atoms remain octet, but there is no bond between Y and Z.&lt;br&gt;
&lt;br /&gt;

[[File:no bond resonance.jpg|300px|left]]
&lt;br /&gt;
&lt;br /&gt;


It is important to recognize in this example that the no-bond form is only one resonance structure, and therefore the Z atom is still bound to Y.  If the two resonance structures in this example have the same energy, we would expect the X-Y bond order to be 1.5 and the Y-Z bond order to be 0.5.  Therefore the Y-Z bond should be longer than it is in a compound where the bond order is one, and it should be relatively easy to break the Y-Z bond.

Some molecular examples of no-bond resonance are shown below.  In the molecule ONF&lt;sub&gt;3&lt;/sub&gt;, the N-F bond is unusually long relative to the N-F bond in NF&lt;sub&gt;3&lt;/sub&gt;, in which the bond order is 1.  This can be explained by the no-bond resonance forms shown on the right.  Similarly, in the Lewis acid-base adduct formed by combining BH&lt;sub&gt;3&lt;/sub&gt; with CO, we can explain the long B-H bonds using no-bond resonance forms that place a partial positive charge on the H atoms.

[[File:NF no bond resonance.jpg|450px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

No-bond resonance is often used to provide an octet bonding picture for so-called '''[[w:Hypervalent_molecule|hypervalent compounds]]''', which are compounds that appear to have more than 8 valence electrons in the bonding shell of the central atom.  For example, we can consider two different valence bond structures for the triiodide ion, I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, which is formed by reaction of I&lt;sup&gt;-&lt;/sup&gt; with I&lt;sub&gt;2&lt;/sub&gt; in water:

[[File:hypervalent triiodide.jpg|370px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;


[[File:Blue Solution.jpg|200px|right|thumb|The deep blue color of starch-iodine solutions results from the complexation of linear polyiodide ions (I&lt;sub&gt;n&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;) by the starch (amylose) left-handed helix. The interior of the helix is hydrophobic.  In electron donor solvents such as ethanol and water, I&lt;sub&gt;2&lt;/sub&gt; and salts of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; have a brown color, the result of a charge transfer interaction between the solvent and solute.&lt;ref&gt;W. Saenger, &quot;The structure of the blue starch-iodine complex,&quot; Naturwissenschaften 71, 31-36 (1984).&lt;/ref&gt;&lt;ref&gt;R. D. Hancock and B. J. Tarbet, &quot;The other double helix - the fascinating chemistry of starch,&quot; J. Chem. Ed. 77, 988-992 (2000).&lt;/ref&gt;]]In this structure, the central iodine atom has 10 electrons in its valence shell, in violation of the octet rule.  [[w:Raman_spectroscopy|Raman spectra]] of the triiodide ion show that the I-I bond is weaker than the I-I single bond in I&lt;sub&gt;2&lt;/sub&gt;, suggesting that this picture is not an accurate description of the bonding.  A better representation of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; can be obtained with no-bond resonance structures, as shown below.  We will see that this picture is consistent with the MO description of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; in Chapter 2:

[[File:octet triiodide.jpg|350px|left]][[File:IodineStarch left en.svg|200px|right]]

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;br /&gt;


We can draw a similar picture for the XeF&lt;sub&gt;2&lt;/sub&gt; molecule, which has the same number of valence electrons as I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.  This picture is consistent with XPS data, which show a partial negative charge on the F atoms, as well as vibrational spectra, which show that the Xe-F bond is weaker in XeF&lt;sub&gt;2&lt;/sub&gt; than it is in the singly-bonded cation Xe-F&lt;sup&gt;+&lt;/sup&gt;.


[[File:octet XeF2.jpg|170px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Other well known examples of hypervalent compounds are PF&lt;sub&gt;5&lt;/sub&gt;, P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, and SF&lt;sub&gt;6&lt;/sub&gt;, as well as oxyacids such as H&lt;sub&gt;2&lt;/sub&gt;SO&lt;sub&gt;4&lt;/sub&gt; and HClO&lt;sub&gt;4&lt;/sub&gt;.  The hypervalent structure is often drawn for these molecules, with the explanation that d-orbitals on the central atom contribute to the bonding in dsp&lt;sup&gt;3&lt;/sup&gt; and d&lt;sup&gt;2&lt;/sup&gt;sp&lt;sup&gt;3&lt;/sup&gt; hybrids for 5- and 6-coordinate molecules, respectively.  However, realistic molecular orbital calculations show that the phosphorus and sulfur 3d orbitals are too high in energy to contribute significantly to bonding in PF&lt;sub&gt;5&lt;/sub&gt; and SF&lt;sub&gt;6&lt;/sub&gt;. For these molecules, we can use no-bond resonance to make reasonable octet structures that predict polar bonds between the central atom and F.  [[File:sf6 bonding.jpg|380px|left]][[File:Sulfur-hexafluoride-from-xtal-3D-SF.png|right|200px|thumb|Space-filling model of sulfur hexafluoride.  [[w:Sulfur_hexafluoride|SF&lt;sub&gt;6&lt;/sub&gt;]] is surprisingly unreactive with water, relative to other compounds that contain S-F bonds. The tight packing of F atoms around S prevents nucleophilic attack by water.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

In other cases, such as P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, the octet structure is unreasonable because it suggests a polar bond between P and C, with a partial negative charge on C.  Further, in the case of oxyacids such as H&lt;sub&gt;2&lt;/sub&gt;SO&lt;sub&gt;4&lt;/sub&gt; and HClO&lt;sub&gt;4&lt;/sub&gt;, X-ray crystallographic data establish that the S-O and Cl-O bonds are shorter for the oxygen atoms not bonded to hydrogen, which is more consistent with the hypervalent picture:
&lt;br&gt;&lt;br&gt;
[[File:octet&amp;hypervalent H2SO4.jpg|200px|left]][[File:Sulfuric-acid-2D-dimensions.svg|130px]]
&lt;br&gt;


The question of whether hypervalency and the octet rule are really useful descriptions of the bonding in these compounds has been considered in a number of computational studies, which have used increasingly accurate quantum mechanical calculations to determine the number of electrons associated with the central atom.  In a 2002 study, Gillespie and Silvi&lt;ref&gt;R. J. Gillespie and B. Silvi, &quot;The octet rule and hypervalence: two misunderstood concepts,&quot; Coord. Chem. Rev. 233-234, 53-62 (2002).&lt;/ref&gt; found that the population of the valence shell is greater than eight for compounds with electropositive ligands, such as P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, and less than eight for compounds such as PF&lt;sub&gt;5&lt;/sub&gt;.  They concluded that these valence electron shell populations depend primarily on the coordination numbers and electronegativities of the central atoms and their ligands, and that there is no fundamental difference between the bonding in hypervalent and non-hypervalent (Lewis octet) molecules.  This reminds us that the octet rule is not a law of nature, but rather an empirical rule that is useful within certain limits.&lt;ref&gt;R. Crabtree, &quot;Hypervalency, secondary bonding and hydrogen
bonding: siblings under the skin,&quot; Chem. Soc. Rev., 2017,
46, 1720.&lt;/ref&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:A man breathing in nitrous oxide (laughing gas) and a man ex Wellcome L0023721.jpg|right|300px|thumb|Nitrous oxide (N&lt;sub&gt;2&lt;/sub&gt;O), or laughing gas, is isoelectronic with CO&lt;sub&gt;2&lt;/sub&gt;.  The two molecules have the same shape (linear) and similar physical properties.  CO&lt;sub&gt;2&lt;/sub&gt; sublimes at -78 °C, whereas N&lt;sub&gt;2&lt;/sub&gt;O melts at -91 °C and boils at -88 °C.]]
'''The isoelectronic principle'''&lt;br /&gt;
In calculating the octet structures of molecules using the N-V method, we needed to know only the number of atoms and the number of electrons, not the identities of the atoms themselves.  This means that we will get the same answer (and the same set of octet and resonance structures) for ''any'' molecule or ion that contains (a) the same number of non-hydrogen atoms, and (b) the same total number of valence electrons.  Such molecules are said to be ''isoelectronic.''  This is a powerful conclusion because, once we have determined the electronic structure of one molecule, we can write down the same solution for ''all other molecules'' that are isoelectronic.  For example, we noted above that I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; and XeF&lt;sub&gt;2&lt;/sub&gt;, which both have 22 valence electrons, have the same valence bond structure.  We can further expect that isoelectronic molecules will have the same shapes and, very often, similar physical properties.  

The four molecules and ions below all contain three non-hydrogen atoms and 16 valence electrons.  All of them are linear molecules with two double bonds.  The four molecules and ions shown below them all contain four non-hydrogen atoms and 24 valence electrons.  These four have a trigonal planar shape.  While BF&lt;sub&gt;3&lt;/sub&gt; is a member of this isoelectronic series, we do not write it in the resonance form that contains a B=F double bond, because that would put a positive formal charge on F.
[[File:isoelectronic molecules.jpg|320px|left]]  &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;      [[File:24e molecules.jpg|left|400px]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Similarly we can show that CH&lt;sub&gt;4&lt;/sub&gt;, NH&lt;sub&gt;3&lt;/sub&gt;, NH&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;, H&lt;sub&gt;2&lt;/sub&gt;O, H&lt;sub&gt;3&lt;/sub&gt;O&lt;sup&gt;+&lt;/sup&gt;, HF, F&lt;sup&gt;-&lt;/sup&gt;, and OH&lt;sup&gt;-&lt;/sup&gt; are all isoelectronic with one non-H atom and eight valence electrons.  In the next section we will see that this gives rise to nearly identical electronic shapes for these molecules.
[[File:Gallium-arsenide-unit-cell-3D-balls.png|200px|thumb|right|Fig. 1.1.2. The tetrahedral bonding in crystals of GaAs, CdTe, CuIn&lt;sub&gt;1-x&lt;/sub&gt;Ga&lt;sub&gt;x&lt;/sub&gt;Se&lt;sub&gt;2&lt;/sub&gt; and other semiconductors is similar to that in isoelectronic Si and Ge.]]
&lt;br&gt;

'''Isoelectronic solids.'''  The isoelectronic principle works not just for molecules but for extended solids as well.  One technologically important set of isoelectronic solids are the p-block semiconductors.  The group 14 element Si is the most widely used semiconductor for electronics, but, as we will discuss later, it is not a good light emitter.  Light-emitting diodes (LEDs), which are used in lasers, high efficiency lighting, and display technologies, are made from compounds that are isoelectronic with Si and Ge, especially GaAs, GaP, AlAs, and GaN (all contain four valence electrons per atom).  CdTe and CuIn&lt;sub&gt;1-x&lt;/sub&gt;Ga&lt;sub&gt;x&lt;/sub&gt;Se&lt;sub&gt;2&lt;/sub&gt; (CIGS) are promising solar cell materials that also have the same number of valence electrons per atom.  Like Si and Ge, these compounds have tetrahedrally bonded structures in the solid state and absorb light across most of the solar spectrum, as we will discuss in more detail in Chapters 8 and 10.


The isoelectronic principle is also a powerful tool in materials research, because it provides guidance about where to look for new materials with similar and perhaps improved properties.  For example, the discovery that 8.5% efficient thin layer solar cells could be made with the compound CsSnI&lt;sub&gt;3&lt;/sub&gt;&lt;ref&gt;I. Chung, B. Lee,  J. He,	R. P. H. Chang	 and M. G. Kanatzidis, All-solid-state dye-sensitized solar cells with high efficiency, Nature 485, 486-489 (2012). doi:10.1038/nature11067&lt;/ref&gt; stimulated the exploration of many isoelectronic ABX&lt;sub&gt;3&lt;/sub&gt; compounds with the same perovskite crystal structure. Very recently thin film solar cells based on light absorbers in this structural family (MA)PbI&lt;sub&gt;3-x&lt;/sub&gt;Cl&lt;sub&gt;x&lt;/sub&gt; and FA&lt;sub&gt;x&lt;/sub&gt;MA&lt;sub&gt;1−x&lt;/sub&gt;PbBr&lt;sub&gt;y&lt;/sub&gt;I&lt;sub&gt;3−y&lt;/sub&gt; (MA&lt;sup&gt;+&lt;/sup&gt; = methylammonium, CH&lt;sub&gt;3&lt;/sub&gt;NH&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;; FA&lt;sup&gt;+&lt;/sup&gt; = formamidinium, HC(NH&lt;sub&gt;2&lt;/sub&gt;)&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;) have been reported with efficiencies as high as 22%.&lt;ref&gt;S.D. Stranks,  G. E. Eperon, G. Grancini,  C. Menelaou,  M. J. P. Alcocer, T. Leijtens, L. M. Herz, A. Petrozza, and H. J. Snaith, Electron-Hole Diffusion Lengths Exceeding 1 Micrometer in an Organometal Trihalide Perovskite Absorber, Science 342, 341-344 (2013). DOI: 10.1126/science.1243982&lt;/ref&gt;&lt;ref&gt;G. Xing,  N. Mathews, S. Sun, S. S. Lim, Y. M. Lam, M. Grätzel, S. Mhaisalkar, and T. C. Sum, Long-Range Balanced Electron- and Hole-Transport Lengths in Organic-Inorganic CH3NH3PbI3, Science 342, 344-347 (2013). DOI: 10.1126/science.1243167 &lt;/ref&gt;&lt;ref&gt;J.-P. Correa-Baena, A. Abate, M. Saliba, W. Tress, T. J. Jacobsson, M. Grätzel, and A. Hagfeldt, The rapid evolution of highly efficient perovskite solar cells, Energy Environ. Sci., 10, 710-727 (2017). DOI: 10.1039/C6EE03397K &lt;/ref&gt;

==1.2 The shapes of molecules (VSEPR theory) and orbital hybridization ==
[[Image:Water molecule dimensions.svg|thumb|200px|Geometry of the [[w:water (molecule)|water molecule]]]]
The [[w:VSEPR_theory|Valence Shell Electron Pair Repulsion (VSEPR) theory]] is a simple and useful way to predict and rationalize the shapes of molecules.  The theory is based on the idea of minimizing the electrostatic repulsion between electron pairs, as first proposed by Sidgwick and Powell in 1940,&lt;ref&gt;N. V. Sidgwick and H. M. Powell, Proc. Roy. Soc. A176, 153 (1940),&lt;/ref&gt; then generalized by Gillespie and Nyholm in 1957,&lt;ref&gt;R. J. Gillespie and R. S. Nyholm, Quart. Rev. Chem. Soc., 11, 339 (1957).&lt;/ref&gt; and then broadly applied over the intervening 50+ years.&lt;ref&gt;R. J. Gillespie, &quot;Fifty years of the VSEPR model,&quot; Coord. Chem. Rev. 252, 1315-1327 (2008). DOI: 10.1016/j.ccr.2007.07.007&lt;/ref&gt;

To use the VSEPR model, one begins with the Lewis dot picture to determine the number of lone pairs and bonding domains around a central atom.  Because VSEPR considers all bonding domains equally (i.e., a single bond, a double bond, and a half bond all count as one electron domain), one can use either an octet or hypervalent structure, provided that the number of lone pairs (which should be the same in both) is calculated correctly.  For example, in either the hypervalent or octet structure of the I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; ion above, there are three lone pairs on the central I atom and two bonding domains.  We then follow these steps to obtain the '''electronic geometry''':
&lt;br /&gt;
&lt;br /&gt;
*Determine the number of lone pairs on the central atom in the molecule, and add the number of bonded atoms (a.k.a. bonding domains)
*This number (the ''steric number'') defines the electronic shape of the molecule by minimizing repulsion.  For example a steric number of three gives a trigonal planar electronic shape.
*The angles between electron domains are determined primarily by the electronic geometry (e.g., 109.5° for a steric number of 4, which implies that the electronic shape is a tetrahedron)
*These angles are adjusted by the hierarchy of repulsions:  (lone pair - lone pair) &gt; (lone pair - bond) &gt; (bond - bond)
&lt;br /&gt;

The '''molecular geometry''' is deduced from the electronic geometry by considering the lone pairs to be present but invisible.  The most commonly used methods to determine molecular structure - [[w:X-ray_diffraction|X-ray diffraction]], [[w:Neutron_diffraction|neutron diffraction]], and [[w:Electron_diffraction|electron diffraction]] - have a hard time seeing lone pairs, but they can accurately determine the lengths of bonds between atoms and the bond angles.

The table below gives examples of electronic and molecular shapes for steric numbers between 2 and 9.  We are most often concerned with molecules that have steric numbers between 2 and 6.

{| class=&quot;wikitable sortable&quot;
|-
! Bonding electron pairs
! Lone pairs
! Electron domains (Steric #)
! Shape
! Ideal bond angle (example's bond angle)
! Example
! Image
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:linear molecular geometry|linear]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:carbon dioxide|CO&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Linear-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal planar molecular geometry|trigonal planar]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;120°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Boron trifluoride|BF&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Trigonal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bent molecular geometry|bent]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;120° (119°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Sulfur dioxide|SO&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Bent-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:tetrahedral molecular geometry|tetrahedral]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:methane|CH&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX4E0-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal pyramidal molecular geometry|trigonal pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5° (107°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:ammonia|NH&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bent molecular geometry|bent]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5° (104.5°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:H2O|H&lt;sub&gt;2&lt;/sub&gt;O]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Bent-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal bipyramidal molecular geometry|trigonal bipyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 120°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:phosphorus pentachloride|PCl&lt;sub&gt;5&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Trigonal-bipyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:seesaw molecular geometry|seesaw]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°, 120°, 90° (173.1°, 101.6°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:sulfur tetrafluoride|SF&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Seesaw-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:T-shaped molecular geometry|T-shaped]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180° (87.5°, &lt; 180°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:chlorine trifluoride|ClF&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:T-shaped-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:linear molecular geometry|linear]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:xenon difluoride|XeF&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Linear-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:octahedral molecular geometry|octahedral]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:sulfur hexafluoride|SF&lt;sub&gt;6&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX6E0-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square pyramidal molecular geometry|square pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90° (84.8°), 180° &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bromine pentafluoride|BrF&lt;sub&gt;5&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square planar molecular geometry|square planar]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:xenon tetrafluoride|XeF&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-planar-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal bipyramidal molecular geometry|pentagonal bipyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 72°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:iodine heptafluoride|IF&lt;sub&gt;7&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-bipyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal pyramidal molecular geometry|pentagonal pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;72°, 90°, 144°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;XeOF&lt;sub&gt;5&lt;/sub&gt;&lt;sup&gt;−&lt;/sup&gt;&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal planar molecular geometry|planar pentagonal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;72°, 144°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Tetramethylammonium pentafluoroxenate|XeF&lt;sub&gt;5&lt;/sub&gt;&lt;sup&gt;−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-planar-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;8&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;8&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square antiprismatic molecular geometry|square antiprismatic]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt; &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Nitrosonium octafluoroxenate(VI)|XeF&lt;sub&gt;8&lt;/sub&gt;&lt;sup&gt;2−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-antiprismatic-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;9&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;9&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:tricapped trigonal prismatic molecular geometry|tricapped trigonal prismatic]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt; &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Potassium_nonahydridorhenate|ReH&lt;sub&gt;9&lt;/sub&gt;&lt;sup&gt;2−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX9E0-3D-balls.png|50px]]&lt;/div&gt;
|}
&lt;br /&gt;
From the Table, we see that some of the molecules shown as examples have bond angles that depart from the ideal electronic geometry.  For example, the H-N-H bond angle in ammonia is 107°, and the H-O-H angle in water is 104.5°.  We can rationalize this in terms of the last rule above.  The lone pair in ammonia repels the electrons in the N-H bonds more than the bonds repel each other.  This lone pair repulsion exerts even more steric influence in the case of water, where there are two lone pairs.  Similarly, the axial F-S-F angle in the &quot;seesaw&quot; molecule SF&lt;sub&gt;4&lt;/sub&gt; is a few degrees less than 180° because of repulsion by the lone pair in the molecule.

'''Geometrical isomers'''&lt;br /&gt;

For some molecules in the Table, we note that there is more than one possible shape that would satisfy the VSEPR rules.  For example, the XeF&lt;sub&gt;2&lt;/sub&gt; molecule has a steric number of five and a trigonal bipyramidal geometry.  There are three possible stereoisomers:  one in which the F atoms occupy axial sites, resulting in linear molecule, one in which the F atoms occupy one equatorial and one axial site (resulting in a 90° bond angle), and one in which the F atoms are both on equatorial sites, with a F-Xe-F bond angle of 120°.

[[File:XeF2 geometry.jpg|130px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

The observed geometry of XeF&lt;sub&gt;2&lt;/sub&gt; is linear, which can be rationalized by considering the orbitals that are used to make bonds (or lone pairs) in the axial and equatorial positions.  There are four available orbitals, s, p&lt;sub&gt;x&lt;/sub&gt;, p&lt;sub&gt;y&lt;/sub&gt;, and p&lt;sub&gt;z&lt;/sub&gt;.  If we choose the z-axis as the axial direction, we can see that the p&lt;sub&gt;x&lt;/sub&gt; and p&lt;sub&gt;y&lt;/sub&gt; orbitals lie in the equatorial plane.  We assume that the spherical s orbital is shared equally by the five electron domains in the molecule, the two axial bonds share the p&lt;sub&gt;z&lt;/sub&gt; orbital, and the three equatorial bonds share the p&lt;sub&gt;x&lt;/sub&gt; and p&lt;sub&gt;y&lt;/sub&gt; orbitals.  We can then calculate the bond orders to axial and equatorial F atoms as follows:
&lt;br /&gt;

axial:  1/5 s + 1/2 p&lt;sub&gt;z&lt;/sub&gt; = 0.7 bond (formal charge = -0.3)&lt;br /&gt;
equatorial: 1/5 s + 1/3 p&lt;sub&gt;x&lt;/sub&gt; + 1/3 p&lt;sub&gt;y&lt;/sub&gt; = 0.867 bond (formal charge = -0.133)
&lt;br /&gt;

Because fluorine is more electronegative than a lone pair, it prefers the axial site where it will have more negative formal charge.  In general, by this reasoning, lone pairs and electropositive ligands such as CH&lt;sub&gt;3&lt;/sub&gt; will always prefer the equatorial sites in the trigonal bipyramidal geometry.  Electronegative ligands such as F will always go to the axial sites.

In the case of the BrF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; anion, which is isoelectronic with XeF&lt;sub&gt;4&lt;/sub&gt; in the Table, the electronic geometry is octahedral and there are two possible isomers in which the two lone pairs are ''cis'' or ''trans'' to each other.  In this case, lone pair - lone pair repulsion dominates and we obtain the ''trans'' arrangement of lone pairs, giving a square planar molecular geometry.
&lt;br /&gt;
[[File:BrF4-VSEPR.jpg|350px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

'''Orbital hybridization'''
&lt;br /&gt;
The observation of molecules in the various electronic shapes shown above is, at first blush, in conflict with our picture of [[w:Atomic_orbitals|atomic orbitals]].  For an atom such as oxygen, we know that the 2s orbital is spherical, and that the 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals are dumbell-shaped and point along the Cartesian axes.  The water molecule contains two hydrogen atoms bound to oxygen not at a 90° angle, but at an angle of 104.5°.  Given the relative orientations of the atomic orbitals, how do we arrive at angles between electron domains of 104.5°, 120°, and so on? To understand this we will need to learn a little bit about the quantum mechanics of electrons in atoms and molecules.&lt;br&gt;
&lt;br&gt;

The atomic orbitals ψ represent solutions to the [[w:Schrödinger equation|'''Schrödinger wave equation''']], 


:&lt;math&gt; E \psi = \hat{H}\psi&lt;/math&gt;


Here E is the energy of an electron in the orbital, and &lt;math&gt; \hat{H}&lt;/math&gt; is the Hamiltonian operator.

By analogy with classical mechanics, the Hamiltonian is commonly expressed as the sum of [[w:Hermitian operators|operators]] corresponding to the [[w:kinetic energy|kinetic]] and [[w:potential energy|potential]] energies of a system in the form


:&lt;math&gt; \hat{H} = \hat{T} + \hat{V}, &lt;/math&gt;


where  &lt;math&gt; \hat{V} = V(\mathbf{r},t) &lt;/math&gt; is the potential energy, and 


:&lt;math&gt;\hat{T} = \frac{\mathbf{\hat{p}}\cdot\mathbf{\hat{p}}}{2m} = \frac{\hat{p}^2}{2m} = -\frac{\hbar^2}{2m}\nabla^2,&lt;/math&gt;


is the kinetic energy operator in which ''m'' is the mass of the particle and the momentum operator is:


:&lt;math&gt; \hat{p} = -i\hbar\nabla ,&lt;/math&gt; where &lt;math&gt;\nabla = {\partial \over \partial x} +  {\partial \over \partial y} +  {\partial \over \partial z}&lt;/math&gt;


Here &lt;math&gt;\hbar&lt;/math&gt; is h/2π, where h is Planck's constant, and the Laplacian operator ∇&lt;sup&gt;2&lt;/sup&gt; is:


:&lt;math&gt;\nabla^2 = \frac{\partial^2}{{\partial x}^2} + \frac{\partial^2}{{\partial y}^2} + \frac{\partial^2}{{\partial z}^2}&lt;/math&gt;


Although this is not the technical definition of the [[w:Hamiltonian mechanics|Hamiltonian in classical mechanics]], it is the form it most commonly takes in quantum mechanics. Combining these together yields the familiar form used in the Schrödinger equation:


:&lt;math&gt;\begin{align}\hat{H} &amp; = \hat{T} + \hat{V} \ = \frac{\mathbf{\hat{p}}\cdot\mathbf{\hat{p}}}{2m}+ V(\mathbf{r},t) \ = -\frac{\hbar^2}{2m}\nabla^2+ V(\mathbf{r},t)\end{align}&lt;/math&gt;


For hydrogen-like (one-electron) atoms, the Schrödinger equation can be written as:&lt;br /&gt;


:&lt;math&gt; E \psi = -\frac{\hbar^2}{2\mu}\nabla^2\psi - \frac{Ze^2}{4\pi\epsilon_0 r}\psi &lt;/math&gt;


where '''Z''' is the nuclear charge, ''e'' is the electron charge, and '''r''' is the position of the electron. The radial potential term on the right side of the equation is due to the [[w:Coulomb's law|Coulomb interaction]], i.e., the electrostatic attraction between the nucleus and the electron, in which ''ε''&lt;sub&gt;0&lt;/sub&gt; is the [[w:electric constant|dielectric constant]] (permittivity of free space) and


:&lt;math&gt; \mu = \frac{m_em_n}{m_e+m_n} &lt;/math&gt;


is the 2-body [[w:reduced mass|reduced mass]] of the [[w:Nucleus (atomic structure)|nucleus]] of mass ''m''&lt;sub&gt;n&lt;/sub&gt; and the electron of mass ''m''&lt;sub&gt;e&lt;/sub&gt;.  To a good approximation, µ ≈ ''m''&lt;sub&gt;e&lt;/sub&gt;.
[[File:Erwin_Schrodinger2.jpg|right|thumb|150px|Erwin Schrödinger as a young scientist]]


This is the equation that [[w:Erwin_Schrödinger|Erwin Schrödinger]] famously derived in 1926 to solve for the energies and shapes of the s, p, d, and f [[w:Atomic_orbital|atomic orbitals]] in hydrogen-like atoms.  It was a huge conceptual leap for both physics and chemistry because it not only explained the quantized energy levels of the hydrogen atom, but also provided the theoretical basis for the octet rule and the arrangement of elements in the periodic table.


The Schrödinger equation can be used to describe chemical systems that are more complicated than the hydrogen atom (e.g., multi-electron atoms, molecules, infinite crystals, and the dynamics of those systems) if we substitute the appropriate potential energy function V(r,t) into the Hamiltonian.  The math becomes more complicated and the equation must be solved numerically in those cases, so for our purposes we will stick with the simplest case of time-invariant, one-electron, hydrogen-like atoms.
&lt;br&gt;&lt;br&gt;
[[File:Neon orbitals rotated.png|right|thumb|170px|The shapes of the first five [[w:Atomic_orbitals|atomic orbitals]]: 1s, 2s, 2p&lt;sub&gt;''x''&lt;/sub&gt;, 2p&lt;sub&gt;''y''&lt;/sub&gt;, and 2p&lt;sub&gt;''z''&lt;/sub&gt;. The colors denote the sign of the wave function.]]
Without going into too much detail about the Schrödinger equation, we can point out some of its most important properties:&lt;br&gt;
:&lt;math&gt; E \psi = -\frac{\hbar^2}{2\mu}\nabla^2\psi - \frac{Ze^2}{4\pi\epsilon_0 r}\psi &lt;/math&gt;
*The equation derives from the fact that the total energy (E) is the sum of the kinetic energy (KE) and the potential energy (PE).  These three quantities are represented mathematically as [[w:Operator_(physics)|'''operators''']] in the equation.
*On the left side of the equation, the total energy operator (E) is a scalar that is multiplied by the [[w:Wave_function|wavefunction]] ψ. ψ is a function of the spatial coordinates (x,y,z) and is related to the probability that the electron is at that point in space.
*The first term on the right side of the equation represents the kinetic energy (KE).  The kinetic energy operator is proportional to ∇&lt;sup&gt;2&lt;/sup&gt; (the [[w:Laplacian|Laplacian operator]]) which takes the second derivative (with respect to three spatial coordinates) of ψ.  Thus, the Schrödinger equation is a '''differential equation'''.
*The second term on the right side of the equation represents the Coulomb potential (PE), i.e. the attractive energy between the positively charged nucleus and the negatively charged electron.
*The solutions to the Schrödinger equation are a set of '''energies''' E (which are scalar quantities) and [[w:Wave_function|'''wavefunctions''']] (a.k.a. '''[[w:Atomic_orbitals|atomic orbitals]]''') ψ, which are functions of the spatial coordinates.  You will sometimes see the energies referred to as [[w:Eigenvalue|''eigenvalues'']] and the orbitals as [[w:eigenfunction|''eigenfunctions'']], because mathematically the Schrödinger equation is an eigenfunction-eigenvalue equation.  Although ψ is a function of the coordinates, E is not.  So an electron in a 2p&lt;sub&gt;z&lt;/sub&gt; orbital has the same total energy E (= PE + KE) no matter where it is in space. 
*These E values and their associated [[w:Wave_function|wavefunctions]] ψ are catalogued according to their '''[[w:Quantum_number|quantum numbers]]''' ''n,'' ''l,'' and ''m&lt;sub&gt;l&lt;/sub&gt;.''  That is, there are many solutions to the differential equation, and each solution (ψ(xyz) and E) has a unique set of quantum numbers.  Some sets of orbitals are '''degenerate''', meaning that they have the same energy (e.g., 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt;).
*The solutions ψ(xyz) to the Schrödinger equation (e.g., the 1s, 2s, 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals) represent '''probability amplitudes''' for finding the electron at a particular point (x,y,z) in space.  A probability amplitude can have either '''+ or - sign'''.  We typically represent the different signs by shading or by + and - signs on the two lobes of a 2p orbital.  
*The square of the probability amplitude, ψ&lt;sup&gt;2&lt;/sup&gt;, is always a positive number and represents the '''probability''' of finding the electron at a point x,y,z in space.  Because the total probability of finding the electron somewhere is 1, the wavefunction must be '''normalized''' so that the integral of ψ&lt;sup&gt;2&lt;/sup&gt; over the spatial coordinates (from -∞ to +∞) is 1.
*The solutions to the Schrödinger equation are '''orthogonal''', meaning that the product of any two (integrated over all space) is zero.  For example the product of the 2s and 2p&lt;sub&gt;x&lt;/sub&gt; orbitals, integrated over the spatial coordinates from -∞ to +∞, is zero.
&lt;br&gt;
Orbital hybridization involves making ''linear combinations'' of the [[w:Atomic_orbitals|atomic orbitals]] that are solutions to the Schrödinger equation.  Mathematically, this is justified by recognizing that the Schrödinger equation is a ''linear'' differential equation.  As such, any sum of solutions to the Schrödinger equation is also a valid solution.  However, we still impose the constraint that our hybrid orbitals must be '''orthogonal''' and '''normalized'''.
&lt;br /&gt;

'''Rules for orbital hybridization:'''

* Add and subtract [[w:Atomic_orbitals|atomic orbitals]] to get hybrid orbitals.
* We get the same number of orbitals out as we put in.
* The energy of a hybrid orbital is the weighted average of the [[w:Atomic_orbitals|atomic orbitals]] that make it up.
* The coefficients are determined by the constraints that the hybrid orbitals must be orthogonal and normalized.


For '''sp hybridization''', as in the BeF&lt;sub&gt;2&lt;/sub&gt; or CO&lt;sub&gt;2&lt;/sub&gt; molecule, we make two linear combinations of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals (assigning z as the axis of the Be-F bond):

:&lt;math&gt;\psi_1 = \frac{1}{\sqrt 2}(2s) + \frac{1}{\sqrt 2}(2p_z)&lt;/math&gt;&lt;br&gt;
:&lt;math&gt;\psi_2 = \frac{1}{\sqrt 2}(2s) - \frac{1}{\sqrt 2}(2p_z)&lt;/math&gt;&lt;br&gt;

Here we have simply added and subtracted the 2s and 2pz orbitals; we leave it as an exercise for the interested student to show that both orbitals are normalized (i.e., {{Unicode|∫}}ψ&lt;sub&gt;1&lt;/sub&gt;&lt;sup&gt;2&lt;/sup&gt;dτ = {{Unicode|∫}}ψ&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;2&lt;/sup&gt;dτ = 1) and orthogonal (i.e., {{Unicode|∫}}ψ&lt;sub&gt;1&lt;/sub&gt;ψ&lt;sub&gt;2&lt;/sub&gt;dτ = 0).

What this means physically is explained in the figure below.  By combining the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals we have created two new orbitals with large lobes (high electron probability) pointing along the z-axis.  These two orbitals are degenerate and have an energy that is halfway between the energy of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals.
[[File:sp hybridization.jpg|thumb|500px|center|Linear combinations of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; [[w:Atomic_orbitals|atomic orbitals]] make two 2sp&lt;sub&gt;z&lt;/sub&gt; hybrids.  The 2p&lt;sub&gt;x&lt;/sub&gt; and 2p&lt;sub&gt;y&lt;/sub&gt; orbitals are unchanged.]]
For an isolated Be atom, which has two valence electrons, the lowest energy state would have two electrons spin-paired in the 2s orbital.  However, these electrons would not be available for bonding.  By '''promoting''' these electrons to the degenerate 2sp&lt;sub&gt;z&lt;/sub&gt; hybrid orbitals, they become unpaired and are prepared for bonding to the F atoms in BeF&lt;sub&gt;2&lt;/sub&gt;.  This will occur if the '''bonding energy''' (in the promoted state) exceeds the promotion energy.  The '''overall bonding energy''', i.e., the energy released by combining a Be atom in its ground state with two F atoms, is the difference between the bonding and promotion energies.

We can similarly construct '''sp&lt;sup&gt;2&lt;/sup&gt; hybrids''' (e.g., for the BF&lt;sub&gt;3&lt;/sub&gt; molecule or the NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; anion) from one 2s and two 2p [[w:Atomic_orbitals|atomic orbitals]].  Taking the plane of the molecule as the xy plane, we obtain three hybrid orbitals at 120° to each other.  The three hybrids are:
[[File:sp2hybrids.jpg|200px|right]]&lt;br /&gt;

:&lt;math&gt;\psi_1 = \frac{1}{\sqrt 3}(2s) + \frac{\sqrt 2}{\sqrt 3}(2p_x)&lt;/math&gt;
:&lt;math&gt;\psi_2 = \frac{1}{\sqrt 3}(2s) - \frac{1}{\sqrt 6}(2p_x) + \frac{1}{\sqrt 2}(2p_y)&lt;/math&gt;
:&lt;math&gt;\psi_3 = \frac{1}{\sqrt 3}(2s) - \frac{1}{\sqrt 6}(2p_x) - \frac{1}{\sqrt 2}(2p_y)&lt;/math&gt;
&lt;br /&gt;

These orbitals are again degenerate and their energy is the weighted average of the energies of the 2s, 2p&lt;sub&gt;x&lt;/sub&gt;, and 2p&lt;sub&gt;y&lt;/sub&gt; [[w:Atomic_orbitals|atomic orbitals]].

Finally, to make a sp&lt;sup&gt;3&lt;/sup&gt; hybrid, as in CH&lt;sub&gt;4&lt;/sub&gt;, H&lt;sub&gt;2&lt;/sub&gt;O, etc., we combine all four [[w:Atomic_orbitals|atomic orbitals]] to make four degenerate hybrids:
[[File:Ch4 hybridization.svg|130px|right]]&lt;br /&gt;
 [[File:CH4-structure.svg|130px|right]]&lt;br /&gt;

:&lt;math&gt;\psi_1 = \frac{1}{2}(2s + 2p_x + 2p_y + 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_2 = \frac{1}{2}(2s - 2p_x - 2p_y + 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_3 = \frac{1}{2}(2s + 2p_x - 2p_y - 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_4 = \frac{1}{2}(2s - 2p_x + 2p_y - 2p_z)&lt;/math&gt;&lt;br&gt;


The lobes of the '''sp&lt;sup&gt;3&lt;/sup&gt; hybrid''' orbitals point towards the vertices of a tetrahedron (or alternate corners of a cube), consistent with the tetrahedral bond angle in CH&lt;sub&gt;4&lt;/sub&gt; and the nearly tetrahedral angles in NH&lt;sub&gt;3&lt;/sub&gt; and H&lt;sub&gt;2&lt;/sub&gt;O. Similarly, we can show that we can construct the trigonal bipyramidal electronic shape by making sp and sp&lt;sup&gt;2&lt;/sup&gt; hybrids, and the octahedral geometry from three sets of sp hybrids. The picture that emerges from this is that the [[w:Atomic_orbitals|atomic orbitals]] can hybridize as required by the shape that best minimizes electron pair repulsions.
[[File:Hydrogen-sulfide-2D-dimensions.svg|130px|right]]
Interestingly however, the bond angles in PH&lt;sub&gt;3&lt;/sub&gt;, H&lt;sub&gt;2&lt;/sub&gt;S and H&lt;sub&gt;2&lt;/sub&gt;Se are close to 90°, suggesting that P, S, and Se primarily use their p-orbitals in bonding to H in these molecules.  This is consistent with the fact that the energy difference between s and p orbitals stays roughly constant going down the periodic table, but the bond energy ''decreases'' as the valence electrons get farther away from the nucleus.  In compounds of elements in the 3rd, 4th, and 5th rows of the periodic table, there thus is a ''decreasing tendency to use s-p orbital hybrids in bonding''.  For these heavier elements, the bonding energy is not enough to offset the energy needed to promote the s electrons to s-p hybrid orbitals.

==1.3 Bond polarity and bond strength==
[[Image:Water-elpot-transparent-3D-balls.png|thumb|right|250px|Fig. 1.3.1. A [[w:water molecule|water molecule]], a commonly used example of polarity. The two charges are present with a negative charge in the middle (red), and a positive charge at the ends (blue).]]
[[w:Linus Pauling|Linus Pauling]] introduced the concept of [[w:electronegativity|electronegativity]] 1932 in order to explain the extra stability of molecules with polar bonds. &lt;ref name=&quot;paulingJACS&quot;&gt;{{cite journal |author= Pauling, L.
 |authorlink=Linus Pauling
 |year= 1932
 |journal= [[w:Journal of the American Chemical Society|J. Am. Chem. Soc.]]
 |volume= 54
 |issue= 9
 |pages= 3570–3582
 |title= The Nature of the Chemical Bond. IV. The Energy of Single Bonds and the Relative Electronegativity of Atoms
 |doi= 10.1021/ja01348a011}}&lt;/ref&gt;  The electronegativity of an atom, represented by the Greek letter ''χ'', can be defined as the tendency of an atom to draw electrons to itself in a chemical bond.  On the Pauling scale, the electronegativity difference between two atoms A and B was defined in terms of the [[w:Bond dissociation energy|dissociation energies]] ''E''&lt;sub&gt;d&lt;/sub&gt; of the  A-A, B-B, and A-B bonds:&lt;br&gt;&lt;br&gt;

::&lt;small&gt;&lt;math&gt;\chi_{\rm A} - \chi_{\rm B} = \sqrt{E_{\rm d}({\rm AB}) - [E_{\rm d}({\rm AA}) + E_{\rm d}({\rm BB})]/2}&lt;/math&gt;&lt;/small&gt;&lt;br&gt;&lt;br&gt;
where the energies are expressed in electron volts.

This definition, while directly relevant to the strength of chemical bonds, requires thermochemical input data from many compounds, some of which were not available at the time.  Mulliken&lt;ref&gt;{{cite journal
|author = Mulliken, R. S.
|year =1934
|journal = [[w:Journal of Chemical Physics|J. Chem. Phys.]]
|volume = 2
|title = A New Electroaffinity Scale; Together with Data on Valence States and on Valence Ionization Potentials and Electron Affinities
|doi = 10.1063/1.1749394
|pages = 782–793
|issue = 11|bibcode = 1934JChPh...2..782M }}&lt;/ref&gt;&lt;ref&gt;{{cite journal
|author = Mulliken, R. S.
|year =1935
|title = Electronic Structures of Molecules XI. Electroaffinity, Molecular Orbitals and Dipole Moments
|journal = [[w:Journal of Chemical Physics|J. Chem. Phys.]]
|volume = 3
|doi = 10.1063/1.1749731
|pages = 573–585
|issue = 9|bibcode = 1935JChPh...3..573M }}&lt;/ref&gt; and later Pearson&lt;ref&gt;{{cite journal|author = Pearson, R. G.
|title = Absolute electronegativity and absolute hardness of Lewis acids and bases
|year = 1985
|journal = [[w:Journal of the American Chemical Society|J. Am. Chem. Soc.]]
|volume = 107
|pages = 6801
|doi = 10.1021/ja00310a009|issue = 24}}&lt;/ref&gt; developed a scale of electronegativities based on the average of the electron affinity and ionization energy of the free A and B atoms, which they correlated with thermochemical data and the Pauling scale.  

On the Pauling scale, the least electronegative elements are the alkali metals (χ = 0.7-1.0) and the most electronegative are oxygen (3.5) and fluorine (4.0) at the upper right of the periodic table.  Carbon and hydrogen have intermediate electronegativities (2.6 and 2.2 on the Pauling scale, respectively).  The general trend (see table below) is that electronegativities increase going up and to the right in the periodic table.  There are some interesting exceptions to this behavior, most notably two islands of high electronegativity at the bottom of the transition series, peaking at tungsten (χ = 2.4) and gold (χ = 2.5).  The first of these can be explained by the very high metal-metal bond energy of elements such as Mo and W, which can use all six of their valence electrons in bonding, as we will discuss in Chapter 6.  The second however occurs with more weakly bonded noble metals such as Pt and Au, and is responsible for  their low position in the [[w:Reactivity_series|activity series]],&lt;ref&gt;B. Hammer and J. K. Norskov, &quot;Why gold is the noblest of all the metals,&quot; ''Nature'' '''376,''' 238 - 240 (2002. doi:10.1038/376238a0&lt;/ref&gt; as well as their extraordinary properties as catalysts.&lt;br&gt;&lt;br&gt;
[[image:periodic table Pauling electronegatvity.jpg|500px|left]]

[[w:Electronegativities_of_the_elements_(data_page)#Electronegativity_.28Pauling_scale.29|Table of Pauling electronegativities]]

The polarity of bonds is determined by electronegativity differences.  As a guideline we define bonds as:

* '''ionic''' if Δχ &gt; 2.0
* '''polar''' if 2.0 &gt; Δχ &gt; 0.5
* '''nonpolar''' if 0.5 &gt; Δχ

The polarity of bonds helps us understand [[w:Intermolecular_force|non-covalent forces]] between molecules, such as [[w:Hydrogen_bonding|hydrogen bonding]] and dipole-dipole interactions. It also helps us interpret the reactivity of molecules.  For example, the Si-H bond (χ&lt;sub&gt;Si&lt;/sub&gt; = 1.8, χ&lt;sub&gt;H&lt;/sub&gt; = 2.1) is more hydride-like than the C-H bond (χ&lt;sub&gt;C&lt;/sub&gt; = 2.5, χ&lt;sub&gt;H&lt;/sub&gt; = 2.1).  Therefore silanes react with acids to make H&lt;sub&gt;2&lt;/sub&gt;, whereas phosphines (χ&lt;sub&gt;P&lt;/sub&gt; = 2.1) and hydrocarbons do not.  Similarly, electrophilic substitution reactions occur more readily on Si-H and P-H compounds than they do on C-H compounds.

There is also a correlation between the strength of a chemical bond and the bond length, longer bonds being weaker because of weaker orbital overlap.  Pauling introduced an empirical formula relating bond length to bond strength.  For a given pair of atoms (for example, two carbon atoms):&lt;br&gt;&lt;br&gt;

:&lt;big&gt;'''D(n) = D(1) - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(n)'''&lt;/big&gt;&lt;br&gt;&lt;br&gt;

where D(n) represents the bond length in Å and n is the bond order. D(1) in this case would be the length of a C-C single bond, which we can obtain from the average bond length in alkanes (1.54 Å).  Using this formula we can predict that the bond lengths in ethylene (C=C double bond) and acetylene (C≡C triple bond) should be 1.36 and 1.25 Å, respectively, which are close to the experimental values of 1.33 and 1.20 Å.  In a related form the Pauling formula can be used to calculate bond lengths when the single bond length D(1) is not available:&lt;br&gt;&lt;br&gt;

:&lt;big&gt;'''D(n) = D(m) - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(n/m)'''&lt;/big&gt;&lt;br&gt;


Here n and m represent two different bond orders between the same kinds of atoms.  This tells, for example, that the difference in length between a triple and double bond, D(2)-D(3), should be - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(2/3) = 0.11 Å.
&lt;br /&gt;
&lt;br /&gt;

[[File:Bond length of fluorine graph.JPG|right|350px|thumb|Trends in covalent radii for p-block elements. The [[w:Covalent_radius_of_fluorine|covalent radius of F]] has been difficult to determine because of electron pair repulsion effects. Early reports (Shomaker and Stevenson, Pauling) overestimated the size of the F atom.&lt;ref&gt;{{cite journal|last1=Schomaker|first1=Verner|last2=Stevenson|first2=D. P.|journal=Journal of the American Chemical Society|volume=63|pages=37–40|year=1941|doi=10.1021/ja01846a007|title=Some Revisions of the Covalent Radii and the Additivity Rule for the Lengths of Partially Ionic Single Covalent Bonds *}}&lt;/ref&gt;&lt;ref&gt;Pauling, L. The Nature of the Chemical Bond, 3rd ed.; Cornell University Press: Ithaca, NY, 1960; p. 224.&lt;/ref&gt;&lt;ref&gt;{{cite journal|last1=Robinson|first1=Edward A.|last2=Johnson|first2=Samuel A.|last3=Tang|first3=Ting-Hua|last4=Gillespie|first4=Ronald J.|title=Reinterpretation of the Lengths of Bonds to Fluorine in Terms of an Almost Ionic Model|journal=Inorganic Chemistry|volume=36|issue=14|pages=3022–3030|year=1997|pmid=11669953|doi=10.1021/ic961315b}}&lt;/ref&gt;  Accurate quantum chemical calculations place the F single-bond covalent radius at about 0.64 Å.&lt;ref&gt;{{cite journal|doi=10.1002/chem.200901472|title=Molecular Double-Bond Covalent Radii for Elements Li–E112|year=2009|last1=Pyykkö|first1=Pekka|last2=Atsumi|first2=Michiko|journal=Chemistry: A European Journal|volume=15|issue=46|pages=12770–12779}}&lt;/ref&gt;]]Some bond lengths and bond energies are anomalous. For example, the F-F bond length in F&lt;sub&gt;2&lt;/sub&gt; is 1.43 Å, which is 0.15 Å ''longer'' than twice the covalent radius of the F atom (0.64 Å).  The F-F bond is also quite weak (bond dissociation energy = 155 kJ/mol) relative to the Cl-Cl bond (242 kJ/mol).  By putting the extra bond length into the Pauling formula, we calculate that the bond order in the F&lt;sub&gt;2&lt;/sub&gt; molecule is only 0.6, i.e., substantially weaker than a F-F single bond.  The physical reason for this is that the F-F bond is &quot;stretched&quot; by repulsion of the lone pairs on the F atoms.  This crowding is caused by the fact that the [He] 1s&lt;sup&gt;2&lt;/sup&gt; core orbital, as well as the valence orbitals of the fluorine atoms, are contracted by the high nuclear charge.  The Cl atom in Cl&lt;sub&gt;2&lt;/sub&gt; has a larger [Ne] (1s&lt;sup&gt;2&lt;/sup&gt;2s&lt;sup&gt;2&lt;/sup&gt;2p&lt;sup&gt;6&lt;/sup&gt;) core, in contrast, so Cl-Cl has a &quot;normal&quot; single bond length (1.98 Å) that is twice the covalent radius of the Cl atom (0.99 Å).  A similar lone pair repulsion effect explains the anomalously long and weak N-N and O-O single bonds in hydrazine (H&lt;sub&gt;2&lt;/sub&gt;N-NH&lt;sub&gt;2&lt;/sub&gt;) and hydrogen peroxide (HO-OH), which are both highly reactive molecules.  
&lt;br /&gt;

The important roles of electronegativity differences and lone pair repulsion are evident when comparing trends in bond strengths.  The table below shows the average single-bond enthalpies of p-block elements with H and F.  H makes stronger bonds with 2nd row elements (C, N, O, F) than with third row elements (Si, P, S, Cl) because the 2p valence electrons are closer to the nucleus and thus make stronger bonds than electrons in 3p orbitals.  The bonds to H also follow the expected trend of increasing bond strength with increasing electronegativity difference.  Bonds between second row elements (C, N, O, F) and F are however anomalously weak because of lone pair repulsion.  For this reason, the Si-F bond is substantially stronger than the C-F bond, whereas the C-H bond is much stronger than the Si-H bond.  The strong Si-F bond is the reason that HF etches glass (to produce the SiF&lt;sub&gt;6&lt;/sub&gt;&lt;sup&gt;2-&lt;/sup&gt; anion), and the strong C-H bond is an important factor in the stability of hydrocarbons and other organic molecules.


'''Average E-H and E-F bond enthalpies (kJ/mol)'''
{| class=&quot;wikitable&quot;
|C-H&amp;nbsp;&amp;nbsp;&amp;nbsp;413&amp;nbsp;&amp;nbsp;&amp;nbsp;||N-H&amp;nbsp;&amp;nbsp;&amp;nbsp;391&amp;nbsp;&amp;nbsp;&amp;nbsp;||O-H&amp;nbsp;&amp;nbsp;&amp;nbsp;483&amp;nbsp;&amp;nbsp;&amp;nbsp;||H-F&amp;nbsp;&amp;nbsp;&amp;nbsp;567&amp;nbsp;&amp;nbsp;&amp;nbsp;
|-
|Si-H&amp;nbsp;&amp;nbsp;&amp;nbsp;323||P-H&amp;nbsp;&amp;nbsp;&amp;nbsp;322||S-H&amp;nbsp;&amp;nbsp;&amp;nbsp;339||H-Cl&amp;nbsp;&amp;nbsp;&amp;nbsp;431
|-
|


|
|
|
|-
|C-F&amp;nbsp;&amp;nbsp;&amp;nbsp;485||N-F&amp;nbsp;&amp;nbsp;&amp;nbsp;272||O-F&amp;nbsp;&amp;nbsp;&amp;nbsp;190||F-F &amp;nbsp;&amp;nbsp;&amp;nbsp;155
|-
|Si-F&amp;nbsp;&amp;nbsp;&amp;nbsp;565||P-F &amp;nbsp;&amp;nbsp;&amp;nbsp;490  ||S-F&amp;nbsp;&amp;nbsp;&amp;nbsp;327||Cl-F&amp;nbsp;&amp;nbsp;&amp;nbsp;253
|}


[[File:A water droplet DWR-coated surface2 edit1.jpg|thumb|150px|right|alt=A shiny spherical drop of water on blue cloth|Fabric treated with fluorosurfactant]]The anomalously weak bond in F&lt;sub&gt;2&lt;/sub&gt; is responsible for the high electronegativity of fluorine, as well as the legendary reactivity of elemental fluorine gas, which reacts explosively with hydrogen and powdered metals.  Because of the instability of elemental fluorine and the polar nature of its bonds with more electropositive elements, fluorine compounds tend to be very stable.  For example, the noble gases Xe and Kr react with fluorine to make covalent compounds, whereas other halogens do not react.  Fluorocarbon compounds contain strong C-F bonds and have high thermal and chemical stability.  Perfluorocarbons such as [[w:Teflon|Teflon]] (poly(tetrafluoroethylene), -(CF&lt;sub&gt;2&lt;/sub&gt;CF&lt;sub&gt;2&lt;/sub&gt;)n-, PTFE) are also highly hydrophobic.  The extraordinary hydrophobicity of perfluorocarbons arises from the fact that -CF&lt;sub&gt;2&lt;/sub&gt;- and -CF&lt;sub&gt;3&lt;/sub&gt; groups are &quot;fatter&quot; than -CH&lt;sub&gt;2&lt;/sub&gt;- and -CH&lt;sub&gt;3&lt;/sub&gt; groups; dissolving them in water is therefore more disruptive to the hydrogen bonding network than is dissolving a hydrocarbon. &lt;ref&gt;V. H. Dalvi and P. J. Rossky, Molecular origins of fluorocarbon hydrophobicity, Proc. Natl. Acad. Sci. USA 107,13603–13607 (2010). DOI: 10.1073/pnas.0915169107.&lt;/ref&gt;

==1.4 Discussion questions==
'''Group essay project:'''&lt;br&gt;
Join a group of classmates from your inorganic chemistry course.  Each group should have 3 or 4 students.  Arrange a time to meet for an hour or so.  Prior to the meeting, read part I (pp. 1367-1391) as well as the summary at the end of Linus Pauling's [http://courses.chem.psu.edu/chem310/ja01355a027.pdf article] (J. Am. Chem. Soc. 1931, 53, 1367-1400) on the nature of the chemical bond.  

This paper was published only a few years after Schrödinger developed the quantum mechanical theory of atomic orbitals and is considered one of the most important papers in the history of modern chemistry.  At the meeting, discuss the following questions:  (1) What was understood about chemical bonding in molecules before Pauling published this work? (2) What new concepts did the paper introduce that we still use today? (3) Why were these ideas important? and (4) What, if anything, did Pauling get wrong, and why?

Together with your classmates, write a 1-2 page essay addressing these questions.  Please include the names of all students in your group on the first page; all of you will receive the same grade on this assignment.  Anonymous excerpts from a few of these essays will be shared with the class.


'''In-class discussion questions from this chapter:'''
* What are inequivalent resonance structures? Illustrate with some new examples not covered above.
* Explain no-bond resonance and hypervalency, using some new examples.
* What are the limitations of valence bond theory for molecules that contain an odd number of electrons? Illustrate with one or two examples.

==1.5 Problems==
1.	Draw composite octet structures (including formal charges, bond order, and molecular shape) for the following: (a) BrO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (b) SF&lt;sub&gt;6&lt;/sub&gt;, (c) KrF&lt;sub&gt;2&lt;/sub&gt;, (d) HClO&lt;sub&gt;4&lt;/sub&gt; (= HOClO&lt;sub&gt;3&lt;/sub&gt;), (e) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, and (f) ClO&lt;sub&gt;2&lt;/sub&gt;.

2.	Draw composite octet structures (including formal charges, bond order, and molecular shape) for the following: (a) Al&lt;sub&gt;2&lt;/sub&gt;Cl&lt;sub&gt;6&lt;/sub&gt;, (b) SnCl&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (c) BrF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;,(d) HOClO, (e) SO&lt;sub&gt;3&lt;/sub&gt;, and (f) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;.

3.	Show using resonance why the CO bond distance in formamide (HCONH&lt;sub&gt;2&lt;/sub&gt;) is longer than the CO bond distance in acetone.

4.	Give the formulas for five stable molecules and/or ions that are isoelectronic with ammonia.

5.	Name three well known molecules or ions that are isoelectronic with (a) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;, (b) BF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (c) CH&lt;sub&gt;4&lt;/sub&gt;, and (d) HCN.


6.	Name three well known molecules or ions that are isoelectronic with (a) CN&lt;sup&gt;-&lt;/sup&gt;, (b) H&lt;sub&gt;2&lt;/sub&gt;O, (c) BF&lt;sub&gt;3&lt;/sub&gt;, and (d) CO&lt;sub&gt;2&lt;/sub&gt;.

7.	The C-C bond distance is 1.20 Å in acetylene.  Using  the Pauling bond length – bond strength formula, D(n) = D(m) - 0.6 log(n/m), estimate the C-C bond distance in ketene (H&lt;sub&gt;2&lt;/sub&gt;CCO).  

8.	In hydroxylamine, H&lt;sub&gt;2&lt;/sub&gt;NOH, the N-O bond distance is 1.46 Å.  Using the Pauling bond length - bond strength formula, estimate the N-O bond distances in NO&lt;sub&gt;2&lt;/sub&gt; and NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.


9.	Nitrogen can exist in the +5 oxidation state in compounds that contain ions such a NF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; and NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.  However the neutral binary compound NF&lt;sub&gt;5&lt;/sub&gt; is unknown.  Can you draw octet structures for each of these compounds?  Why would NF&lt;sub&gt;5&lt;/sub&gt; be unstable?

10.	Consider the compounds NH&lt;sub&gt;3&lt;/sub&gt; and PH&lt;sub&gt;3&lt;/sub&gt;.  The H-N-H bond angle in ammonia is 108&lt;sup&gt;o&lt;/sup&gt; (close to the tetrahedral angle, 109.5&lt;sup&gt;o&lt;/sup&gt;), but the analogous angle in PH&lt;sub&gt;3&lt;/sub&gt; is 93&lt;sup&gt;o&lt;/sup&gt;.   Why is the angle in PH&lt;sub&gt;3&lt;/sub&gt; closer to 90&lt;sup&gt;o&lt;/sup&gt; than it is to the tetrahedral angle?

11.	Two hypothetical structures for the N&lt;sub&gt;2&lt;/sub&gt;F&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; ion are [N-NF&lt;sub&gt;3&lt;/sub&gt;]&lt;sup&gt;+&lt;/sup&gt; and [F-N-NF&lt;sub&gt;2&lt;/sub&gt;]&lt;sup&gt;+&lt;/sup&gt;.  Which one is more stable? Explain.  (Note:  lines in the formulas can represent either single or multiple bonds)

12.	Krypton difluoride, KrF&lt;sub&gt;2&lt;/sub&gt;, decomposes at dry ice temperature to Kr and F&lt;sub&gt;2&lt;/sub&gt;.  However, several salts of the [KrF]&lt;sup&gt;+&lt;/sup&gt; ion are relatively stable.  Draw valence bond pictures for KrF&lt;sub&gt;2&lt;/sub&gt; and [KrF]&lt;sup&gt;+&lt;/sup&gt;, showing lone pairs, possible resonance structures, formal charges, bond orders, and bond angles.  Why is [KrF]&lt;sup&gt;+&lt;/sup&gt; more stable than KrF&lt;sub&gt;2&lt;/sub&gt;?


13.	Consider the anion SF&lt;sub&gt;3&lt;/sub&gt;O&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; (with S the central atom).  How many isomers are possible? Which is the most stable?

14. 	The Br-F bond distance in the interhalogen compound BrF is 1.76 Å.  Use this information to estimate the average bond lengths in BrF&lt;sub&gt;3&lt;/sub&gt; and BrF&lt;sub&gt;5&lt;/sub&gt;.


15. 	The B-H bond distances are about the same in BH&lt;sub&gt;3&lt;/sub&gt; and BH&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;. however, the B-F bond distance in BF&lt;sub&gt;3&lt;/sub&gt; is shorter than that in the BF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; ion.  Explain.


16.	The N-N bond dissociation energy in hydrazine (H&lt;sub&gt;2&lt;/sub&gt;N-NH&lt;sub&gt;2&lt;/sub&gt;) is 159 kJ/mol.  The dissociation energy of the N-N triple bond in N&lt;sub&gt;2&lt;/sub&gt; is 941 kJ/mol, i.e., much greater than three times the N-N single bond dissociation energy in hydrazine.  Explain why the N-N bond in hydrazine is so weak, and why this effect is not seen in N&lt;sub&gt;2&lt;/sub&gt;.


17.	Show that a set of four sp&lt;sup&gt;3&lt;/sup&gt; hybrid orbitals satisfies the following criteria:  (a) any two orbitals in the sp&lt;sup&gt;3&lt;/sup&gt; set are orthogonal, and (b) the orbitals are properly normalized.


18.	Quantum mechanically, the momentum (p) of a particle traveling in a specific direction (e.g., the x direction) can be obtained by operating on its wavefunction &lt;math&gt;\psi&lt;/math&gt; with the [[w:Momentum_operator|'''momentum operator''']]:

:&lt;math&gt; \hat{p}\psi = p\psi&lt;/math&gt;, where &lt;math&gt; \hat{p} = -i\hbar{\partial \over \partial x} &lt;/math&gt;

Knowing the correct form of this operator was the key to Schrödinger's formulation of  the Hamiltonian operator, &lt;math&gt;\hat{H} = \frac{\hat{p}^2}{2m} + V&lt;/math&gt;, which operates on a wavefunction to give the total energy.  The momentum operator must also be consistent with the [[w:Matter_wave|'''de Broglie relation''']], p = h/λ, which relates the momentum to the particle wavelength.


By analogy to electromagnetic waves, Schrödinger knew that a wavelike particle (such as an electron) traveling in free space in the x-direction could be described by the wavefunction:

:&lt;math&gt;\psi(x,t)= Ae^{i(kx - \omega t +\varphi)}&lt;/math&gt;

where the [[w:Wavenumber|'''wavenumber''']] k is inversely related to the particle's [[w:Matter_wave|'''de Broglie wavelength''']] λ by k = 2π/λ.  Here A is a normalization constant, ω is the frequency of the wave, and &lt;math&gt;\varphi&lt;/math&gt; represents its phase. 

Show using the momentum operator &lt;math&gt;\hat{p}&lt;/math&gt; that the value of the momentum p we obtain for a free particle from &lt;math&gt; \hat{p}\psi = p\psi&lt;/math&gt; is consistent with the de Broglie relation, p = h/λ.  &lt;br&gt;
(Hint: k, ω, and &lt;math&gt;\varphi&lt;/math&gt; are independent of x)


19.	N&lt;sub&gt;3&lt;/sub&gt;S&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; is a cyclic cation that contains no N-N bonds. Draw the structure of the seven-membered ring and use the electron counting method to determine the number of single bonds, double bonds, and lone pairs. Draw out the possible resonance structures for this ion showing formal charges and indicate which one is the most stable. Which S-N bonds would you predict to be the shortest? The atomic connectivity in the ring is: -S-S-N-S-N-S-N-. (''Hint'': determine the number of π-bonds in the molecule by electron counting and then find the most stable resonance structures.)


20.	F has a higher electronegativity than Cl, and F&lt;sub&gt;2&lt;/sub&gt; is a much stronger oxidizing agent than Cl&lt;sub&gt;2&lt;/sub&gt;, despite the fact that the electron affinity of fluorine (-328 kJ/mol) is weaker than that of chlorine (-349 kJ/mol).  Explain this apparent contradiction.

21.	The single bonds in methane (CH&lt;sub&gt;4&lt;/sub&gt;), ammonia (NH&lt;sub&gt;3&lt;/sub&gt;) and water (H&lt;sub&gt;2&lt;/sub&gt;O) are stronger than those in SiH&lt;sub&gt;4&lt;/sub&gt;, PH&lt;sub&gt;3&lt;/sub&gt;, and H&lt;sub&gt;2&lt;/sub&gt;S, respectively. The analogous fluorine containing compounds follow the opposite trend: the single bonds in CF&lt;sub&gt;4&lt;/sub&gt;, NF&lt;sub&gt;3&lt;/sub&gt;, and OF&lt;sub&gt;2&lt;/sub&gt; are weaker than those in SiF&lt;sub&gt;4&lt;/sub&gt;, PF&lt;sub&gt;3&lt;/sub&gt;, and SF&lt;sub&gt;2&lt;/sub&gt;. Can you explain these two opposite trends?

==1.6 References==
{{reflist|colwidth=30em}}

{{BookCat}}</text>
      <sha1>4zyoy61r0vlar119zicnm93prek7rdj</sha1>
    </revision>
    <revision>
      <id>4678485</id>
      <parentid>4678484</parentid>
      <timestamp>2026-10-27T13:09:17Z</timestamp>
      <contributor>
        <username>Tem5psu</username>
        <id>1013978</id>
      </contributor>
      <minor />
      <origin>4678485</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="77769" sha1="pd8i8kiler2g0ibkbskxxe5cybsw4ez" xml:space="preserve">
== Chapter 1:  Review of Chemical Bonding==
[[File:Phosphorus-pentoxide-3D-balls.png|thumb|right|Ball-and-stick representation of chemical bonding in the molecules P&lt;sub&gt;4&lt;/sub&gt;O&lt;sub&gt;10&lt;/sub&gt; and P&lt;sub&gt;4&lt;/sub&gt;S&lt;sub&gt;10&lt;/sub&gt;.]]Molecules (and extended solids) are built from atoms that form chemical bonds.  Theories of bonding seek to explain why molecules and solids form, what their structures are, why some are more stable than others, and how they react.  As we will learn in Chapter 2, quantum mechanics gives us the most realistic picture of chemical bonding via molecular orbital (MO) theory.  However, the MO description of bonding is conceptually difficult and mathematically intensive.  This chapter will review less rigorous (but still useful) models such as Lewis dot structures and valence shell electron-pair repulsion (VSEPR) theory.  When combined with a qualitative quantum mechanical description of bonding through the concepts of orbital hybridization and resonance, these simple models can help us understand a great deal about the structures, stabilities, and reactions of inorganic molecules.

The theory of chemical bonding has a long history, dating back to ancient Greece and the atomists [[w:Democritus|Democritus]], [[w:Leucippus|Leucippus]], and the [[w:Epicureanism|Epicureans]].  They postulated the existence of immutable atoms moving through the void, and envisioned the physical properties of materials as arising from the kinds and shapes of atoms.  In his epic poem ''[[w:de_rerum_natura|De rerum natura]]'' (On the Nature of Things), the Roman poet [[w:Lucretius|Lucretius]] (c. 99 BC – c. 50 BC), drawing on his Epicurean beliefs, describes some atoms and chemical bonding in the following way:

''What seems to us the hardened and condensed''&lt;br&gt;
''Must be of atoms among themselves more hooked,''&lt;br&gt;
''Be held compacted deep within, as 'twere''&lt;br&gt;
''By branch-like atoms -- of which sort the chief''&lt;br&gt;
''Are diamond stones, despisers of all blows''&lt;br&gt;
''And stalwart flint and strength of solid iron''&lt;br&gt;
''And brazen bars, which, budging hard in locks,''&lt;br&gt;
''Do grate and scream.  But what are liquid, formed''&lt;br&gt;
''Of fluid body, they indeed must be''&lt;br&gt;
''Of elements more smooth and round -- because''&lt;br&gt;
''Their globules severally will not cohere.''

Lucretius' [https://www.gutenberg.org/files/785/785-h/785-h.htm poem] is enjoyable reading and contains some remarkable insights into the microscopic world, given the tools available at the time.  Modern analytical methods show that he was off base with his ideas about hooks and spheres, however.  We will revisit the nature of chemical bonding in the substances Lucretius mentions (diamond, quartz, iron, brass, and water) in the context of modern chemical theories to understand why they have the special properties they do.


'''Learning goals for Chapter 1:'''

*Be able to draw Lewis dot structures, assign formal charges, predict molecular geometries (including bond angles), and calculate bond orders for molecules, including hypervalent molecules and ions.
*Describe hypervalent molecules using no-bond resonance.
*Understand and articulate how predictions of molecular structure and bonding can be experimentally verified.
*Learn to construct hybrid orbitals from s and p atomic orbitals.
*Use the isoelectronic principle to design new molecules and solids.
*Rationalize bond strength and chemical reactivity using bond polarity arguments.
*Interrelate bond length and bond strength.

==1.1 Valence bond theory: Lewis dot structures, the octet rule, formal charge, resonance, and the isoelectronic principle==
[[File:electron dot.svg|350px|thumb|right|Fig. 1.1.1.  Examples of Lewis dot diagrams showing chemical bonds between carbon, hydrogen, and oxygen, and non-bonding electron pairs.]]
'''Atoms and Molecules'''&lt;br&gt;
[[w:Atomism|Atomism]], because it was dismissed by [[w:Aristotle|Aristotle]], enjoyed a long sleep in scientific discourse until it was reconsidered by  [[w:Galileo_Galilei|Galileo]], [[w:René_Descartes|Decartes]], and [[w:Pierre_Gassendi|Gassendi]] in the 1600s.  [[w:John_Dalton|Dalton]] postulated the modern atomic theory in 1808 based on his observation that elements such as hydrogen and oxygen combined in specific ratios (the Law of Definite Proportions), but the atomic theory remained contentious throughout most of the 19th century.  [[w:JJ_Thompson|Thompson]], [[w:Ernest_Rutherford|Rutherford]], [[w:Nils_Bohr|Bohr]], and others around the turn of the 20th century established that matter was indeed composed of atoms that contained heavy nuclei and light electrons, and that atoms could exist in excited states that could be interpreted as excitations of their electrons to different energy levels.  However the atomic theory did not provide a ready explanation for the bonded states of atoms in molecules.

In 1916, still more than a decade before modern quantum theory would adequately describe the shapes of [[w:Atomic_orbitals|atomic orbitals]], [[w:Gilbert_N._Lewis|Lewis]] proposed the octet theory based on the empirically observed rules of valence, i.e., the combining ratios of atoms in molecules.&lt;ref&gt;G. N. Lewis, &quot;The atom and the molecule,&quot; J. Am. Chem. Soc. 1916, 38, 762-785&lt;/ref&gt;  This theory, in hindsight, can be rationalized for s- and p-block elements by observing that main-group atoms can use their four valence orbitals (s, p&lt;sub&gt;x&lt;/sub&gt;, p&lt;sub&gt;y&lt;/sub&gt;, and p&lt;sub&gt;z&lt;/sub&gt;) to accommodate up to eight electrons, some or all of which may be shared with other atoms. In Lewis' model, the valence electrons of an atom were situated at the corners of a cube, and the cubes could share edges or faces to complete their octets.  Lewis developed a shorthand notation for these structures based on dots that represented the valence electrons, as illustrated in Fig. 1.1.1. A pair of electrons shared between atoms constitutes a chemical bond, and can also be represented as a line joining the atoms.  Four electrons shared between atoms, represented by two lines, is a double bond, and so forth.  Any pairs of electrons not involved in bonding form &quot;lone pairs&quot; that belong to one atom only and are thus not involved in bonding.

The Lewis picture is powerful in its simplicity.  It can be readily used to rationalize or predict the combining ratios of atoms, to sort plausible and unlikely structures for molecules (including large ones), and to rationalize the acid-base properties of many molecules.  It is important to remember that the model is built on a shaky, pre-quantum mechanical description of atoms and so with it, we will make mistakes.  Nevertheless it is useful to see how far we can go with the Lewis model.
&lt;br /&gt;
&lt;br /&gt;

'''Constructing the octet valence bond picture for a molecule'''&lt;br /&gt;&lt;br/&gt;
We can construct an octet picture for any molecule using the '''N-V method:'''&lt;br /&gt;

:Number of electrons ''needed'' to make separate octets around all atoms = '''N'''&lt;br /&gt;

:(N = 8 for non-H atoms, N = 2 for H)&lt;br /&gt;

:Number of ''valence'' electrons = '''V'''  (add up using group numbers; don't forget to add or subtract for charges on ions)&lt;br /&gt;

:Number of ''shared'' electrons = '''S''' = N-V; and therefore the number of bonds = S/2&lt;br /&gt;

:Fill in lone pairs everywhere else to complete octets&lt;br /&gt;


Example:  nitrate anion, NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;&lt;br /&gt;

:N = 4 atoms x 8 electrons = 32&lt;br /&gt;
:V = 5 + 6 + 6 + 6 + 1 = 24  	(N + O + O + O + charge)&lt;br /&gt;
:S = 32-24 = 8 shared electrons = '''4 bonds'''&lt;br /&gt;

:The number of lone pairs is obtained by difference: (V-S)/2 = (24-8)/2 = 8&lt;br /&gt;

:Now draw the molecule, starting with the four bonds and adding eight lone pairs to complete the octets:
&lt;br /&gt;

::[[File:Nitrate Lewis dot structure.svg|100px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:Count the shared and unshared electrons around each atom in the nitrate ion and you will see that all atoms are '''octet''' and that the total number of valence electrons (V) is 24.  If you do the N-V calculation according to the rules above, you should always get an octet structure.
&lt;br /&gt;
[[File:System2.gif|right|400px|thumb|The charges on atoms in a molecule (or an extended solid such as SiO&lt;sub&gt;2&lt;/sub&gt;) can be estimated from X-ray photoelectron spectra (XPS).  Energetic X-rays ionize atoms by kicking out electrons from their core orbitals.  By conservation of energy, the kinetic energy (KE) of an emitted electron is related to its binding energy (BE) and the energy of the incoming X-ray photon (hν) by BE = hν - KE. Electrons are harder to remove from positively charged atoms (higher BE), and easier to remove from negatively charged atoms (lower BE), relative to the neutral element.]] 
The '''formal charge''' distribution is assigned by dividing the shared (bonding) electrons equally between atoms.  Thus, the singly bonded O atoms each possess 7 electrons, and because O is in group 6, their formal charge is -1.  The doubly bonded O has a formal charge of zero.  The N atom has a formal charge of +1 because it &quot;owns&quot; 4 valence electrons and is in group 5.  

Note that the '''formal charge''' is '''not''' the same thing as the '''oxidation number''' (or '''oxidation state''').  In the nitrate ion, the oxidation state of nitrogen is +5 and the oxidation state of oxygen is -2.  The formal charge is typically closer to the &quot;real&quot; charge on the atom (as measured, e.g., by [[w:X-ray_photoelectron_spectroscopy|X-ray photoelectron spectroscopy]]).  Oxidation states are a useful bookkeeping device for keeping track of oxidation-reduction reactions, as we will discuss in Chapter 4.  Like oxidation states, the formal charges on the atoms in a molecule or ion must ''add up to its overall charge''. 

We can similarly draw the Lewis structure for ammonia as shown below:
&lt;br /&gt;

::[[File:ammonia Lewis structure.svg|200px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

&lt;br /&gt;
When we divide the shared electrons equally between the atoms, we see that the N atom has five electrons and each H atom has one. These are the same as their group numbers, and thus, all the formal charges in the ammonia molecule are zero.

Octet structures of the Lewis acid-base adduct NH&lt;sub&gt;3&lt;/sub&gt;BF&lt;sub&gt;3&lt;/sub&gt;, the hydronium ion H&lt;sub&gt;3&lt;/sub&gt;O&lt;sup&gt;+&lt;/sup&gt;, and the sulfate anion SO&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;2-&lt;/sup&gt; are shown below.  In this case (and in many Lewis structures we will draw), we leave off the implied lone pairs around the peripheral atoms.  Try calculating the number of bonds in each of these molecules using the N-V method, and fill in the lone pairs that are not explicitly drawn in.
::[[File:octet structures.jpg|400px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In cases where more than one valence bond structure is possible, we can use formal charges to decide which structures should be more or less stable.  The rules are:&lt;br /&gt;

*The formal charges on atoms are minimized in stable structures, zero being the best case.
*Negative formal charges should be placed on the most electronegative atom(s).
*Positive formal charges should be placed on the least electronegative atom(s).
*It is unfavorable to place like charges (++ or --) on neighboring atoms in a molecule.
&lt;br /&gt;

Examples of these rules are shown below for alternative structures of BF&lt;sub&gt;3&lt;/sub&gt; and ONF.  

::[[File:Boron trifluoride resonance.svg|300px|left]][[File:Atmospheric ozone.svg|400px|right|thumb|Life outside of the ocean owes its existence to the presence of ozone (O&lt;sub&gt;3&lt;/sub&gt;) in the stratosphere.  Ozone absorbs the ultraviolet light in the solar spectrum, which otherwise would cause catastrophic damage to DNA and other biological molecules.  Because ozone is produced photochemically from O&lt;sub&gt;2&lt;/sub&gt;, which is itself generated by photosynthesis, the spectroscopic signature of ozone in the atmosphere of distant planets is one possible way to look for extraterrestrial life.]][[File:Susan Solomon-Desk With Globe.jpg|right|400px|thumb|[[w:Susan_Solomon|Susan Solomon]] discovered the heterogeneous catalytic mechanism whereby ozone is decomposed by chlorofluorocarbons (freons), creating the Antarctic ozone hole.  Her work formed the basis of the [[w:Montreal_Protocol|U.N. Montreal Protocol]], an international agreement to protect the ozone layer by regulating damaging chemicals.]] 

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;br /&gt;

In the BF&lt;sub&gt;3&lt;/sub&gt; case, the structure on the left is non-octet, because there are only six electrons (three bonds) in the valence shell of B.  Such structures are said to be ''electron deficient.''  An octet structure (right) can be drawn, but it places a positive formal charge on F, the most electronegative atom in the molecule.  Thus, neither structure is completely &quot;happy,&quot; but the formal charge rules tell us that the electron-deficient structure on the left is more stable.  The electron deficiency of BF&lt;sub&gt;3&lt;/sub&gt; makes it a powerful Lewis acid.


In the case of ONF, the structure on the left is unfavorable for two reasons.  First, it places a positive formal charge on F, the most electronegative atom.  Second, there is another possible structure (right) that has zero formal charge, which is preferable to one with non-zero charge.  This means that the structure on the right, with a double bond between N and O, is more reasonable.
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::[[File:ONF resonance structures.jpg|225px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

'''Resonance structures'''&lt;/br&gt;
The ozone (O&lt;sub&gt;3&lt;/sub&gt;) molecule has two equivalent octet structures, shown below:
&lt;br /&gt;
&lt;br /&gt;

::[[File:ozone resonance structures.jpg|225px|left]]

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In both cases, the Lewis dot diagram suggests that there are three kinds of oxygen atoms in the molecule, with +1, 0, and -1 formal charges.  These structures also suggest that ozone should have one single and one double bond.  Experimentally (by [[w:Electron_diffraction|electron diffraction]]), however, we find that the molecule is symmetric, with both O-O bond lengths the same. The real (instantaneous) structure is the average of the two forms, as shown below.  In the classical Lewis picture of the molecule, we can rationalize resonance by observing that electrons, being thousands of times lighter than the nuclei of atoms, move very fast on the timescale of molecular vibrations.  Thus, in the time it takes for the oxygen atoms to adjust their positions, the electrons can move back and forth many times.  In the quantum mechanical MO picture (Chapter 2), we will see that resonance involves electrons that are fully delocalized over the atoms in the molecule. We represent resonance structures with a double-headed arrow to signify that the only difference between the Lewis structures is the distribution of electrons.

In the instantaneous structure of ozone, the formal (-) charge is shared between the two terminal oxygen atoms and therefore each one has a formal charge of -1/2.  The O-O bonds are the average of a single and a double bond, i.e., each O-O bond order is 1.5.
[[File:ozone avg structure.jpg|150px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Similarly, the nitrate anion has three resonance structures, and experimentally (by X-ray crystallography of nitrate salts) we find that all the N-O bonds in the ion are the same.  In this case, in the averaged structure, each O atom has a formal charge of -2/3 and the N-O bond order is 4/3 (=1.33...).


[[File:Nitrate ion resonance structures.png|300px|left]] = [[File:Nitrate-ion-resonance-hybrid-2D.png|119x119px]]
&lt;br/&gt;
&lt;br/&gt;
'''Inequivalent resonance structures'''&lt;br&gt;
The rules of resonance also apply to inequivalent structures, which in general will have different energies from each other.  In this case the structure of the molecule represents a weighted average of the low energy structures.  A good example is the cyanate ion, OCN&lt;sup&gt;-&lt;/sup&gt;. We can write three inequivalent octet structures for the molecule:

:&lt;math chem&gt;\ce{~^{-}O-C\equiv N  &lt;-&gt;  O=C=N^- &lt;-&gt;  ^+  O\equiv C-N^{2-}}&lt;/math&gt;

The first two are reasonable resonance structures, although we suspect the one on the left is the best because it puts the negative formal charge on the most electronegative atom.  The last one is clearly a bad resonance structure, because the formal charges are high and there is a positive charge on the oxygen atom.  The real structure is thus a weighted average of the first two.&lt;br&gt;
&lt;br /&gt;

'''No-bond resonance'''&lt;br&gt;
An interesting and useful kind of inequivalent resonance structure is one in which there is a bond order of ''zero'' between two of the atoms.  This concept of '''no-bond resonance''' is important in understanding the bonding in many halogen- and hydrogen-containing compounds. The idea is illustrated below for the generic molecule X-Y-Z, where Z might be an electronegative halogen atom such as F.  By moving the bonding electrons from the Y-Z bond onto the Z atom, and moving a lone pair from X into the X-Y bond, we generate the resonance structure shown on the right in which all atoms remain octet, but there is no bond between Y and Z.&lt;br&gt;
&lt;br /&gt;

[[File:no bond resonance.jpg|300px|left]]
&lt;br /&gt;
&lt;br /&gt;


It is important to recognize in this example that the no-bond form is only one resonance structure, and therefore the Z atom is still bound to Y.  If the two resonance structures in this example have the same energy, we would expect the X-Y bond order to be 1.5 and the Y-Z bond order to be 0.5.  Therefore the Y-Z bond should be longer than it is in a compound where the bond order is one, and it should be relatively easy to break the Y-Z bond.

Some molecular examples of no-bond resonance are shown below.  In the molecule ONF&lt;sub&gt;3&lt;/sub&gt;, the N-F bond is unusually long relative to the N-F bond in NF&lt;sub&gt;3&lt;/sub&gt;, in which the bond order is 1.  This can be explained by the no-bond resonance forms shown on the right.  Similarly, in the Lewis acid-base adduct formed by combining BH&lt;sub&gt;3&lt;/sub&gt; with CO, we can explain the long B-H bonds using no-bond resonance forms that place a partial positive charge on the H atoms.

[[File:NF no bond resonance.jpg|450px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

No-bond resonance is often used to provide an octet bonding picture for so-called '''[[w:Hypervalent_molecule|hypervalent compounds]]''', which are compounds that appear to have more than 8 valence electrons in the bonding shell of the central atom.  For example, we can consider two different valence bond structures for the triiodide ion, I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, which is formed by reaction of I&lt;sup&gt;-&lt;/sup&gt; with I&lt;sub&gt;2&lt;/sub&gt; in water:

[[File:hypervalent triiodide.jpg|370px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;


[[File:Blue Solution.jpg|200px|right|thumb|The deep blue color of starch-iodine solutions results from the complexation of linear polyiodide ions (I&lt;sub&gt;n&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;) by the starch (amylose) left-handed helix. The interior of the helix is hydrophobic.  In electron donor solvents such as ethanol and water, I&lt;sub&gt;2&lt;/sub&gt; and salts of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; have a brown color, the result of a charge transfer interaction between the solvent and solute.&lt;ref&gt;W. Saenger, &quot;The structure of the blue starch-iodine complex,&quot; Naturwissenschaften 71, 31-36 (1984).&lt;/ref&gt;&lt;ref&gt;R. D. Hancock and B. J. Tarbet, &quot;The other double helix - the fascinating chemistry of starch,&quot; J. Chem. Ed. 77, 988-992 (2000).&lt;/ref&gt;]]In this structure, the central iodine atom has 10 electrons in its valence shell, in violation of the octet rule.  [[w:Raman_spectroscopy|Raman spectra]] of the triiodide ion show that the I-I bond is weaker than the I-I single bond in I&lt;sub&gt;2&lt;/sub&gt;, suggesting that this picture is not an accurate description of the bonding.  A better representation of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; can be obtained with no-bond resonance structures, as shown below.  We will see that this picture is consistent with the MO description of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; in Chapter 2:

[[File:octet triiodide.jpg|350px|left]][[File:IodineStarch left en.svg|200px|right]]

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;br /&gt;


We can draw a similar picture for the XeF&lt;sub&gt;2&lt;/sub&gt; molecule, which has the same number of valence electrons as I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.  This picture is consistent with XPS data, which show a partial negative charge on the F atoms, as well as vibrational spectra, which show that the Xe-F bond is weaker in XeF&lt;sub&gt;2&lt;/sub&gt; than it is in the singly-bonded cation Xe-F&lt;sup&gt;+&lt;/sup&gt;.


[[File:octet XeF2.jpg|170px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Other well known examples of hypervalent compounds are PF&lt;sub&gt;5&lt;/sub&gt;, P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, and SF&lt;sub&gt;6&lt;/sub&gt;, as well as oxyacids such as H&lt;sub&gt;2&lt;/sub&gt;SO&lt;sub&gt;4&lt;/sub&gt; and HClO&lt;sub&gt;4&lt;/sub&gt;.  The hypervalent structure is often drawn for these molecules, with the explanation that d-orbitals on the central atom contribute to the bonding in dsp&lt;sup&gt;3&lt;/sup&gt; and d&lt;sup&gt;2&lt;/sup&gt;sp&lt;sup&gt;3&lt;/sup&gt; hybrids for 5- and 6-coordinate molecules, respectively.  However, realistic molecular orbital calculations show that the phosphorus and sulfur 3d orbitals are too high in energy to contribute significantly to bonding in PF&lt;sub&gt;5&lt;/sub&gt; and SF&lt;sub&gt;6&lt;/sub&gt;. For these molecules, we can use no-bond resonance to make reasonable octet structures that predict polar bonds between the central atom and F.  [[File:sf6 bonding.jpg|380px|left]][[File:Sulfur-hexafluoride-from-xtal-3D-SF.png|right|200px|thumb|Space-filling model of sulfur hexafluoride.  [[w:Sulfur_hexafluoride|SF&lt;sub&gt;6&lt;/sub&gt;]] is surprisingly unreactive with water, relative to other compounds that contain S-F bonds. The tight packing of F atoms around S prevents nucleophilic attack by water.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

In other cases, such as P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, the octet structure is unreasonable because it suggests a polar bond between P and C, with a partial negative charge on C.  Further, in the case of oxyacids such as H&lt;sub&gt;2&lt;/sub&gt;SO&lt;sub&gt;4&lt;/sub&gt; and HClO&lt;sub&gt;4&lt;/sub&gt;, X-ray crystallographic data establish that the S-O and Cl-O bonds are shorter for the oxygen atoms not bonded to hydrogen, which is more consistent with the hypervalent picture:
&lt;br&gt;&lt;br&gt;
[[File:octet&amp;hypervalent H2SO4.jpg|200px|left]][[File:Sulfuric-acid-2D-dimensions.svg|130px]]
&lt;br&gt;


The question of whether hypervalency and the octet rule are really useful descriptions of the bonding in these compounds has been considered in a number of computational studies, which have used increasingly accurate quantum mechanical calculations to determine the number of electrons associated with the central atom.  In a 2002 study, Gillespie and Silvi&lt;ref&gt;R. J. Gillespie and B. Silvi, &quot;The octet rule and hypervalence: two misunderstood concepts,&quot; Coord. Chem. Rev. 233-234, 53-62 (2002).&lt;/ref&gt; found that the population of the valence shell is greater than eight for compounds with electropositive ligands, such as P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, and less than eight for compounds such as PF&lt;sub&gt;5&lt;/sub&gt;.  They concluded that these valence electron shell populations depend primarily on the coordination numbers and electronegativities of the central atoms and their ligands, and that there is no fundamental difference between the bonding in hypervalent and non-hypervalent (Lewis octet) molecules.  This reminds us that the octet rule is not a law of nature, but rather an empirical rule that is useful within certain limits.&lt;ref&gt;R. Crabtree, &quot;Hypervalency, secondary bonding and hydrogen
bonding: siblings under the skin,&quot; Chem. Soc. Rev.,
46, 1720-1729 (2017).&lt;/ref&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:A man breathing in nitrous oxide (laughing gas) and a man ex Wellcome L0023721.jpg|right|300px|thumb|Nitrous oxide (N&lt;sub&gt;2&lt;/sub&gt;O), or laughing gas, is isoelectronic with CO&lt;sub&gt;2&lt;/sub&gt;.  The two molecules have the same shape (linear) and similar physical properties.  CO&lt;sub&gt;2&lt;/sub&gt; sublimes at -78 °C, whereas N&lt;sub&gt;2&lt;/sub&gt;O melts at -91 °C and boils at -88 °C.]]
'''The isoelectronic principle'''&lt;br /&gt;
In calculating the octet structures of molecules using the N-V method, we needed to know only the number of atoms and the number of electrons, not the identities of the atoms themselves.  This means that we will get the same answer (and the same set of octet and resonance structures) for ''any'' molecule or ion that contains (a) the same number of non-hydrogen atoms, and (b) the same total number of valence electrons.  Such molecules are said to be ''isoelectronic.''  This is a powerful conclusion because, once we have determined the electronic structure of one molecule, we can write down the same solution for ''all other molecules'' that are isoelectronic.  For example, we noted above that I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; and XeF&lt;sub&gt;2&lt;/sub&gt;, which both have 22 valence electrons, have the same valence bond structure.  We can further expect that isoelectronic molecules will have the same shapes and, very often, similar physical properties.  

The four molecules and ions below all contain three non-hydrogen atoms and 16 valence electrons.  All of them are linear molecules with two double bonds.  The four molecules and ions shown below them all contain four non-hydrogen atoms and 24 valence electrons.  These four have a trigonal planar shape.  While BF&lt;sub&gt;3&lt;/sub&gt; is a member of this isoelectronic series, we do not write it in the resonance form that contains a B=F double bond, because that would put a positive formal charge on F.
[[File:isoelectronic molecules.jpg|320px|left]]  &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;      [[File:24e molecules.jpg|left|400px]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Similarly we can show that CH&lt;sub&gt;4&lt;/sub&gt;, NH&lt;sub&gt;3&lt;/sub&gt;, NH&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;, H&lt;sub&gt;2&lt;/sub&gt;O, H&lt;sub&gt;3&lt;/sub&gt;O&lt;sup&gt;+&lt;/sup&gt;, HF, F&lt;sup&gt;-&lt;/sup&gt;, and OH&lt;sup&gt;-&lt;/sup&gt; are all isoelectronic with one non-H atom and eight valence electrons.  In the next section we will see that this gives rise to nearly identical electronic shapes for these molecules.
[[File:Gallium-arsenide-unit-cell-3D-balls.png|200px|thumb|right|Fig. 1.1.2. The tetrahedral bonding in crystals of GaAs, CdTe, CuIn&lt;sub&gt;1-x&lt;/sub&gt;Ga&lt;sub&gt;x&lt;/sub&gt;Se&lt;sub&gt;2&lt;/sub&gt; and other semiconductors is similar to that in isoelectronic Si and Ge.]]
&lt;br&gt;

'''Isoelectronic solids.'''  The isoelectronic principle works not just for molecules but for extended solids as well.  One technologically important set of isoelectronic solids are the p-block semiconductors.  The group 14 element Si is the most widely used semiconductor for electronics, but, as we will discuss later, it is not a good light emitter.  Light-emitting diodes (LEDs), which are used in lasers, high efficiency lighting, and display technologies, are made from compounds that are isoelectronic with Si and Ge, especially GaAs, GaP, AlAs, and GaN (all contain four valence electrons per atom).  CdTe and CuIn&lt;sub&gt;1-x&lt;/sub&gt;Ga&lt;sub&gt;x&lt;/sub&gt;Se&lt;sub&gt;2&lt;/sub&gt; (CIGS) are promising solar cell materials that also have the same number of valence electrons per atom.  Like Si and Ge, these compounds have tetrahedrally bonded structures in the solid state and absorb light across most of the solar spectrum, as we will discuss in more detail in Chapters 8 and 10.


The isoelectronic principle is also a powerful tool in materials research, because it provides guidance about where to look for new materials with similar and perhaps improved properties.  For example, the discovery that 8.5% efficient thin layer solar cells could be made with the compound CsSnI&lt;sub&gt;3&lt;/sub&gt;&lt;ref&gt;I. Chung, B. Lee,  J. He,	R. P. H. Chang	 and M. G. Kanatzidis, All-solid-state dye-sensitized solar cells with high efficiency, Nature 485, 486-489 (2012). doi:10.1038/nature11067&lt;/ref&gt; stimulated the exploration of many isoelectronic ABX&lt;sub&gt;3&lt;/sub&gt; compounds with the same perovskite crystal structure. Very recently thin film solar cells based on light absorbers in this structural family (MA)PbI&lt;sub&gt;3-x&lt;/sub&gt;Cl&lt;sub&gt;x&lt;/sub&gt; and FA&lt;sub&gt;x&lt;/sub&gt;MA&lt;sub&gt;1−x&lt;/sub&gt;PbBr&lt;sub&gt;y&lt;/sub&gt;I&lt;sub&gt;3−y&lt;/sub&gt; (MA&lt;sup&gt;+&lt;/sup&gt; = methylammonium, CH&lt;sub&gt;3&lt;/sub&gt;NH&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;; FA&lt;sup&gt;+&lt;/sup&gt; = formamidinium, HC(NH&lt;sub&gt;2&lt;/sub&gt;)&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;) have been reported with efficiencies as high as 22%.&lt;ref&gt;S.D. Stranks,  G. E. Eperon, G. Grancini,  C. Menelaou,  M. J. P. Alcocer, T. Leijtens, L. M. Herz, A. Petrozza, and H. J. Snaith, Electron-Hole Diffusion Lengths Exceeding 1 Micrometer in an Organometal Trihalide Perovskite Absorber, Science 342, 341-344 (2013). DOI: 10.1126/science.1243982&lt;/ref&gt;&lt;ref&gt;G. Xing,  N. Mathews, S. Sun, S. S. Lim, Y. M. Lam, M. Grätzel, S. Mhaisalkar, and T. C. Sum, Long-Range Balanced Electron- and Hole-Transport Lengths in Organic-Inorganic CH3NH3PbI3, Science 342, 344-347 (2013). DOI: 10.1126/science.1243167 &lt;/ref&gt;&lt;ref&gt;J.-P. Correa-Baena, A. Abate, M. Saliba, W. Tress, T. J. Jacobsson, M. Grätzel, and A. Hagfeldt, The rapid evolution of highly efficient perovskite solar cells, Energy Environ. Sci., 10, 710-727 (2017). DOI: 10.1039/C6EE03397K &lt;/ref&gt;

==1.2 The shapes of molecules (VSEPR theory) and orbital hybridization ==
[[Image:Water molecule dimensions.svg|thumb|200px|Geometry of the [[w:water (molecule)|water molecule]]]]
The [[w:VSEPR_theory|Valence Shell Electron Pair Repulsion (VSEPR) theory]] is a simple and useful way to predict and rationalize the shapes of molecules.  The theory is based on the idea of minimizing the electrostatic repulsion between electron pairs, as first proposed by Sidgwick and Powell in 1940,&lt;ref&gt;N. V. Sidgwick and H. M. Powell, Proc. Roy. Soc. A176, 153 (1940),&lt;/ref&gt; then generalized by Gillespie and Nyholm in 1957,&lt;ref&gt;R. J. Gillespie and R. S. Nyholm, Quart. Rev. Chem. Soc., 11, 339 (1957).&lt;/ref&gt; and then broadly applied over the intervening 50+ years.&lt;ref&gt;R. J. Gillespie, &quot;Fifty years of the VSEPR model,&quot; Coord. Chem. Rev. 252, 1315-1327 (2008). DOI: 10.1016/j.ccr.2007.07.007&lt;/ref&gt;

To use the VSEPR model, one begins with the Lewis dot picture to determine the number of lone pairs and bonding domains around a central atom.  Because VSEPR considers all bonding domains equally (i.e., a single bond, a double bond, and a half bond all count as one electron domain), one can use either an octet or hypervalent structure, provided that the number of lone pairs (which should be the same in both) is calculated correctly.  For example, in either the hypervalent or octet structure of the I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; ion above, there are three lone pairs on the central I atom and two bonding domains.  We then follow these steps to obtain the '''electronic geometry''':
&lt;br /&gt;
&lt;br /&gt;
*Determine the number of lone pairs on the central atom in the molecule, and add the number of bonded atoms (a.k.a. bonding domains)
*This number (the ''steric number'') defines the electronic shape of the molecule by minimizing repulsion.  For example a steric number of three gives a trigonal planar electronic shape.
*The angles between electron domains are determined primarily by the electronic geometry (e.g., 109.5° for a steric number of 4, which implies that the electronic shape is a tetrahedron)
*These angles are adjusted by the hierarchy of repulsions:  (lone pair - lone pair) &gt; (lone pair - bond) &gt; (bond - bond)
&lt;br /&gt;

The '''molecular geometry''' is deduced from the electronic geometry by considering the lone pairs to be present but invisible.  The most commonly used methods to determine molecular structure - [[w:X-ray_diffraction|X-ray diffraction]], [[w:Neutron_diffraction|neutron diffraction]], and [[w:Electron_diffraction|electron diffraction]] - have a hard time seeing lone pairs, but they can accurately determine the lengths of bonds between atoms and the bond angles.

The table below gives examples of electronic and molecular shapes for steric numbers between 2 and 9.  We are most often concerned with molecules that have steric numbers between 2 and 6.

{| class=&quot;wikitable sortable&quot;
|-
! Bonding electron pairs
! Lone pairs
! Electron domains (Steric #)
! Shape
! Ideal bond angle (example's bond angle)
! Example
! Image
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:linear molecular geometry|linear]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:carbon dioxide|CO&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Linear-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal planar molecular geometry|trigonal planar]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;120°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Boron trifluoride|BF&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Trigonal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bent molecular geometry|bent]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;120° (119°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Sulfur dioxide|SO&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Bent-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:tetrahedral molecular geometry|tetrahedral]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:methane|CH&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX4E0-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal pyramidal molecular geometry|trigonal pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5° (107°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:ammonia|NH&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bent molecular geometry|bent]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5° (104.5°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:H2O|H&lt;sub&gt;2&lt;/sub&gt;O]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Bent-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal bipyramidal molecular geometry|trigonal bipyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 120°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:phosphorus pentachloride|PCl&lt;sub&gt;5&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Trigonal-bipyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:seesaw molecular geometry|seesaw]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°, 120°, 90° (173.1°, 101.6°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:sulfur tetrafluoride|SF&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Seesaw-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:T-shaped molecular geometry|T-shaped]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180° (87.5°, &lt; 180°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:chlorine trifluoride|ClF&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:T-shaped-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:linear molecular geometry|linear]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:xenon difluoride|XeF&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Linear-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:octahedral molecular geometry|octahedral]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:sulfur hexafluoride|SF&lt;sub&gt;6&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX6E0-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square pyramidal molecular geometry|square pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90° (84.8°), 180° &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bromine pentafluoride|BrF&lt;sub&gt;5&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square planar molecular geometry|square planar]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:xenon tetrafluoride|XeF&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-planar-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal bipyramidal molecular geometry|pentagonal bipyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 72°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:iodine heptafluoride|IF&lt;sub&gt;7&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-bipyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal pyramidal molecular geometry|pentagonal pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;72°, 90°, 144°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;XeOF&lt;sub&gt;5&lt;/sub&gt;&lt;sup&gt;−&lt;/sup&gt;&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal planar molecular geometry|planar pentagonal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;72°, 144°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Tetramethylammonium pentafluoroxenate|XeF&lt;sub&gt;5&lt;/sub&gt;&lt;sup&gt;−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-planar-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;8&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;8&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square antiprismatic molecular geometry|square antiprismatic]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt; &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Nitrosonium octafluoroxenate(VI)|XeF&lt;sub&gt;8&lt;/sub&gt;&lt;sup&gt;2−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-antiprismatic-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;9&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;9&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:tricapped trigonal prismatic molecular geometry|tricapped trigonal prismatic]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt; &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Potassium_nonahydridorhenate|ReH&lt;sub&gt;9&lt;/sub&gt;&lt;sup&gt;2−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX9E0-3D-balls.png|50px]]&lt;/div&gt;
|}
&lt;br /&gt;
From the Table, we see that some of the molecules shown as examples have bond angles that depart from the ideal electronic geometry.  For example, the H-N-H bond angle in ammonia is 107°, and the H-O-H angle in water is 104.5°.  We can rationalize this in terms of the last rule above.  The lone pair in ammonia repels the electrons in the N-H bonds more than the bonds repel each other.  This lone pair repulsion exerts even more steric influence in the case of water, where there are two lone pairs.  Similarly, the axial F-S-F angle in the &quot;seesaw&quot; molecule SF&lt;sub&gt;4&lt;/sub&gt; is a few degrees less than 180° because of repulsion by the lone pair in the molecule.

'''Geometrical isomers'''&lt;br /&gt;

For some molecules in the Table, we note that there is more than one possible shape that would satisfy the VSEPR rules.  For example, the XeF&lt;sub&gt;2&lt;/sub&gt; molecule has a steric number of five and a trigonal bipyramidal geometry.  There are three possible stereoisomers:  one in which the F atoms occupy axial sites, resulting in linear molecule, one in which the F atoms occupy one equatorial and one axial site (resulting in a 90° bond angle), and one in which the F atoms are both on equatorial sites, with a F-Xe-F bond angle of 120°.

[[File:XeF2 geometry.jpg|130px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

The observed geometry of XeF&lt;sub&gt;2&lt;/sub&gt; is linear, which can be rationalized by considering the orbitals that are used to make bonds (or lone pairs) in the axial and equatorial positions.  There are four available orbitals, s, p&lt;sub&gt;x&lt;/sub&gt;, p&lt;sub&gt;y&lt;/sub&gt;, and p&lt;sub&gt;z&lt;/sub&gt;.  If we choose the z-axis as the axial direction, we can see that the p&lt;sub&gt;x&lt;/sub&gt; and p&lt;sub&gt;y&lt;/sub&gt; orbitals lie in the equatorial plane.  We assume that the spherical s orbital is shared equally by the five electron domains in the molecule, the two axial bonds share the p&lt;sub&gt;z&lt;/sub&gt; orbital, and the three equatorial bonds share the p&lt;sub&gt;x&lt;/sub&gt; and p&lt;sub&gt;y&lt;/sub&gt; orbitals.  We can then calculate the bond orders to axial and equatorial F atoms as follows:
&lt;br /&gt;

axial:  1/5 s + 1/2 p&lt;sub&gt;z&lt;/sub&gt; = 0.7 bond (formal charge = -0.3)&lt;br /&gt;
equatorial: 1/5 s + 1/3 p&lt;sub&gt;x&lt;/sub&gt; + 1/3 p&lt;sub&gt;y&lt;/sub&gt; = 0.867 bond (formal charge = -0.133)
&lt;br /&gt;

Because fluorine is more electronegative than a lone pair, it prefers the axial site where it will have more negative formal charge.  In general, by this reasoning, lone pairs and electropositive ligands such as CH&lt;sub&gt;3&lt;/sub&gt; will always prefer the equatorial sites in the trigonal bipyramidal geometry.  Electronegative ligands such as F will always go to the axial sites.

In the case of the BrF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; anion, which is isoelectronic with XeF&lt;sub&gt;4&lt;/sub&gt; in the Table, the electronic geometry is octahedral and there are two possible isomers in which the two lone pairs are ''cis'' or ''trans'' to each other.  In this case, lone pair - lone pair repulsion dominates and we obtain the ''trans'' arrangement of lone pairs, giving a square planar molecular geometry.
&lt;br /&gt;
[[File:BrF4-VSEPR.jpg|350px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

'''Orbital hybridization'''
&lt;br /&gt;
The observation of molecules in the various electronic shapes shown above is, at first blush, in conflict with our picture of [[w:Atomic_orbitals|atomic orbitals]].  For an atom such as oxygen, we know that the 2s orbital is spherical, and that the 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals are dumbell-shaped and point along the Cartesian axes.  The water molecule contains two hydrogen atoms bound to oxygen not at a 90° angle, but at an angle of 104.5°.  Given the relative orientations of the atomic orbitals, how do we arrive at angles between electron domains of 104.5°, 120°, and so on? To understand this we will need to learn a little bit about the quantum mechanics of electrons in atoms and molecules.&lt;br&gt;
&lt;br&gt;

The atomic orbitals ψ represent solutions to the [[w:Schrödinger equation|'''Schrödinger wave equation''']], 


:&lt;math&gt; E \psi = \hat{H}\psi&lt;/math&gt;


Here E is the energy of an electron in the orbital, and &lt;math&gt; \hat{H}&lt;/math&gt; is the Hamiltonian operator.

By analogy with classical mechanics, the Hamiltonian is commonly expressed as the sum of [[w:Hermitian operators|operators]] corresponding to the [[w:kinetic energy|kinetic]] and [[w:potential energy|potential]] energies of a system in the form


:&lt;math&gt; \hat{H} = \hat{T} + \hat{V}, &lt;/math&gt;


where  &lt;math&gt; \hat{V} = V(\mathbf{r},t) &lt;/math&gt; is the potential energy, and 


:&lt;math&gt;\hat{T} = \frac{\mathbf{\hat{p}}\cdot\mathbf{\hat{p}}}{2m} = \frac{\hat{p}^2}{2m} = -\frac{\hbar^2}{2m}\nabla^2,&lt;/math&gt;


is the kinetic energy operator in which ''m'' is the mass of the particle and the momentum operator is:


:&lt;math&gt; \hat{p} = -i\hbar\nabla ,&lt;/math&gt; where &lt;math&gt;\nabla = {\partial \over \partial x} +  {\partial \over \partial y} +  {\partial \over \partial z}&lt;/math&gt;


Here &lt;math&gt;\hbar&lt;/math&gt; is h/2π, where h is Planck's constant, and the Laplacian operator ∇&lt;sup&gt;2&lt;/sup&gt; is:


:&lt;math&gt;\nabla^2 = \frac{\partial^2}{{\partial x}^2} + \frac{\partial^2}{{\partial y}^2} + \frac{\partial^2}{{\partial z}^2}&lt;/math&gt;


Although this is not the technical definition of the [[w:Hamiltonian mechanics|Hamiltonian in classical mechanics]], it is the form it most commonly takes in quantum mechanics. Combining these together yields the familiar form used in the Schrödinger equation:


:&lt;math&gt;\begin{align}\hat{H} &amp; = \hat{T} + \hat{V} \ = \frac{\mathbf{\hat{p}}\cdot\mathbf{\hat{p}}}{2m}+ V(\mathbf{r},t) \ = -\frac{\hbar^2}{2m}\nabla^2+ V(\mathbf{r},t)\end{align}&lt;/math&gt;


For hydrogen-like (one-electron) atoms, the Schrödinger equation can be written as:&lt;br /&gt;


:&lt;math&gt; E \psi = -\frac{\hbar^2}{2\mu}\nabla^2\psi - \frac{Ze^2}{4\pi\epsilon_0 r}\psi &lt;/math&gt;


where '''Z''' is the nuclear charge, ''e'' is the electron charge, and '''r''' is the position of the electron. The radial potential term on the right side of the equation is due to the [[w:Coulomb's law|Coulomb interaction]], i.e., the electrostatic attraction between the nucleus and the electron, in which ''ε''&lt;sub&gt;0&lt;/sub&gt; is the [[w:electric constant|dielectric constant]] (permittivity of free space) and


:&lt;math&gt; \mu = \frac{m_em_n}{m_e+m_n} &lt;/math&gt;


is the 2-body [[w:reduced mass|reduced mass]] of the [[w:Nucleus (atomic structure)|nucleus]] of mass ''m''&lt;sub&gt;n&lt;/sub&gt; and the electron of mass ''m''&lt;sub&gt;e&lt;/sub&gt;.  To a good approximation, µ ≈ ''m''&lt;sub&gt;e&lt;/sub&gt;.
[[File:Erwin_Schrodinger2.jpg|right|thumb|150px|Erwin Schrödinger as a young scientist]]


This is the equation that [[w:Erwin_Schrödinger|Erwin Schrödinger]] famously derived in 1926 to solve for the energies and shapes of the s, p, d, and f [[w:Atomic_orbital|atomic orbitals]] in hydrogen-like atoms.  It was a huge conceptual leap for both physics and chemistry because it not only explained the quantized energy levels of the hydrogen atom, but also provided the theoretical basis for the octet rule and the arrangement of elements in the periodic table.


The Schrödinger equation can be used to describe chemical systems that are more complicated than the hydrogen atom (e.g., multi-electron atoms, molecules, infinite crystals, and the dynamics of those systems) if we substitute the appropriate potential energy function V(r,t) into the Hamiltonian.  The math becomes more complicated and the equation must be solved numerically in those cases, so for our purposes we will stick with the simplest case of time-invariant, one-electron, hydrogen-like atoms.
&lt;br&gt;&lt;br&gt;
[[File:Neon orbitals rotated.png|right|thumb|170px|The shapes of the first five [[w:Atomic_orbitals|atomic orbitals]]: 1s, 2s, 2p&lt;sub&gt;''x''&lt;/sub&gt;, 2p&lt;sub&gt;''y''&lt;/sub&gt;, and 2p&lt;sub&gt;''z''&lt;/sub&gt;. The colors denote the sign of the wave function.]]
Without going into too much detail about the Schrödinger equation, we can point out some of its most important properties:&lt;br&gt;
:&lt;math&gt; E \psi = -\frac{\hbar^2}{2\mu}\nabla^2\psi - \frac{Ze^2}{4\pi\epsilon_0 r}\psi &lt;/math&gt;
*The equation derives from the fact that the total energy (E) is the sum of the kinetic energy (KE) and the potential energy (PE).  These three quantities are represented mathematically as [[w:Operator_(physics)|'''operators''']] in the equation.
*On the left side of the equation, the total energy operator (E) is a scalar that is multiplied by the [[w:Wave_function|wavefunction]] ψ. ψ is a function of the spatial coordinates (x,y,z) and is related to the probability that the electron is at that point in space.
*The first term on the right side of the equation represents the kinetic energy (KE).  The kinetic energy operator is proportional to ∇&lt;sup&gt;2&lt;/sup&gt; (the [[w:Laplacian|Laplacian operator]]) which takes the second derivative (with respect to three spatial coordinates) of ψ.  Thus, the Schrödinger equation is a '''differential equation'''.
*The second term on the right side of the equation represents the Coulomb potential (PE), i.e. the attractive energy between the positively charged nucleus and the negatively charged electron.
*The solutions to the Schrödinger equation are a set of '''energies''' E (which are scalar quantities) and [[w:Wave_function|'''wavefunctions''']] (a.k.a. '''[[w:Atomic_orbitals|atomic orbitals]]''') ψ, which are functions of the spatial coordinates.  You will sometimes see the energies referred to as [[w:Eigenvalue|''eigenvalues'']] and the orbitals as [[w:eigenfunction|''eigenfunctions'']], because mathematically the Schrödinger equation is an eigenfunction-eigenvalue equation.  Although ψ is a function of the coordinates, E is not.  So an electron in a 2p&lt;sub&gt;z&lt;/sub&gt; orbital has the same total energy E (= PE + KE) no matter where it is in space. 
*These E values and their associated [[w:Wave_function|wavefunctions]] ψ are catalogued according to their '''[[w:Quantum_number|quantum numbers]]''' ''n,'' ''l,'' and ''m&lt;sub&gt;l&lt;/sub&gt;.''  That is, there are many solutions to the differential equation, and each solution (ψ(xyz) and E) has a unique set of quantum numbers.  Some sets of orbitals are '''degenerate''', meaning that they have the same energy (e.g., 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt;).
*The solutions ψ(xyz) to the Schrödinger equation (e.g., the 1s, 2s, 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals) represent '''probability amplitudes''' for finding the electron at a particular point (x,y,z) in space.  A probability amplitude can have either '''+ or - sign'''.  We typically represent the different signs by shading or by + and - signs on the two lobes of a 2p orbital.  
*The square of the probability amplitude, ψ&lt;sup&gt;2&lt;/sup&gt;, is always a positive number and represents the '''probability''' of finding the electron at a point x,y,z in space.  Because the total probability of finding the electron somewhere is 1, the wavefunction must be '''normalized''' so that the integral of ψ&lt;sup&gt;2&lt;/sup&gt; over the spatial coordinates (from -∞ to +∞) is 1.
*The solutions to the Schrödinger equation are '''orthogonal''', meaning that the product of any two (integrated over all space) is zero.  For example the product of the 2s and 2p&lt;sub&gt;x&lt;/sub&gt; orbitals, integrated over the spatial coordinates from -∞ to +∞, is zero.
&lt;br&gt;
Orbital hybridization involves making ''linear combinations'' of the [[w:Atomic_orbitals|atomic orbitals]] that are solutions to the Schrödinger equation.  Mathematically, this is justified by recognizing that the Schrödinger equation is a ''linear'' differential equation.  As such, any sum of solutions to the Schrödinger equation is also a valid solution.  However, we still impose the constraint that our hybrid orbitals must be '''orthogonal''' and '''normalized'''.
&lt;br /&gt;

'''Rules for orbital hybridization:'''

* Add and subtract [[w:Atomic_orbitals|atomic orbitals]] to get hybrid orbitals.
* We get the same number of orbitals out as we put in.
* The energy of a hybrid orbital is the weighted average of the [[w:Atomic_orbitals|atomic orbitals]] that make it up.
* The coefficients are determined by the constraints that the hybrid orbitals must be orthogonal and normalized.


For '''sp hybridization''', as in the BeF&lt;sub&gt;2&lt;/sub&gt; or CO&lt;sub&gt;2&lt;/sub&gt; molecule, we make two linear combinations of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals (assigning z as the axis of the Be-F bond):

:&lt;math&gt;\psi_1 = \frac{1}{\sqrt 2}(2s) + \frac{1}{\sqrt 2}(2p_z)&lt;/math&gt;&lt;br&gt;
:&lt;math&gt;\psi_2 = \frac{1}{\sqrt 2}(2s) - \frac{1}{\sqrt 2}(2p_z)&lt;/math&gt;&lt;br&gt;

Here we have simply added and subtracted the 2s and 2pz orbitals; we leave it as an exercise for the interested student to show that both orbitals are normalized (i.e., {{Unicode|∫}}ψ&lt;sub&gt;1&lt;/sub&gt;&lt;sup&gt;2&lt;/sup&gt;dτ = {{Unicode|∫}}ψ&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;2&lt;/sup&gt;dτ = 1) and orthogonal (i.e., {{Unicode|∫}}ψ&lt;sub&gt;1&lt;/sub&gt;ψ&lt;sub&gt;2&lt;/sub&gt;dτ = 0).

What this means physically is explained in the figure below.  By combining the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals we have created two new orbitals with large lobes (high electron probability) pointing along the z-axis.  These two orbitals are degenerate and have an energy that is halfway between the energy of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals.
[[File:sp hybridization.jpg|thumb|500px|center|Linear combinations of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; [[w:Atomic_orbitals|atomic orbitals]] make two 2sp&lt;sub&gt;z&lt;/sub&gt; hybrids.  The 2p&lt;sub&gt;x&lt;/sub&gt; and 2p&lt;sub&gt;y&lt;/sub&gt; orbitals are unchanged.]]
For an isolated Be atom, which has two valence electrons, the lowest energy state would have two electrons spin-paired in the 2s orbital.  However, these electrons would not be available for bonding.  By '''promoting''' these electrons to the degenerate 2sp&lt;sub&gt;z&lt;/sub&gt; hybrid orbitals, they become unpaired and are prepared for bonding to the F atoms in BeF&lt;sub&gt;2&lt;/sub&gt;.  This will occur if the '''bonding energy''' (in the promoted state) exceeds the promotion energy.  The '''overall bonding energy''', i.e., the energy released by combining a Be atom in its ground state with two F atoms, is the difference between the bonding and promotion energies.

We can similarly construct '''sp&lt;sup&gt;2&lt;/sup&gt; hybrids''' (e.g., for the BF&lt;sub&gt;3&lt;/sub&gt; molecule or the NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; anion) from one 2s and two 2p [[w:Atomic_orbitals|atomic orbitals]].  Taking the plane of the molecule as the xy plane, we obtain three hybrid orbitals at 120° to each other.  The three hybrids are:
[[File:sp2hybrids.jpg|200px|right]]&lt;br /&gt;

:&lt;math&gt;\psi_1 = \frac{1}{\sqrt 3}(2s) + \frac{\sqrt 2}{\sqrt 3}(2p_x)&lt;/math&gt;
:&lt;math&gt;\psi_2 = \frac{1}{\sqrt 3}(2s) - \frac{1}{\sqrt 6}(2p_x) + \frac{1}{\sqrt 2}(2p_y)&lt;/math&gt;
:&lt;math&gt;\psi_3 = \frac{1}{\sqrt 3}(2s) - \frac{1}{\sqrt 6}(2p_x) - \frac{1}{\sqrt 2}(2p_y)&lt;/math&gt;
&lt;br /&gt;

These orbitals are again degenerate and their energy is the weighted average of the energies of the 2s, 2p&lt;sub&gt;x&lt;/sub&gt;, and 2p&lt;sub&gt;y&lt;/sub&gt; [[w:Atomic_orbitals|atomic orbitals]].

Finally, to make a sp&lt;sup&gt;3&lt;/sup&gt; hybrid, as in CH&lt;sub&gt;4&lt;/sub&gt;, H&lt;sub&gt;2&lt;/sub&gt;O, etc., we combine all four [[w:Atomic_orbitals|atomic orbitals]] to make four degenerate hybrids:
[[File:Ch4 hybridization.svg|130px|right]]&lt;br /&gt;
 [[File:CH4-structure.svg|130px|right]]&lt;br /&gt;

:&lt;math&gt;\psi_1 = \frac{1}{2}(2s + 2p_x + 2p_y + 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_2 = \frac{1}{2}(2s - 2p_x - 2p_y + 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_3 = \frac{1}{2}(2s + 2p_x - 2p_y - 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_4 = \frac{1}{2}(2s - 2p_x + 2p_y - 2p_z)&lt;/math&gt;&lt;br&gt;


The lobes of the '''sp&lt;sup&gt;3&lt;/sup&gt; hybrid''' orbitals point towards the vertices of a tetrahedron (or alternate corners of a cube), consistent with the tetrahedral bond angle in CH&lt;sub&gt;4&lt;/sub&gt; and the nearly tetrahedral angles in NH&lt;sub&gt;3&lt;/sub&gt; and H&lt;sub&gt;2&lt;/sub&gt;O. Similarly, we can show that we can construct the trigonal bipyramidal electronic shape by making sp and sp&lt;sup&gt;2&lt;/sup&gt; hybrids, and the octahedral geometry from three sets of sp hybrids. The picture that emerges from this is that the [[w:Atomic_orbitals|atomic orbitals]] can hybridize as required by the shape that best minimizes electron pair repulsions.
[[File:Hydrogen-sulfide-2D-dimensions.svg|130px|right]]
Interestingly however, the bond angles in PH&lt;sub&gt;3&lt;/sub&gt;, H&lt;sub&gt;2&lt;/sub&gt;S and H&lt;sub&gt;2&lt;/sub&gt;Se are close to 90°, suggesting that P, S, and Se primarily use their p-orbitals in bonding to H in these molecules.  This is consistent with the fact that the energy difference between s and p orbitals stays roughly constant going down the periodic table, but the bond energy ''decreases'' as the valence electrons get farther away from the nucleus.  In compounds of elements in the 3rd, 4th, and 5th rows of the periodic table, there thus is a ''decreasing tendency to use s-p orbital hybrids in bonding''.  For these heavier elements, the bonding energy is not enough to offset the energy needed to promote the s electrons to s-p hybrid orbitals.

==1.3 Bond polarity and bond strength==
[[Image:Water-elpot-transparent-3D-balls.png|thumb|right|250px|Fig. 1.3.1. A [[w:water molecule|water molecule]], a commonly used example of polarity. The two charges are present with a negative charge in the middle (red), and a positive charge at the ends (blue).]]
[[w:Linus Pauling|Linus Pauling]] introduced the concept of [[w:electronegativity|electronegativity]] 1932 in order to explain the extra stability of molecules with polar bonds. &lt;ref name=&quot;paulingJACS&quot;&gt;{{cite journal |author= Pauling, L.
 |authorlink=Linus Pauling
 |year= 1932
 |journal= [[w:Journal of the American Chemical Society|J. Am. Chem. Soc.]]
 |volume= 54
 |issue= 9
 |pages= 3570–3582
 |title= The Nature of the Chemical Bond. IV. The Energy of Single Bonds and the Relative Electronegativity of Atoms
 |doi= 10.1021/ja01348a011}}&lt;/ref&gt;  The electronegativity of an atom, represented by the Greek letter ''χ'', can be defined as the tendency of an atom to draw electrons to itself in a chemical bond.  On the Pauling scale, the electronegativity difference between two atoms A and B was defined in terms of the [[w:Bond dissociation energy|dissociation energies]] ''E''&lt;sub&gt;d&lt;/sub&gt; of the  A-A, B-B, and A-B bonds:&lt;br&gt;&lt;br&gt;

::&lt;small&gt;&lt;math&gt;\chi_{\rm A} - \chi_{\rm B} = \sqrt{E_{\rm d}({\rm AB}) - [E_{\rm d}({\rm AA}) + E_{\rm d}({\rm BB})]/2}&lt;/math&gt;&lt;/small&gt;&lt;br&gt;&lt;br&gt;
where the energies are expressed in electron volts.

This definition, while directly relevant to the strength of chemical bonds, requires thermochemical input data from many compounds, some of which were not available at the time.  Mulliken&lt;ref&gt;{{cite journal
|author = Mulliken, R. S.
|year =1934
|journal = [[w:Journal of Chemical Physics|J. Chem. Phys.]]
|volume = 2
|title = A New Electroaffinity Scale; Together with Data on Valence States and on Valence Ionization Potentials and Electron Affinities
|doi = 10.1063/1.1749394
|pages = 782–793
|issue = 11|bibcode = 1934JChPh...2..782M }}&lt;/ref&gt;&lt;ref&gt;{{cite journal
|author = Mulliken, R. S.
|year =1935
|title = Electronic Structures of Molecules XI. Electroaffinity, Molecular Orbitals and Dipole Moments
|journal = [[w:Journal of Chemical Physics|J. Chem. Phys.]]
|volume = 3
|doi = 10.1063/1.1749731
|pages = 573–585
|issue = 9|bibcode = 1935JChPh...3..573M }}&lt;/ref&gt; and later Pearson&lt;ref&gt;{{cite journal|author = Pearson, R. G.
|title = Absolute electronegativity and absolute hardness of Lewis acids and bases
|year = 1985
|journal = [[w:Journal of the American Chemical Society|J. Am. Chem. Soc.]]
|volume = 107
|pages = 6801
|doi = 10.1021/ja00310a009|issue = 24}}&lt;/ref&gt; developed a scale of electronegativities based on the average of the electron affinity and ionization energy of the free A and B atoms, which they correlated with thermochemical data and the Pauling scale.  

On the Pauling scale, the least electronegative elements are the alkali metals (χ = 0.7-1.0) and the most electronegative are oxygen (3.5) and fluorine (4.0) at the upper right of the periodic table.  Carbon and hydrogen have intermediate electronegativities (2.6 and 2.2 on the Pauling scale, respectively).  The general trend (see table below) is that electronegativities increase going up and to the right in the periodic table.  There are some interesting exceptions to this behavior, most notably two islands of high electronegativity at the bottom of the transition series, peaking at tungsten (χ = 2.4) and gold (χ = 2.5).  The first of these can be explained by the very high metal-metal bond energy of elements such as Mo and W, which can use all six of their valence electrons in bonding, as we will discuss in Chapter 6.  The second however occurs with more weakly bonded noble metals such as Pt and Au, and is responsible for  their low position in the [[w:Reactivity_series|activity series]],&lt;ref&gt;B. Hammer and J. K. Norskov, &quot;Why gold is the noblest of all the metals,&quot; ''Nature'' '''376,''' 238 - 240 (2002. doi:10.1038/376238a0&lt;/ref&gt; as well as their extraordinary properties as catalysts.&lt;br&gt;&lt;br&gt;
[[image:periodic table Pauling electronegatvity.jpg|500px|left]]

[[w:Electronegativities_of_the_elements_(data_page)#Electronegativity_.28Pauling_scale.29|Table of Pauling electronegativities]]

The polarity of bonds is determined by electronegativity differences.  As a guideline we define bonds as:

* '''ionic''' if Δχ &gt; 2.0
* '''polar''' if 2.0 &gt; Δχ &gt; 0.5
* '''nonpolar''' if 0.5 &gt; Δχ

The polarity of bonds helps us understand [[w:Intermolecular_force|non-covalent forces]] between molecules, such as [[w:Hydrogen_bonding|hydrogen bonding]] and dipole-dipole interactions. It also helps us interpret the reactivity of molecules.  For example, the Si-H bond (χ&lt;sub&gt;Si&lt;/sub&gt; = 1.8, χ&lt;sub&gt;H&lt;/sub&gt; = 2.1) is more hydride-like than the C-H bond (χ&lt;sub&gt;C&lt;/sub&gt; = 2.5, χ&lt;sub&gt;H&lt;/sub&gt; = 2.1).  Therefore silanes react with acids to make H&lt;sub&gt;2&lt;/sub&gt;, whereas phosphines (χ&lt;sub&gt;P&lt;/sub&gt; = 2.1) and hydrocarbons do not.  Similarly, electrophilic substitution reactions occur more readily on Si-H and P-H compounds than they do on C-H compounds.

There is also a correlation between the strength of a chemical bond and the bond length, longer bonds being weaker because of weaker orbital overlap.  Pauling introduced an empirical formula relating bond length to bond strength.  For a given pair of atoms (for example, two carbon atoms):&lt;br&gt;&lt;br&gt;

:&lt;big&gt;'''D(n) = D(1) - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(n)'''&lt;/big&gt;&lt;br&gt;&lt;br&gt;

where D(n) represents the bond length in Å and n is the bond order. D(1) in this case would be the length of a C-C single bond, which we can obtain from the average bond length in alkanes (1.54 Å).  Using this formula we can predict that the bond lengths in ethylene (C=C double bond) and acetylene (C≡C triple bond) should be 1.36 and 1.25 Å, respectively, which are close to the experimental values of 1.33 and 1.20 Å.  In a related form the Pauling formula can be used to calculate bond lengths when the single bond length D(1) is not available:&lt;br&gt;&lt;br&gt;

:&lt;big&gt;'''D(n) = D(m) - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(n/m)'''&lt;/big&gt;&lt;br&gt;


Here n and m represent two different bond orders between the same kinds of atoms.  This tells, for example, that the difference in length between a triple and double bond, D(2)-D(3), should be - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(2/3) = 0.11 Å.
&lt;br /&gt;
&lt;br /&gt;

[[File:Bond length of fluorine graph.JPG|right|350px|thumb|Trends in covalent radii for p-block elements. The [[w:Covalent_radius_of_fluorine|covalent radius of F]] has been difficult to determine because of electron pair repulsion effects. Early reports (Shomaker and Stevenson, Pauling) overestimated the size of the F atom.&lt;ref&gt;{{cite journal|last1=Schomaker|first1=Verner|last2=Stevenson|first2=D. P.|journal=Journal of the American Chemical Society|volume=63|pages=37–40|year=1941|doi=10.1021/ja01846a007|title=Some Revisions of the Covalent Radii and the Additivity Rule for the Lengths of Partially Ionic Single Covalent Bonds *}}&lt;/ref&gt;&lt;ref&gt;Pauling, L. The Nature of the Chemical Bond, 3rd ed.; Cornell University Press: Ithaca, NY, 1960; p. 224.&lt;/ref&gt;&lt;ref&gt;{{cite journal|last1=Robinson|first1=Edward A.|last2=Johnson|first2=Samuel A.|last3=Tang|first3=Ting-Hua|last4=Gillespie|first4=Ronald J.|title=Reinterpretation of the Lengths of Bonds to Fluorine in Terms of an Almost Ionic Model|journal=Inorganic Chemistry|volume=36|issue=14|pages=3022–3030|year=1997|pmid=11669953|doi=10.1021/ic961315b}}&lt;/ref&gt;  Accurate quantum chemical calculations place the F single-bond covalent radius at about 0.64 Å.&lt;ref&gt;{{cite journal|doi=10.1002/chem.200901472|title=Molecular Double-Bond Covalent Radii for Elements Li–E112|year=2009|last1=Pyykkö|first1=Pekka|last2=Atsumi|first2=Michiko|journal=Chemistry: A European Journal|volume=15|issue=46|pages=12770–12779}}&lt;/ref&gt;]]Some bond lengths and bond energies are anomalous. For example, the F-F bond length in F&lt;sub&gt;2&lt;/sub&gt; is 1.43 Å, which is 0.15 Å ''longer'' than twice the covalent radius of the F atom (0.64 Å).  The F-F bond is also quite weak (bond dissociation energy = 155 kJ/mol) relative to the Cl-Cl bond (242 kJ/mol).  By putting the extra bond length into the Pauling formula, we calculate that the bond order in the F&lt;sub&gt;2&lt;/sub&gt; molecule is only 0.6, i.e., substantially weaker than a F-F single bond.  The physical reason for this is that the F-F bond is &quot;stretched&quot; by repulsion of the lone pairs on the F atoms.  This crowding is caused by the fact that the [He] 1s&lt;sup&gt;2&lt;/sup&gt; core orbital, as well as the valence orbitals of the fluorine atoms, are contracted by the high nuclear charge.  The Cl atom in Cl&lt;sub&gt;2&lt;/sub&gt; has a larger [Ne] (1s&lt;sup&gt;2&lt;/sup&gt;2s&lt;sup&gt;2&lt;/sup&gt;2p&lt;sup&gt;6&lt;/sup&gt;) core, in contrast, so Cl-Cl has a &quot;normal&quot; single bond length (1.98 Å) that is twice the covalent radius of the Cl atom (0.99 Å).  A similar lone pair repulsion effect explains the anomalously long and weak N-N and O-O single bonds in hydrazine (H&lt;sub&gt;2&lt;/sub&gt;N-NH&lt;sub&gt;2&lt;/sub&gt;) and hydrogen peroxide (HO-OH), which are both highly reactive molecules.  
&lt;br /&gt;

The important roles of electronegativity differences and lone pair repulsion are evident when comparing trends in bond strengths.  The table below shows the average single-bond enthalpies of p-block elements with H and F.  H makes stronger bonds with 2nd row elements (C, N, O, F) than with third row elements (Si, P, S, Cl) because the 2p valence electrons are closer to the nucleus and thus make stronger bonds than electrons in 3p orbitals.  The bonds to H also follow the expected trend of increasing bond strength with increasing electronegativity difference.  Bonds between second row elements (C, N, O, F) and F are however anomalously weak because of lone pair repulsion.  For this reason, the Si-F bond is substantially stronger than the C-F bond, whereas the C-H bond is much stronger than the Si-H bond.  The strong Si-F bond is the reason that HF etches glass (to produce the SiF&lt;sub&gt;6&lt;/sub&gt;&lt;sup&gt;2-&lt;/sup&gt; anion), and the strong C-H bond is an important factor in the stability of hydrocarbons and other organic molecules.


'''Average E-H and E-F bond enthalpies (kJ/mol)'''
{| class=&quot;wikitable&quot;
|C-H&amp;nbsp;&amp;nbsp;&amp;nbsp;413&amp;nbsp;&amp;nbsp;&amp;nbsp;||N-H&amp;nbsp;&amp;nbsp;&amp;nbsp;391&amp;nbsp;&amp;nbsp;&amp;nbsp;||O-H&amp;nbsp;&amp;nbsp;&amp;nbsp;483&amp;nbsp;&amp;nbsp;&amp;nbsp;||H-F&amp;nbsp;&amp;nbsp;&amp;nbsp;567&amp;nbsp;&amp;nbsp;&amp;nbsp;
|-
|Si-H&amp;nbsp;&amp;nbsp;&amp;nbsp;323||P-H&amp;nbsp;&amp;nbsp;&amp;nbsp;322||S-H&amp;nbsp;&amp;nbsp;&amp;nbsp;339||H-Cl&amp;nbsp;&amp;nbsp;&amp;nbsp;431
|-
|


|
|
|
|-
|C-F&amp;nbsp;&amp;nbsp;&amp;nbsp;485||N-F&amp;nbsp;&amp;nbsp;&amp;nbsp;272||O-F&amp;nbsp;&amp;nbsp;&amp;nbsp;190||F-F &amp;nbsp;&amp;nbsp;&amp;nbsp;155
|-
|Si-F&amp;nbsp;&amp;nbsp;&amp;nbsp;565||P-F &amp;nbsp;&amp;nbsp;&amp;nbsp;490  ||S-F&amp;nbsp;&amp;nbsp;&amp;nbsp;327||Cl-F&amp;nbsp;&amp;nbsp;&amp;nbsp;253
|}


[[File:A water droplet DWR-coated surface2 edit1.jpg|thumb|150px|right|alt=A shiny spherical drop of water on blue cloth|Fabric treated with fluorosurfactant]]The anomalously weak bond in F&lt;sub&gt;2&lt;/sub&gt; is responsible for the high electronegativity of fluorine, as well as the legendary reactivity of elemental fluorine gas, which reacts explosively with hydrogen and powdered metals.  Because of the instability of elemental fluorine and the polar nature of its bonds with more electropositive elements, fluorine compounds tend to be very stable.  For example, the noble gases Xe and Kr react with fluorine to make covalent compounds, whereas other halogens do not react.  Fluorocarbon compounds contain strong C-F bonds and have high thermal and chemical stability.  Perfluorocarbons such as [[w:Teflon|Teflon]] (poly(tetrafluoroethylene), -(CF&lt;sub&gt;2&lt;/sub&gt;CF&lt;sub&gt;2&lt;/sub&gt;)n-, PTFE) are also highly hydrophobic.  The extraordinary hydrophobicity of perfluorocarbons arises from the fact that -CF&lt;sub&gt;2&lt;/sub&gt;- and -CF&lt;sub&gt;3&lt;/sub&gt; groups are &quot;fatter&quot; than -CH&lt;sub&gt;2&lt;/sub&gt;- and -CH&lt;sub&gt;3&lt;/sub&gt; groups; dissolving them in water is therefore more disruptive to the hydrogen bonding network than is dissolving a hydrocarbon. &lt;ref&gt;V. H. Dalvi and P. J. Rossky, Molecular origins of fluorocarbon hydrophobicity, Proc. Natl. Acad. Sci. USA 107,13603–13607 (2010). DOI: 10.1073/pnas.0915169107.&lt;/ref&gt;

==1.4 Discussion questions==
'''Group essay project:'''&lt;br&gt;
Join a group of classmates from your inorganic chemistry course.  Each group should have 3 or 4 students.  Arrange a time to meet for an hour or so.  Prior to the meeting, read part I (pp. 1367-1391) as well as the summary at the end of Linus Pauling's [http://courses.chem.psu.edu/chem310/ja01355a027.pdf article] (J. Am. Chem. Soc. 1931, 53, 1367-1400) on the nature of the chemical bond.  

This paper was published only a few years after Schrödinger developed the quantum mechanical theory of atomic orbitals and is considered one of the most important papers in the history of modern chemistry.  At the meeting, discuss the following questions:  (1) What was understood about chemical bonding in molecules before Pauling published this work? (2) What new concepts did the paper introduce that we still use today? (3) Why were these ideas important? and (4) What, if anything, did Pauling get wrong, and why?

Together with your classmates, write a 1-2 page essay addressing these questions.  Please include the names of all students in your group on the first page; all of you will receive the same grade on this assignment.  Anonymous excerpts from a few of these essays will be shared with the class.


'''In-class discussion questions from this chapter:'''
* What are inequivalent resonance structures? Illustrate with some new examples not covered above.
* Explain no-bond resonance and hypervalency, using some new examples.
* What are the limitations of valence bond theory for molecules that contain an odd number of electrons? Illustrate with one or two examples.

==1.5 Problems==
1.	Draw composite octet structures (including formal charges, bond order, and molecular shape) for the following: (a) BrO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (b) SF&lt;sub&gt;6&lt;/sub&gt;, (c) KrF&lt;sub&gt;2&lt;/sub&gt;, (d) HClO&lt;sub&gt;4&lt;/sub&gt; (= HOClO&lt;sub&gt;3&lt;/sub&gt;), (e) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, and (f) ClO&lt;sub&gt;2&lt;/sub&gt;.

2.	Draw composite octet structures (including formal charges, bond order, and molecular shape) for the following: (a) Al&lt;sub&gt;2&lt;/sub&gt;Cl&lt;sub&gt;6&lt;/sub&gt;, (b) SnCl&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (c) BrF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;,(d) HOClO, (e) SO&lt;sub&gt;3&lt;/sub&gt;, and (f) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;.

3.	Show using resonance why the CO bond distance in formamide (HCONH&lt;sub&gt;2&lt;/sub&gt;) is longer than the CO bond distance in acetone.

4.	Give the formulas for five stable molecules and/or ions that are isoelectronic with ammonia.

5.	Name three well known molecules or ions that are isoelectronic with (a) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;, (b) BF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (c) CH&lt;sub&gt;4&lt;/sub&gt;, and (d) HCN.


6.	Name three well known molecules or ions that are isoelectronic with (a) CN&lt;sup&gt;-&lt;/sup&gt;, (b) H&lt;sub&gt;2&lt;/sub&gt;O, (c) BF&lt;sub&gt;3&lt;/sub&gt;, and (d) CO&lt;sub&gt;2&lt;/sub&gt;.

7.	The C-C bond distance is 1.20 Å in acetylene.  Using  the Pauling bond length – bond strength formula, D(n) = D(m) - 0.6 log(n/m), estimate the C-C bond distance in ketene (H&lt;sub&gt;2&lt;/sub&gt;CCO).  

8.	In hydroxylamine, H&lt;sub&gt;2&lt;/sub&gt;NOH, the N-O bond distance is 1.46 Å.  Using the Pauling bond length - bond strength formula, estimate the N-O bond distances in NO&lt;sub&gt;2&lt;/sub&gt; and NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.


9.	Nitrogen can exist in the +5 oxidation state in compounds that contain ions such a NF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; and NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.  However the neutral binary compound NF&lt;sub&gt;5&lt;/sub&gt; is unknown.  Can you draw octet structures for each of these compounds?  Why would NF&lt;sub&gt;5&lt;/sub&gt; be unstable?

10.	Consider the compounds NH&lt;sub&gt;3&lt;/sub&gt; and PH&lt;sub&gt;3&lt;/sub&gt;.  The H-N-H bond angle in ammonia is 108&lt;sup&gt;o&lt;/sup&gt; (close to the tetrahedral angle, 109.5&lt;sup&gt;o&lt;/sup&gt;), but the analogous angle in PH&lt;sub&gt;3&lt;/sub&gt; is 93&lt;sup&gt;o&lt;/sup&gt;.   Why is the angle in PH&lt;sub&gt;3&lt;/sub&gt; closer to 90&lt;sup&gt;o&lt;/sup&gt; than it is to the tetrahedral angle?

11.	Two hypothetical structures for the N&lt;sub&gt;2&lt;/sub&gt;F&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; ion are [N-NF&lt;sub&gt;3&lt;/sub&gt;]&lt;sup&gt;+&lt;/sup&gt; and [F-N-NF&lt;sub&gt;2&lt;/sub&gt;]&lt;sup&gt;+&lt;/sup&gt;.  Which one is more stable? Explain.  (Note:  lines in the formulas can represent either single or multiple bonds)

12.	Krypton difluoride, KrF&lt;sub&gt;2&lt;/sub&gt;, decomposes at dry ice temperature to Kr and F&lt;sub&gt;2&lt;/sub&gt;.  However, several salts of the [KrF]&lt;sup&gt;+&lt;/sup&gt; ion are relatively stable.  Draw valence bond pictures for KrF&lt;sub&gt;2&lt;/sub&gt; and [KrF]&lt;sup&gt;+&lt;/sup&gt;, showing lone pairs, possible resonance structures, formal charges, bond orders, and bond angles.  Why is [KrF]&lt;sup&gt;+&lt;/sup&gt; more stable than KrF&lt;sub&gt;2&lt;/sub&gt;?


13.	Consider the anion SF&lt;sub&gt;3&lt;/sub&gt;O&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; (with S the central atom).  How many isomers are possible? Which is the most stable?

14. 	The Br-F bond distance in the interhalogen compound BrF is 1.76 Å.  Use this information to estimate the average bond lengths in BrF&lt;sub&gt;3&lt;/sub&gt; and BrF&lt;sub&gt;5&lt;/sub&gt;.


15. 	The B-H bond distances are about the same in BH&lt;sub&gt;3&lt;/sub&gt; and BH&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;. however, the B-F bond distance in BF&lt;sub&gt;3&lt;/sub&gt; is shorter than that in the BF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; ion.  Explain.


16.	The N-N bond dissociation energy in hydrazine (H&lt;sub&gt;2&lt;/sub&gt;N-NH&lt;sub&gt;2&lt;/sub&gt;) is 159 kJ/mol.  The dissociation energy of the N-N triple bond in N&lt;sub&gt;2&lt;/sub&gt; is 941 kJ/mol, i.e., much greater than three times the N-N single bond dissociation energy in hydrazine.  Explain why the N-N bond in hydrazine is so weak, and why this effect is not seen in N&lt;sub&gt;2&lt;/sub&gt;.


17.	Show that a set of four sp&lt;sup&gt;3&lt;/sup&gt; hybrid orbitals satisfies the following criteria:  (a) any two orbitals in the sp&lt;sup&gt;3&lt;/sup&gt; set are orthogonal, and (b) the orbitals are properly normalized.


18.	Quantum mechanically, the momentum (p) of a particle traveling in a specific direction (e.g., the x direction) can be obtained by operating on its wavefunction &lt;math&gt;\psi&lt;/math&gt; with the [[w:Momentum_operator|'''momentum operator''']]:

:&lt;math&gt; \hat{p}\psi = p\psi&lt;/math&gt;, where &lt;math&gt; \hat{p} = -i\hbar{\partial \over \partial x} &lt;/math&gt;

Knowing the correct form of this operator was the key to Schrödinger's formulation of  the Hamiltonian operator, &lt;math&gt;\hat{H} = \frac{\hat{p}^2}{2m} + V&lt;/math&gt;, which operates on a wavefunction to give the total energy.  The momentum operator must also be consistent with the [[w:Matter_wave|'''de Broglie relation''']], p = h/λ, which relates the momentum to the particle wavelength.


By analogy to electromagnetic waves, Schrödinger knew that a wavelike particle (such as an electron) traveling in free space in the x-direction could be described by the wavefunction:

:&lt;math&gt;\psi(x,t)= Ae^{i(kx - \omega t +\varphi)}&lt;/math&gt;

where the [[w:Wavenumber|'''wavenumber''']] k is inversely related to the particle's [[w:Matter_wave|'''de Broglie wavelength''']] λ by k = 2π/λ.  Here A is a normalization constant, ω is the frequency of the wave, and &lt;math&gt;\varphi&lt;/math&gt; represents its phase. 

Show using the momentum operator &lt;math&gt;\hat{p}&lt;/math&gt; that the value of the momentum p we obtain for a free particle from &lt;math&gt; \hat{p}\psi = p\psi&lt;/math&gt; is consistent with the de Broglie relation, p = h/λ.  &lt;br&gt;
(Hint: k, ω, and &lt;math&gt;\varphi&lt;/math&gt; are independent of x)


19.	N&lt;sub&gt;3&lt;/sub&gt;S&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; is a cyclic cation that contains no N-N bonds. Draw the structure of the seven-membered ring and use the electron counting method to determine the number of single bonds, double bonds, and lone pairs. Draw out the possible resonance structures for this ion showing formal charges and indicate which one is the most stable. Which S-N bonds would you predict to be the shortest? The atomic connectivity in the ring is: -S-S-N-S-N-S-N-. (''Hint'': determine the number of π-bonds in the molecule by electron counting and then find the most stable resonance structures.)


20.	F has a higher electronegativity than Cl, and F&lt;sub&gt;2&lt;/sub&gt; is a much stronger oxidizing agent than Cl&lt;sub&gt;2&lt;/sub&gt;, despite the fact that the electron affinity of fluorine (-328 kJ/mol) is weaker than that of chlorine (-349 kJ/mol).  Explain this apparent contradiction.

21.	The single bonds in methane (CH&lt;sub&gt;4&lt;/sub&gt;), ammonia (NH&lt;sub&gt;3&lt;/sub&gt;) and water (H&lt;sub&gt;2&lt;/sub&gt;O) are stronger than those in SiH&lt;sub&gt;4&lt;/sub&gt;, PH&lt;sub&gt;3&lt;/sub&gt;, and H&lt;sub&gt;2&lt;/sub&gt;S, respectively. The analogous fluorine containing compounds follow the opposite trend: the single bonds in CF&lt;sub&gt;4&lt;/sub&gt;, NF&lt;sub&gt;3&lt;/sub&gt;, and OF&lt;sub&gt;2&lt;/sub&gt; are weaker than those in SiF&lt;sub&gt;4&lt;/sub&gt;, PF&lt;sub&gt;3&lt;/sub&gt;, and SF&lt;sub&gt;2&lt;/sub&gt;. Can you explain these two opposite trends?

==1.6 References==
{{reflist|colwidth=30em}}

{{BookCat}}</text>
      <sha1>pd8i8kiler2g0ibkbskxxe5cybsw4ez</sha1>
    </revision>
    <revision>
      <id>4678486</id>
      <parentid>4678485</parentid>
      <timestamp>2026-10-27T13:39:54Z</timestamp>
      <contributor>
        <username>Tem5psu</username>
        <id>1013978</id>
      </contributor>
      <comment>/* 1.1 Valence bond theory: Lewis dot structures, the octet rule, formal charge, resonance, and the isoelectronic principle */</comment>
      <origin>4678486</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="77793" sha1="awnh9z5bcgc33hlutjflo92chg0qt4z" xml:space="preserve">
== Chapter 1:  Review of Chemical Bonding==
[[File:Phosphorus-pentoxide-3D-balls.png|thumb|right|Ball-and-stick representation of chemical bonding in the molecules P&lt;sub&gt;4&lt;/sub&gt;O&lt;sub&gt;10&lt;/sub&gt; and P&lt;sub&gt;4&lt;/sub&gt;S&lt;sub&gt;10&lt;/sub&gt;.]]Molecules (and extended solids) are built from atoms that form chemical bonds.  Theories of bonding seek to explain why molecules and solids form, what their structures are, why some are more stable than others, and how they react.  As we will learn in Chapter 2, quantum mechanics gives us the most realistic picture of chemical bonding via molecular orbital (MO) theory.  However, the MO description of bonding is conceptually difficult and mathematically intensive.  This chapter will review less rigorous (but still useful) models such as Lewis dot structures and valence shell electron-pair repulsion (VSEPR) theory.  When combined with a qualitative quantum mechanical description of bonding through the concepts of orbital hybridization and resonance, these simple models can help us understand a great deal about the structures, stabilities, and reactions of inorganic molecules.

The theory of chemical bonding has a long history, dating back to ancient Greece and the atomists [[w:Democritus|Democritus]], [[w:Leucippus|Leucippus]], and the [[w:Epicureanism|Epicureans]].  They postulated the existence of immutable atoms moving through the void, and envisioned the physical properties of materials as arising from the kinds and shapes of atoms.  In his epic poem ''[[w:de_rerum_natura|De rerum natura]]'' (On the Nature of Things), the Roman poet [[w:Lucretius|Lucretius]] (c. 99 BC – c. 50 BC), drawing on his Epicurean beliefs, describes some atoms and chemical bonding in the following way:

''What seems to us the hardened and condensed''&lt;br&gt;
''Must be of atoms among themselves more hooked,''&lt;br&gt;
''Be held compacted deep within, as 'twere''&lt;br&gt;
''By branch-like atoms -- of which sort the chief''&lt;br&gt;
''Are diamond stones, despisers of all blows''&lt;br&gt;
''And stalwart flint and strength of solid iron''&lt;br&gt;
''And brazen bars, which, budging hard in locks,''&lt;br&gt;
''Do grate and scream.  But what are liquid, formed''&lt;br&gt;
''Of fluid body, they indeed must be''&lt;br&gt;
''Of elements more smooth and round -- because''&lt;br&gt;
''Their globules severally will not cohere.''

Lucretius' [https://www.gutenberg.org/files/785/785-h/785-h.htm poem] is enjoyable reading and contains some remarkable insights into the microscopic world, given the tools available at the time.  Modern analytical methods show that he was off base with his ideas about hooks and spheres, however.  We will revisit the nature of chemical bonding in the substances Lucretius mentions (diamond, quartz, iron, brass, and water) in the context of modern chemical theories to understand why they have the special properties they do.


'''Learning goals for Chapter 1:'''

*Be able to draw Lewis dot structures, assign formal charges, predict molecular geometries (including bond angles), and calculate bond orders for molecules, including hypervalent molecules and ions.
*Describe hypervalent molecules using no-bond resonance.
*Understand and articulate how predictions of molecular structure and bonding can be experimentally verified.
*Learn to construct hybrid orbitals from s and p atomic orbitals.
*Use the isoelectronic principle to design new molecules and solids.
*Rationalize bond strength and chemical reactivity using bond polarity arguments.
*Interrelate bond length and bond strength.

==1.1 Valence bond theory: Lewis dot structures, the octet rule, formal charge, resonance, and the isoelectronic principle==
[[File:electron dot.svg|350px|thumb|right|Fig. 1.1.1.  Examples of Lewis dot diagrams showing chemical bonds between carbon, hydrogen, and oxygen, and non-bonding electron pairs.]]
'''Atoms and Molecules'''&lt;br&gt;
[[w:Atomism|Atomism]], because it was dismissed by [[w:Aristotle|Aristotle]], enjoyed a long sleep in scientific discourse until it was reconsidered by  [[w:Galileo_Galilei|Galileo]], [[w:René_Descartes|Decartes]], and [[w:Pierre_Gassendi|Gassendi]] in the 1600s.  [[w:John_Dalton|Dalton]] postulated the modern atomic theory in 1808 based on his observation that elements such as hydrogen and oxygen combined in specific ratios (the Law of Definite Proportions), but the atomic theory remained contentious throughout most of the 19th century.  [[w:JJ_Thompson|Thompson]], [[w:Ernest_Rutherford|Rutherford]], [[w:Nils_Bohr|Bohr]], and others around the turn of the 20th century established that matter was indeed composed of atoms that contained heavy nuclei and light electrons, and that atoms could exist in excited states that could be interpreted as excitations of their electrons to different energy levels.  However the atomic theory did not provide a ready explanation for the bonded states of atoms in molecules.

In 1916, still more than a decade before modern quantum theory would adequately describe the shapes of [[w:Atomic_orbitals|atomic orbitals]], [[w:Gilbert_N._Lewis|Lewis]] proposed the octet theory based on the empirically observed rules of valence, i.e., the combining ratios of atoms in molecules.&lt;ref&gt;G. N. Lewis, &quot;The atom and the molecule,&quot; J. Am. Chem. Soc. 1916, 38, 762-785&lt;/ref&gt;  This theory, in hindsight, can be rationalized for s- and p-block elements by observing that main-group atoms can use their four valence orbitals (s, p&lt;sub&gt;x&lt;/sub&gt;, p&lt;sub&gt;y&lt;/sub&gt;, and p&lt;sub&gt;z&lt;/sub&gt;) to accommodate up to eight electrons, some or all of which may be shared with other atoms. In Lewis' model, the valence electrons of an atom were situated at the corners of a cube, and the cubes could share edges or faces to complete their octets.  Lewis developed a shorthand notation for these structures based on dots that represented the valence electrons, as illustrated in Fig. 1.1.1. A pair of electrons shared between atoms constitutes a chemical bond, and can also be represented as a line joining the atoms.  Four electrons shared between atoms, represented by two lines, is a double bond, and so forth.  Any pairs of electrons not involved in bonding form &quot;lone pairs&quot; that belong to one atom only and are thus not involved in bonding.

The Lewis picture is powerful in its simplicity.  It can be readily used to rationalize or predict the combining ratios of atoms, to sort plausible and unlikely structures for molecules (including large ones), and to rationalize the acid-base properties of many molecules.  It is important to remember that the model is built on a shaky, pre-quantum mechanical description of atoms and so with it, we will make mistakes.  Nevertheless it is useful to see how far we can go with the Lewis model.
&lt;br /&gt;
&lt;br /&gt;

'''Constructing the octet valence bond picture for a molecule'''&lt;br /&gt;&lt;br/&gt;
We can construct an octet picture for any molecule using the '''N-V method:'''&lt;br /&gt;

:Number of electrons ''needed'' to make separate octets around all atoms = '''N'''&lt;br /&gt;

:(N = 8 for non-H atoms, N = 2 for H)&lt;br /&gt;

:Number of ''valence'' electrons = '''V'''  (add up using group numbers; don't forget to add or subtract for charges on ions)&lt;br /&gt;

:Number of ''shared'' electrons = '''S''' = N-V; and therefore the number of bonds = S/2&lt;br /&gt;

:Fill in lone pairs everywhere else to complete octets&lt;br /&gt;


Example:  nitrate anion, NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;&lt;br /&gt;

:N = 4 atoms x 8 electrons = 32&lt;br /&gt;
:V = 5 + 6 + 6 + 6 + 1 = 24  	(N + O + O + O + charge)&lt;br /&gt;
:S = 32-24 = 8 shared electrons = '''4 bonds'''&lt;br /&gt;

:The number of lone pairs is obtained by difference: (V-S)/2 = (24-8)/2 = 8&lt;br /&gt;

:Now draw the molecule, starting with the four bonds and adding eight lone pairs to complete the octets:
&lt;br /&gt;

::[[File:Nitrate Lewis dot structure.svg|100px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:Count the shared and unshared electrons around each atom in the nitrate ion and you will see that all atoms are '''octet''' and that the total number of valence electrons (V) is 24.  If you do the N-V calculation according to the rules above, you should always get an octet structure.
&lt;br /&gt;
[[File:System2.gif|right|400px|thumb|The charges on atoms in a molecule (or an extended solid such as SiO&lt;sub&gt;2&lt;/sub&gt;) can be estimated from X-ray photoelectron spectra (XPS).  Energetic X-rays ionize atoms by kicking out electrons from their core orbitals.  By conservation of energy, the kinetic energy (KE) of an emitted electron is related to its binding energy (BE) and the energy of the incoming X-ray photon (hν) by BE = hν - KE. Electrons are harder to remove from positively charged atoms (higher BE), and easier to remove from negatively charged atoms (lower BE), relative to the neutral element.]] 
The '''formal charge''' distribution is assigned by dividing the shared (bonding) electrons equally between atoms.  Thus, the singly bonded O atoms each possess 7 electrons, and because O is in group 6, their formal charge is -1.  The doubly bonded O has a formal charge of zero.  The N atom has a formal charge of +1 because it &quot;owns&quot; 4 valence electrons and is in group 5.  

Note that the '''formal charge''' is '''not''' the same thing as the '''oxidation number''' (or '''oxidation state''').  In the nitrate ion, the oxidation state of nitrogen is +5 and the oxidation state of oxygen is -2.  The formal charge is typically closer to the &quot;real&quot; charge on the atom (as measured, e.g., by [[w:X-ray_photoelectron_spectroscopy|X-ray photoelectron spectroscopy]]).  Oxidation states are a useful bookkeeping device for keeping track of oxidation-reduction reactions, as we will discuss in Chapter 4.  Like oxidation states, the formal charges on the atoms in a molecule or ion must ''add up to its overall charge''. 

We can similarly draw the Lewis structure for ammonia as shown below:
&lt;br /&gt;

::[[File:ammonia Lewis structure.svg|200px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

&lt;br /&gt;
When we divide the shared electrons equally between the atoms, we see that the N atom has five electrons and each H atom has one. These are the same as their group numbers, and thus, all the formal charges in the ammonia molecule are zero.

Octet structures of the Lewis acid-base adduct NH&lt;sub&gt;3&lt;/sub&gt;BF&lt;sub&gt;3&lt;/sub&gt;, the hydronium ion H&lt;sub&gt;3&lt;/sub&gt;O&lt;sup&gt;+&lt;/sup&gt;, and the sulfate anion SO&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;2-&lt;/sup&gt; are shown below.  In this case (and in many Lewis structures we will draw), we leave off the implied lone pairs around the peripheral atoms.  Try calculating the number of bonds in each of these molecules using the N-V method, and fill in the lone pairs that are not explicitly drawn in.
::[[File:octet structures.jpg|400px|left]]			
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In cases where more than one valence bond structure is possible, we can use formal charges to decide which structures should be more or less stable.  The rules are:&lt;br /&gt;

*The formal charges on atoms are minimized in stable structures, zero being the best case.
*Negative formal charges should be placed on the most electronegative atom(s).
*Positive formal charges should be placed on the least electronegative atom(s).
*It is unfavorable to place like charges (++ or --) on neighboring atoms in a molecule.
&lt;br /&gt;

Examples of these rules are shown below for alternative structures of BF&lt;sub&gt;3&lt;/sub&gt; and ONF.  

::[[File:Boron trifluoride resonance.svg|300px|left]][[File:Atmospheric ozone.svg|400px|right|thumb|Life outside of the ocean owes its existence to the presence of ozone (O&lt;sub&gt;3&lt;/sub&gt;) in the stratosphere.  Ozone absorbs the ultraviolet light in the solar spectrum, which otherwise would cause catastrophic damage to DNA and other biological molecules.  Because ozone is produced photochemically from O&lt;sub&gt;2&lt;/sub&gt;, which is itself generated by photosynthesis, the spectroscopic signature of ozone in the atmosphere of distant planets is one possible way to look for extraterrestrial life.]][[File:Susan Solomon-Desk With Globe.jpg|right|400px|thumb|[[w:Susan_Solomon|Susan Solomon]] discovered the heterogeneous catalytic mechanism whereby ozone is decomposed by chlorofluorocarbons (freons), creating the Antarctic ozone hole.  Her work formed the basis of the [[w:Montreal_Protocol|U.N. Montreal Protocol]], an international agreement to protect the ozone layer by regulating damaging chemicals.]] 

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;br /&gt;

In the BF&lt;sub&gt;3&lt;/sub&gt; case, the structure on the left is non-octet, because there are only six electrons (three bonds) in the valence shell of B.  Such structures are said to be ''electron deficient.''  An octet structure (right) can be drawn, but it places a positive formal charge on F, the most electronegative atom in the molecule.  Thus, neither structure is completely &quot;happy,&quot; but the formal charge rules tell us that the electron-deficient structure on the left is more stable.  The electron deficiency of BF&lt;sub&gt;3&lt;/sub&gt; makes it a powerful Lewis acid.


In the case of ONF, the structure on the left is unfavorable for two reasons.  First, it places a positive formal charge on F, the most electronegative atom.  Second, there is another possible structure (right) that has zero formal charge, which is preferable to one with non-zero charge.  This means that the structure on the right, with a double bond between N and O, is more reasonable.
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::[[File:ONF resonance structures.jpg|225px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

'''Resonance structures'''&lt;/br&gt;
The ozone (O&lt;sub&gt;3&lt;/sub&gt;) molecule has two equivalent octet structures, shown below:
&lt;br /&gt;
&lt;br /&gt;

::[[File:ozone resonance structures.jpg|225px|left]]

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In both cases, the Lewis dot diagram suggests that there are three kinds of oxygen atoms in the molecule, with +1, 0, and -1 formal charges.  These structures also suggest that ozone should have one single and one double bond.  Experimentally (by [[w:Electron_diffraction|electron diffraction]]), however, we find that the molecule is symmetric, with both O-O bond lengths the same. The real (instantaneous) structure is the average of the two forms, as shown below.  In the classical Lewis picture of the molecule, we can rationalize resonance by observing that electrons, being thousands of times lighter than the nuclei of atoms, move very fast on the timescale of molecular vibrations.  Thus, in the time it takes for the oxygen atoms to adjust their positions, the electrons can move back and forth many times.  In the quantum mechanical MO picture (Chapter 2), we will see that resonance involves electrons that are fully delocalized over the atoms in the molecule. We represent resonance structures with a double-headed arrow to signify that the only difference between the Lewis structures is the distribution of electrons.

In the instantaneous structure of ozone, the formal (-) charge is shared between the two terminal oxygen atoms and therefore each one has a formal charge of -1/2.  The O-O bonds are the average of a single and a double bond, i.e., each O-O bond order is 1.5.
[[File:ozone avg structure.jpg|150px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Similarly, the nitrate anion has three resonance structures, and experimentally (by X-ray crystallography of nitrate salts) we find that all the N-O bonds in the ion are the same.  In this case, in the averaged structure, each O atom has a formal charge of -2/3 and the N-O bond order is 4/3 (=1.33...).


[[File:Nitrate ion resonance structures.png|300px|left]] = [[File:Nitrate-ion-resonance-hybrid-2D.png|119x119px]]
&lt;br/&gt;
&lt;br/&gt;
'''Inequivalent resonance structures'''&lt;br&gt;
The rules of resonance also apply to inequivalent structures, which in general will have different energies from each other.  In this case the structure of the molecule represents a weighted average of the low energy structures.  A good example is the cyanate ion, OCN&lt;sup&gt;-&lt;/sup&gt;. We can write three inequivalent octet structures for the molecule:

:&lt;math chem&gt;\ce{~^{-}O-C\equiv N  &lt;-&gt;  O=C=N^- &lt;-&gt;  ^+  O\equiv C-N^{2-}}&lt;/math&gt;

The first two are reasonable resonance structures, although we suspect the one on the left is the best because it puts the negative formal charge on the most electronegative atom.  The last one is clearly a bad resonance structure, because the formal charges are high and there is a positive charge on the oxygen atom.  The real structure is thus a weighted average of the first two.&lt;br&gt;
&lt;br /&gt;

'''No-bond resonance'''&lt;br&gt;
An interesting and useful kind of inequivalent resonance structure is one in which there is a bond order of ''zero'' between two of the atoms.  This concept of '''no-bond resonance''' is important in understanding the bonding in many halogen- and hydrogen-containing compounds. The idea is illustrated below for the generic molecule X-Y-Z, where Z might be an electronegative halogen atom such as F.  By moving the bonding electrons from the Y-Z bond onto the Z atom, and moving a lone pair from X into the X-Y bond, we generate the resonance structure shown on the right in which all atoms remain octet, but there is no bond between Y and Z.&lt;br&gt;
&lt;br /&gt;

[[File:no bond resonance.jpg|300px|left]]
&lt;br /&gt;
&lt;br /&gt;


It is important to recognize in this example that the no-bond form is only one resonance structure, and therefore the Z atom is still bound to Y.  If the two resonance structures in this example have the same energy, we would expect the X-Y bond order to be 1.5 and the Y-Z bond order to be 0.5.  Therefore the Y-Z bond should be longer than it is in a compound where the bond order is one, and it should be relatively easy to break the Y-Z bond.

Some molecular examples of no-bond resonance are shown below.  In the molecule ONF&lt;sub&gt;3&lt;/sub&gt;, the N-F bond is unusually long relative to the N-F bond in NF&lt;sub&gt;3&lt;/sub&gt;, in which the bond order is 1.  This can be explained by the no-bond resonance forms shown on the right.  Similarly, in the Lewis acid-base adduct formed by combining BH&lt;sub&gt;3&lt;/sub&gt; with CO, we can explain the long B-H bonds using no-bond resonance forms that place a partial positive charge on the H atoms.

[[File:NF no bond resonance.jpg|450px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

No-bond resonance is often used to provide an octet bonding picture for so-called '''[[w:Hypervalent_molecule|hypervalent compounds]]''', which are compounds that appear to have more than 8 valence electrons in the bonding shell of the central atom.  For example, we can consider two different valence bond structures for the triiodide ion, I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, which is formed by reaction of I&lt;sup&gt;-&lt;/sup&gt; with I&lt;sub&gt;2&lt;/sub&gt; in water:

[[File:hypervalent triiodide.jpg|370px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;


[[File:Blue Solution.jpg|200px|right|thumb|The deep blue color of starch-iodine solutions results from the complexation of linear polyiodide ions (I&lt;sub&gt;n&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;) by the starch (amylose) left-handed helix. The interior of the helix is hydrophobic.  In electron donor solvents such as ethanol and water, I&lt;sub&gt;2&lt;/sub&gt; and salts of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; have a brown color, the result of a charge transfer interaction between the solvent and solute.&lt;ref&gt;W. Saenger, &quot;The structure of the blue starch-iodine complex,&quot; Naturwissenschaften 71, 31-36 (1984).&lt;/ref&gt;&lt;ref&gt;R. D. Hancock and B. J. Tarbet, &quot;The other double helix - the fascinating chemistry of starch,&quot; J. Chem. Ed. 77, 988-992 (2000).&lt;/ref&gt;]]In this structure, the central iodine atom has 10 electrons in its valence shell, in violation of the octet rule.  [[w:Raman_spectroscopy|Raman spectra]] of the triiodide ion show that the I-I bond is weaker than the I-I single bond in I&lt;sub&gt;2&lt;/sub&gt;, suggesting that this picture is not an accurate description of the bonding.  A better representation of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; can be obtained with no-bond resonance structures, as shown below.  We will see that this picture is consistent with the MO description of I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; in Chapter 2:

[[File:octet triiodide.jpg|350px|left]][[File:IodineStarch left en.svg|200px|right]]

&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;br /&gt;


We can draw a similar picture for the XeF&lt;sub&gt;2&lt;/sub&gt; molecule, which has the same number of valence electrons as I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.  This picture is consistent with XPS data, which show a partial negative charge on the F atoms, as well as vibrational spectra, which show that the Xe-F bond is weaker in XeF&lt;sub&gt;2&lt;/sub&gt; than it is in the singly-bonded cation Xe-F&lt;sup&gt;+&lt;/sup&gt;.


[[File:octet XeF2.jpg|170px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Other well known examples of hypervalent compounds are PF&lt;sub&gt;5&lt;/sub&gt;, P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, and SF&lt;sub&gt;6&lt;/sub&gt;, as well as oxyacids such as H&lt;sub&gt;2&lt;/sub&gt;SO&lt;sub&gt;4&lt;/sub&gt; and HClO&lt;sub&gt;4&lt;/sub&gt;.  The hypervalent structure is often drawn for these molecules, with the explanation that d-orbitals on the central atom contribute to the bonding in dsp&lt;sup&gt;3&lt;/sup&gt; and d&lt;sup&gt;2&lt;/sup&gt;sp&lt;sup&gt;3&lt;/sup&gt; hybrids for 5- and 6-coordinate molecules, respectively.  However, realistic molecular orbital calculations show that the phosphorus and sulfur 3d orbitals are too high in energy to contribute significantly to bonding in PF&lt;sub&gt;5&lt;/sub&gt; and SF&lt;sub&gt;6&lt;/sub&gt;. For these molecules, we can use no-bond resonance to make reasonable octet structures that predict polar bonds between the central atom and F.  [[File:sf6 bonding.jpg|380px|left]][[File:Sulfur-hexafluoride-from-xtal-3D-SF.png|right|200px|thumb|Space-filling model of sulfur hexafluoride.  [[w:Sulfur_hexafluoride|SF&lt;sub&gt;6&lt;/sub&gt;]] is surprisingly unreactive with water, relative to other compounds that contain S-F bonds. The tight packing of F atoms around S prevents nucleophilic attack by water.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

In other cases, such as P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, the octet structure is unreasonable because it suggests a polar bond between P and C, with a partial negative charge on C.  Further, in the case of oxyacids such as H&lt;sub&gt;2&lt;/sub&gt;SO&lt;sub&gt;4&lt;/sub&gt; and HClO&lt;sub&gt;4&lt;/sub&gt;, X-ray crystallographic data establish that the S-O and Cl-O bonds are shorter for the oxygen atoms not bonded to hydrogen, which is more consistent with the hypervalent picture:
&lt;br&gt;&lt;br&gt;
[[File:octet&amp;hypervalent H2SO4.jpg|200px|left]][[File:Sulfuric-acid-2D-dimensions.svg|130px]]
&lt;br&gt;


The question of whether hypervalency and the octet rule are really useful descriptions of the bonding in these compounds has been considered in a number of computational studies, which have used increasingly accurate quantum mechanical calculations to determine the number of electrons associated with the central atom.  In a 2002 study, Gillespie and Silvi&lt;ref&gt;R. J. Gillespie and B. Silvi, &quot;The octet rule and hypervalence: two misunderstood concepts,&quot; Coord. Chem. Rev. 233-234, 53-62 (2002).&lt;/ref&gt; found that the population of the valence shell is greater than eight for compounds with electropositive ligands, such as P(CH&lt;sub&gt;3&lt;/sub&gt;)&lt;sub&gt;5&lt;/sub&gt;, and less than eight for compounds such as PF&lt;sub&gt;5&lt;/sub&gt;.  They concluded that these valence electron shell populations depend primarily on the coordination numbers and electronegativities of the central atoms and their ligands, and that there is no fundamental difference between the bonding in hypervalent and non-hypervalent (Lewis octet) molecules.  This reminds us that the octet rule is not a law of nature, but rather an empirical rule that is useful within certain limits.&lt;ref&gt;R. Crabtree, &quot;Hypervalency, secondary bonding and hydrogen
bonding: siblings under the skin,&quot; Chem. Soc. Rev.,
46, 1720-1729 (2017). DOI: 10.1039/c6cs00688d&lt;/ref&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:A man breathing in nitrous oxide (laughing gas) and a man ex Wellcome L0023721.jpg|right|300px|thumb|Nitrous oxide (N&lt;sub&gt;2&lt;/sub&gt;O), or laughing gas, is isoelectronic with CO&lt;sub&gt;2&lt;/sub&gt;.  The two molecules have the same shape (linear) and similar physical properties.  CO&lt;sub&gt;2&lt;/sub&gt; sublimes at -78 °C, whereas N&lt;sub&gt;2&lt;/sub&gt;O melts at -91 °C and boils at -88 °C.]]
'''The isoelectronic principle'''&lt;br /&gt;
In calculating the octet structures of molecules using the N-V method, we needed to know only the number of atoms and the number of electrons, not the identities of the atoms themselves.  This means that we will get the same answer (and the same set of octet and resonance structures) for ''any'' molecule or ion that contains (a) the same number of non-hydrogen atoms, and (b) the same total number of valence electrons.  Such molecules are said to be ''isoelectronic.''  This is a powerful conclusion because, once we have determined the electronic structure of one molecule, we can write down the same solution for ''all other molecules'' that are isoelectronic.  For example, we noted above that I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; and XeF&lt;sub&gt;2&lt;/sub&gt;, which both have 22 valence electrons, have the same valence bond structure.  We can further expect that isoelectronic molecules will have the same shapes and, very often, similar physical properties.  

The four molecules and ions below all contain three non-hydrogen atoms and 16 valence electrons.  All of them are linear molecules with two double bonds.  The four molecules and ions shown below them all contain four non-hydrogen atoms and 24 valence electrons.  These four have a trigonal planar shape.  While BF&lt;sub&gt;3&lt;/sub&gt; is a member of this isoelectronic series, we do not write it in the resonance form that contains a B=F double bond, because that would put a positive formal charge on F.
[[File:isoelectronic molecules.jpg|320px|left]]  &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;      [[File:24e molecules.jpg|left|400px]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

Similarly we can show that CH&lt;sub&gt;4&lt;/sub&gt;, NH&lt;sub&gt;3&lt;/sub&gt;, NH&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;, H&lt;sub&gt;2&lt;/sub&gt;O, H&lt;sub&gt;3&lt;/sub&gt;O&lt;sup&gt;+&lt;/sup&gt;, HF, F&lt;sup&gt;-&lt;/sup&gt;, and OH&lt;sup&gt;-&lt;/sup&gt; are all isoelectronic with one non-H atom and eight valence electrons.  In the next section we will see that this gives rise to nearly identical electronic shapes for these molecules.
[[File:Gallium-arsenide-unit-cell-3D-balls.png|200px|thumb|right|Fig. 1.1.2. The tetrahedral bonding in crystals of GaAs, CdTe, CuIn&lt;sub&gt;1-x&lt;/sub&gt;Ga&lt;sub&gt;x&lt;/sub&gt;Se&lt;sub&gt;2&lt;/sub&gt; and other semiconductors is similar to that in isoelectronic Si and Ge.]]
&lt;br&gt;

'''Isoelectronic solids.'''  The isoelectronic principle works not just for molecules but for extended solids as well.  One technologically important set of isoelectronic solids are the p-block semiconductors.  The group 14 element Si is the most widely used semiconductor for electronics, but, as we will discuss later, it is not a good light emitter.  Light-emitting diodes (LEDs), which are used in lasers, high efficiency lighting, and display technologies, are made from compounds that are isoelectronic with Si and Ge, especially GaAs, GaP, AlAs, and GaN (all contain four valence electrons per atom).  CdTe and CuIn&lt;sub&gt;1-x&lt;/sub&gt;Ga&lt;sub&gt;x&lt;/sub&gt;Se&lt;sub&gt;2&lt;/sub&gt; (CIGS) are promising solar cell materials that also have the same number of valence electrons per atom.  Like Si and Ge, these compounds have tetrahedrally bonded structures in the solid state and absorb light across most of the solar spectrum, as we will discuss in more detail in Chapters 8 and 10.


The isoelectronic principle is also a powerful tool in materials research, because it provides guidance about where to look for new materials with similar and perhaps improved properties.  For example, the discovery that 8.5% efficient thin layer solar cells could be made with the compound CsSnI&lt;sub&gt;3&lt;/sub&gt;&lt;ref&gt;I. Chung, B. Lee,  J. He,	R. P. H. Chang	 and M. G. Kanatzidis, All-solid-state dye-sensitized solar cells with high efficiency, Nature 485, 486-489 (2012). doi:10.1038/nature11067&lt;/ref&gt; stimulated the exploration of many isoelectronic ABX&lt;sub&gt;3&lt;/sub&gt; compounds with the same perovskite crystal structure. Very recently thin film solar cells based on light absorbers in this structural family (MA)PbI&lt;sub&gt;3-x&lt;/sub&gt;Cl&lt;sub&gt;x&lt;/sub&gt; and FA&lt;sub&gt;x&lt;/sub&gt;MA&lt;sub&gt;1−x&lt;/sub&gt;PbBr&lt;sub&gt;y&lt;/sub&gt;I&lt;sub&gt;3−y&lt;/sub&gt; (MA&lt;sup&gt;+&lt;/sup&gt; = methylammonium, CH&lt;sub&gt;3&lt;/sub&gt;NH&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;; FA&lt;sup&gt;+&lt;/sup&gt; = formamidinium, HC(NH&lt;sub&gt;2&lt;/sub&gt;)&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;) have been reported with efficiencies as high as 22%.&lt;ref&gt;S.D. Stranks,  G. E. Eperon, G. Grancini,  C. Menelaou,  M. J. P. Alcocer, T. Leijtens, L. M. Herz, A. Petrozza, and H. J. Snaith, Electron-Hole Diffusion Lengths Exceeding 1 Micrometer in an Organometal Trihalide Perovskite Absorber, Science 342, 341-344 (2013). DOI: 10.1126/science.1243982&lt;/ref&gt;&lt;ref&gt;G. Xing,  N. Mathews, S. Sun, S. S. Lim, Y. M. Lam, M. Grätzel, S. Mhaisalkar, and T. C. Sum, Long-Range Balanced Electron- and Hole-Transport Lengths in Organic-Inorganic CH3NH3PbI3, Science 342, 344-347 (2013). DOI: 10.1126/science.1243167 &lt;/ref&gt;&lt;ref&gt;J.-P. Correa-Baena, A. Abate, M. Saliba, W. Tress, T. J. Jacobsson, M. Grätzel, and A. Hagfeldt, The rapid evolution of highly efficient perovskite solar cells, Energy Environ. Sci., 10, 710-727 (2017). DOI: 10.1039/C6EE03397K &lt;/ref&gt;

==1.2 The shapes of molecules (VSEPR theory) and orbital hybridization ==
[[Image:Water molecule dimensions.svg|thumb|200px|Geometry of the [[w:water (molecule)|water molecule]]]]
The [[w:VSEPR_theory|Valence Shell Electron Pair Repulsion (VSEPR) theory]] is a simple and useful way to predict and rationalize the shapes of molecules.  The theory is based on the idea of minimizing the electrostatic repulsion between electron pairs, as first proposed by Sidgwick and Powell in 1940,&lt;ref&gt;N. V. Sidgwick and H. M. Powell, Proc. Roy. Soc. A176, 153 (1940),&lt;/ref&gt; then generalized by Gillespie and Nyholm in 1957,&lt;ref&gt;R. J. Gillespie and R. S. Nyholm, Quart. Rev. Chem. Soc., 11, 339 (1957).&lt;/ref&gt; and then broadly applied over the intervening 50+ years.&lt;ref&gt;R. J. Gillespie, &quot;Fifty years of the VSEPR model,&quot; Coord. Chem. Rev. 252, 1315-1327 (2008). DOI: 10.1016/j.ccr.2007.07.007&lt;/ref&gt;

To use the VSEPR model, one begins with the Lewis dot picture to determine the number of lone pairs and bonding domains around a central atom.  Because VSEPR considers all bonding domains equally (i.e., a single bond, a double bond, and a half bond all count as one electron domain), one can use either an octet or hypervalent structure, provided that the number of lone pairs (which should be the same in both) is calculated correctly.  For example, in either the hypervalent or octet structure of the I&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; ion above, there are three lone pairs on the central I atom and two bonding domains.  We then follow these steps to obtain the '''electronic geometry''':
&lt;br /&gt;
&lt;br /&gt;
*Determine the number of lone pairs on the central atom in the molecule, and add the number of bonded atoms (a.k.a. bonding domains)
*This number (the ''steric number'') defines the electronic shape of the molecule by minimizing repulsion.  For example a steric number of three gives a trigonal planar electronic shape.
*The angles between electron domains are determined primarily by the electronic geometry (e.g., 109.5° for a steric number of 4, which implies that the electronic shape is a tetrahedron)
*These angles are adjusted by the hierarchy of repulsions:  (lone pair - lone pair) &gt; (lone pair - bond) &gt; (bond - bond)
&lt;br /&gt;

The '''molecular geometry''' is deduced from the electronic geometry by considering the lone pairs to be present but invisible.  The most commonly used methods to determine molecular structure - [[w:X-ray_diffraction|X-ray diffraction]], [[w:Neutron_diffraction|neutron diffraction]], and [[w:Electron_diffraction|electron diffraction]] - have a hard time seeing lone pairs, but they can accurately determine the lengths of bonds between atoms and the bond angles.

The table below gives examples of electronic and molecular shapes for steric numbers between 2 and 9.  We are most often concerned with molecules that have steric numbers between 2 and 6.

{| class=&quot;wikitable sortable&quot;
|-
! Bonding electron pairs
! Lone pairs
! Electron domains (Steric #)
! Shape
! Ideal bond angle (example's bond angle)
! Example
! Image
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:linear molecular geometry|linear]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:carbon dioxide|CO&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Linear-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal planar molecular geometry|trigonal planar]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;120°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Boron trifluoride|BF&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Trigonal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bent molecular geometry|bent]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;120° (119°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Sulfur dioxide|SO&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Bent-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:tetrahedral molecular geometry|tetrahedral]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:methane|CH&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX4E0-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal pyramidal molecular geometry|trigonal pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5° (107°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:ammonia|NH&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bent molecular geometry|bent]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;109.5° (104.5°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:H2O|H&lt;sub&gt;2&lt;/sub&gt;O]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Bent-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:trigonal bipyramidal molecular geometry|trigonal bipyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 120°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:phosphorus pentachloride|PCl&lt;sub&gt;5&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Trigonal-bipyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:seesaw molecular geometry|seesaw]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°, 120°, 90° (173.1°, 101.6°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:sulfur tetrafluoride|SF&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Seesaw-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:T-shaped molecular geometry|T-shaped]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180° (87.5°, &lt; 180°) &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:chlorine trifluoride|ClF&lt;sub&gt;3&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:T-shaped-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;3&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:linear molecular geometry|linear]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:xenon difluoride|XeF&lt;sub&gt;2&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Linear-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:octahedral molecular geometry|octahedral]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:sulfur hexafluoride|SF&lt;sub&gt;6&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX6E0-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square pyramidal molecular geometry|square pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90° (84.8°), 180° &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:bromine pentafluoride|BrF&lt;sub&gt;5&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;4&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square planar molecular geometry|square planar]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:xenon tetrafluoride|XeF&lt;sub&gt;4&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-planar-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal bipyramidal molecular geometry|pentagonal bipyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;90°, 72°, 180°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:iodine heptafluoride|IF&lt;sub&gt;7&lt;/sub&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-bipyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;6&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;1&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal pyramidal molecular geometry|pentagonal pyramidal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;72°, 90°, 144°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;XeOF&lt;sub&gt;5&lt;/sub&gt;&lt;sup&gt;−&lt;/sup&gt;&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-pyramidal-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;5&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;2&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;7&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:pentagonal planar molecular geometry|planar pentagonal]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;72°, 144°&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Tetramethylammonium pentafluoroxenate|XeF&lt;sub&gt;5&lt;/sub&gt;&lt;sup&gt;−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Pentagonal-planar-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;8&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;8&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:square antiprismatic molecular geometry|square antiprismatic]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt; &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Nitrosonium octafluoroxenate(VI)|XeF&lt;sub&gt;8&lt;/sub&gt;&lt;sup&gt;2−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:Square-antiprismatic-3D-balls.png|50px]]&lt;/div&gt;
|-
| &lt;div style=&quot;text-align: center;&quot;&gt;9&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;0&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;9&lt;/div&gt;
|  &lt;div style=&quot;text-align: center;&quot;&gt;[[w:tricapped trigonal prismatic molecular geometry|tricapped trigonal prismatic]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt; &lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[w:Potassium_nonahydridorhenate|ReH&lt;sub&gt;9&lt;/sub&gt;&lt;sup&gt;2−&lt;/sup&gt;]]&lt;/div&gt;
| &lt;div style=&quot;text-align: center;&quot;&gt;[[Image:AX9E0-3D-balls.png|50px]]&lt;/div&gt;
|}
&lt;br /&gt;
From the Table, we see that some of the molecules shown as examples have bond angles that depart from the ideal electronic geometry.  For example, the H-N-H bond angle in ammonia is 107°, and the H-O-H angle in water is 104.5°.  We can rationalize this in terms of the last rule above.  The lone pair in ammonia repels the electrons in the N-H bonds more than the bonds repel each other.  This lone pair repulsion exerts even more steric influence in the case of water, where there are two lone pairs.  Similarly, the axial F-S-F angle in the &quot;seesaw&quot; molecule SF&lt;sub&gt;4&lt;/sub&gt; is a few degrees less than 180° because of repulsion by the lone pair in the molecule.

'''Geometrical isomers'''&lt;br /&gt;

For some molecules in the Table, we note that there is more than one possible shape that would satisfy the VSEPR rules.  For example, the XeF&lt;sub&gt;2&lt;/sub&gt; molecule has a steric number of five and a trigonal bipyramidal geometry.  There are three possible stereoisomers:  one in which the F atoms occupy axial sites, resulting in linear molecule, one in which the F atoms occupy one equatorial and one axial site (resulting in a 90° bond angle), and one in which the F atoms are both on equatorial sites, with a F-Xe-F bond angle of 120°.

[[File:XeF2 geometry.jpg|130px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

The observed geometry of XeF&lt;sub&gt;2&lt;/sub&gt; is linear, which can be rationalized by considering the orbitals that are used to make bonds (or lone pairs) in the axial and equatorial positions.  There are four available orbitals, s, p&lt;sub&gt;x&lt;/sub&gt;, p&lt;sub&gt;y&lt;/sub&gt;, and p&lt;sub&gt;z&lt;/sub&gt;.  If we choose the z-axis as the axial direction, we can see that the p&lt;sub&gt;x&lt;/sub&gt; and p&lt;sub&gt;y&lt;/sub&gt; orbitals lie in the equatorial plane.  We assume that the spherical s orbital is shared equally by the five electron domains in the molecule, the two axial bonds share the p&lt;sub&gt;z&lt;/sub&gt; orbital, and the three equatorial bonds share the p&lt;sub&gt;x&lt;/sub&gt; and p&lt;sub&gt;y&lt;/sub&gt; orbitals.  We can then calculate the bond orders to axial and equatorial F atoms as follows:
&lt;br /&gt;

axial:  1/5 s + 1/2 p&lt;sub&gt;z&lt;/sub&gt; = 0.7 bond (formal charge = -0.3)&lt;br /&gt;
equatorial: 1/5 s + 1/3 p&lt;sub&gt;x&lt;/sub&gt; + 1/3 p&lt;sub&gt;y&lt;/sub&gt; = 0.867 bond (formal charge = -0.133)
&lt;br /&gt;

Because fluorine is more electronegative than a lone pair, it prefers the axial site where it will have more negative formal charge.  In general, by this reasoning, lone pairs and electropositive ligands such as CH&lt;sub&gt;3&lt;/sub&gt; will always prefer the equatorial sites in the trigonal bipyramidal geometry.  Electronegative ligands such as F will always go to the axial sites.

In the case of the BrF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; anion, which is isoelectronic with XeF&lt;sub&gt;4&lt;/sub&gt; in the Table, the electronic geometry is octahedral and there are two possible isomers in which the two lone pairs are ''cis'' or ''trans'' to each other.  In this case, lone pair - lone pair repulsion dominates and we obtain the ''trans'' arrangement of lone pairs, giving a square planar molecular geometry.
&lt;br /&gt;
[[File:BrF4-VSEPR.jpg|350px|left]]
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;

'''Orbital hybridization'''
&lt;br /&gt;
The observation of molecules in the various electronic shapes shown above is, at first blush, in conflict with our picture of [[w:Atomic_orbitals|atomic orbitals]].  For an atom such as oxygen, we know that the 2s orbital is spherical, and that the 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals are dumbell-shaped and point along the Cartesian axes.  The water molecule contains two hydrogen atoms bound to oxygen not at a 90° angle, but at an angle of 104.5°.  Given the relative orientations of the atomic orbitals, how do we arrive at angles between electron domains of 104.5°, 120°, and so on? To understand this we will need to learn a little bit about the quantum mechanics of electrons in atoms and molecules.&lt;br&gt;
&lt;br&gt;

The atomic orbitals ψ represent solutions to the [[w:Schrödinger equation|'''Schrödinger wave equation''']], 


:&lt;math&gt; E \psi = \hat{H}\psi&lt;/math&gt;


Here E is the energy of an electron in the orbital, and &lt;math&gt; \hat{H}&lt;/math&gt; is the Hamiltonian operator.

By analogy with classical mechanics, the Hamiltonian is commonly expressed as the sum of [[w:Hermitian operators|operators]] corresponding to the [[w:kinetic energy|kinetic]] and [[w:potential energy|potential]] energies of a system in the form


:&lt;math&gt; \hat{H} = \hat{T} + \hat{V}, &lt;/math&gt;


where  &lt;math&gt; \hat{V} = V(\mathbf{r},t) &lt;/math&gt; is the potential energy, and 


:&lt;math&gt;\hat{T} = \frac{\mathbf{\hat{p}}\cdot\mathbf{\hat{p}}}{2m} = \frac{\hat{p}^2}{2m} = -\frac{\hbar^2}{2m}\nabla^2,&lt;/math&gt;


is the kinetic energy operator in which ''m'' is the mass of the particle and the momentum operator is:


:&lt;math&gt; \hat{p} = -i\hbar\nabla ,&lt;/math&gt; where &lt;math&gt;\nabla = {\partial \over \partial x} +  {\partial \over \partial y} +  {\partial \over \partial z}&lt;/math&gt;


Here &lt;math&gt;\hbar&lt;/math&gt; is h/2π, where h is Planck's constant, and the Laplacian operator ∇&lt;sup&gt;2&lt;/sup&gt; is:


:&lt;math&gt;\nabla^2 = \frac{\partial^2}{{\partial x}^2} + \frac{\partial^2}{{\partial y}^2} + \frac{\partial^2}{{\partial z}^2}&lt;/math&gt;


Although this is not the technical definition of the [[w:Hamiltonian mechanics|Hamiltonian in classical mechanics]], it is the form it most commonly takes in quantum mechanics. Combining these together yields the familiar form used in the Schrödinger equation:


:&lt;math&gt;\begin{align}\hat{H} &amp; = \hat{T} + \hat{V} \ = \frac{\mathbf{\hat{p}}\cdot\mathbf{\hat{p}}}{2m}+ V(\mathbf{r},t) \ = -\frac{\hbar^2}{2m}\nabla^2+ V(\mathbf{r},t)\end{align}&lt;/math&gt;


For hydrogen-like (one-electron) atoms, the Schrödinger equation can be written as:&lt;br /&gt;


:&lt;math&gt; E \psi = -\frac{\hbar^2}{2\mu}\nabla^2\psi - \frac{Ze^2}{4\pi\epsilon_0 r}\psi &lt;/math&gt;


where '''Z''' is the nuclear charge, ''e'' is the electron charge, and '''r''' is the position of the electron. The radial potential term on the right side of the equation is due to the [[w:Coulomb's law|Coulomb interaction]], i.e., the electrostatic attraction between the nucleus and the electron, in which ''ε''&lt;sub&gt;0&lt;/sub&gt; is the [[w:electric constant|dielectric constant]] (permittivity of free space) and


:&lt;math&gt; \mu = \frac{m_em_n}{m_e+m_n} &lt;/math&gt;


is the 2-body [[w:reduced mass|reduced mass]] of the [[w:Nucleus (atomic structure)|nucleus]] of mass ''m''&lt;sub&gt;n&lt;/sub&gt; and the electron of mass ''m''&lt;sub&gt;e&lt;/sub&gt;.  To a good approximation, µ ≈ ''m''&lt;sub&gt;e&lt;/sub&gt;.
[[File:Erwin_Schrodinger2.jpg|right|thumb|150px|Erwin Schrödinger as a young scientist]]


This is the equation that [[w:Erwin_Schrödinger|Erwin Schrödinger]] famously derived in 1926 to solve for the energies and shapes of the s, p, d, and f [[w:Atomic_orbital|atomic orbitals]] in hydrogen-like atoms.  It was a huge conceptual leap for both physics and chemistry because it not only explained the quantized energy levels of the hydrogen atom, but also provided the theoretical basis for the octet rule and the arrangement of elements in the periodic table.


The Schrödinger equation can be used to describe chemical systems that are more complicated than the hydrogen atom (e.g., multi-electron atoms, molecules, infinite crystals, and the dynamics of those systems) if we substitute the appropriate potential energy function V(r,t) into the Hamiltonian.  The math becomes more complicated and the equation must be solved numerically in those cases, so for our purposes we will stick with the simplest case of time-invariant, one-electron, hydrogen-like atoms.
&lt;br&gt;&lt;br&gt;
[[File:Neon orbitals rotated.png|right|thumb|170px|The shapes of the first five [[w:Atomic_orbitals|atomic orbitals]]: 1s, 2s, 2p&lt;sub&gt;''x''&lt;/sub&gt;, 2p&lt;sub&gt;''y''&lt;/sub&gt;, and 2p&lt;sub&gt;''z''&lt;/sub&gt;. The colors denote the sign of the wave function.]]
Without going into too much detail about the Schrödinger equation, we can point out some of its most important properties:&lt;br&gt;
:&lt;math&gt; E \psi = -\frac{\hbar^2}{2\mu}\nabla^2\psi - \frac{Ze^2}{4\pi\epsilon_0 r}\psi &lt;/math&gt;
*The equation derives from the fact that the total energy (E) is the sum of the kinetic energy (KE) and the potential energy (PE).  These three quantities are represented mathematically as [[w:Operator_(physics)|'''operators''']] in the equation.
*On the left side of the equation, the total energy operator (E) is a scalar that is multiplied by the [[w:Wave_function|wavefunction]] ψ. ψ is a function of the spatial coordinates (x,y,z) and is related to the probability that the electron is at that point in space.
*The first term on the right side of the equation represents the kinetic energy (KE).  The kinetic energy operator is proportional to ∇&lt;sup&gt;2&lt;/sup&gt; (the [[w:Laplacian|Laplacian operator]]) which takes the second derivative (with respect to three spatial coordinates) of ψ.  Thus, the Schrödinger equation is a '''differential equation'''.
*The second term on the right side of the equation represents the Coulomb potential (PE), i.e. the attractive energy between the positively charged nucleus and the negatively charged electron.
*The solutions to the Schrödinger equation are a set of '''energies''' E (which are scalar quantities) and [[w:Wave_function|'''wavefunctions''']] (a.k.a. '''[[w:Atomic_orbitals|atomic orbitals]]''') ψ, which are functions of the spatial coordinates.  You will sometimes see the energies referred to as [[w:Eigenvalue|''eigenvalues'']] and the orbitals as [[w:eigenfunction|''eigenfunctions'']], because mathematically the Schrödinger equation is an eigenfunction-eigenvalue equation.  Although ψ is a function of the coordinates, E is not.  So an electron in a 2p&lt;sub&gt;z&lt;/sub&gt; orbital has the same total energy E (= PE + KE) no matter where it is in space. 
*These E values and their associated [[w:Wave_function|wavefunctions]] ψ are catalogued according to their '''[[w:Quantum_number|quantum numbers]]''' ''n,'' ''l,'' and ''m&lt;sub&gt;l&lt;/sub&gt;.''  That is, there are many solutions to the differential equation, and each solution (ψ(xyz) and E) has a unique set of quantum numbers.  Some sets of orbitals are '''degenerate''', meaning that they have the same energy (e.g., 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt;).
*The solutions ψ(xyz) to the Schrödinger equation (e.g., the 1s, 2s, 2p&lt;sub&gt;x&lt;/sub&gt;, 2p&lt;sub&gt;y&lt;/sub&gt;, and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals) represent '''probability amplitudes''' for finding the electron at a particular point (x,y,z) in space.  A probability amplitude can have either '''+ or - sign'''.  We typically represent the different signs by shading or by + and - signs on the two lobes of a 2p orbital.  
*The square of the probability amplitude, ψ&lt;sup&gt;2&lt;/sup&gt;, is always a positive number and represents the '''probability''' of finding the electron at a point x,y,z in space.  Because the total probability of finding the electron somewhere is 1, the wavefunction must be '''normalized''' so that the integral of ψ&lt;sup&gt;2&lt;/sup&gt; over the spatial coordinates (from -∞ to +∞) is 1.
*The solutions to the Schrödinger equation are '''orthogonal''', meaning that the product of any two (integrated over all space) is zero.  For example the product of the 2s and 2p&lt;sub&gt;x&lt;/sub&gt; orbitals, integrated over the spatial coordinates from -∞ to +∞, is zero.
&lt;br&gt;
Orbital hybridization involves making ''linear combinations'' of the [[w:Atomic_orbitals|atomic orbitals]] that are solutions to the Schrödinger equation.  Mathematically, this is justified by recognizing that the Schrödinger equation is a ''linear'' differential equation.  As such, any sum of solutions to the Schrödinger equation is also a valid solution.  However, we still impose the constraint that our hybrid orbitals must be '''orthogonal''' and '''normalized'''.
&lt;br /&gt;

'''Rules for orbital hybridization:'''

* Add and subtract [[w:Atomic_orbitals|atomic orbitals]] to get hybrid orbitals.
* We get the same number of orbitals out as we put in.
* The energy of a hybrid orbital is the weighted average of the [[w:Atomic_orbitals|atomic orbitals]] that make it up.
* The coefficients are determined by the constraints that the hybrid orbitals must be orthogonal and normalized.


For '''sp hybridization''', as in the BeF&lt;sub&gt;2&lt;/sub&gt; or CO&lt;sub&gt;2&lt;/sub&gt; molecule, we make two linear combinations of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals (assigning z as the axis of the Be-F bond):

:&lt;math&gt;\psi_1 = \frac{1}{\sqrt 2}(2s) + \frac{1}{\sqrt 2}(2p_z)&lt;/math&gt;&lt;br&gt;
:&lt;math&gt;\psi_2 = \frac{1}{\sqrt 2}(2s) - \frac{1}{\sqrt 2}(2p_z)&lt;/math&gt;&lt;br&gt;

Here we have simply added and subtracted the 2s and 2pz orbitals; we leave it as an exercise for the interested student to show that both orbitals are normalized (i.e., {{Unicode|∫}}ψ&lt;sub&gt;1&lt;/sub&gt;&lt;sup&gt;2&lt;/sup&gt;dτ = {{Unicode|∫}}ψ&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;2&lt;/sup&gt;dτ = 1) and orthogonal (i.e., {{Unicode|∫}}ψ&lt;sub&gt;1&lt;/sub&gt;ψ&lt;sub&gt;2&lt;/sub&gt;dτ = 0).

What this means physically is explained in the figure below.  By combining the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals we have created two new orbitals with large lobes (high electron probability) pointing along the z-axis.  These two orbitals are degenerate and have an energy that is halfway between the energy of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; orbitals.
[[File:sp hybridization.jpg|thumb|500px|center|Linear combinations of the 2s and 2p&lt;sub&gt;z&lt;/sub&gt; [[w:Atomic_orbitals|atomic orbitals]] make two 2sp&lt;sub&gt;z&lt;/sub&gt; hybrids.  The 2p&lt;sub&gt;x&lt;/sub&gt; and 2p&lt;sub&gt;y&lt;/sub&gt; orbitals are unchanged.]]
For an isolated Be atom, which has two valence electrons, the lowest energy state would have two electrons spin-paired in the 2s orbital.  However, these electrons would not be available for bonding.  By '''promoting''' these electrons to the degenerate 2sp&lt;sub&gt;z&lt;/sub&gt; hybrid orbitals, they become unpaired and are prepared for bonding to the F atoms in BeF&lt;sub&gt;2&lt;/sub&gt;.  This will occur if the '''bonding energy''' (in the promoted state) exceeds the promotion energy.  The '''overall bonding energy''', i.e., the energy released by combining a Be atom in its ground state with two F atoms, is the difference between the bonding and promotion energies.

We can similarly construct '''sp&lt;sup&gt;2&lt;/sup&gt; hybrids''' (e.g., for the BF&lt;sub&gt;3&lt;/sub&gt; molecule or the NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; anion) from one 2s and two 2p [[w:Atomic_orbitals|atomic orbitals]].  Taking the plane of the molecule as the xy plane, we obtain three hybrid orbitals at 120° to each other.  The three hybrids are:
[[File:sp2hybrids.jpg|200px|right]]&lt;br /&gt;

:&lt;math&gt;\psi_1 = \frac{1}{\sqrt 3}(2s) + \frac{\sqrt 2}{\sqrt 3}(2p_x)&lt;/math&gt;
:&lt;math&gt;\psi_2 = \frac{1}{\sqrt 3}(2s) - \frac{1}{\sqrt 6}(2p_x) + \frac{1}{\sqrt 2}(2p_y)&lt;/math&gt;
:&lt;math&gt;\psi_3 = \frac{1}{\sqrt 3}(2s) - \frac{1}{\sqrt 6}(2p_x) - \frac{1}{\sqrt 2}(2p_y)&lt;/math&gt;
&lt;br /&gt;

These orbitals are again degenerate and their energy is the weighted average of the energies of the 2s, 2p&lt;sub&gt;x&lt;/sub&gt;, and 2p&lt;sub&gt;y&lt;/sub&gt; [[w:Atomic_orbitals|atomic orbitals]].

Finally, to make a sp&lt;sup&gt;3&lt;/sup&gt; hybrid, as in CH&lt;sub&gt;4&lt;/sub&gt;, H&lt;sub&gt;2&lt;/sub&gt;O, etc., we combine all four [[w:Atomic_orbitals|atomic orbitals]] to make four degenerate hybrids:
[[File:Ch4 hybridization.svg|130px|right]]&lt;br /&gt;
 [[File:CH4-structure.svg|130px|right]]&lt;br /&gt;

:&lt;math&gt;\psi_1 = \frac{1}{2}(2s + 2p_x + 2p_y + 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_2 = \frac{1}{2}(2s - 2p_x - 2p_y + 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_3 = \frac{1}{2}(2s + 2p_x - 2p_y - 2p_z)&lt;/math&gt;&lt;br&gt;

:&lt;math&gt;\psi_4 = \frac{1}{2}(2s - 2p_x + 2p_y - 2p_z)&lt;/math&gt;&lt;br&gt;


The lobes of the '''sp&lt;sup&gt;3&lt;/sup&gt; hybrid''' orbitals point towards the vertices of a tetrahedron (or alternate corners of a cube), consistent with the tetrahedral bond angle in CH&lt;sub&gt;4&lt;/sub&gt; and the nearly tetrahedral angles in NH&lt;sub&gt;3&lt;/sub&gt; and H&lt;sub&gt;2&lt;/sub&gt;O. Similarly, we can show that we can construct the trigonal bipyramidal electronic shape by making sp and sp&lt;sup&gt;2&lt;/sup&gt; hybrids, and the octahedral geometry from three sets of sp hybrids. The picture that emerges from this is that the [[w:Atomic_orbitals|atomic orbitals]] can hybridize as required by the shape that best minimizes electron pair repulsions.
[[File:Hydrogen-sulfide-2D-dimensions.svg|130px|right]]
Interestingly however, the bond angles in PH&lt;sub&gt;3&lt;/sub&gt;, H&lt;sub&gt;2&lt;/sub&gt;S and H&lt;sub&gt;2&lt;/sub&gt;Se are close to 90°, suggesting that P, S, and Se primarily use their p-orbitals in bonding to H in these molecules.  This is consistent with the fact that the energy difference between s and p orbitals stays roughly constant going down the periodic table, but the bond energy ''decreases'' as the valence electrons get farther away from the nucleus.  In compounds of elements in the 3rd, 4th, and 5th rows of the periodic table, there thus is a ''decreasing tendency to use s-p orbital hybrids in bonding''.  For these heavier elements, the bonding energy is not enough to offset the energy needed to promote the s electrons to s-p hybrid orbitals.

==1.3 Bond polarity and bond strength==
[[Image:Water-elpot-transparent-3D-balls.png|thumb|right|250px|Fig. 1.3.1. A [[w:water molecule|water molecule]], a commonly used example of polarity. The two charges are present with a negative charge in the middle (red), and a positive charge at the ends (blue).]]
[[w:Linus Pauling|Linus Pauling]] introduced the concept of [[w:electronegativity|electronegativity]] 1932 in order to explain the extra stability of molecules with polar bonds. &lt;ref name=&quot;paulingJACS&quot;&gt;{{cite journal |author= Pauling, L.
 |authorlink=Linus Pauling
 |year= 1932
 |journal= [[w:Journal of the American Chemical Society|J. Am. Chem. Soc.]]
 |volume= 54
 |issue= 9
 |pages= 3570–3582
 |title= The Nature of the Chemical Bond. IV. The Energy of Single Bonds and the Relative Electronegativity of Atoms
 |doi= 10.1021/ja01348a011}}&lt;/ref&gt;  The electronegativity of an atom, represented by the Greek letter ''χ'', can be defined as the tendency of an atom to draw electrons to itself in a chemical bond.  On the Pauling scale, the electronegativity difference between two atoms A and B was defined in terms of the [[w:Bond dissociation energy|dissociation energies]] ''E''&lt;sub&gt;d&lt;/sub&gt; of the  A-A, B-B, and A-B bonds:&lt;br&gt;&lt;br&gt;

::&lt;small&gt;&lt;math&gt;\chi_{\rm A} - \chi_{\rm B} = \sqrt{E_{\rm d}({\rm AB}) - [E_{\rm d}({\rm AA}) + E_{\rm d}({\rm BB})]/2}&lt;/math&gt;&lt;/small&gt;&lt;br&gt;&lt;br&gt;
where the energies are expressed in electron volts.

This definition, while directly relevant to the strength of chemical bonds, requires thermochemical input data from many compounds, some of which were not available at the time.  Mulliken&lt;ref&gt;{{cite journal
|author = Mulliken, R. S.
|year =1934
|journal = [[w:Journal of Chemical Physics|J. Chem. Phys.]]
|volume = 2
|title = A New Electroaffinity Scale; Together with Data on Valence States and on Valence Ionization Potentials and Electron Affinities
|doi = 10.1063/1.1749394
|pages = 782–793
|issue = 11|bibcode = 1934JChPh...2..782M }}&lt;/ref&gt;&lt;ref&gt;{{cite journal
|author = Mulliken, R. S.
|year =1935
|title = Electronic Structures of Molecules XI. Electroaffinity, Molecular Orbitals and Dipole Moments
|journal = [[w:Journal of Chemical Physics|J. Chem. Phys.]]
|volume = 3
|doi = 10.1063/1.1749731
|pages = 573–585
|issue = 9|bibcode = 1935JChPh...3..573M }}&lt;/ref&gt; and later Pearson&lt;ref&gt;{{cite journal|author = Pearson, R. G.
|title = Absolute electronegativity and absolute hardness of Lewis acids and bases
|year = 1985
|journal = [[w:Journal of the American Chemical Society|J. Am. Chem. Soc.]]
|volume = 107
|pages = 6801
|doi = 10.1021/ja00310a009|issue = 24}}&lt;/ref&gt; developed a scale of electronegativities based on the average of the electron affinity and ionization energy of the free A and B atoms, which they correlated with thermochemical data and the Pauling scale.  

On the Pauling scale, the least electronegative elements are the alkali metals (χ = 0.7-1.0) and the most electronegative are oxygen (3.5) and fluorine (4.0) at the upper right of the periodic table.  Carbon and hydrogen have intermediate electronegativities (2.6 and 2.2 on the Pauling scale, respectively).  The general trend (see table below) is that electronegativities increase going up and to the right in the periodic table.  There are some interesting exceptions to this behavior, most notably two islands of high electronegativity at the bottom of the transition series, peaking at tungsten (χ = 2.4) and gold (χ = 2.5).  The first of these can be explained by the very high metal-metal bond energy of elements such as Mo and W, which can use all six of their valence electrons in bonding, as we will discuss in Chapter 6.  The second however occurs with more weakly bonded noble metals such as Pt and Au, and is responsible for  their low position in the [[w:Reactivity_series|activity series]],&lt;ref&gt;B. Hammer and J. K. Norskov, &quot;Why gold is the noblest of all the metals,&quot; ''Nature'' '''376,''' 238 - 240 (2002. doi:10.1038/376238a0&lt;/ref&gt; as well as their extraordinary properties as catalysts.&lt;br&gt;&lt;br&gt;
[[image:periodic table Pauling electronegatvity.jpg|500px|left]]

[[w:Electronegativities_of_the_elements_(data_page)#Electronegativity_.28Pauling_scale.29|Table of Pauling electronegativities]]

The polarity of bonds is determined by electronegativity differences.  As a guideline we define bonds as:

* '''ionic''' if Δχ &gt; 2.0
* '''polar''' if 2.0 &gt; Δχ &gt; 0.5
* '''nonpolar''' if 0.5 &gt; Δχ

The polarity of bonds helps us understand [[w:Intermolecular_force|non-covalent forces]] between molecules, such as [[w:Hydrogen_bonding|hydrogen bonding]] and dipole-dipole interactions. It also helps us interpret the reactivity of molecules.  For example, the Si-H bond (χ&lt;sub&gt;Si&lt;/sub&gt; = 1.8, χ&lt;sub&gt;H&lt;/sub&gt; = 2.1) is more hydride-like than the C-H bond (χ&lt;sub&gt;C&lt;/sub&gt; = 2.5, χ&lt;sub&gt;H&lt;/sub&gt; = 2.1).  Therefore silanes react with acids to make H&lt;sub&gt;2&lt;/sub&gt;, whereas phosphines (χ&lt;sub&gt;P&lt;/sub&gt; = 2.1) and hydrocarbons do not.  Similarly, electrophilic substitution reactions occur more readily on Si-H and P-H compounds than they do on C-H compounds.

There is also a correlation between the strength of a chemical bond and the bond length, longer bonds being weaker because of weaker orbital overlap.  Pauling introduced an empirical formula relating bond length to bond strength.  For a given pair of atoms (for example, two carbon atoms):&lt;br&gt;&lt;br&gt;

:&lt;big&gt;'''D(n) = D(1) - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(n)'''&lt;/big&gt;&lt;br&gt;&lt;br&gt;

where D(n) represents the bond length in Å and n is the bond order. D(1) in this case would be the length of a C-C single bond, which we can obtain from the average bond length in alkanes (1.54 Å).  Using this formula we can predict that the bond lengths in ethylene (C=C double bond) and acetylene (C≡C triple bond) should be 1.36 and 1.25 Å, respectively, which are close to the experimental values of 1.33 and 1.20 Å.  In a related form the Pauling formula can be used to calculate bond lengths when the single bond length D(1) is not available:&lt;br&gt;&lt;br&gt;

:&lt;big&gt;'''D(n) = D(m) - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(n/m)'''&lt;/big&gt;&lt;br&gt;


Here n and m represent two different bond orders between the same kinds of atoms.  This tells, for example, that the difference in length between a triple and double bond, D(2)-D(3), should be - 0.6 log&lt;sub&gt;&lt;small&gt;10&lt;/small&gt;&lt;/sub&gt;(2/3) = 0.11 Å.
&lt;br /&gt;
&lt;br /&gt;

[[File:Bond length of fluorine graph.JPG|right|350px|thumb|Trends in covalent radii for p-block elements. The [[w:Covalent_radius_of_fluorine|covalent radius of F]] has been difficult to determine because of electron pair repulsion effects. Early reports (Shomaker and Stevenson, Pauling) overestimated the size of the F atom.&lt;ref&gt;{{cite journal|last1=Schomaker|first1=Verner|last2=Stevenson|first2=D. P.|journal=Journal of the American Chemical Society|volume=63|pages=37–40|year=1941|doi=10.1021/ja01846a007|title=Some Revisions of the Covalent Radii and the Additivity Rule for the Lengths of Partially Ionic Single Covalent Bonds *}}&lt;/ref&gt;&lt;ref&gt;Pauling, L. The Nature of the Chemical Bond, 3rd ed.; Cornell University Press: Ithaca, NY, 1960; p. 224.&lt;/ref&gt;&lt;ref&gt;{{cite journal|last1=Robinson|first1=Edward A.|last2=Johnson|first2=Samuel A.|last3=Tang|first3=Ting-Hua|last4=Gillespie|first4=Ronald J.|title=Reinterpretation of the Lengths of Bonds to Fluorine in Terms of an Almost Ionic Model|journal=Inorganic Chemistry|volume=36|issue=14|pages=3022–3030|year=1997|pmid=11669953|doi=10.1021/ic961315b}}&lt;/ref&gt;  Accurate quantum chemical calculations place the F single-bond covalent radius at about 0.64 Å.&lt;ref&gt;{{cite journal|doi=10.1002/chem.200901472|title=Molecular Double-Bond Covalent Radii for Elements Li–E112|year=2009|last1=Pyykkö|first1=Pekka|last2=Atsumi|first2=Michiko|journal=Chemistry: A European Journal|volume=15|issue=46|pages=12770–12779}}&lt;/ref&gt;]]Some bond lengths and bond energies are anomalous. For example, the F-F bond length in F&lt;sub&gt;2&lt;/sub&gt; is 1.43 Å, which is 0.15 Å ''longer'' than twice the covalent radius of the F atom (0.64 Å).  The F-F bond is also quite weak (bond dissociation energy = 155 kJ/mol) relative to the Cl-Cl bond (242 kJ/mol).  By putting the extra bond length into the Pauling formula, we calculate that the bond order in the F&lt;sub&gt;2&lt;/sub&gt; molecule is only 0.6, i.e., substantially weaker than a F-F single bond.  The physical reason for this is that the F-F bond is &quot;stretched&quot; by repulsion of the lone pairs on the F atoms.  This crowding is caused by the fact that the [He] 1s&lt;sup&gt;2&lt;/sup&gt; core orbital, as well as the valence orbitals of the fluorine atoms, are contracted by the high nuclear charge.  The Cl atom in Cl&lt;sub&gt;2&lt;/sub&gt; has a larger [Ne] (1s&lt;sup&gt;2&lt;/sup&gt;2s&lt;sup&gt;2&lt;/sup&gt;2p&lt;sup&gt;6&lt;/sup&gt;) core, in contrast, so Cl-Cl has a &quot;normal&quot; single bond length (1.98 Å) that is twice the covalent radius of the Cl atom (0.99 Å).  A similar lone pair repulsion effect explains the anomalously long and weak N-N and O-O single bonds in hydrazine (H&lt;sub&gt;2&lt;/sub&gt;N-NH&lt;sub&gt;2&lt;/sub&gt;) and hydrogen peroxide (HO-OH), which are both highly reactive molecules.  
&lt;br /&gt;

The important roles of electronegativity differences and lone pair repulsion are evident when comparing trends in bond strengths.  The table below shows the average single-bond enthalpies of p-block elements with H and F.  H makes stronger bonds with 2nd row elements (C, N, O, F) than with third row elements (Si, P, S, Cl) because the 2p valence electrons are closer to the nucleus and thus make stronger bonds than electrons in 3p orbitals.  The bonds to H also follow the expected trend of increasing bond strength with increasing electronegativity difference.  Bonds between second row elements (C, N, O, F) and F are however anomalously weak because of lone pair repulsion.  For this reason, the Si-F bond is substantially stronger than the C-F bond, whereas the C-H bond is much stronger than the Si-H bond.  The strong Si-F bond is the reason that HF etches glass (to produce the SiF&lt;sub&gt;6&lt;/sub&gt;&lt;sup&gt;2-&lt;/sup&gt; anion), and the strong C-H bond is an important factor in the stability of hydrocarbons and other organic molecules.


'''Average E-H and E-F bond enthalpies (kJ/mol)'''
{| class=&quot;wikitable&quot;
|C-H&amp;nbsp;&amp;nbsp;&amp;nbsp;413&amp;nbsp;&amp;nbsp;&amp;nbsp;||N-H&amp;nbsp;&amp;nbsp;&amp;nbsp;391&amp;nbsp;&amp;nbsp;&amp;nbsp;||O-H&amp;nbsp;&amp;nbsp;&amp;nbsp;483&amp;nbsp;&amp;nbsp;&amp;nbsp;||H-F&amp;nbsp;&amp;nbsp;&amp;nbsp;567&amp;nbsp;&amp;nbsp;&amp;nbsp;
|-
|Si-H&amp;nbsp;&amp;nbsp;&amp;nbsp;323||P-H&amp;nbsp;&amp;nbsp;&amp;nbsp;322||S-H&amp;nbsp;&amp;nbsp;&amp;nbsp;339||H-Cl&amp;nbsp;&amp;nbsp;&amp;nbsp;431
|-
|


|
|
|
|-
|C-F&amp;nbsp;&amp;nbsp;&amp;nbsp;485||N-F&amp;nbsp;&amp;nbsp;&amp;nbsp;272||O-F&amp;nbsp;&amp;nbsp;&amp;nbsp;190||F-F &amp;nbsp;&amp;nbsp;&amp;nbsp;155
|-
|Si-F&amp;nbsp;&amp;nbsp;&amp;nbsp;565||P-F &amp;nbsp;&amp;nbsp;&amp;nbsp;490  ||S-F&amp;nbsp;&amp;nbsp;&amp;nbsp;327||Cl-F&amp;nbsp;&amp;nbsp;&amp;nbsp;253
|}


[[File:A water droplet DWR-coated surface2 edit1.jpg|thumb|150px|right|alt=A shiny spherical drop of water on blue cloth|Fabric treated with fluorosurfactant]]The anomalously weak bond in F&lt;sub&gt;2&lt;/sub&gt; is responsible for the high electronegativity of fluorine, as well as the legendary reactivity of elemental fluorine gas, which reacts explosively with hydrogen and powdered metals.  Because of the instability of elemental fluorine and the polar nature of its bonds with more electropositive elements, fluorine compounds tend to be very stable.  For example, the noble gases Xe and Kr react with fluorine to make covalent compounds, whereas other halogens do not react.  Fluorocarbon compounds contain strong C-F bonds and have high thermal and chemical stability.  Perfluorocarbons such as [[w:Teflon|Teflon]] (poly(tetrafluoroethylene), -(CF&lt;sub&gt;2&lt;/sub&gt;CF&lt;sub&gt;2&lt;/sub&gt;)n-, PTFE) are also highly hydrophobic.  The extraordinary hydrophobicity of perfluorocarbons arises from the fact that -CF&lt;sub&gt;2&lt;/sub&gt;- and -CF&lt;sub&gt;3&lt;/sub&gt; groups are &quot;fatter&quot; than -CH&lt;sub&gt;2&lt;/sub&gt;- and -CH&lt;sub&gt;3&lt;/sub&gt; groups; dissolving them in water is therefore more disruptive to the hydrogen bonding network than is dissolving a hydrocarbon. &lt;ref&gt;V. H. Dalvi and P. J. Rossky, Molecular origins of fluorocarbon hydrophobicity, Proc. Natl. Acad. Sci. USA 107,13603–13607 (2010). DOI: 10.1073/pnas.0915169107.&lt;/ref&gt;

==1.4 Discussion questions==
'''Group essay project:'''&lt;br&gt;
Join a group of classmates from your inorganic chemistry course.  Each group should have 3 or 4 students.  Arrange a time to meet for an hour or so.  Prior to the meeting, read part I (pp. 1367-1391) as well as the summary at the end of Linus Pauling's [http://courses.chem.psu.edu/chem310/ja01355a027.pdf article] (J. Am. Chem. Soc. 1931, 53, 1367-1400) on the nature of the chemical bond.  

This paper was published only a few years after Schrödinger developed the quantum mechanical theory of atomic orbitals and is considered one of the most important papers in the history of modern chemistry.  At the meeting, discuss the following questions:  (1) What was understood about chemical bonding in molecules before Pauling published this work? (2) What new concepts did the paper introduce that we still use today? (3) Why were these ideas important? and (4) What, if anything, did Pauling get wrong, and why?

Together with your classmates, write a 1-2 page essay addressing these questions.  Please include the names of all students in your group on the first page; all of you will receive the same grade on this assignment.  Anonymous excerpts from a few of these essays will be shared with the class.


'''In-class discussion questions from this chapter:'''
* What are inequivalent resonance structures? Illustrate with some new examples not covered above.
* Explain no-bond resonance and hypervalency, using some new examples.
* What are the limitations of valence bond theory for molecules that contain an odd number of electrons? Illustrate with one or two examples.

==1.5 Problems==
1.	Draw composite octet structures (including formal charges, bond order, and molecular shape) for the following: (a) BrO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (b) SF&lt;sub&gt;6&lt;/sub&gt;, (c) KrF&lt;sub&gt;2&lt;/sub&gt;, (d) HClO&lt;sub&gt;4&lt;/sub&gt; (= HOClO&lt;sub&gt;3&lt;/sub&gt;), (e) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, and (f) ClO&lt;sub&gt;2&lt;/sub&gt;.

2.	Draw composite octet structures (including formal charges, bond order, and molecular shape) for the following: (a) Al&lt;sub&gt;2&lt;/sub&gt;Cl&lt;sub&gt;6&lt;/sub&gt;, (b) SnCl&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (c) BrF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;,(d) HOClO, (e) SO&lt;sub&gt;3&lt;/sub&gt;, and (f) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;.

3.	Show using resonance why the CO bond distance in formamide (HCONH&lt;sub&gt;2&lt;/sub&gt;) is longer than the CO bond distance in acetone.

4.	Give the formulas for five stable molecules and/or ions that are isoelectronic with ammonia.

5.	Name three well known molecules or ions that are isoelectronic with (a) NO&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt;, (b) BF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;, (c) CH&lt;sub&gt;4&lt;/sub&gt;, and (d) HCN.


6.	Name three well known molecules or ions that are isoelectronic with (a) CN&lt;sup&gt;-&lt;/sup&gt;, (b) H&lt;sub&gt;2&lt;/sub&gt;O, (c) BF&lt;sub&gt;3&lt;/sub&gt;, and (d) CO&lt;sub&gt;2&lt;/sub&gt;.

7.	The C-C bond distance is 1.20 Å in acetylene.  Using  the Pauling bond length – bond strength formula, D(n) = D(m) - 0.6 log(n/m), estimate the C-C bond distance in ketene (H&lt;sub&gt;2&lt;/sub&gt;CCO).  

8.	In hydroxylamine, H&lt;sub&gt;2&lt;/sub&gt;NOH, the N-O bond distance is 1.46 Å.  Using the Pauling bond length - bond strength formula, estimate the N-O bond distances in NO&lt;sub&gt;2&lt;/sub&gt; and NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.


9.	Nitrogen can exist in the +5 oxidation state in compounds that contain ions such a NF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; and NO&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;.  However the neutral binary compound NF&lt;sub&gt;5&lt;/sub&gt; is unknown.  Can you draw octet structures for each of these compounds?  Why would NF&lt;sub&gt;5&lt;/sub&gt; be unstable?

10.	Consider the compounds NH&lt;sub&gt;3&lt;/sub&gt; and PH&lt;sub&gt;3&lt;/sub&gt;.  The H-N-H bond angle in ammonia is 108&lt;sup&gt;o&lt;/sup&gt; (close to the tetrahedral angle, 109.5&lt;sup&gt;o&lt;/sup&gt;), but the analogous angle in PH&lt;sub&gt;3&lt;/sub&gt; is 93&lt;sup&gt;o&lt;/sup&gt;.   Why is the angle in PH&lt;sub&gt;3&lt;/sub&gt; closer to 90&lt;sup&gt;o&lt;/sup&gt; than it is to the tetrahedral angle?

11.	Two hypothetical structures for the N&lt;sub&gt;2&lt;/sub&gt;F&lt;sub&gt;3&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; ion are [N-NF&lt;sub&gt;3&lt;/sub&gt;]&lt;sup&gt;+&lt;/sup&gt; and [F-N-NF&lt;sub&gt;2&lt;/sub&gt;]&lt;sup&gt;+&lt;/sup&gt;.  Which one is more stable? Explain.  (Note:  lines in the formulas can represent either single or multiple bonds)

12.	Krypton difluoride, KrF&lt;sub&gt;2&lt;/sub&gt;, decomposes at dry ice temperature to Kr and F&lt;sub&gt;2&lt;/sub&gt;.  However, several salts of the [KrF]&lt;sup&gt;+&lt;/sup&gt; ion are relatively stable.  Draw valence bond pictures for KrF&lt;sub&gt;2&lt;/sub&gt; and [KrF]&lt;sup&gt;+&lt;/sup&gt;, showing lone pairs, possible resonance structures, formal charges, bond orders, and bond angles.  Why is [KrF]&lt;sup&gt;+&lt;/sup&gt; more stable than KrF&lt;sub&gt;2&lt;/sub&gt;?


13.	Consider the anion SF&lt;sub&gt;3&lt;/sub&gt;O&lt;sub&gt;2&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; (with S the central atom).  How many isomers are possible? Which is the most stable?

14. 	The Br-F bond distance in the interhalogen compound BrF is 1.76 Å.  Use this information to estimate the average bond lengths in BrF&lt;sub&gt;3&lt;/sub&gt; and BrF&lt;sub&gt;5&lt;/sub&gt;.


15. 	The B-H bond distances are about the same in BH&lt;sub&gt;3&lt;/sub&gt; and BH&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt;. however, the B-F bond distance in BF&lt;sub&gt;3&lt;/sub&gt; is shorter than that in the BF&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;-&lt;/sup&gt; ion.  Explain.


16.	The N-N bond dissociation energy in hydrazine (H&lt;sub&gt;2&lt;/sub&gt;N-NH&lt;sub&gt;2&lt;/sub&gt;) is 159 kJ/mol.  The dissociation energy of the N-N triple bond in N&lt;sub&gt;2&lt;/sub&gt; is 941 kJ/mol, i.e., much greater than three times the N-N single bond dissociation energy in hydrazine.  Explain why the N-N bond in hydrazine is so weak, and why this effect is not seen in N&lt;sub&gt;2&lt;/sub&gt;.


17.	Show that a set of four sp&lt;sup&gt;3&lt;/sup&gt; hybrid orbitals satisfies the following criteria:  (a) any two orbitals in the sp&lt;sup&gt;3&lt;/sup&gt; set are orthogonal, and (b) the orbitals are properly normalized.


18.	Quantum mechanically, the momentum (p) of a particle traveling in a specific direction (e.g., the x direction) can be obtained by operating on its wavefunction &lt;math&gt;\psi&lt;/math&gt; with the [[w:Momentum_operator|'''momentum operator''']]:

:&lt;math&gt; \hat{p}\psi = p\psi&lt;/math&gt;, where &lt;math&gt; \hat{p} = -i\hbar{\partial \over \partial x} &lt;/math&gt;

Knowing the correct form of this operator was the key to Schrödinger's formulation of  the Hamiltonian operator, &lt;math&gt;\hat{H} = \frac{\hat{p}^2}{2m} + V&lt;/math&gt;, which operates on a wavefunction to give the total energy.  The momentum operator must also be consistent with the [[w:Matter_wave|'''de Broglie relation''']], p = h/λ, which relates the momentum to the particle wavelength.


By analogy to electromagnetic waves, Schrödinger knew that a wavelike particle (such as an electron) traveling in free space in the x-direction could be described by the wavefunction:

:&lt;math&gt;\psi(x,t)= Ae^{i(kx - \omega t +\varphi)}&lt;/math&gt;

where the [[w:Wavenumber|'''wavenumber''']] k is inversely related to the particle's [[w:Matter_wave|'''de Broglie wavelength''']] λ by k = 2π/λ.  Here A is a normalization constant, ω is the frequency of the wave, and &lt;math&gt;\varphi&lt;/math&gt; represents its phase. 

Show using the momentum operator &lt;math&gt;\hat{p}&lt;/math&gt; that the value of the momentum p we obtain for a free particle from &lt;math&gt; \hat{p}\psi = p\psi&lt;/math&gt; is consistent with the de Broglie relation, p = h/λ.  &lt;br&gt;
(Hint: k, ω, and &lt;math&gt;\varphi&lt;/math&gt; are independent of x)


19.	N&lt;sub&gt;3&lt;/sub&gt;S&lt;sub&gt;4&lt;/sub&gt;&lt;sup&gt;+&lt;/sup&gt; is a cyclic cation that contains no N-N bonds. Draw the structure of the seven-membered ring and use the electron counting method to determine the number of single bonds, double bonds, and lone pairs. Draw out the possible resonance structures for this ion showing formal charges and indicate which one is the most stable. Which S-N bonds would you predict to be the shortest? The atomic connectivity in the ring is: -S-S-N-S-N-S-N-. (''Hint'': determine the number of π-bonds in the molecule by electron counting and then find the most stable resonance structures.)


20.	F has a higher electronegativity than Cl, and F&lt;sub&gt;2&lt;/sub&gt; is a much stronger oxidizing agent than Cl&lt;sub&gt;2&lt;/sub&gt;, despite the fact that the electron affinity of fluorine (-328 kJ/mol) is weaker than that of chlorine (-349 kJ/mol).  Explain this apparent contradiction.

21.	The single bonds in methane (CH&lt;sub&gt;4&lt;/sub&gt;), ammonia (NH&lt;sub&gt;3&lt;/sub&gt;) and water (H&lt;sub&gt;2&lt;/sub&gt;O) are stronger than those in SiH&lt;sub&gt;4&lt;/sub&gt;, PH&lt;sub&gt;3&lt;/sub&gt;, and H&lt;sub&gt;2&lt;/sub&gt;S, respectively. The analogous fluorine containing compounds follow the opposite trend: the single bonds in CF&lt;sub&gt;4&lt;/sub&gt;, NF&lt;sub&gt;3&lt;/sub&gt;, and OF&lt;sub&gt;2&lt;/sub&gt; are weaker than those in SiF&lt;sub&gt;4&lt;/sub&gt;, PF&lt;sub&gt;3&lt;/sub&gt;, and SF&lt;sub&gt;2&lt;/sub&gt;. Can you explain these two opposite trends?

==1.6 References==
{{reflist|colwidth=30em}}

{{BookCat}}</text>
      <sha1>awnh9z5bcgc33hlutjflo92chg0qt4z</sha1>
    </revision>
  </page>
  <page>
    <title>User:Tyoyafud/sandbox</title>
    <ns>2</ns>
    <id>392990</id>
    <revision>
      <id>4678608</id>
      <parentid>4622876</parentid>
      <timestamp>2026-10-27T20:56:45Z</timestamp>
      <contributor>
        <username>Tyoyafud</username>
        <id>6233</id>
      </contributor>
      <comment>/* Root Morphemes */</comment>
      <origin>4678608</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="518" sha1="1har9vxcd0m7t96g3lkl76r0llv4gai" xml:space="preserve">&lt;b&gt;teater&lt;/b&gt; &lt;i&gt;vt.&lt;/i&gt; [te-a-`ter] (&lt; &lt;b&gt;teab&lt;/b&gt; &lt;i&gt;eye&lt;/i&gt;). to see
:&lt;b&gt;teatea&lt;/b&gt; &lt;i&gt;prp.&lt;/i&gt; seeing
:&lt;b&gt;teaten&lt;/b&gt; &lt;i&gt;ger.&lt;/i&gt; seeing
:: &lt;b&gt;Teaten se vyatexen.&lt;/b&gt; Seeing is believing.
:&lt;b&gt;teatwa&lt;/b&gt; &lt;i&gt;pp.&lt;/i&gt; seen
:&lt;b&gt;teat&lt;/b&gt; &lt;i&gt;n.&lt;/i&gt; sight, vision
::&lt;b&gt;teata&lt;/b&gt; &lt;i&gt;a.&lt;/i&gt; visual
:&lt;b&gt;teatyaf&lt;/b&gt; &lt;i&gt;n.&lt;/i&gt; ability to see, vision, eyesight
::&lt;b&gt;teatyafa&lt;/b&gt; &lt;i&gt;a.&lt;/i&gt; able to see, sighted
::&lt;b&gt;teatyafwa&lt;/b&gt; &lt;i&gt;a.&lt;/i&gt; visible
:::&lt;b&gt;teatyafwan&lt;/b&gt; &lt;i&gt;n.&lt;/i&gt; visiblity
:::&lt;b&gt;teatyafway&lt;/b&gt; &lt;i&gt;adv.&lt;/i&gt; visibly.</text>
      <sha1>1har9vxcd0m7t96g3lkl76r0llv4gai</sha1>
    </revision>
    <revision>
      <id>4678610</id>
      <parentid>4678608</parentid>
      <timestamp>2026-10-27T21:05:48Z</timestamp>
      <contributor>
        <username>Tyoyafud</username>
        <id>6233</id>
      </contributor>
      <origin>4678610</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="704" sha1="aoqxa884yedtlnhbhl6iwi18wio8aq1" xml:space="preserve">&lt;b&gt;teater&lt;/b&gt; &lt;i&gt;vt.&lt;/i&gt; [te-a-`ter] (&lt; &lt;b&gt;teab&lt;/b&gt; &lt;i&gt;eye&lt;/i&gt;). to see
:&lt;b&gt;teatea&lt;/b&gt; &lt;i&gt;prp.&lt;/i&gt; seeing
:&lt;b&gt;teaten&lt;/b&gt; &lt;i&gt;ger.&lt;/i&gt; seeing
:: &lt;b&gt;Teaten se vyatexen.&lt;/b&gt; Seeing is believing.
:&lt;b&gt;teatwa&lt;/b&gt; &lt;i&gt;pp.&lt;/i&gt; seen
:&lt;b&gt;teat&lt;/b&gt; &lt;i&gt;n.&lt;/i&gt; sight, vision, view
::&lt;b&gt;teata&lt;/b&gt; &lt;i&gt;a.&lt;/i&gt; visual, optical
:&lt;b&gt;teatyaf&lt;/b&gt; &lt;i&gt;n.&lt;/i&gt; ability to see, vision, eyesight
::&lt;b&gt;teatyafa&lt;/b&gt; &lt;i&gt;a.&lt;/i&gt; able to see, sighted
::&lt;b&gt;teatyafer&lt;/b&gt; &lt;i&gt;v.t.&lt;/i&gt; to be able to see
:::&lt;b&gt;teatyafxer&lt;/b&gt; &lt;i&gt;v.t.&lt;/i&gt; to show
::&lt;b&gt;teatyafwa&lt;/b&gt; &lt;i&gt;a.&lt;/i&gt; visible
:::&lt;b&gt;teatyafwan&lt;/b&gt; &lt;i&gt;n.&lt;/i&gt; visiblity
:::&lt;b&gt;teatyafway&lt;/b&gt; &lt;i&gt;adv.&lt;/i&gt; visibly.
:::&lt;b&gt;teatyafwer&lt;/b&gt; &lt;i&gt;v.i.&lt;/i&gt; to be visible
::&lt;b&gt;teatyofa&lt;/b&gt; &lt;i&gt;a.&lt;/i&gt; blind</text>
      <sha1>aoqxa884yedtlnhbhl6iwi18wio8aq1</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Edit filter/False positives</title>
    <ns>4</ns>
    <id>396216</id>
    <revision>
      <id>4678663</id>
      <parentid>4677569</parentid>
      <timestamp>2026-10-28T08:10:40Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <minor />
      <comment>Bot: Archiving 2 threads (older than 75 days) to [[Wikibooks:Edit filter/False positives/Archive 5]]</comment>
      <origin>4678663</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9368" sha1="emzxparw2rngwjt3zc62pf4p3kjihrz" xml:space="preserve">__NONEWSECTIONLINK__ __NOINDEX__ {{Wikibooks:Edit filter/False positives/Header}} {{shortcut|WB:EFFP}} {{User:MiszaBot/config
|archive = Wikibooks:Edit filter/False positives/Archive %(counter)d
|algo = old(75d)
|counter = 5
|maxarchivesize = 150K
|minthreadstoarchive = 1
|minthreadsleft = 3
}}

== LoveElectronicLiterature ==

;Username
: [[:b:User:LoveElectronicLiterature|LoveElectronicLiterature]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:LoveElectronicLiterature|discuss]]
|[[:b:Special:Emailuser/LoveElectronicLiterature|email]]
|[[:b:Special:Contributions/LoveElectronicLiterature|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:LoveElectronicLiterature}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:LoveElectronicLiterature}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=LoveElectronicLiterature}} filter log]&lt;/span&gt;)
;Page you were editing
: [[https://en.wikibooks.org/w/index.php?title=Hereditary_Multiple_Exostoses&amp;veaction=edit&amp;section=7]] &lt;span class=&quot;plainlinks&quot;&gt;([{{fullurl:Special:AbuseLog|wpSearchTitle=https%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DHereditary_Multiple_Exostoses%26veaction%3Dedit%26section%3D7}} filter log]) ([{{fullurl:Special:AbuseLog|wpSearchTitle=https%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DHereditary_Multiple_Exostoses%26veaction%3Dedit%26section%3D7&amp;wpSearchUser=LoveElectronicLiterature}} user filter log])&lt;/span&gt;
;Description
: I was trying to copy the references and abstracts that I have been maintaining for over 20 years at http COLON SLASH SLASH tinyurl DOT com SLASH MHETalk.  I copied a bunch of references, and then I shortened the description and put the citations in. But I got flagged for copying.  Is there any way to fix this?  thanks!
;Date and time
: 16:23, 16 July 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;
: {{EFFP|notdone}} You attempted to add a large edit to a book, so please try doing this in smaller edits. – [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:52, 15 August 2026 (UTC)

== ~2026-49041-81 ==

;Username
: [[:b:User:~2026-49041-81|~2026-49041-81]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:~2026-49041-81|discuss]]
|[[:b:Special:Emailuser/~2026-49041-81|email]]
|[[:b:Special:Contributions/~2026-49041-81|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:~2026-49041-81}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:~2026-49041-81}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=%7E2026-49041-81}} filter log]&lt;/span&gt;)
;Page you were editing
: [[Danish]] &lt;span class=&quot;plainlinks&quot;&gt;([{{fullurl:Special:AbuseLog|wpSearchTitle=Danish}} filter log]) ([{{fullurl:Special:AbuseLog|wpSearchTitle=Danish&amp;wpSearchUser=%7E2026-49041-81}} user filter log])&lt;/span&gt;
;Description
: Tried to add this link to my-danish-tutor.com This one has a ton of free resources and interactive materials for learning Danish. Reading, listening, conversations, grammar, word lists, flashcards and much more.
;Date and time
: 17:50, 10 September 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;

== ActStuffOGWiki ==

;Username
: [[:b:User:ActStuffOGWiki|ActStuffOGWiki]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:ActStuffOGWiki|discuss]]
|[[:b:Special:Emailuser/ActStuffOGWiki|email]]
|[[:b:Special:Contributions/ActStuffOGWiki|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:ActStuffOGWiki}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:ActStuffOGWiki}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=ActStuffOGWiki}} filter log]&lt;/span&gt;)
;Page you were editing
: [[Indian Railways/History]] &lt;span class=&quot;plainlinks&quot;&gt;([{{fullurl:Special:AbuseLog|wpSearchTitle=Indian+Railways%2FHistory}} filter log]) ([{{fullurl:Special:AbuseLog|wpSearchTitle=Indian+Railways%2FHistory&amp;wpSearchUser=ActStuffOGWiki}} user filter log])&lt;/span&gt;
;Description
: It says I added a &quot;large amount of content&quot; to this page. Even though I did copy paste the Introduction, the rest was me typing.
;Date and time
: 08:49, 18 September 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;

== ActStuffOGWiki ==

;Username
: [[:b:User:ActStuffOGWiki|ActStuffOGWiki]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:ActStuffOGWiki|discuss]]
|[[:b:Special:Emailuser/ActStuffOGWiki|email]]
|[[:b:Special:Contributions/ActStuffOGWiki|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:ActStuffOGWiki}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:ActStuffOGWiki}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=ActStuffOGWiki}} filter log]&lt;/span&gt;)
;Page you were editing
: [[Indian Railways/History]] &lt;span class=&quot;plainlinks&quot;&gt;([{{fullurl:Special:AbuseLog|wpSearchTitle=Indian+Railways%2FHistory}} filter log]) ([{{fullurl:Special:AbuseLog|wpSearchTitle=Indian+Railways%2FHistory&amp;wpSearchUser=ActStuffOGWiki}} user filter log])&lt;/span&gt;
;Description
: ''Note: This page is not published yet. '' I tried to make this page normally, but the [[Wikibooks:edit filter|edit filter]] told that there has been a '''large amount of content''' added. I did it again but copy-pasted sentence by sentence because I didn't want to type the whole thing again. It still says the same warning.
;Date and time
: 09:02, 18 September 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;

== Benson Benjamin. M ==

;Username
: [[:b:User:Benson Benjamin. M|Benson Benjamin. M]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:Benson Benjamin. M|discuss]]
|[[:b:Special:Emailuser/Benson Benjamin. M|email]]
|[[:b:Special:Contributions/Benson Benjamin. M|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:Benson Benjamin. M}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:Benson Benjamin. M}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=Benson+Benjamin.+M}} filter log]&lt;/span&gt;)
;Page you were editing
: Page not specified
;Description
: 
;Date and time
: 13:19, 28 September 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;
: {{EFFP|notdone}}  – [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:12, 21 October 2026 (UTC)

== ~2026-56325-65 ==

;Username
: [[:b:User:~2026-56325-65|~2026-56325-65]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:~2026-56325-65|discuss]]
|[[:b:Special:Emailuser/~2026-56325-65|email]]
|[[:b:Special:Contributions/~2026-56325-65|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:~2026-56325-65}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:~2026-56325-65}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=%7E2026-56325-65}} filter log]&lt;/span&gt;)
;Page you were editing
: [[https://en.wikibooks.org/wiki/Funding_and_Finance_of_Transportation_Projects_in_the_United_States_of_America]] &lt;span class=&quot;plainlinks&quot;&gt;([{{fullurl:Special:AbuseLog|wpSearchTitle=https%3A%2F%2Fen.wikibooks.org%2Fwiki%2FFunding_and_Finance_of_Transportation_Projects_in_the_United_States_of_America}} filter log]) ([{{fullurl:Special:AbuseLog|wpSearchTitle=https%3A%2F%2Fen.wikibooks.org%2Fwiki%2FFunding_and_Finance_of_Transportation_Projects_in_the_United_States_of_America&amp;wpSearchUser=%7E2026-56325-65}} user filter log])&lt;/span&gt;
;Description
: i was told to divide my page into chapters which I did and after that i wanted to delete  the actual material from the Table of Contents page but the system thought I was deleting a lot of material.
;Date and time
: 10:01, 21 October 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;
: {{EFFP|fixed}} by myself. {{ping|~2026-56325-65}} Feel free to retry your edit(s) again. I included an exemption for the filter. – [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:12, 21 October 2026 (UTC)</text>
      <sha1>emzxparw2rngwjt3zc62pf4p3kjihrz</sha1>
    </revision>
  </page>
  <page>
    <title>User:Wargo/common.js</title>
    <ns>2</ns>
    <id>405875</id>
    <revision>
      <id>4678668</id>
      <parentid>4460251</parentid>
      <timestamp>2026-10-28T09:36:50Z</timestamp>
      <contributor>
        <username>Wargo</username>
        <id>1009988</id>
      </contributor>
      <comment>Wersje przejrzane wyłączone</comment>
      <origin>4678668</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="154" sha1="s4upvi28urjo8wiqr8cpxbgn4bqxydf" xml:space="preserve">$(document).ready(function () {
	mw.loader.load('//pl.wikipedia.org/w/index.php?title=Wikipedysta:BZPN/Rollback.js&amp;action=raw&amp;ctype=text/javascript');
});</text>
      <sha1>s4upvi28urjo8wiqr8cpxbgn4bqxydf</sha1>
    </revision>
  </page>
  <page>
    <title>Wikijunior:The Elements/Krypton</title>
    <ns>110</ns>
    <id>410694</id>
    <revision>
      <id>4678618</id>
      <parentid>4678423</parentid>
      <timestamp>2026-10-27T21:22:29Z</timestamp>
      <contributor>
        <username>How hardy</username>
        <id>3627644</id>
      </contributor>
      <minor />
      <comment>/* References */</comment>
      <origin>4678618</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2450" sha1="mmzcav92kbb7wb491wxmafq4ued0dug" xml:space="preserve">__NOTOC__

[[File:Kr-TableImage.svg|thumb|left|500px|Shows the position of Krypton on the periodic chart.]]
[[File:Krypton.svg|thumb|55px|Krypton's symbol on the Periodic Table]]
{{clear}}
==What does it look, feel, taste, or smell like?==
Krypton is an odorless and colorless gas. 

In the gaseous state, krypton sometimes emits green and yellow light. In the solid state it is white. Since krypton is a gas under normal conditions, it has no tactile texture or feel. If inhaled, it would feel heavier than air. It has no smell. Krypton has no taste because it does not react with taste receptors on the tongue.

==How was it discovered?==
It was discovered on May 30, 1898, by Sir William Ramsay, a Scottish chemist, and Morris M. Travers, an English chemist. They discovered it by boiling liquified air and some of the liquid that was left was krypton. Due to krypton's (relatively) high boiling point at -153.415 C, the more abundant gases or low boiling point gases evaporated and what was left was krypton.

The method they used was called fractional distillation. Components were removed one-by-one from the evaporated liquid air. A tiny residue remained after oxygen, nitrogen, and other gases were removed. The residue was krypton, a previously unknown noble gas.
[[File:Electron shell 036 Krypton.svg|thumb|Krypton element form]]

==Where did its name come from?==
The name comes from the Greek word ''kryptos'', which translates to English as ''hidden''.

==Where is it found?==
The only source for Krypton is the Earth’s atmosphere. It is believed that the Earth’s atmosphere is around 0.0001% Krypton gas.

==What are its uses?==
[[File:KrTube.jpg|thumb|left|Krypton gas discharge tube]]
Krypton is used as a filling gas in fluorescent light. It is also used for flash lamps and high speed photography. It can also be used for lasers and was also used in the Cold War to measure Soviet nuclear production.

==Is it dangerous?==
Krypton is an odorless and colorless gas. Since it is a [[{{BOOKNAME}}/Elements#Noble Gases|noble gas]], it is inactive. Noble gases barely react to anything, so they are not considered dangerous. The only gas Krypton reacts to is Fluorine which creates Krypton Difluoride.

== References ==

Beyond The Elements. (2023). '''Krypton: This gas powered both lasers and spacecraft''' [Video]. YouTube. &lt;code&gt;&lt;nowiki&gt;https://www.youtube.com/watch?v=N0Gw6-xMLlo&lt;/nowiki&gt;&lt;/code&gt; (youtube.com in Bing){{BookCat}}</text>
      <sha1>mmzcav92kbb7wb491wxmafq4ued0dug</sha1>
    </revision>
    <revision>
      <id>4678619</id>
      <parentid>4678618</parentid>
      <timestamp>2026-10-27T21:24:44Z</timestamp>
      <contributor>
        <username>How hardy</username>
        <id>3627644</id>
      </contributor>
      <comment>/* Where did its name come from? */</comment>
      <origin>4678619</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2446" sha1="d9lmxyvtgylno45gzukrjd54ghq87k4" xml:space="preserve">__NOTOC__

[[File:Kr-TableImage.svg|thumb|left|500px|Shows the position of Krypton on the periodic chart.]]
[[File:Krypton.svg|thumb|55px|Krypton's symbol on the Periodic Table]]
{{clear}}
==What does it look, feel, taste, or smell like?==
Krypton is an odorless and colorless gas. 

In the gaseous state, krypton sometimes emits green and yellow light. In the solid state it is white. Since krypton is a gas under normal conditions, it has no tactile texture or feel. If inhaled, it would feel heavier than air. It has no smell. Krypton has no taste because it does not react with taste receptors on the tongue.

==How was it discovered?==
It was discovered on May 30, 1898, by Sir William Ramsay, a Scottish chemist, and Morris M. Travers, an English chemist. They discovered it by boiling liquified air and some of the liquid that was left was krypton. Due to krypton's (relatively) high boiling point at -153.415 C, the more abundant gases or low boiling point gases evaporated and what was left was krypton.

The method they used was called fractional distillation. Components were removed one-by-one from the evaporated liquid air. A tiny residue remained after oxygen, nitrogen, and other gases were removed. The residue was krypton, a previously unknown noble gas.
[[File:Electron shell 036 Krypton.svg|thumb|Krypton element form]]

==Where did its name come from?==
The name comes from the Greek word ''kryptos'', which translates to English as hidden.

==Where is it found?==
The only source for Krypton is the Earth’s atmosphere. It is believed that the Earth’s atmosphere is around 0.0001% Krypton gas.

==What are its uses?==
[[File:KrTube.jpg|thumb|left|Krypton gas discharge tube]]
Krypton is used as a filling gas in fluorescent light. It is also used for flash lamps and high speed photography. It can also be used for lasers and was also used in the Cold War to measure Soviet nuclear production.

==Is it dangerous?==
Krypton is an odorless and colorless gas. Since it is a [[{{BOOKNAME}}/Elements#Noble Gases|noble gas]], it is inactive. Noble gases barely react to anything, so they are not considered dangerous. The only gas Krypton reacts to is Fluorine which creates Krypton Difluoride.

== References ==

Beyond The Elements. (2023). '''Krypton: This gas powered both lasers and spacecraft''' [Video]. YouTube. &lt;code&gt;&lt;nowiki&gt;https://www.youtube.com/watch?v=N0Gw6-xMLlo&lt;/nowiki&gt;&lt;/code&gt; (youtube.com in Bing){{BookCat}}</text>
      <sha1>d9lmxyvtgylno45gzukrjd54ghq87k4</sha1>
    </revision>
  </page>
  <page>
    <title>Create Vampires</title>
    <ns>0</ns>
    <id>415358</id>
    <revision>
      <id>4678494</id>
      <parentid>4678469</parentid>
      <timestamp>2026-10-27T14:24:57Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678494</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7763" sha1="0lv1gzgkdk30huvqy5a5x8t3s6lkosn" xml:space="preserve">
 &lt;br&gt;''Create Vampires'' is a book intended as a guide to avoid literary pitfalls, and as a nonfiction resource for those fascinated by vampires. This book examines vampires through a cultural, literary, and historical lens to help writers create authentic vampire narratives.

== Vampires ''Of The Imagination'' ==

Although vampires are creatures of folklore, monsters from the ''afterlife'' that are sometimes called the &quot;undead,&quot; vampires are uniquely different from ghost, those lingering spirits who refuse to die.

Although vampires, by definition, are animated corpses, most vampires ''of the imagination'' must feed on human blood in order to continue their earthly existence. This unique quality makes vampires a popular and original type of fiction, slightly different from other creatures found in folklore. Because of their unique characteristics, vampires have become massively popular in popular culture and in literature. 

We hope this book will clear up many misconceptions, and common misunderstandings associated with the &quot;undead,&quot; especially a common confusion ''about'' the actual people who did inspire vampire folklore, verses the evolved horror creations called vampires of the imagination.

'''Create Vampires''' aims to treat vampires as a cultural, literary and historical construct. Perhaps Create Vampires should be considered a friendly craft-manual for building a believable vampire concept, available across different medias.

== Preface: The Factual Roots Of Vampires ==
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! Factual Basis For Vampires?
|-
| [[/Factual Basis For Vampires/]] is a special page intended to offer information about the factual bases for vampires.
|}
&lt;br&gt;
 
'''What Type Of Book Is This?'''
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! '''Create Vampires''' is one of many free Wikibooks
|-
|  Wikibooks.org is a part of the Wikimedia project. Writers and contributors are volunteers who cull through websites, &lt;BR&gt; use online search engines to find facts, and volunteer to work on special projects that are open to the public. &lt;BR&gt; Volunteers are people who write, edit, and help people understand the powerful tools at their fingertips. &lt;br&gt;
|}
 &lt;br&gt; &quot;You shall not eat the blood of any flesh at all, because the life of the flesh is in the blood, and whosoever eateth it shall be cut off.&quot; - The Bible, Leviticus, chapter 17, verse 14. &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|-
! Edvard Munch - Love and Pain / Vampire (1895) || &quot;Les Vampires&quot;
|-
| [[File:Edvard Munch - Vampire (1895) - Google Art Project.jpg|thumb|Edvard Munch - Vampire (1895) - Google Art Project]] || [[File:Les vampires.jpg|thumb|Les vampires]]
|}


== All About Vampires ==
 '''Not All Links Work'''

{| class=&quot;wikitable&quot;
|-
! Table Of Content
|-
| Introduction: [[Create Vampires/Original Fictional Creations|&quot;Original Fictional Creations&quot;]]
|-
| Proper Spelling:  [[Create Vampires/Vam-Pai-Yer|&quot;How do you spell vampire?]]
|-
| [[Create Vampires/Alternative Spelling| &quot;Alternative Spellings&quot;]]
|-
| What ''Is'' A Vampire? [[Create Vampires/A Definition For Vampire|Create Vampires /A Definition For Vampire - Wikibooks, open books for an open world]]
|-
| Why Create A Vampire? : [[Create Vampires/Why Create Vampires|Create Vampires/Why Create Vampires - Wikibooks, open books for an open world]]
|-
|- '''Cultural Origins'''
|-
|'''Cultural Vampire Construct'''
|-
|What Is A Cultural Construct? - [[Create Vampires/Cultural Construct|Create Vampires/Cultural Construct - Wikibooks, open books for an open world]]
|-
| '''Vampire Folklore:''' [[Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes|Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes - Wikibooks]]
|-
| African Folklore: [[Create Vampires/African Folklore|Create Vampires/African Folklore - Wikibooks, open books for an open world]]
|-
| Latin-American Folklore: [[Create Vampires/Latin American Folklore|Create Vampires/Latin American Folklore - Wikibooks, open books for an open world]]
|-
| Asian Folklore: [[Create Vampires/Asian Folklore#Asian Folklore|Create Vampires/Asian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Asian Folklore Part Two|Create Vampires/Asian Folklore Part Two - Wikibooks, open books for an open world]]
|-
|Eastern Folklore: [[Create Vampires/Eastern European Folklore| &quot;Eastern European Folklore&quot;]]
|-
| Eastern Folklore: [[Create Vampires/Dracula Behind Vlad-The Impaler|Create Vampires/Dracula Behind Vlad-The Impaler - Wikibooks, open books for an open world]]
|-
|Oceanian Folklore: [[Create Vampires/Oceanian Folklore|Create Vampires/Oceanian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Cultural Traditions Shaped Vampire Traits|Create Vampires/How Cultural Traditions Shaped Vampire Traits - Wikibooks, open books for an open world]]
|-
|- '''Literary Construct'''
|-
|'''Literary Construct'''
|-
|[[Create Vampires/Literary Construction|Create Vampires/Literary Construction - Wikibooks, open books for an open world]]
|-
|What Is A Literary Trope? [[Create Vampires/What Is A Literary Trope]] 
|-
| Literary And Media Pitfalls To Avoid: [[Create Vampires/Examples Of Literary Pitfalls|Create Vampires/Examples Of Literary Pitfalls - Wikibooks, open books for an open world]]
|-
| Authors Who Created Influential Vampires Of The Imagination: [[Create Vampires/Authors Who Created Vampire Tropes]] 
|-
| [[Create Vampires/writers who did not create vampires| &quot;Writers Who Did Not Create Vampires&quot;]]
|-
|[[Create Vampires/Vampires In Poetry|Create Vampires/Vampires In Poetry - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Vampire Historic Fiction|Create Vampires/Vampire Historic Fiction - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Dracula|Create Vampires/Dracula - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Popular Are Vampires|Create Vampires/How Popular Are Vampires - Wikibooks, open books for an open world]]
|-
| Popular Culture: [[Create Vampires/Vampires In Popular Culture|Create Vampires/Vampires In Popular Culture - Wikibooks, open books for an open world]]
|-
| Vampire Memes? [[Create Vampires/Vampires Memes|Create Vampires/Vampires Memes - Wikibooks, open books for an open world]]
|-
|'''Are Vampires Real? Historical Construct''' [[Create Vampires/What Is A Historical Construct|Create Vampires/What Is A Historical Construct - Wikibooks, open books]]
|-
|[[Create Vampires/Factual Basis For Vampires]]
|-
|[[Create Vampires/Historical Construction|Create Vampires/Historical Construction - Wikibooks, open books for an open world]]
|-
|History of Vampires: [[Create Vampires/Vampire History]] 
|-
|  [[Create Vampires/Scientific Evidence| &quot;Science and Vampirism&quot;]]
|-
| For Vampires: [[Create Vampires/Scientific Evidence For Vampires| &quot;Scientific Evidence For Vampires&quot;]]
|-
| Against Vampires: [[Create Vampires/Scientific Evidence Against Vampirism| &quot;Scientific Evidence Against Vampires&quot;]]
|-
| Writing Vampire Prose: [[Create Vampires/Writing Vampire Prose| &quot;Writing Vampire Prose&quot;]]
|-
|- Are Vampires Real? Historical Construct
|-
| [[Create Vampires/Ethics Of Creating Vampire Lore|Create Vampires/Ethics Of Creating Vampire Lore - Wikibooks, open books for an open world]]
|-
|Public Domain Primary Sources: [[Create Vampires/PublicDomainPrimarySources]]
|-
| Information for Spanish speakers: [[:es:Vampiro|&quot;Vampiro&quot;]] &lt;br /&gt;
|-
| Closing: [[Create Vampires/All About Vampires|Create Vampires /All About Vampires - Wikibooks, open books for an open world]]
|-
| [[:Category:Book:Create Vampires|List of All Pages in This Book]]
|}

== Reference ==


{{WikipediaCredit}}
&lt;br /&gt;
{{Shelves|Literature|Paranormal|Cultural anthropology}}
{{Status|75%}}</text>
      <sha1>0lv1gzgkdk30huvqy5a5x8t3s6lkosn</sha1>
    </revision>
    <revision>
      <id>4678537</id>
      <parentid>4678494</parentid>
      <timestamp>2026-10-27T18:01:35Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>/* All About Vampires */</comment>
      <origin>4678537</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7757" sha1="mimjdxv5m7suxa4tqp9ra9q5sx5ev1u" xml:space="preserve">
 &lt;br&gt;''Create Vampires'' is a book intended as a guide to avoid literary pitfalls, and as a nonfiction resource for those fascinated by vampires. This book examines vampires through a cultural, literary, and historical lens to help writers create authentic vampire narratives.

== Vampires ''Of The Imagination'' ==

Although vampires are creatures of folklore, monsters from the ''afterlife'' that are sometimes called the &quot;undead,&quot; vampires are uniquely different from ghost, those lingering spirits who refuse to die.

Although vampires, by definition, are animated corpses, most vampires ''of the imagination'' must feed on human blood in order to continue their earthly existence. This unique quality makes vampires a popular and original type of fiction, slightly different from other creatures found in folklore. Because of their unique characteristics, vampires have become massively popular in popular culture and in literature. 

We hope this book will clear up many misconceptions, and common misunderstandings associated with the &quot;undead,&quot; especially a common confusion ''about'' the actual people who did inspire vampire folklore, verses the evolved horror creations called vampires of the imagination.

'''Create Vampires''' aims to treat vampires as a cultural, literary and historical construct. Perhaps Create Vampires should be considered a friendly craft-manual for building a believable vampire concept, available across different medias.

== Preface: The Factual Roots Of Vampires ==
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! Factual Basis For Vampires?
|-
| [[/Factual Basis For Vampires/]] is a special page intended to offer information about the factual bases for vampires.
|}
&lt;br&gt;
 
'''What Type Of Book Is This?'''
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! '''Create Vampires''' is one of many free Wikibooks
|-
|  Wikibooks.org is a part of the Wikimedia project. Writers and contributors are volunteers who cull through websites, &lt;BR&gt; use online search engines to find facts, and volunteer to work on special projects that are open to the public. &lt;BR&gt; Volunteers are people who write, edit, and help people understand the powerful tools at their fingertips. &lt;br&gt;
|}
 &lt;br&gt; &quot;You shall not eat the blood of any flesh at all, because the life of the flesh is in the blood, and whosoever eateth it shall be cut off.&quot; - The Bible, Leviticus, chapter 17, verse 14. &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|-
! Edvard Munch - Love and Pain / Vampire (1895) || &quot;Les Vampires&quot;
|-
| [[File:Edvard Munch - Vampire (1895) - Google Art Project.jpg|thumb|Edvard Munch - Vampire (1895) - Google Art Project]] || [[File:Les vampires.jpg|thumb|Les vampires]]
|}


== All About Vampires ==
 '''Not All Links Work'''

{| class=&quot;wikitable&quot;
|-
! Table Of Content
|-
| Introduction: [[Create Vampires/Original Fictional Creations|&quot;Original Fictional Creations&quot;]]
|-
| Proper Spelling:  [[Create Vampires/Vam-Pai-Yer|&quot;How do you spell vampire?]]
|-
| [[Create Vampires/Alternative Spelling| &quot;Alternative Spellings&quot;]]
|-
| What ''Is'' A Vampire? [[Create Vampires/A Definition For Vampire|Create Vampires /A Definition For Vampire - Wikibooks, open books for an open world]]
|-
| Why Create A Vampire? : [[Create Vampires/Why Create Vampires|Create Vampires/Why Create Vampires - Wikibooks, open books for an open world]]
|-
|- '''Cultural Origins'''
|-
|'''Cultural Vampire Construct'''
|-
|What Is A Cultural Construct? - [[Create Vampires/Cultural Construct|Create Vampires/Cultural Construct - Wikibooks, open books for an open world]]
|-
| '''Vampire Folklore:''' [[Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes|Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes - Wikibooks]]
|-
| African Folklore: [[Create Vampires/African Folklore|Create Vampires/African Folklore - Wikibooks, open books for an open world]]
|-
| Latin-American Folklore: [[Create Vampires/Latin American Folklore|Create Vampires/Latin American Folklore - Wikibooks, open books for an open world]]
|-
| Asian Folklore: [[Create Vampires/Asian Folklore#Asian Folklore|Create Vampires/Asian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Asian Folklore Part Two|Create Vampires/Asian Folklore Part Two - Wikibooks, open books for an open world]]
|-
|Eastern Folklore: [[Create Vampires/Eastern European Folklore| &quot;Eastern European Folklore&quot;]]
|-
| Eastern Folklore: [[Create Vampires/Dracula Behind Vlad-The Impaler|Create Vampires/Dracula Behind Vlad-The Impaler - Wikibooks, open books for an open world]]
|-
|Oceanian Folklore: [[Create Vampires/Oceanian Folklore|Create Vampires/Oceanian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Cultural Traditions Shaped Vampire Traits|Create Vampires/How Cultural Traditions Shaped Vampire Traits - Wikibooks, open books for an open world]]
|-
|- '''Literary Construct'''
|-
|'''Literary Construct'''
|-
|[[Create Vampires/Literary Construction|Create Vampires/Literary Construction - Wikibooks, open books for an open world]]
|-
|What Is A Literary Trope? [[Create Vampires/What Is A Literary Trope]] 
|-
| Literary And Media Pitfalls To Avoid: [[Create Vampires/Examples Of Literary Pitfalls|Create Vampires/Examples Of Literary Pitfalls - Wikibooks, open books for an open world]]
|-
| Authors Who Created Influential Vampires Of The Imagination: [[Create Vampires/Authors Who Created Vampire Tropes]] 
|-
| [[Create Vampires/writers who did not create vampires| &quot;Writers Who Did Not Create Vampires&quot;]]
|-
|[[Create Vampires/Vampires In Poetry|Create Vampires/Vampires In Poetry - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Vampire Historic Fiction|Create Vampires/Vampire Historic Fiction - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Dracula|Create Vampires/Dracula - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Popular Are Vampires|Create Vampires/How Popular Are Vampires - Wikibooks, open books for an open world]]
|-
| Popular Culture: [[Create Vampires/Vampires In Popular Culture|Create Vampires/Vampires In Popular Culture - Wikibooks, open books for an open world]]
|-
| Vampire Memes? [[Create Vampires/Vampires Memes|Create Vampires/Vampires Memes - Wikibooks, open books for an open world]]
|-
|'''Are Vampires Real? Historical Construct''' [[Create Vampires/What Is A Historical Construct|Create Vampires/What Is A Historical Construct - Wikibooks, open books]]
|-
|[[Create Vampires/Factual Basis For Vampires]]
|-
|[[Create Vampires/Historical Construction|Create Vampires/Historical Construction - Wikibooks, open books for an open world]]
|-
|History of Vampires: [[Create Vampires/Vampire History]] 
|-
|  [[Create Vampires/Scientific Evidence| &quot;Science and Vampirism&quot;]]
|-
| For Vampires: [[Create Vampires/Scientific Evidence For Vampires| &quot;Scientific Evidence For Vampires&quot;]]
|-
| Against Vampires: [[Create Vampires/Scientific Evidence Against Vampirism| &quot;Scientific Evidence Against Vampires&quot;]]
|-
|- Are Vampires Real? Historical Construct
|-
| [[Create Vampires/Ethics Of Creating Vampire Lore|Create Vampires/Ethics Of Creating Vampire Lore - Wikibooks, open books for an open world]]
|-
| Closing: [[Create Vampires/All About Vampires|Create Vampires /All About Vampires - Wikibooks, open books for an open world]]
|-
| Information for Spanish speakers: [[:es:Vampiro|&quot;Vampiro&quot;]] 
|-
| Writing Vampire Prose: [[Create Vampires/Writing Vampire Prose| &quot;Writing Vampire Prose&quot;]]
|-
|Public Domain Primary Sources: [[Create Vampires/PublicDomainPrimarySources]]
|-
| [[:Category:Book:Create Vampires|List of All Pages in This Book]]
|}

== Reference ==


{{WikipediaCredit}}
&lt;br /&gt;
{{Shelves|Literature|Paranormal|Cultural anthropology}}
{{Status|75%}}</text>
      <sha1>mimjdxv5m7suxa4tqp9ra9q5sx5ev1u</sha1>
    </revision>
    <revision>
      <id>4678538</id>
      <parentid>4678537</parentid>
      <timestamp>2026-10-27T18:04:19Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678538</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7781" sha1="059f0jq0wf95apr4bhl87p3d8679hym" xml:space="preserve">
 &lt;br&gt;''Create Vampires'' is a book intended as a guide to avoid literary pitfalls, and as a nonfiction resource for those fascinated by vampires. This book examines vampires through a cultural, literary, and historical lens to help writers create authentic vampire narratives.

== Vampires ''Of The Imagination'' ==

Although vampires are creatures of folklore, monsters from the ''afterlife'' that are sometimes called the &quot;undead,&quot; vampires are uniquely different from ghost, those lingering spirits who refuse to die.

Although vampires, by definition, are animated corpses, most vampires ''of the imagination'' must feed on human blood in order to continue their earthly existence. This unique quality makes vampires a popular and original type of fiction, slightly different from other creatures found in folklore. Because of their unique characteristics, vampires have become massively popular in popular culture and in literature. 

We hope this book will clear up many misconceptions, and common misunderstandings associated with the &quot;undead,&quot; especially a common confusion ''about'' the actual people who did inspire vampire folklore, verses the evolved horror creations called vampires of the imagination.

'''Create Vampires''' aims to treat vampires as a cultural, literary and historical construct. Perhaps Create Vampires should be considered a friendly craft-manual for building a believable vampire concept, available across different medias.

== Preface: The Factual Roots Of Vampires ==
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! Factual Basis For Vampires?
|-
| [[/Factual Basis For Vampires/]] is a special page intended to offer information about the factual bases for vampires.
|}
&lt;br&gt;
 
'''What Type Of Book Is This?'''
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! '''Create Vampires''' is one of many free Wikibooks
|-
|  Wikibooks.org is a part of the Wikimedia project. Writers and contributors are volunteers who cull through websites, &lt;BR&gt; use online search engines to find facts, and volunteer to work on special projects that are open to the public. &lt;BR&gt; Volunteers are people who write, edit, and help people understand the powerful tools at their fingertips. &lt;br&gt;
|}
 &lt;br&gt; &quot;You shall not eat the blood of any flesh at all, because the life of the flesh is in the blood, and whosoever eateth it shall be cut off.&quot; - The Bible, Leviticus, chapter 17, verse 14. &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|-
! Edvard Munch - Love and Pain / Vampire (1895) || &quot;Les Vampires&quot;
|-
| [[File:Edvard Munch - Vampire (1895) - Google Art Project.jpg|thumb|Edvard Munch - Vampire (1895) - Google Art Project]] || [[File:Les vampires.jpg|thumb|Les vampires]]
|}


== All About Vampires ==
 '''Not All Links Work'''

{| class=&quot;wikitable&quot;
|-
! Table Of Content
|-
| Introduction: [[Create Vampires/Original Fictional Creations|&quot;Original Fictional Creations&quot;]]
|-
| Proper Spelling:  [[Create Vampires/Vam-Pai-Yer|&quot;How do you spell vampire?]]
|-
| [[Create Vampires/Alternative Spelling| &quot;Alternative Spellings&quot;]]
|-
| What ''Is'' A Vampire? [[Create Vampires/A Definition For Vampire|Create Vampires /A Definition For Vampire - Wikibooks, open books for an open world]]
|-
| Why Create A Vampire? : [[Create Vampires/Why Create Vampires|Create Vampires/Why Create Vampires - Wikibooks, open books for an open world]]
|-
|- '''Cultural Origins'''
|-
|'''Cultural Vampire Construct'''
|-
|What Is A Cultural Construct? - [[Create Vampires/Cultural Construct|Create Vampires/Cultural Construct - Wikibooks, open books for an open world]]
|-
| '''Vampire Folklore:''' [[Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes|Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes - Wikibooks]]
|-
| African Folklore: [[Create Vampires/African Folklore|Create Vampires/African Folklore - Wikibooks, open books for an open world]]
|-
| Latin-American Folklore: [[Create Vampires/Latin American Folklore|Create Vampires/Latin American Folklore - Wikibooks, open books for an open world]]
|-
| Asian Folklore: [[Create Vampires/Asian Folklore#Asian Folklore|Create Vampires/Asian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Asian Folklore Part Two|Create Vampires/Asian Folklore Part Two - Wikibooks, open books for an open world]]
|-
|Eastern Folklore: [[Create Vampires/Eastern European Folklore| &quot;Eastern European Folklore&quot;]]
|-
| Eastern Folklore: [[Create Vampires/Dracula Behind Vlad-The Impaler|Create Vampires/Dracula Behind Vlad-The Impaler - Wikibooks, open books for an open world]]
|-
|Oceanian Folklore: [[Create Vampires/Oceanian Folklore|Create Vampires/Oceanian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Cultural Traditions Shaped Vampire Traits|Create Vampires/How Cultural Traditions Shaped Vampire Traits - Wikibooks, open books for an open world]]
|-
|- '''Literary Construct'''
|-
|'''Literary Construct'''
|-
|[[Create Vampires/Literary Construction|Create Vampires/Literary Construction - Wikibooks, open books for an open world]]
|-
|What Is A Literary Trope? [[Create Vampires/What Is A Literary Trope]] 
|-
| Literary And Media Pitfalls To Avoid: [[Create Vampires/Examples Of Literary Pitfalls|Create Vampires/Examples Of Literary Pitfalls - Wikibooks, open books for an open world]]
|-
| Authors Who Created Influential Vampires Of The Imagination: [[Create Vampires/Authors Who Created Vampire Tropes]] 
|-
| [[Create Vampires/writers who did not create vampires| &quot;Writers Who Did Not Create Vampires&quot;]]
|-
|[[Create Vampires/Vampires In Poetry|Create Vampires/Vampires In Poetry - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Vampire Historic Fiction|Create Vampires/Vampire Historic Fiction - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Dracula|Create Vampires/Dracula - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Popular Are Vampires|Create Vampires/How Popular Are Vampires - Wikibooks, open books for an open world]]
|-
| Popular Culture: [[Create Vampires/Vampires In Popular Culture|Create Vampires/Vampires In Popular Culture - Wikibooks, open books for an open world]]
|-
| Vampire Memes? [[Create Vampires/Vampires Memes|Create Vampires/Vampires Memes - Wikibooks, open books for an open world]]
|-
|'''Are Vampires Real? Historical Construct''' [[Create Vampires/What Is A Historical Construct|Create Vampires/What Is A Historical Construct - Wikibooks, open books]]
|-
|[[Create Vampires/Factual Basis For Vampires]]
|-
|[[Create Vampires/Historical Construction|Create Vampires/Historical Construction - Wikibooks, open books for an open world]]
|-
|History of Vampires: [[Create Vampires/Vampire History]] 
|-
|  [[Create Vampires/Scientific Evidence| &quot;Science and Vampirism&quot;]]
|-
| For Vampires: [[Create Vampires/Scientific Evidence For Vampires| &quot;Scientific Evidence For Vampires&quot;]]
|-
| Against Vampires: [[Create Vampires/Scientific Evidence Against Vampirism| &quot;Scientific Evidence Against Vampires&quot;]]
|-
|- Are Vampires Real? Historical Construct
|-
| [[Create Vampires/Ethics Of Creating Vampire Lore|Create Vampires/Ethics Of Creating Vampire Lore - Wikibooks, open books for an open world]]
|-
|Women As Vampires: 
|-
| Closing: [[Create Vampires/All About Vampires|Create Vampires /All About Vampires - Wikibooks, open books for an open world]]
|-
| Information for Spanish speakers: [[:es:Vampiro|&quot;Vampiro&quot;]] 
|-
| Writing Vampire Prose: [[Create Vampires/Writing Vampire Prose| &quot;Writing Vampire Prose&quot;]]
|-
|Public Domain Primary Sources: [[Create Vampires/PublicDomainPrimarySources]]
|-
| [[:Category:Book:Create Vampires|List of All Pages in This Book]]
|}

== Reference ==


{{WikipediaCredit}}
&lt;br /&gt;
{{Shelves|Literature|Paranormal|Cultural anthropology}}
{{Status|75%}}</text>
      <sha1>059f0jq0wf95apr4bhl87p3d8679hym</sha1>
    </revision>
    <revision>
      <id>4678539</id>
      <parentid>4678538</parentid>
      <timestamp>2026-10-27T18:05:03Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678539</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7786" sha1="j45n3zp7e23q6bod6l4wvdytyfi2d7x" xml:space="preserve">
 &lt;br&gt;''Create Vampires'' is a book intended as a guide to avoid literary pitfalls, and as a nonfiction resource for those fascinated by vampires. This book examines vampires through a cultural, literary, and historical lens to help writers create authentic vampire narratives.

== Vampires ''Of The Imagination'' ==

Although vampires are creatures of folklore, monsters from the ''afterlife'' that are sometimes called the &quot;undead,&quot; vampires are uniquely different from ghost, those lingering spirits who refuse to die.

Although vampires, by definition, are animated corpses, most vampires ''of the imagination'' must feed on human blood in order to continue their earthly existence. This unique quality makes vampires a popular and original type of fiction, slightly different from other creatures found in folklore. Because of their unique characteristics, vampires have become massively popular in popular culture and in literature. 

We hope this book will clear up many misconceptions, and common misunderstandings associated with the &quot;undead,&quot; especially a common confusion ''about'' the actual people who did inspire vampire folklore, verses the evolved horror creations called vampires of the imagination.

'''Create Vampires''' aims to treat vampires as a cultural, literary and historical construct. Perhaps Create Vampires should be considered a friendly craft-manual for building a believable vampire concept, available across different medias.

== Preface: The Factual Roots Of Vampires ==
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! Factual Basis For Vampires?
|-
| [[/Factual Basis For Vampires/]] is a special page intended to offer information about the factual bases for vampires.
|}
&lt;br&gt;
 
'''What Type Of Book Is This?'''
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! '''Create Vampires''' is one of many free Wikibooks
|-
|  Wikibooks.org is a part of the Wikimedia project. Writers and contributors are volunteers who cull through websites, &lt;BR&gt; use online search engines to find facts, and volunteer to work on special projects that are open to the public. &lt;BR&gt; Volunteers are people who write, edit, and help people understand the powerful tools at their fingertips. &lt;br&gt;
|}
 &lt;br&gt; &quot;You shall not eat the blood of any flesh at all, because the life of the flesh is in the blood, and whosoever eateth it shall be cut off.&quot; - The Bible, Leviticus, chapter 17, verse 14. &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|-
! Edvard Munch - Love and Pain / Vampire (1895) || &quot;Les Vampires&quot;
|-
| [[File:Edvard Munch - Vampire (1895) - Google Art Project.jpg|thumb|Edvard Munch - Vampire (1895) - Google Art Project]] || [[File:Les vampires.jpg|thumb|Les vampires]]
|}


== All About Vampires ==
 '''Not All Links Work'''

{| class=&quot;wikitable&quot;
|-
! Table Of Content
|-
| Introduction: [[Create Vampires/Original Fictional Creations|&quot;Original Fictional Creations&quot;]]
|-
| Proper Spelling:  [[Create Vampires/Vam-Pai-Yer|&quot;How do you spell vampire?]]
|-
| [[Create Vampires/Alternative Spelling| &quot;Alternative Spellings&quot;]]
|-
| What ''Is'' A Vampire? [[Create Vampires/A Definition For Vampire|Create Vampires /A Definition For Vampire - Wikibooks, open books for an open world]]
|-
| Why Create A Vampire? : [[Create Vampires/Why Create Vampires|Create Vampires/Why Create Vampires - Wikibooks, open books for an open world]]
|-
|- '''Cultural Origins'''
|-
|'''Cultural Vampire Construct'''
|-
|What Is A Cultural Construct? - [[Create Vampires/Cultural Construct|Create Vampires/Cultural Construct - Wikibooks, open books for an open world]]
|-
| '''Vampire Folklore:''' [[Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes|Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes - Wikibooks]]
|-
| African Folklore: [[Create Vampires/African Folklore|Create Vampires/African Folklore - Wikibooks, open books for an open world]]
|-
| Latin-American Folklore: [[Create Vampires/Latin American Folklore|Create Vampires/Latin American Folklore - Wikibooks, open books for an open world]]
|-
| Asian Folklore: [[Create Vampires/Asian Folklore#Asian Folklore|Create Vampires/Asian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Asian Folklore Part Two|Create Vampires/Asian Folklore Part Two - Wikibooks, open books for an open world]]
|-
|Eastern Folklore: [[Create Vampires/Eastern European Folklore| &quot;Eastern European Folklore&quot;]]
|-
| Eastern Folklore: [[Create Vampires/Dracula Behind Vlad-The Impaler|Create Vampires/Dracula Behind Vlad-The Impaler - Wikibooks, open books for an open world]]
|-
|Oceanian Folklore: [[Create Vampires/Oceanian Folklore|Create Vampires/Oceanian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Cultural Traditions Shaped Vampire Traits|Create Vampires/How Cultural Traditions Shaped Vampire Traits - Wikibooks, open books for an open world]]
|-
|- '''Literary Construct'''
|-
|'''Literary Construct'''
|-
|[[Create Vampires/Literary Construction|Create Vampires/Literary Construction - Wikibooks, open books for an open world]]
|-
|What Is A Literary Trope? [[Create Vampires/What Is A Literary Trope]] 
|-
| Literary And Media Pitfalls To Avoid: [[Create Vampires/Examples Of Literary Pitfalls|Create Vampires/Examples Of Literary Pitfalls - Wikibooks, open books for an open world]]
|-
| Authors Who Created Influential Vampires Of The Imagination: [[Create Vampires/Authors Who Created Vampire Tropes]] 
|-
| [[Create Vampires/writers who did not create vampires| &quot;Writers Who Did Not Create Vampires&quot;]]
|-
|[[Create Vampires/Vampires In Poetry|Create Vampires/Vampires In Poetry - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Vampire Historic Fiction|Create Vampires/Vampire Historic Fiction - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Dracula|Create Vampires/Dracula - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Popular Are Vampires|Create Vampires/How Popular Are Vampires - Wikibooks, open books for an open world]]
|-
| Popular Culture: [[Create Vampires/Vampires In Popular Culture|Create Vampires/Vampires In Popular Culture - Wikibooks, open books for an open world]]
|-
| Vampire Memes? [[Create Vampires/Vampires Memes|Create Vampires/Vampires Memes - Wikibooks, open books for an open world]]
|-
|'''Are Vampires Real? Historical Construct''' [[Create Vampires/What Is A Historical Construct|Create Vampires/What Is A Historical Construct - Wikibooks, open books]]
|-
|[[Create Vampires/Factual Basis For Vampires]]
|-
|[[Create Vampires/Historical Construction|Create Vampires/Historical Construction - Wikibooks, open books for an open world]]
|-
|History of Vampires: [[Create Vampires/Vampire History]] 
|-
|  [[Create Vampires/Scientific Evidence| &quot;Science and Vampirism&quot;]]
|-
| For Vampires: [[Create Vampires/Scientific Evidence For Vampires| &quot;Scientific Evidence For Vampires&quot;]]
|-
| Against Vampires: [[Create Vampires/Scientific Evidence Against Vampirism| &quot;Scientific Evidence Against Vampires&quot;]]
|-
|- Are Vampires Real? Historical Construct
|-
| [[Create Vampires/Ethics Of Creating Vampire Lore|Create Vampires/Ethics Of Creating Vampire Lore - Wikibooks, open books for an open world]]
|-
|'''Women As Vampires:'''
|-
| Closing: [[Create Vampires/All About Vampires|Create Vampires /All About Vampires - Wikibooks, open books for an open world]]
|-
| Information for Spanish speakers: [[:es:Vampiro|&quot;Vampiro&quot;]] 
|-
| Writing Vampire Prose: [[Create Vampires/Writing Vampire Prose| &quot;Writing Vampire Prose&quot;]]
|-
|Public Domain Primary Sources: [[Create Vampires/PublicDomainPrimarySources]]
|-
| [[:Category:Book:Create Vampires|List of All Pages in This Book]]
|}

== Reference ==


{{WikipediaCredit}}
&lt;br /&gt;
{{Shelves|Literature|Paranormal|Cultural anthropology}}
{{Status|75%}}</text>
      <sha1>j45n3zp7e23q6bod6l4wvdytyfi2d7x</sha1>
    </revision>
    <revision>
      <id>4678541</id>
      <parentid>4678539</parentid>
      <timestamp>2026-10-27T18:06:11Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678541</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7777" sha1="ltpdhn67ok0zkbp28brwy6acuu3jj1n" xml:space="preserve">
 &lt;br&gt;''Create Vampires'' is a book intended as a guide to avoid literary pitfalls, and as a nonfiction resource for those fascinated by vampires. This book examines vampires through a cultural, literary, and historical lens to help writers create authentic vampire narratives.

== Vampires ''Of The Imagination'' ==

Although vampires are creatures of folklore, monsters from the ''afterlife'' that are sometimes called the &quot;undead,&quot; vampires are uniquely different from ghost, those lingering spirits who refuse to die.

Although vampires, by definition, are animated corpses, most vampires ''of the imagination'' must feed on human blood in order to continue their earthly existence. This unique quality makes vampires a popular and original type of fiction, slightly different from other creatures found in folklore. Because of their unique characteristics, vampires have become massively popular in popular culture and in literature. 

We hope this book will clear up many misconceptions, and common misunderstandings associated with the &quot;undead,&quot; especially a common confusion ''about'' the actual people who did inspire vampire folklore, verses the evolved horror creations called vampires of the imagination.

'''Create Vampires''' aims to treat vampires as a cultural, literary and historical construct. Perhaps Create Vampires should be considered a friendly craft-manual for building a believable vampire concept, available across different medias.

== Preface: The Factual Roots Of Vampires ==
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! Factual Basis For Vampires?
|-
| [[/Factual Basis For Vampires/]] is a special page intended to offer information about the factual bases for vampires.
|}
&lt;br&gt;
 
'''What Type Of Book Is This?'''
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! '''Create Vampires''' is one of many free Wikibooks
|-
|  Wikibooks.org is a part of the Wikimedia project. Writers and contributors are volunteers who cull through websites, &lt;BR&gt; use online search engines to find facts, and volunteer to work on special projects that are open to the public. &lt;BR&gt; Volunteers are people who write, edit, and help people understand the powerful tools at their fingertips. &lt;br&gt;
|}
 &lt;br&gt; &quot;You shall not eat the blood of any flesh at all, because the life of the flesh is in the blood, and whosoever eateth it shall be cut off.&quot; - The Bible, Leviticus, chapter 17, verse 14. &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|-
! Edvard Munch - Love and Pain / Vampire (1895) || &quot;Les Vampires&quot;
|-
| [[File:Edvard Munch - Vampire (1895) - Google Art Project.jpg|thumb|Edvard Munch - Vampire (1895) - Google Art Project]] || [[File:Les vampires.jpg|thumb|Les vampires]]
|}


== All About Vampires ==
 '''Not All Links Work'''

{| class=&quot;wikitable&quot;
|-
! Table Of Content
|-
| Introduction: [[Create Vampires/Original Fictional Creations|&quot;Original Fictional Creations&quot;]]
|-
| Proper Spelling:  [[Create Vampires/Vam-Pai-Yer|&quot;How do you spell vampire?]]
|-
| [[Create Vampires/Alternative Spelling| &quot;Alternative Spellings&quot;]]
|-
| What ''Is'' A Vampire? [[Create Vampires/A Definition For Vampire|Create Vampires /A Definition For Vampire - Wikibooks, open books for an open world]]
|-
| Why Create A Vampire? : [[Create Vampires/Why Create Vampires|Create Vampires/Why Create Vampires - Wikibooks, open books for an open world]]
|-
|- '''Cultural Origins'''
|-
|'''Cultural Vampire Construct'''
|-
|What Is A Cultural Construct? - [[Create Vampires/Cultural Construct|Create Vampires/Cultural Construct - Wikibooks, open books for an open world]]
|-
| '''Vampire Folklore:''' [[Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes|Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes - Wikibooks]]
|-
| African Folklore: [[Create Vampires/African Folklore|Create Vampires/African Folklore - Wikibooks, open books for an open world]]
|-
| Latin-American Folklore: [[Create Vampires/Latin American Folklore|Create Vampires/Latin American Folklore - Wikibooks, open books for an open world]]
|-
| Asian Folklore: [[Create Vampires/Asian Folklore#Asian Folklore|Create Vampires/Asian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Asian Folklore Part Two|Create Vampires/Asian Folklore Part Two - Wikibooks, open books for an open world]]
|-
|Eastern Folklore: [[Create Vampires/Eastern European Folklore| &quot;Eastern European Folklore&quot;]]
|-
| Eastern Folklore: [[Create Vampires/Dracula Behind Vlad-The Impaler|Create Vampires/Dracula Behind Vlad-The Impaler - Wikibooks, open books for an open world]]
|-
|Oceanian Folklore: [[Create Vampires/Oceanian Folklore|Create Vampires/Oceanian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Cultural Traditions Shaped Vampire Traits|Create Vampires/How Cultural Traditions Shaped Vampire Traits - Wikibooks, open books for an open world]]
|-
|- '''Literary Construct'''
|-
|'''Literary Construct'''
|-
|[[Create Vampires/Literary Construction|Create Vampires/Literary Construction - Wikibooks, open books for an open world]]
|-
|What Is A Literary Trope? [[Create Vampires/What Is A Literary Trope]] 
|-
| Literary And Media Pitfalls To Avoid: [[Create Vampires/Examples Of Literary Pitfalls|Create Vampires/Examples Of Literary Pitfalls - Wikibooks, open books for an open world]]
|-
| Authors Who Created Influential Vampires Of The Imagination: [[Create Vampires/Authors Who Created Vampire Tropes]] 
|-
| [[Create Vampires/writers who did not create vampires| &quot;Writers Who Did Not Create Vampires&quot;]]
|-
|[[Create Vampires/Vampires In Poetry|Create Vampires/Vampires In Poetry - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Vampire Historic Fiction|Create Vampires/Vampire Historic Fiction - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Dracula|Create Vampires/Dracula - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Popular Are Vampires|Create Vampires/How Popular Are Vampires - Wikibooks, open books for an open world]]
|-
| Popular Culture: [[Create Vampires/Vampires In Popular Culture|Create Vampires/Vampires In Popular Culture - Wikibooks, open books for an open world]]
|-
| Vampire Memes? [[Create Vampires/Vampires Memes|Create Vampires/Vampires Memes - Wikibooks, open books for an open world]]
|-
|'''Are Vampires Real? Historical Construct''' [[Create Vampires/What Is A Historical Construct|Create Vampires/What Is A Historical Construct - Wikibooks, open books]]
|-
|[[Create Vampires/Factual Basis For Vampires]]
|-
|[[Create Vampires/Historical Construction|Create Vampires/Historical Construction - Wikibooks, open books for an open world]]
|-
|History of Vampires: [[Create Vampires/Vampire History]] 
|-
|  [[Create Vampires/Scientific Evidence| &quot;Science and Vampirism&quot;]]
|-
| For Vampires: [[Create Vampires/Scientific Evidence For Vampires| &quot;Scientific Evidence For Vampires&quot;]]
|-
| Against Vampires: [[Create Vampires/Scientific Evidence Against Vampirism| &quot;Scientific Evidence Against Vampires&quot;]]
|-
|- Are Vampires Real? Historical Construct
|-
| [[Create Vampires/Ethics Of Creating Vampire Lore|Create Vampires/Ethics Of Creating Vampire Lore - Wikibooks, open books for an open world]]
|-
|'''Women As Vampires:'''
|-
| Closing: [[Create Vampires/All About Vampires|Create Vampires /All About Vampires - Wikibooks, open books for an open world]]
|-
| Information for Spanish speakers: [[:es:Vampiro|&quot;Vampiro&quot;]] 
|-
| Writing Tips: [[Create Vampires/Writing Vampire Prose| &quot;Writing Vampire Prose&quot;]]
|-
|Public Domain Primary Sources: [[Create Vampires/PublicDomainPrimarySources]]
|-
| [[:Category:Book:Create Vampires|List of All Pages in This Book]]
|}

== Reference ==


{{WikipediaCredit}}
&lt;br /&gt;
{{Shelves|Literature|Paranormal|Cultural anthropology}}
{{Status|75%}}</text>
      <sha1>ltpdhn67ok0zkbp28brwy6acuu3jj1n</sha1>
    </revision>
    <revision>
      <id>4678615</id>
      <parentid>4678541</parentid>
      <timestamp>2026-10-27T21:15:12Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678615</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7891" sha1="qzh50j51mp318t59fv861lxjeky777w" xml:space="preserve">
 &lt;br&gt;''Create Vampires'' is a book intended as a guide to avoid literary pitfalls, and as a nonfiction resource for those fascinated by vampires. This book examines vampires through a cultural, literary, and historical lens to help writers create authentic vampire narratives.

== Vampires ''Of The Imagination'' ==

Although vampires are creatures of folklore, monsters from the ''afterlife'' that are sometimes called the &quot;undead,&quot; vampires are uniquely different from ghost, those lingering spirits who refuse to die.

Although vampires, by definition, are animated corpses, most vampires ''of the imagination'' must feed on human blood in order to continue their earthly existence. This unique quality makes vampires a popular and original type of fiction, slightly different from other creatures found in folklore. Because of their unique characteristics, vampires have become massively popular in popular culture and in literature. 

We hope this book will clear up many misconceptions, and common misunderstandings associated with the &quot;undead,&quot; especially a common confusion ''about'' the actual people who did inspire vampire folklore, verses the evolved horror creations called vampires of the imagination.

'''Create Vampires''' aims to treat vampires as a cultural, literary and historical construct. Perhaps Create Vampires should be considered a friendly craft-manual for building a believable vampire concept, available across different medias.

== Preface: The Factual Roots Of Vampires ==
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! Factual Basis For Vampires?
|-
| [[/Factual Basis For Vampires/]] is a special page intended to offer information about the factual bases for vampires.
|}
&lt;br&gt;
 
'''What Type Of Book Is This?'''
&lt;br /&gt;
{| class=&quot;wikitable&quot;
|-
! '''Create Vampires''' is one of many free Wikibooks
|-
|  Wikibooks.org is a part of the Wikimedia project. Writers and contributors are volunteers who cull through websites, &lt;BR&gt; use online search engines to find facts, and volunteer to work on special projects that are open to the public. &lt;BR&gt; Volunteers are people who write, edit, and help people understand the powerful tools at their fingertips. &lt;br&gt;
|}
 &lt;br&gt; &quot;You shall not eat the blood of any flesh at all, because the life of the flesh is in the blood, and whosoever eateth it shall be cut off.&quot; - The Bible, Leviticus, chapter 17, verse 14. &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|-
! Edvard Munch - Love and Pain / Vampire (1895) || &quot;Les Vampires&quot;
|-
| [[File:Edvard Munch - Vampire (1895) - Google Art Project.jpg|thumb|Edvard Munch - Vampire (1895) - Google Art Project]] || [[File:Les vampires.jpg|thumb|Les vampires]]
|}


== All About Vampires ==
 '''Not All Links Work'''

{| class=&quot;wikitable&quot;
|-
! Table Of Content
|-
| Introduction: [[Create Vampires/Original Fictional Creations|&quot;Original Fictional Creations&quot;]]
|-
| Proper Spelling:  [[Create Vampires/Vam-Pai-Yer|&quot;How do you spell vampire?]]
|-
| [[Create Vampires/Alternative Spelling| &quot;Alternative Spellings&quot;]]
|-
| What ''Is'' A Vampire? [[Create Vampires/A Definition For Vampire|Create Vampires /A Definition For Vampire - Wikibooks, open books for an open world]]
|-
| Why Create A Vampire? : [[Create Vampires/Why Create Vampires|Create Vampires/Why Create Vampires - Wikibooks, open books for an open world]]
|-
|- '''Cultural Origins'''
|-
|'''Cultural Vampire Construct'''
|-
|What Is A Cultural Construct? - [[Create Vampires/Cultural Construct|Create Vampires/Cultural Construct - Wikibooks, open books for an open world]]
|-
| '''Vampire Folklore:''' [[Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes|Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes - Wikibooks]]
|-
| African Folklore: [[Create Vampires/African Folklore|Create Vampires/African Folklore - Wikibooks, open books for an open world]]
|-
| Latin-American Folklore: [[Create Vampires/Latin American Folklore|Create Vampires/Latin American Folklore - Wikibooks, open books for an open world]]
|-
| Asian Folklore: [[Create Vampires/Asian Folklore#Asian Folklore|Create Vampires/Asian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Asian Folklore Part Two|Create Vampires/Asian Folklore Part Two - Wikibooks, open books for an open world]]
|-
|Eastern Folklore: [[Create Vampires/Eastern European Folklore| &quot;Eastern European Folklore&quot;]]
|-
| Eastern Folklore: [[Create Vampires/Dracula Behind Vlad-The Impaler|Create Vampires/Dracula Behind Vlad-The Impaler - Wikibooks, open books for an open world]]
|-
|Oceanian Folklore: [[Create Vampires/Oceanian Folklore|Create Vampires/Oceanian Folklore - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Cultural Traditions Shaped Vampire Traits|Create Vampires/How Cultural Traditions Shaped Vampire Traits - Wikibooks, open books for an open world]]
|-
|- '''Literary Construct'''
|-
|'''Literary Construct'''
|-
|[[Create Vampires/Literary Construction|Create Vampires/Literary Construction - Wikibooks, open books for an open world]]
|-
|What Is A Literary Trope? [[Create Vampires/What Is A Literary Trope]] 
|-
| Literary And Media Pitfalls To Avoid: [[Create Vampires/Examples Of Literary Pitfalls|Create Vampires/Examples Of Literary Pitfalls - Wikibooks, open books for an open world]]
|-
| Authors Who Created Influential Vampires Of The Imagination: [[Create Vampires/Authors Who Created Vampire Tropes]] 
|-
| [[Create Vampires/writers who did not create vampires| &quot;Writers Who Did Not Create Vampires&quot;]]
|-
|[[Create Vampires/Vampires In Poetry|Create Vampires/Vampires In Poetry - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Vampire Historic Fiction|Create Vampires/Vampire Historic Fiction - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/Dracula|Create Vampires/Dracula - Wikibooks, open books for an open world]]
|-
|[[Create Vampires/How Popular Are Vampires|Create Vampires/How Popular Are Vampires - Wikibooks, open books for an open world]]
|-
| Popular Culture: [[Create Vampires/Vampires In Popular Culture|Create Vampires/Vampires In Popular Culture - Wikibooks, open books for an open world]]
|-
| Vampire Memes? [[Create Vampires/Vampires Memes|Create Vampires/Vampires Memes - Wikibooks, open books for an open world]]
|-
|'''Are Vampires Real? Historical Construct''' [[Create Vampires/What Is A Historical Construct|Create Vampires/What Is A Historical Construct - Wikibooks, open books]]
|-
|[[Create Vampires/Factual Basis For Vampires]]
|-
|[[Create Vampires/Historical Construction|Create Vampires/Historical Construction - Wikibooks, open books for an open world]]
|-
|History of Vampires: [[Create Vampires/Vampire History]] 
|-
|  [[Create Vampires/Scientific Evidence| &quot;Science and Vampirism&quot;]]
|-
| For Vampires: [[Create Vampires/Scientific Evidence For Vampires| &quot;Scientific Evidence For Vampires&quot;]]
|-
| Against Vampires: [[Create Vampires/Scientific Evidence Against Vampirism| &quot;Scientific Evidence Against Vampires&quot;]]
|-
|- Are Vampires Real? Historical Construct
|-
| [[Create Vampires/Ethics Of Creating Vampire Lore|Create Vampires/Ethics Of Creating Vampire Lore - Wikibooks, open books for an open world]]
|-
|'''Women As Vampires:''' [[Create Vampires/Women As Vampires|Create Vampires/Women As Vampires - Wikibooks, open books for an open world]]
|-
| Closing: [[Create Vampires/All About Vampires|Create Vampires /All About Vampires - Wikibooks, open books for an open world]]
|-
| Information for Spanish speakers: [[:es:Vampiro|&quot;Vampiro&quot;]] 
|-
| Writing Tips: [[Create Vampires/Writing Vampire Prose| &quot;Writing Vampire Prose&quot;]]
|-
|Public Domain Primary Sources: [[Create Vampires/PublicDomainPrimarySources]]
|-
| [[:Category:Book:Create Vampires|List of All Pages in This Book]]
|}

== Reference ==


{{WikipediaCredit}}
&lt;br /&gt;
{{Shelves|Literature|Paranormal|Cultural anthropology}}
{{Status|75%}}</text>
      <sha1>qzh50j51mp318t59fv861lxjeky777w</sha1>
    </revision>
  </page>
  <page>
    <title>Create Vampires/Factual Basis For Vampires</title>
    <ns>0</ns>
    <id>415670</id>
    <revision>
      <id>4678495</id>
      <parentid>4678414</parentid>
      <timestamp>2026-10-27T14:25:48Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678495</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1638" sha1="hlx35ac20xd188p6qa95qi0kpfutbc8" xml:space="preserve">== Create Vampires: Factual Basis For Vampires ==
People have offered factual explanations for the &quot;un-dead,&quot; plausible reasons for vampires found mostly in folklore. &lt;br&gt;
Folk-stories were based on people buried alive, &lt;u&gt;''then mistaken''&lt;/u&gt; for un-dead creatures when they clawed and crawled their way from their premature graves. &lt;br&gt;
The appearance of actual people, mistaken for dead, crawling from graves, started warnings that evolved into what we call the vampire stories and folklores that influence our modern popular culture.  &lt;br&gt;
&lt;br&gt;
Premature burial is the most popular explanation for vampire sightings and reports. As early as the eighteenth century, many Physicians knew of catalepsy, a disease in which the affected person appears dead. Occasionally, people suffering from this disease may have been buried before they awakened. &lt;br&gt;
&lt;br&gt;
Herbert Mayo argues for this theory in his ''On the Truths Contained in Popular Superstitions'' (1851). Other noted scholars who argued for the plausibility of premature burials as the root of vampire stories include Franz Hartmann, Montague Summers and Anthony Masters. [1]  
&lt;br&gt;
&lt;br&gt;

LINK: [[Create Vampires/Vampire History]]
 
&lt;br&gt;
LINK: [[Create Vampires/Original Fictional Creations]]&lt;br&gt;
&lt;br&gt;
LINK:[[Create_Vampires/Scientific_Evidence]] &lt;br&gt;
&lt;br&gt;
LINK:[[Create_Vampires/Scientific_Evidence_For_Vampires]]
&lt;br&gt;
&lt;br&gt;
==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia of The Undead [Third Edition], Visible Ink Press, 2014.
&lt;br&gt;
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Historical Construction|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;

{{BookCat}}</text>
      <sha1>hlx35ac20xd188p6qa95qi0kpfutbc8</sha1>
    </revision>
  </page>
  <page>
    <title>Infrastructure Past, Present, and Future Casebook</title>
    <ns>0</ns>
    <id>437837</id>
    <revision>
      <id>4678508</id>
      <parentid>4672315</parentid>
      <timestamp>2026-10-27T15:54:01Z</timestamp>
      <contributor>
        <username>JGiffordAtMason</username>
        <id>3358507</id>
      </contributor>
      <minor />
      <comment>Update Fall 2026 case list to Glenwood Canyon</comment>
      <origin>4678508</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4926" sha1="taxro84qbe8i8d76sd0ndwvnbrl9q2v" xml:space="preserve">== Introduction ==
[[File:Nordportal Gotthard-Basistunnel.jpg|thumb|1024px|Gotthard Base Tunnel]]
This Casebook contains a set of case studies developed by students enrolled in the '''Infrastructure Past, Present and Future''' ('''CEIE 499''': Special Topics in '''Civil Engineering''' / '''GOVT 490''': Synthesis Seminar for '''Policy and Government''') course taught at George Mason University's [[wikipedia:Schar School of Policy and Government|Schar School of Policy and Government]] and the [https://civil.gmu.edu Sid and Reva Dewberry Department of Civil, Environmental, and Infrastructure Engineering] by Prof. Jonathan Gifford.

== Cases ==

== Fall 2026 Case Studies ==

* [[Infrastructure Past, Present, and Future/Loudoun County Data Centers|Loudoun County Data Centers]]
* [[Infrastructure Past, Present, and Future/Glenwood Canyon|Glenwood Canyon]]
* [[Infrastructure Past, Present, and Future/Puerto Rico Electric Power System|Puerto Rico Electric Power System]]

=== 2026 (Spring) ===

* [[Infrastructure Past, Present, and Future Casebook/Erie Canal|Erie Canal]]
* [[Infrastructure Past, Present, and Future Casebook/Washington Metro|Washington Metro]]
* [[Infrastructure Past, Present, and Future Casebook/Three Gorges Dam|Three Gorges Dam]]
* [[Infrastructure Past, Present, and Future Casebook/Gateway Project|Gateway Project]]

=== 2025 (Fall) ===

* [[Infrastructure Past, Present, and Future Casebook/Heathrow 3rd Runway (UK)|Heathrow 3rd Runway (UK)]]
* [[Infrastructure Past, Present, and Future Casebook/Norway Floating Highway|Norway Floating Highway]]
* [[Infrastructure Past, Present, and Future Casebook/NYC Water Tunnel No. 3 (USA)|NYC Water Tunnel No. 3 (USA)]]
* [[Infrastructure Past, Present, and Future Casebook/DC Clean Rivers Project (USA)|DC Clean Rivers Project (USA)]]
* [[Infrastructure Past, Present, and Future Casebook/Plant Vogtle Units 3 &amp; 4 (Georgia, USA)|Plant Vogtle Units 3 &amp; 4 (Georgia, USA)]]

=== 2025 (Spring) ===

* [[Infrastructure Past, Present, and Future Casebook/Chesapeake Bay Bridge Tunnel|Chesapeake Bay Bridge Tunnel]]
* [[Infrastructure Past, Present, and Future Casebook/2Africa Cable|2Africa Cable]]
* [[Infrastructure Past, Present, and Future Casebook/Three Mile Island|Three Mile Island]]
* [[Infrastructure Past, Present, and Future Casebook/Santa Ynez Reservoir|Santa Ynez Reservoir]]
* [[Infrastructure Past, Present, and Future Casebook/Unita Basin Railway|Unita Basin Railway]]

=== 2024 (Fall) ===
* [[Infrastructure Past, Present, and Future Casebook/JFK Terminal One|JFK Terminal One]]
* [[Infrastructure Past, Present, and Future Casebook/South Fork Wind Farm|South Fork Wind Farm]]
* [[Infrastructure Past, Present, and Future Casebook/Hambantota Port, Sri Lanka|Hambantota Port, Sri Lanka]]
=== 2024 (Spring) ===
* [[Infrastructure Past, Present, and Future Casebook/Skyline Drive|Skyline Drive]]
* [[Infrastructure Past, Present, and Future Casebook/Port Miami Tunnel|Port Miami Tunnel]]
* [[Infrastructure Past, Present, and Future Casebook/Metro Flood Diversion (MN/ND)|Metro Flood Diversion (MN/ND)]]
* [[Infrastructure Past, Present, and Future Casebook/Viet Cong Tunnel Network|Viet Cong Tunnel Network]]
* [[Infrastructure Past, Present, and Future Casebook/Long Bridge|Long Bridge]]
* [[Infrastructure Past, Present, and Future Casebook/PJM Interconnection|PJM Interconnection]]

=== 2023 (Fall) ===
* [[Infrastructure Past, Present, and Future Casebook/Mississippi River Locks and Dams|Mississippi River Locks and Dams]]
*  [[Infrastructure Past, Present, and Future Casebook/5.9 GHz Spectrum|5.9 GHz Spectrum]]
*  [[Infrastructure Past, Present, and Future Casebook/Texas Power Grid|Texas Power Grid]]
* [[Infrastructure Past, Present, and Future Casebook/Guangzhou South Railway Station|Guangzhou South Railway Station]]
* [[Infrastructure Past, Present, and Future Casebook/Jackson, MS Water and Wastewater Treatment|Jackson, MS Water and Wastewater Treatment]]
*  [[Infrastructure Past, Present, and Future Casebook/U.S./Mexico Border Infrastructure|U.S./Mexico Border Infrastructure]]

=== 2023 (Spring) ===
* [[/Automatic Dependent Surveillance-Broadcast (ADS-B)/]]
* [[Infrastructure Past, Present, and Future Casebook/GPS: Global Positioning System|GPS: Global Positioning System]]
* [[Infrastructure Past, Present, and Future Casebook/Oroville Dam|Oroville Dam Failure]]
* [[/Finnish Underground/]]

=== 2022 (Fall) ===
* [[/Shinkansen High Speed Rail/]]

{{shelves|Civil engineering|George Mason University projects}}
{{Status|75%}}
* [[/Port of Newport News/]]
* [[/Brightline Rail System/]]
* [[/Central Park/]]
* [[/Venetian Flood Control (MOSE)/]]

=== 2022 (Spring) ===
* [[/Dutch Dikes/]]
* [[/Big Dig/]]
* [[/Gotthard Base Tunnel/]]
* [[/Air Traffic Control System/]]

===2021 (Fall)===
* [[/New Orleans Levees/]]
* [[/Transcontinental Railroad/]]
* [[/Maginot Line/]]
* [[/Channel Tunnel/]]
* [[/Hoover Dam/]]__NOTOC__</text>
      <sha1>taxro84qbe8i8d76sd0ndwvnbrl9q2v</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna.js</title>
    <ns>2</ns>
    <id>471466</id>
    <revision>
      <id>4678647</id>
      <parentid>4676663</parentid>
      <timestamp>2026-10-28T03:30:53Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>removing user rights error until [[phab:T442667]] is resolved (my 5000th edit!!!!!)</comment>
      <origin>4678647</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="7298" sha1="ll0eks2yf2gwc9cjtl8aempedqyv6su" xml:space="preserve">const summaryAd = &quot; (using [[:b:en:Wikibooks:WikiProject Little Star/Luna|Luna]])&quot;;

window.isPatroller = true;
var myRights = [];

window.LunaLinks = [];
window.LunaRendered = false;
window.addLunaLink = function(link) {
    window.LunaLinks.push(link);
	document.dispatchEvent(new CustomEvent(&quot;luna-link-added&quot;, {
        detail: link
    }));
	console.log(&quot;Luna: link added&quot;, link.id, performance.now());
	return window.LunaLinks;
};
window.addLunaLinks = function(arr) {
    for (let i of arr) {
		window.addLunaLink(i);
	}
	return window.LunaLinks;
};

console.log(&quot;Luna: Script started.&quot;);

mw.loader.load('//en.wikipedia.org/w/load.php?modules=ext.gadget.morebits');

async function loadScripts() {
    const scripts = [
        'User:JJPMaster/luna/CurateThisPage.js', // Backlink: [[User:JJPMaster/luna/CurateThisPage.js]]
        'User:JJPMaster/luna/rfd.js', // Backlink: [[User:JJPMaster/luna/rfd.js]]
        'User:JJPMaster/luna/warn.js', // Backlink: [[User:JJPMaster/luna/warn.js]]
        'User:JJPMaster/luna/talkback.js', // Backlink: [[User:JJPMaster/luna/talkback.js]]
        'User:JJPMaster/luna/welcome.js', // Backlink: [[User:JJPMaster/luna/welcome.js]]
        'User:JJPMaster/luna/arv.js', // Backlink: [[User:JJPMaster/luna/arv.js]]
        'User:JJPMaster/luna/unlink.js', // Backlink: [[User:JJPMaster/luna/unlink.js]]
        'User:JJPMaster/luna/fileunlink.js', // Backlink: [[User:JJPMaster/luna/fileunlink.js]]
        'User:JJPMaster/luna/csd.js', // Backlink: [[User:JJPMaster/luna/csd.js]]
        'User:JJPMaster/luna/diff.js', // Backlink: [[User:JJPMaster/luna/diff.js]]
        'User:JJPMaster/luna/raddewikify.js', // Backlink: [[User:JJPMaster/luna/raddewikify.js]]
        'User:JJPMaster/luna/rpp.js', // Backlink: [[User:JJPMaster/luna/rpp.js]]
        'User:JJPMaster/luna/CurateThisFile.js', // Backlink: [[User:JJPMaster/luna/CurateThisFile.js]]
        'User:JJPMaster/luna/di.js', // Backlink: [[User:JJPMaster/luna/di.js]]
        'User:JJPMaster/luna/templateunlink.js', // Backlink: [[User:JJPMaster/luna/templateunlink.js]]
        'User:JJPMaster/luna/rollback.js' // Backlink: [[User:JJPMaster/luna/rollback.js]]
    ];

    if (myRights.includes(&quot;delete&quot;)) {
		await $.getScript('/w/index.php?title=User:JJPMaster/luna/d-batch/core.js&amp;action=raw&amp;ctype=text/javascript'), // Backlink: [[User:JJPMaster/luna/d-batch/core.js]]&quot;)
		await $.getScript(`/w/index.php?title=User:JJPMaster/htmlparserfromhell.js&amp;action=raw&amp;ctype=text/javascript`); // Backlink: [[User:JJPMaster/htmlparserfromhell.js]]
        scripts.push(
			'User:JJPMaster/luna/d-batch/links.js', // Backlink: [[User:JJPMaster/luna/d-batch/links.js]]
			'User:JJPMaster/luna/d-batch/cat.js', // Backlink: [[User:JJPMaster/luna/d-batch/cat.js]]
			'User:JJPMaster/luna/d-batch/prefix.js', // Backlink: [[User:JJPMaster/luna/d-batch/prefix.js]]
			'User:JJPMaster/luna/und-batch.js' // Backlink: [[User:JJPMaster/luna/und-batch.js]]
		);
    }

    console.log(&quot;Luna: Loading scripts...&quot;);
    
    await Promise.all(scripts.map(script =&gt; {
		const start = performance.now();
        return $.getScript(`/w/index.php?title=${script}&amp;action=raw&amp;ctype=text/javascript`)
        .then(() =&gt; console.log(`Luna: Loaded ${script} in ${performance.now() - start}ms.`))
        .catch(error =&gt; console.error(`Luna: Failed to load ${script}:`, error))
		}
    ));

    console.log(&quot;Luna: All scripts loaded successfully.&quot;);
}
async function waitForPreferences(maxRetries = 10, delay = 200) {
    for (let i = 0; i &lt; maxRetries; i++) {
        if (typeof Luna !== &quot;undefined&quot; &amp;&amp; Luna.myPreferences &amp;&amp; Luna.myPreferences.CSD) {
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
            return true;
        }
        console.warn(&quot;Luna: Preferences not loaded yet, retrying...&quot;);
        await new Promise(resolve =&gt; setTimeout(resolve, delay));
    }
    console.error(&quot;Luna: Preferences failed to load after multiple attempts.&quot;);
    return false;
}
function renderLunaPortlet() {
	const order = [
		'luna-arv',
		'luna-warn',
		'luna-welcome',
		'luna-welcome-anon',
		'luna-tb',
		'luna-rev',
		'luna-csd',
		'luna-rfd',
		'luna-di',
		'luna-qrb',
		'luna-rpp',
		'luna-dbatch-links',
		'luna-dbatch-prefix',
		'luna-dbatch-cat',
		'luna-undbatch',
		'luna-ctf',
		'luna-ctp',
		'luna-last',
		'luna-since',
		'luna-sincemine',
		'luna-current',
		'luna-dewiki',
		'luna-unlink',
		'luna-fileunlink',
		'luna-tempunlink',
		'luna-debug-link'
	];
	console.log(&quot;Luna: rendering at&quot;, performance.now());
	order.forEach(id =&gt; {
		const i = window.LunaLinks.find(l =&gt; l.id == id);
		if (!i) return;
		const text = i.debug &amp;&amp; Luna.myPreferences?.debug ? `${i.text} [DEBUG]` : i.text;
		const l = mw.util.addPortletLink('luna-actions', i.href, text, i.id, i.tooltip)
		
		if (i.onClick) {
			$(l).on('click', i.onClick);
		}
	});
	mw.util.addPortletLink(
        'luna-actions',
        '/wiki/Wikibooks:WikiProject_Little_Star/Luna/Preferences',
        'Pref',
        'luna-pref-link',
        'Edit your Luna preferences'
    );
	document.dispatchEvent(new Event(&quot;luna-rendered&quot;));
}
function waitForLunaLinksToSettle(callback, delay = 150) {
	let timeout;

	function resetTimer() {
		clearTimeout(timeout);
		timeout = setTimeout(() =&gt; {
			document.removeEventListener(&quot;luna-link-added&quot;, resetTimer);
			callback();
		}, delay);
	}

	document.addEventListener(&quot;luna-link-added&quot;, resetTimer);

	resetTimer();
}
(async function () {
    try {
        console.log(&quot;Luna: Fetching user rights...&quot;);
        myRights = await mw.user.getRights();
        console.log(&quot;Luna: User rights fetched:&quot;, myRights);
    } catch (error) {
        console.error(&quot;Luna: Error fetching user rights:&quot;, error);
        // alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }
    if (!myRights || myRights.length === 0) {
        console.error(&quot;Luna: User rights array is empty or undefined.&quot;);
        // alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }

    if (myRights.includes(&quot;autoconfirmed&quot;)) {
        if (!myRights.includes(&quot;rollback&quot;)) {
            console.log(&quot;Luna: Not a patroller or administrator.&quot;);
            window.isPatroller = false;
        }

        mw.loader.load('jquery.ui');

        console.log(&quot;Luna: Loading preferences script...&quot;);
        try {
            await $.getScript(`/w/index.php?title=User:JJPMaster/luna/pref/unstable.js&amp;action=raw&amp;ctype=text/javascript&amp;cb=${Date.now()}`); // Backlink: [[User:JJPMaster/luna/pref/unstable.js]]
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
        } catch (error) {
            console.error(&quot;Luna: Failed to load preferences script:&quot;, error);
            return;
        }
        mw.loader.load('/w/index.php?title=User:JJPMaster/luna.css&amp;action=raw&amp;ctype=text/css', 'text/css');

        console.log(&quot;Luna: Adding UI elements...&quot;);
        mw.util.addPortlet('luna-actions', 'Luna', '#p-cactions');

        await loadScripts();
		// window.LunaScriptsLoaded = true;
		waitForLunaLinksToSettle(() =&gt; renderLunaPortlet());
    } else {
        console.error(&quot;Luna: User is not autoconfirmed.&quot;);
        mw.notify(&quot;Error: You must be autoconfirmed to use Luna.&quot;);
    }
})();</text>
      <sha1>ll0eks2yf2gwc9cjtl8aempedqyv6su</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/unstable.js</title>
    <ns>2</ns>
    <id>471665</id>
    <revision>
      <id>4678646</id>
      <parentid>4677172</parentid>
      <timestamp>2026-10-28T03:30:25Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>removing user rights error until [[phab:T442667]] is resolved</comment>
      <origin>4678646</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="7335" sha1="8cahjw3njp5btl74ciljv4e447z3jes" xml:space="preserve">const summaryAd = &quot; (using [[:b:en:Wikibooks:WikiProject Little Star/Luna|Luna]])&quot;;

window.isPatroller = true;
var myRights = [];

window.LunaLinks = [];
window.LunaRendered = false;
window.addLunaLink = function(link) {
    window.LunaLinks.push(link);
	document.dispatchEvent(new CustomEvent(&quot;luna-link-added&quot;, {
        detail: link
    }));
	console.log(&quot;Luna: link added&quot;, link.id, performance.now());
	return window.LunaLinks;
};
window.addLunaLinks = function(arr) {
    for (let i of arr) {
		window.addLunaLink(i);
	}
	return window.LunaLinks;
};

console.log(&quot;Luna: Script started.&quot;);

mw.loader.load('//en.wikipedia.org/w/load.php?modules=ext.gadget.morebits');

async function loadScripts() {
    const scripts = [
        'User:JJPMaster/luna/CurateThisPage.js', // Backlink: [[User:JJPMaster/luna/CurateThisPage.js]]
        'User:JJPMaster/luna/rfd.js', // Backlink: [[User:JJPMaster/luna/rfd.js]]
        'User:JJPMaster/luna/warn.js', // Backlink: [[User:JJPMaster/luna/warn.js]]
        'User:JJPMaster/luna/talkback.js', // Backlink: [[User:JJPMaster/luna/talkback.js]]
        'User:JJPMaster/luna/welcome.js', // Backlink: [[User:JJPMaster/luna/welcome.js]]
        'User:JJPMaster/luna/arv.js', // Backlink: [[User:JJPMaster/luna/arv.js]]
        'User:JJPMaster/luna/unlink.js', // Backlink: [[User:JJPMaster/luna/unlink.js]]
        'User:JJPMaster/luna/fileunlink.js', // Backlink: [[User:JJPMaster/luna/fileunlink.js]]
        'User:JJPMaster/luna/csd/unstable.js', // Backlink: [[User:JJPMaster/luna/csd/unstable.js]]
        'User:JJPMaster/luna/diff.js', // Backlink: [[User:JJPMaster/luna/diff.js]]
        'User:JJPMaster/luna/raddewikify.js', // Backlink: [[User:JJPMaster/luna/raddewikify.js]]
        'User:JJPMaster/luna/rpp.js', // Backlink: [[User:JJPMaster/luna/rpp.js]]
        'User:JJPMaster/luna/CurateThisFile.js', // Backlink: [[User:JJPMaster/luna/CurateThisFile.js]]
        'User:JJPMaster/luna/di.js', // Backlink: [[User:JJPMaster/luna/di.js]]
        'User:JJPMaster/luna/templateunlink.js', // Backlink: [[User:JJPMaster/luna/templateunlink.js]]
        'User:JJPMaster/luna/rollback/unstable.js' // Backlink: [[User:JJPMaster/luna/rollback/unstable.js]]
    ];

    if (myRights.includes(&quot;delete&quot;)) {
		await $.getScript('/w/index.php?title=User:JJPMaster/luna/d-batch/core.js&amp;action=raw&amp;ctype=text/javascript'), // Backlink: [[User:JJPMaster/luna/d-batch/core.js]]&quot;)
		await $.getScript(`/w/index.php?title=User:JJPMaster/htmlparserfromhell.js&amp;action=raw&amp;ctype=text/javascript`); // Backlink: [[User:JJPMaster/htmlparserfromhell.js]]
        scripts.push(
			'User:JJPMaster/luna/d-batch/links.js', // Backlink: [[User:JJPMaster/luna/d-batch/links.js]]
			'User:JJPMaster/luna/d-batch/cat.js', // Backlink: [[User:JJPMaster/luna/d-batch/cat.js]]
			'User:JJPMaster/luna/d-batch/prefix.js', // Backlink: [[User:JJPMaster/luna/d-batch/prefix.js]]
			'User:JJPMaster/luna/und-batch.js' // Backlink: [[User:JJPMaster/luna/und-batch.js]]
		);
    }

    console.log(&quot;Luna: Loading scripts...&quot;);
    
    await Promise.all(scripts.map(script =&gt; {
		const start = performance.now();
        return $.getScript(`/w/index.php?title=${script}&amp;action=raw&amp;ctype=text/javascript`)
        .then(() =&gt; console.log(`Luna: Loaded ${script} in ${performance.now() - start}ms.`))
        .catch(error =&gt; console.error(`Luna: Failed to load ${script}:`, error))
		}
    ));

    console.log(&quot;Luna: All scripts loaded successfully.&quot;);
}

async function waitForPreferences(maxRetries = 10, delay = 200) {
    for (let i = 0; i &lt; maxRetries; i++) {
        if (typeof Luna !== &quot;undefined&quot; &amp;&amp; Luna.myPreferences &amp;&amp; Luna.myPreferences.CSD) {
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
            return true;
        }
        console.warn(&quot;Luna: Preferences not loaded yet, retrying...&quot;);
        await new Promise(resolve =&gt; setTimeout(resolve, delay));
    }
    console.error(&quot;Luna: Preferences failed to load after multiple attempts.&quot;);
    return false;
}
function renderLunaPortlet() {
	const order = [
		'luna-arv',
		'luna-warn',
		'luna-welcome',
		'luna-welcome-anon',
		'luna-tb',
		'luna-rev',
		'luna-csd',
		'luna-rfd',
		'luna-di',
		'luna-qrb',
		'luna-rpp',
		'luna-dbatch-links',
		'luna-dbatch-prefix',
		'luna-dbatch-cat',
		'luna-undbatch',
		'luna-ctf',
		'luna-ctp',
		'luna-last',
		'luna-since',
		'luna-sincemine',
		'luna-current',
		'luna-dewiki',
		'luna-unlink',
		'luna-fileunlink',
		'luna-tempunlink',
		'luna-debug-link'
	];
	console.log(&quot;Luna: rendering at&quot;, performance.now());
	order.forEach(id =&gt; {
		const i = window.LunaLinks.find(l =&gt; l.id == id);
		if (!i) return;
		const text = i.debug &amp;&amp; Luna.myPreferences?.debug ? `${i.text} [DEBUG]` : i.text;
		const l = mw.util.addPortletLink('luna-actions', i.href, text, i.id, i.tooltip)
		
		if (i.onClick) {
			$(l).on('click', i.onClick);
		}
	});
	mw.util.addPortletLink(
        'luna-actions',
        '/wiki/Wikibooks:WikiProject_Little_Star/Luna/Preferences',
        'Pref',
        'luna-pref-link',
        'Edit your Luna preferences'
    );
	document.dispatchEvent(new Event(&quot;luna-rendered&quot;));
}
function waitForLunaLinksToSettle(callback, delay = 150) {
	let timeout;

	function resetTimer() {
		clearTimeout(timeout);
		timeout = setTimeout(() =&gt; {
			document.removeEventListener(&quot;luna-link-added&quot;, resetTimer);
			callback();
		}, delay);
	}

	document.addEventListener(&quot;luna-link-added&quot;, resetTimer);

	resetTimer();
}
(async function () {
    try {
        console.log(&quot;Luna: Fetching user rights...&quot;);
        myRights = await mw.user.getRights();
        console.log(&quot;Luna: User rights fetched:&quot;, myRights);
    } catch (error) {
        console.error(&quot;Luna: Error fetching user rights:&quot;, error);
        // alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }
    if (!myRights || myRights.length === 0) {
        console.error(&quot;Luna: User rights array is empty or undefined.&quot;);
        // alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }

    if (myRights.includes(&quot;autoconfirmed&quot;)) {
        if (!myRights.includes(&quot;rollback&quot;)) {
            console.log(&quot;Luna: Not a patroller or administrator.&quot;);
            window.isPatroller = false;
        }

        mw.loader.load('jquery.ui');

        console.log(&quot;Luna: Loading preferences script...&quot;);
        try {
            await $.getScript(`/w/index.php?title=User:JJPMaster/luna/pref/unstable.js&amp;action=raw&amp;ctype=text/javascript&amp;cb=${Date.now()}`); // Backlink: [[User:JJPMaster/luna/pref/unstable.js]]
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
        } catch (error) {
            console.error(&quot;Luna: Failed to load preferences script:&quot;, error);
            return;
        }
        mw.loader.load('/w/index.php?title=User:JJPMaster/luna.css&amp;action=raw&amp;ctype=text/css', 'text/css');

        console.log(&quot;Luna: Adding UI elements...&quot;);
        mw.util.addPortlet('luna-actions', 'Luna', '#p-cactions');

        await loadScripts();
		// window.LunaScriptsLoaded = true;
		waitForLunaLinksToSettle(() =&gt; renderLunaPortlet());
    } else {
        console.error(&quot;Luna: User is not autoconfirmed.&quot;);
        mw.notify(&quot;Error: You must be autoconfirmed to use Luna.&quot;);
    }
})();</text>
      <sha1>8cahjw3njp5btl74ciljv4e447z3jes</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:CheckUser</title>
    <ns>4</ns>
    <id>479107</id>
    <revision>
      <id>4678532</id>
      <parentid>4677763</parentid>
      <timestamp>2026-10-27T17:56:52Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>/* List of functionaries */</comment>
      <origin>4678532</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4672" sha1="guuaeveikllqacva00ay12nuepwt6if" xml:space="preserve">{{draft|shortcut=WB:CU|shortcut2=WB:CHECK}}
{{2FA-required|enforced=yes}}
[[File:Wikibooks Checkuser.svg|150px|right]]
'''CheckUser''' is a tool utilized by a small group of trusted Wikibooks administrators called '''checkusers'''. They can view a list of IP addresses that have been used by an account, or a list of user accounts that have been used by a given IP address or range to edit the English Wikibooks. They also have access to the [[Special:CheckUserLog|CheckUser log]], which logs each time a CheckUser uses their tools to view any of the information listed.

Access to the CheckUser tool is governed by the [[:m:CheckUser policy|global CheckUser policy]]; checkusers must be over 18 years old and have signed the [[:m:Access to nonpublic personal data policy/Noticeboard|Wikimedia Foundation's confidentiality agreement for nonpublic information]] before this permission can be granted.

Per the [[Wikibooks:Global rights policy|global rights policy]], [[:m:Stewards|stewards]] are allowed to use the CheckUser tool, even in non-emergency situations.

== Use of the tool ==
{{See also|m:CheckUser policy}}
The tool is to be used to fight vandalism, spamming, to check for sockpuppet abuse, and to limit disruption of the project. It must be used only to prevent damage to the English Wikibooks.

The tool should not be used for political control, to apply pressure on editors, or as a threat against another editor in a content dispute. There must be a valid reason to use the CheckUser tools to investigate a user.

Notification to the account that is checked is permitted but is not mandatory. Similarly, notification of the check to the community is not mandatory, but may be done subject to the provisions of the privacy policy.

== Privacy policy ==
{{See also|m:Privacy policy|m:Access to nonpublic personal data policy}}
On the English Wikibooks, privacy policy considerations are of tremendous importance. Unless someone is violating policy with their actions (e.g. massive bot vandalism or spam) and revealing information about them is necessary to stop the disruption, it is a violation of the privacy policy to reveal their IP, whereabouts, or other information sufficient to identify them, unless they have already revealed this information themselves on the project.

=== IP information release ===
Even if the user is committing abuse, it's best not to reveal personal information if possible.

* Generally, do not reveal IPs. Only give information such as same network/not same network or similar. If detailed information is provided, make sure the person you are giving it to is a trusted person and will not reveal it himself/herself.
* If the user has said they're from somewhere and the IP confirms it, it's not releasing private information to confirm it if needed.
* If you're in any doubt, give no detail.

=== Temporary account information release ===
{{See also|m:Ombuds commission/2025/Temporary Accounts}}
Similar to the above, checkusers should avoid connecting a temporary account to a registered account, as it has the potential to reveal private information to users who are not authorized to see it.

== Access to CheckUser ==
=== Process for requesting ===
Administrators can request this permission at [[Wikibooks:Requests for permissions]]. The request should remain open for at least 1 week, where the community is invited to support, oppose, comment, and/or to ask questions to the candidate. The following criteria must be met:
* A minimum of 25 supporting votes
* A minimum of 70-80% support

If the criteria is met ''and'' there is consensus to grant the CheckUser permission, the RFP request will be closed, and a user can post a request to [[:m:Steward requests/Permissions]] on Meta-Wiki. After verifying that the candidate has signed the confidentiality agreement, a steward will grant the rights.

=== Process for removal ===
Any user account with CheckUser status that is inactive for more than one year will have their CheckUser access removed.

In case of abusive use of the tool, the steward or the editor with the CheckUser privilege will immediately have their access removed. This will in particular happen if checks are done routinely on editors without a serious motive to do so (links and proofs of bad behavior should be provided).

== Requesting CheckUser information ==
Any editor may request CheckUser assistance by adding a request at [[Wikibooks:Reading room/Administrative Assistance]].

== List of functionaries ==
There are currently [[Special:ListUsers/checkuser|{{NUMBERINGROUP:checkuser}} checkuser{{#ifeq:{{NUMBERINGROUP:checkuser}}|1||s}}]]:

{{Special:ListUsers/checkuser}}

{{User groups}}</text>
      <sha1>guuaeveikllqacva00ay12nuepwt6if</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Kuku Paka</title>
    <ns>102</ns>
    <id>483580</id>
    <revision>
      <id>4678573</id>
      <parentid>4678249</parentid>
      <timestamp>2026-10-27T20:02:39Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the chicken */</comment>
      <origin>4678573</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2680" sha1="06kweh1coxkxdgzfcnts8uus8a7s0ly" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 tomatoes, chopped
* 2 cloves garlic, minced
* 1 teaspoon grated ginger
* 1–2 green chilies, chopped
* 1 teaspoon curry powder
* 1 teaspoon ground cumin
* 1 teaspoon ground coriander
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>06kweh1coxkxdgzfcnts8uus8a7s0ly</sha1>
    </revision>
    <revision>
      <id>4678574</id>
      <parentid>4678573</parentid>
      <timestamp>2026-10-27T20:03:14Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678574</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2701" sha1="iyx6fwl1pj6izlyhu2nqhzxcx2i76bt" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 cloves garlic, minced
* 1 teaspoon grated ginger
* 1–2 green chilies, chopped
* 1 teaspoon curry powder
* 1 teaspoon ground cumin
* 1 teaspoon ground coriander
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>iyx6fwl1pj6izlyhu2nqhzxcx2i76bt</sha1>
    </revision>
    <revision>
      <id>4678575</id>
      <parentid>4678574</parentid>
      <timestamp>2026-10-27T20:04:12Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678575</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2741" sha1="kfijb3gxsuyx2n8fy45n30jepi07bdw" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 teaspoon grated ginger
* 1–2 green chilies, chopped
* 1 teaspoon curry powder
* 1 teaspoon ground cumin
* 1 teaspoon ground coriander
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>kfijb3gxsuyx2n8fy45n30jepi07bdw</sha1>
    </revision>
    <revision>
      <id>4678576</id>
      <parentid>4678575</parentid>
      <timestamp>2026-10-27T20:05:13Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678576</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2785" sha1="ccis0753xqa0j9qg7hn7vnrxnuyv3as" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green chilies, chopped
* 1 teaspoon curry powder
* 1 teaspoon ground cumin
* 1 teaspoon ground coriander
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>ccis0753xqa0j9qg7hn7vnrxnuyv3as</sha1>
    </revision>
    <revision>
      <id>4678577</id>
      <parentid>4678576</parentid>
      <timestamp>2026-10-27T20:05:52Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678577</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2804" sha1="ddg18bjtevezutstevcqy92mjbkklzp" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 teaspoon curry powder
* 1 teaspoon ground cumin
* 1 teaspoon ground coriander
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>ddg18bjtevezutstevcqy92mjbkklzp</sha1>
    </revision>
    <revision>
      <id>4678578</id>
      <parentid>4678577</parentid>
      <timestamp>2026-10-27T20:07:08Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678578</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2846" sha1="596qzdr5ryanu1ijjn33a4kntpncsje" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 teaspoon ground cumin
* 1 teaspoon ground coriander
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>596qzdr5ryanu1ijjn33a4kntpncsje</sha1>
    </revision>
    <revision>
      <id>4678579</id>
      <parentid>4678578</parentid>
      <timestamp>2026-10-27T20:08:17Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678579</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2889" sha1="tszvnbgcvu2aep9dxybigiy6n1hlpos" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 teaspoon ground coriander
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>tszvnbgcvu2aep9dxybigiy6n1hlpos</sha1>
    </revision>
    <revision>
      <id>4678580</id>
      <parentid>4678579</parentid>
      <timestamp>2026-10-27T20:09:19Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678580</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2936" sha1="2zj28qn7fg9di9tzwrb85i42ze4stq0" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml coconut milk
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>2zj28qn7fg9di9tzwrb85i42ze4stq0</sha1>
    </revision>
    <revision>
      <id>4678581</id>
      <parentid>4678580</parentid>
      <timestamp>2026-10-27T20:10:31Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678581</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2963" sha1="j5oerst65zw6jioecl793aprtlcsyqi" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh coriander leaves for garnish
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>j5oerst65zw6jioecl793aprtlcsyqi</sha1>
    </revision>
    <revision>
      <id>4678582</id>
      <parentid>4678581</parentid>
      <timestamp>2026-10-27T20:11:35Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678582</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3009" sha1="7bk2ezhw1blj7zmofu720xe1h27wzym" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* Salt to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>7bk2ezhw1blj7zmofu720xe1h27wzym</sha1>
    </revision>
    <revision>
      <id>4678583</id>
      <parentid>4678582</parentid>
      <timestamp>2026-10-27T20:12:15Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* For the sauce */</comment>
      <origin>4678583</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3027" sha1="1y0wucxxrvkm34ib18coab98r9y8amw" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* Grill or oven
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>1y0wucxxrvkm34ib18coab98r9y8amw</sha1>
    </revision>
    <revision>
      <id>4678584</id>
      <parentid>4678583</parentid>
      <timestamp>2026-10-27T20:13:10Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678584</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3065" sha1="izxvzzx02d0yrubaphckxivh6avs4zk" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large cooking pot or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>izxvzzx02d0yrubaphckxivh6avs4zk</sha1>
    </revision>
    <revision>
      <id>4678585</id>
      <parentid>4678584</parentid>
      <timestamp>2026-10-27T20:13:47Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678585</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3089" sha1="9bqcqnb6iimozo81u0x3gleygo8cakc" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large [[Cookbook: Stock Pot|cooking pot]] or pan
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>9bqcqnb6iimozo81u0x3gleygo8cakc</sha1>
    </revision>
    <revision>
      <id>4678586</id>
      <parentid>4678585</parentid>
      <timestamp>2026-10-27T20:14:28Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678586</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3106" sha1="5geg449rbuyvy39fu9ccynhia0xj2f9" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large [[Cookbook: Stock Pot|cooking pot]] or [[Cookbook:Pan|pan]]
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>5geg449rbuyvy39fu9ccynhia0xj2f9</sha1>
    </revision>
    <revision>
      <id>4678587</id>
      <parentid>4678586</parentid>
      <timestamp>2026-10-27T20:15:45Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678587</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3114" sha1="c8n0kjguv2pzbnonx6v5yminvn87nt3" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large [[Cookbook: Stock Pot|cooking pot]] or [[Cookbook: Frying Pan|pan]]
* Knife
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>c8n0kjguv2pzbnonx6v5yminvn87nt3</sha1>
    </revision>
    <revision>
      <id>4678588</id>
      <parentid>4678587</parentid>
      <timestamp>2026-10-27T20:16:22Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678588</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3134" sha1="p5169872s9qjmjw32oum32vlmf1ri67" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large [[Cookbook: Stock Pot|cooking pot]] or [[Cookbook: Frying Pan|pan]]
* [[Cookbook: Knife|Knife]]
* Cutting board
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>p5169872s9qjmjw32oum32vlmf1ri67</sha1>
    </revision>
    <revision>
      <id>4678589</id>
      <parentid>4678588</parentid>
      <timestamp>2026-10-27T20:17:54Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678589</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3162" sha1="7xa4k2ai63uogdmzrxecj188v3dudpr" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large [[Cookbook: Stock Pot|cooking pot]] or [[Cookbook: Frying Pan|pan]]
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* Mixing bowl
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>7xa4k2ai63uogdmzrxecj188v3dudpr</sha1>
    </revision>
    <revision>
      <id>4678591</id>
      <parentid>4678589</parentid>
      <timestamp>2026-10-27T20:19:32Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678591</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3187" sha1="pzdv0blj0l1lhyosu2wm96usyy12zzp" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large [[Cookbook: Stock Pot|cooking pot]] or [[Cookbook: Frying Pan|pan]]
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* [[Cookbook:Mixing Bowl|Mixing bowl]]
* Wooden spoon

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>pzdv0blj0l1lhyosu2wm96usyy12zzp</sha1>
    </revision>
    <revision>
      <id>4678592</id>
      <parentid>4678591</parentid>
      <timestamp>2026-10-27T20:20:47Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678592</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3215" sha1="0fuzo5uj52bkon332dv5kga2ahlmufh" xml:space="preserve">{{Recipe summary
| Category = Main dish
| Servings = 4–6
| Time = 45 minutes
| Difficulty = 3
}}{{Incomplete recipe|reason=missing appropriate linking, missing appropriate categories}}
'''Kuku Paka''' is a traditional East African chicken dish made with grilled or roasted chicken cooked in a rich coconut curry [[Cookbook:Sauce|sauce]]. It is especially popular along the Swahili coast of Kenya and Tanzania, where it is commonly served with pilau rice, chapati, ugali, fresh salad, or lime wedges.

==Ingredients==
===For the chicken===
* 1 whole [[Cookbook:Chicken|chicken]], cut into pieces
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Lemon|lemon]] or [[Cookbook:Lime|lime]] juice
* 2 [[Cookbook:Clove|cloves]] [[Cookbook:Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* ½ teaspoon [[Cookbook: Turmeric|turmeric]]
* [[Cookbook:Salt|Salt]] to taste
* Black [[Cookbook:Pepper|pepper]] to taste
* 2 [[Cookbook: Tablespoon|tablespoons]] [[Cookbook:Oil|oil]]

===For the sauce===
* 1 large [[Cookbook:Onion|onion]], chopped
* 2 [[Cookbook: Tomato|tomatoes]], chopped
* 2 [[Cookbook:Clove|cloves]] [[Cookbook: Garlic|garlic]], minced
* 1 [[Cookbook: Teaspoon|teaspoon]] grated [[Cookbook: Ginger|ginger]]
* 1–2 green [[Cookbook:Chile|chilies]], chopped
* 1 [[Cookbook: Teaspoon|teaspoon]] [[Cookbook:Curry|curry]] powder
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Cumin|cumin]]
* 1 [[Cookbook: Teaspoon|teaspoon]] ground [[Cookbook: Coriander|coriander]]
* 400 ml [[Cookbook: Coconut Milk|coconut milk]]
* 2 tablespoons tomato paste
* Fresh [[Cookbook: Coriander|coriander]] leaves for [[Cookbook: Garnish|garnish]]
* [[Cookbook:Salt|Salt]] to taste

==Equipment==
* [[Cookbook: Grill|Grill]] or [[Cookbook:Oven|oven]]
* Large [[Cookbook: Stock Pot|cooking pot]] or [[Cookbook: Frying Pan|pan]]
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* [[Cookbook:Mixing Bowl|Mixing bowl]]
* [[Cookbook: Cooking Spoon|Wooden spoon]]

==Procedure==
# In a bowl, combine the chicken with lemon juice, garlic, ginger, curry powder, turmeric, salt, black pepper, and oil.
# Marinate for at least 30 minutes.
# Grill the chicken over charcoal or roast in an oven until lightly charred and partly cooked.
# Heat oil in a large pan over medium heat.
# Add the onions and cook until soft.
# Stir in the garlic, ginger, chilies, tomatoes, tomato paste, curry powder, cumin, and coriander.
# Cook until the tomatoes soften and the mixture becomes fragrant.
# Pour in the coconut milk and stir well.
# Add the grilled chicken pieces to the sauce.
# Simmer gently for 20–30 minutes until the chicken is fully cooked and the sauce thickens.
# Garnish with fresh coriander leaves and serve hot.

==Notes,  tips, and variation==
* Charcoal grilling gives the dish its traditional smoky flavour.
* Coconut cream creates a richer sauce than coconut milk.
* Fresh ginger and garlic improve the aroma.
* Marinating the chicken overnight enhances flavour.
* The sauce should simmer gently to avoid separating the coconut milk.
{{DEFAULTSORT:Somalia}}
[[Category:Kenyan recipes]]</text>
      <sha1>0fuzo5uj52bkon332dv5kga2ahlmufh</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Kunun Zaki</title>
    <ns>102</ns>
    <id>483770</id>
    <revision>
      <id>4678595</id>
      <parentid>4638950</parentid>
      <timestamp>2026-10-27T20:30:37Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4678595</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2403" sha1="1qlh4zmstj6aga62gxvk528pfxvpk9h" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Cloves|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large bowl or container
* Blender or grinding stone
* Sieve or muslin cloth
* Cooking pot
* Wooden spoon
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>1qlh4zmstj6aga62gxvk528pfxvpk9h</sha1>
    </revision>
    <revision>
      <id>4678596</id>
      <parentid>4678595</parentid>
      <timestamp>2026-10-27T20:30:55Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4678596</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2402" sha1="8epft043sawsqq1tur1zpxu7u26r5ce" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large bowl or container
* Blender or grinding stone
* Sieve or muslin cloth
* Cooking pot
* Wooden spoon
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>8epft043sawsqq1tur1zpxu7u26r5ce</sha1>
    </revision>
    <revision>
      <id>4678597</id>
      <parentid>4678596</parentid>
      <timestamp>2026-10-27T20:31:30Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678597</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2428" sha1="3uvl7fh6ej8lah6mj690skczacsiwny" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or container
* Blender or grinding stone
* Sieve or muslin cloth
* Cooking pot
* Wooden spoon
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>3uvl7fh6ej8lah6mj690skczacsiwny</sha1>
    </revision>
    <revision>
      <id>4678598</id>
      <parentid>4678597</parentid>
      <timestamp>2026-10-27T20:32:17Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678598</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2450" sha1="dlzh1xv7i3at3mm3xpkd8ck0ytmurhw" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or container
* [[Cookbook: Blender|Blender]] or grinding stone
* Sieve or muslin cloth
* Cooking pot
* Wooden spoon
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>dlzh1xv7i3at3mm3xpkd8ck0ytmurhw</sha1>
    </revision>
    <revision>
      <id>4678600</id>
      <parentid>4678598</parentid>
      <timestamp>2026-10-27T20:32:54Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678600</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2470" sha1="815wox83oon5wy2863728235ngqf09t" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or container
* [[Cookbook: Blender|Blender]] or grinding stone
* [[Cookbook: Sieve|Sieve]] or muslin cloth
* Cooking pot
* Wooden spoon
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>815wox83oon5wy2863728235ngqf09t</sha1>
    </revision>
    <revision>
      <id>4678602</id>
      <parentid>4678600</parentid>
      <timestamp>2026-10-27T20:34:22Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678602</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2494" sha1="hiuiu2zicgd3urxkb83ylcwz1lxwl3p" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or container
* [[Cookbook: Blender|Blender]] or grinding stone
* [[Cookbook: Sieve|Sieve]] or muslin cloth
* [[Cookbook: Stock Pot|Cooking pot]]
* Wooden spoon
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>hiuiu2zicgd3urxkb83ylcwz1lxwl3p</sha1>
    </revision>
    <revision>
      <id>4678603</id>
      <parentid>4678602</parentid>
      <timestamp>2026-10-27T20:34:55Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678603</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2521" sha1="7hqjz3u50bhky5sncuoqhr2kgulfp1d" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or container
* [[Cookbook: Blender|Blender]] or grinding stone
* [[Cookbook: Sieve|Sieve]] or muslin cloth
* [[Cookbook: Stock Pot|Cooking pot]]
* [[Cookbook: Wooden Spoon|Wooden spoon]]
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>7hqjz3u50bhky5sncuoqhr2kgulfp1d</sha1>
    </revision>
    <revision>
      <id>4678604</id>
      <parentid>4678603</parentid>
      <timestamp>2026-10-27T20:35:53Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678604</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2559" sha1="0n0bwu8hkq116zvb7afsuiuqqdk2yrv" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or container
* [[Cookbook: Blender|Blender]] or grinding stone
* [[Cookbook: Sieve|Sieve]] or muslin cloth
* [[Cookbook: Stock Pot|Cooking pot]]
* [[Cookbook: Wooden Spoon|Wooden spoon]]
* [[Cookbook: Bottle|Bottles]] or [[Cookbook:Jug|jugs]] (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>0n0bwu8hkq116zvb7afsuiuqqdk2yrv</sha1>
    </revision>
    <revision>
      <id>4678606</id>
      <parentid>4678604</parentid>
      <timestamp>2026-10-27T20:38:24Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678606</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2592" sha1="67hf2hjqvnz0mowjuk7do8009q0vxw6" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or [[Cookbook: Storage Containers|container]]
* [[Cookbook: Blender|Blender]] or grinding stone
* [[Cookbook: Sieve|Sieve]] or muslin cloth
* [[Cookbook: Stock Pot|Cooking pot]]
* [[Cookbook: Wooden Spoon|Wooden spoon]]
* [[Cookbook: Bottle|Bottles]] or [[Cookbook:Jug|jugs]] (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>67hf2hjqvnz0mowjuk7do8009q0vxw6</sha1>
    </revision>
    <revision>
      <id>4678607</id>
      <parentid>4678606</parentid>
      <timestamp>2026-10-27T20:40:54Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678607</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2554" sha1="5mhj9p9rcl5bfakqwrl4hidsbtopasb" xml:space="preserve">{{Incomplete recipe|reason=missing/incorrect categories, missing appropriate linking, yeast is not mentioned in the procedure, how much water is mixed with the paste? how much of the liquid should be boiled?}}

{{Recipe}}

[[Cookbook:Recipes|Recipes]] |
[[Cookbook:Ingredients|Ingredients]] |
[[Cookbook:Equipment|Equipment]]

{{Recipe summary
| Cuisine = Nigerian Cuisine
| Origin = Hausa Nigeria
| Yield = 1 bowl
| Servings = 7 servings
| Time = 2 hours
| Difficulty = 2
| Image = [[File:Kunun Zaki a leda.jpg|300px]]
}}

Kunun Zaki is a popular traditional Hausa beverage made from grains such as millet or sorghum, flavored with spices like ginger, cloves, and sometimes sweetened with sugar. It is commonly served chilled as a refreshing drink during meals, ceremonies, and social gatherings in Northern Nigeria.

== Ingredients ==

{| class=&quot;wikitable&quot;
! Ingredient
! Count
! Volume
! Weight
|-
| [[Cookbook:Millet|millet (or sorghum)]]
| –
| 4 cups
| –
|-
| [[Cookbook:Ginger|ginger]]
| –
| 2–3 tablespoons (blended)
| –
|-
| [[Cookbook:Clove|cloves]]
| –
| 1 teaspoon
| –
|-
| [[Cookbook:Sugar|sugar]]
| –
| 1–1½ cups (to taste)
| –
|-
| [[Cookbook:Water|water]]
| –
| 6–8 liters
| –
|-
| [[Cookbook: Yeast|Yeast]] (optional)
| –
| 1 teaspoon
| –
|}

== Equipment ==

* Large [[Cookbook: Mixing Bowl|bowl]] or [[Cookbook: Storage Containers|container]]
* [[Cookbook: Blender|Blender]] or grinding stone
* [[Cookbook: Sieve|Sieve]] or muslin cloth
* [[Cookbook: Stock Pot|Cooking pot]]
* [[Cookbook: Wooden Spoon|Wooden spoon]]
* Bottles or jugs (for storage)

== Procedure ==

# Soak the millet in water for several hours or overnight.
# Wash and grind the millet with ginger and cloves into a smooth paste.
# Mix the paste with water and sieve to extract the liquid.
# Allow the liquid to settle for some hours, then decant the clear water on top.
# Boil part of the extracted liquid while stirring continuously until it thickens slightly.
# Mix the cooked portion with the remaining raw extract.
# Add sugar to taste and stir well.
# Allow to cool completely, then refrigerate before serving.

== Notes, tips, and variations ==

* The drink is best served chilled.
* Adjust sweetness depending on preference.
* Fermentation can be allowed for a slightly sour taste in some variations.
* Sorghum or maize can be used instead of millet.

== Warnings ==

* Ensure proper hygiene during preparation to avoid contamination since it is a beverage.
* Do not leave the drink unrefrigerated for too long after preparation.</text>
      <sha1>5mhj9p9rcl5bfakqwrl4hidsbtopasb</sha1>
    </revision>
  </page>
  <page>
    <title>Create Vampires/Ethics Of Creating Vampire Lore</title>
    <ns>0</ns>
    <id>485677</id>
    <revision>
      <id>4678616</id>
      <parentid>4677851</parentid>
      <timestamp>2026-10-27T21:16:06Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678616</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4535" sha1="tt2mik0wm52ft3c5jyyj8y69dr3i50e" xml:space="preserve">== The Ethics of Creating Vampire Lore ==
When writing about vampires in your fictional narratives, try to
avoid using harmful stereotypes or cultural appropriations. &lt;br&gt;
&lt;br&gt;
Stereotypes are widely held, fixed, and oversimplified beliefs or mental images about a particular group of people. [1] &lt;br&gt;
&lt;br&gt;
According to Wikipedia: &lt;br&gt;
It is an expectation that people might have about every person of a particular group. The type of expectation can vary; it can be, for example, an expectation about the group's personality, preferences, appearance or ability. [2] &lt;br&gt;

Stereotypes are often faulty and resistant to new information. [3] &lt;br&gt;
&lt;br&gt;
People who use stereotypes rely of their previous knowledge about a person, information they then project onto an entire group. This can lead to hasty generalizations when they meet new people in that said group. &lt;br&gt;
&lt;br&gt;
Negative stereotypes should be used with caution. They can lead to prejudice, discrimination and unfair judgment. &lt;br&gt;
&lt;br&gt;
If you think all vampires are white, blood-thirsty decomposing demons from hell, then perhaps you should read more books, and watch more films about vampires. &lt;br&gt;
&lt;br&gt;
In the case of the Vampire Disease, also known as porphyria, Medical Doctors wrote about patients who became depressed by reports in the media linking porphyria, their illness, with vampirism. In this case, negative stereotypes could lead to unfair judgements. &lt;br&gt;
&lt;br&gt;
According to Wikipedia: &lt;br&gt;
Cultural appropriation is an adoption of an element or elements of culture or identity by members of another culture or identity in a manner perceived as inappropriate or unacknowledged. Charges of cultural appropriation typically arise when members of a dominant culture borrow from minority cultures. Cultural appropriation can include the adoption of another culture's religious and cultural traditions, customs, dance steps, fashion, symbols, language, history and music. [4]&lt;br&gt;
&lt;br&gt;
Problems occur when cultural borrowing is unacknowledged, or when borrowed information is used in an inappropriate manner. &lt;br&gt;
&lt;br&gt;
Memes occur when people imitate the behaviors of other people without truly understanding that behavior. For unconscious reasons, that behavior, or idea spreads. &lt;br&gt;
&lt;br&gt;
The entire lore that surrounds the vampire seems like cultural appropriation from the Romanian people who did historically suffer, as a group, from grave robbery. The actual accounts of people who were mistaken for vampires, fed folk stories and modern legends. &lt;br&gt;
&lt;br&gt;
=== Respectful use of folklore? ===
How can writers use folklore respectfully? 
Writers could acknowledge the people who created and kept their folklore alive. By acknowledging the folks who shared their cautionary tales, we share their perspectives, and our stories gain diversity. By acknowledging each storyteller, we show respect. We should honor their stories as they honor their ancestors' stories. &lt;br&gt;
&lt;br&gt;
This section was ''developed'' by the writer using '''digital tools''': &lt;br&gt;
&lt;br&gt;
When writers treat folklore as cultural memory, they acknowledge the grief, fears, community protection, and spiritual beliefs of the people who carried it. &lt;br&gt;
&lt;br&gt;
These vampire stories come from people, from Slavic, Caribbean, Filipino, Chinese, Indigenous, African — People.
These ancestor stories are other people's attempt to explain illness, death, or danger.  &lt;br&gt;
&lt;br&gt;
Unethical use of folklore looks like: using stereotypes, treating traditions as interchangeable with each other, removing cultural context, claiming “ownership” of a culture’s monster.

Ethical vampire lore: avoids stereotypes, preserves meaning, respects the original purpose of the tale, keeps cultural details, acknowledges the source of the story, shares ownership of a monster that can transcend cultural boundaries.
&lt;br&gt;
&lt;br&gt;
Link: [[Create_Vampires/All About Vampires]]
&lt;br&gt;
&lt;br&gt;
=== Reference: ===
1. Oxford Learner's Dictionaries stereotype September 16, 2026 In https://www.oxfordlearnersdictionaries.com/definition/american_english/stereotype_1 
&lt;br&gt;
2. &quot;Stereotype&quot; August 30, 2026. In Wikipedia https://en.wikipedia.org/wiki/Stereotype &lt;br&gt;
&lt;br&gt;
3.  Meyer, David G. (2008). Intuition: Its Powers and Perils. Yale University Press. pp. 114–115. {{ISBN|978-0-300-13027-0}} &lt;br&gt;
&lt;br&gt;
4. &quot;Cultural appropriation&quot; September 8, 2026. In Wikipedia https://en.wikipedia.org/wiki/Cultural_appropriation
&lt;br&gt;
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Women As  Vampires|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;

{{BookCat}}</text>
      <sha1>tt2mik0wm52ft3c5jyyj8y69dr3i50e</sha1>
    </revision>
  </page>
  <page>
    <title>User:MathsScienceNerd1/sandbox</title>
    <ns>2</ns>
    <id>485726</id>
    <revision>
      <id>4678653</id>
      <parentid>4678339</parentid>
      <timestamp>2026-10-28T07:49:27Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>Create.</comment>
      <origin>4678653</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="633" sha1="apw5graah2x1f4iepgp7wds9wsrt1ki" xml:space="preserve">{{User:TechVindicator/QuickAccess}}
The '''Wikibooks Magazine''' is the publication of Wikibooks, providing information about what is going on at Wikibooks. This was inspired by the [https://wikikids.nl/Wikikids:Magazine WikiKids Magazine] originally created by [https://wikikids.nl/Gebruiker:Perquirius Perquirius]. See the table below for each issue. It is published at the end of February (excluding February 29th), May, August and November.
{| class=&quot;wikitable&quot;
|+
!
!28th February
!31st May
!31st August
!30th November
|-
|'''2026'''
|n/a
|n/a
|n/a
|[[Wikibooks:Magazine/1|Link]]
|-
|'''2027'''
|
|
|
|
|-
|'''2028'''
|
|
|
|
|}</text>
      <sha1>apw5graah2x1f4iepgp7wds9wsrt1ki</sha1>
    </revision>
    <revision>
      <id>4678654</id>
      <parentid>4678653</parentid>
      <timestamp>2026-10-28T07:49:53Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>Replaced content with &quot;{{User:TechVindicator/QuickAccess}}&quot;</comment>
      <origin>4678654</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35" sha1="q4w8sfv4xmmj9ke82u0xd90jviybhi0" xml:space="preserve">{{User:TechVindicator/QuickAccess}}</text>
      <sha1>q4w8sfv4xmmj9ke82u0xd90jviybhi0</sha1>
    </revision>
  </page>
  <page>
    <title>Infrastructure Past, Present, and Future/Glenwood Canyon</title>
    <ns>0</ns>
    <id>485863</id>
    <revision>
      <id>4678487</id>
      <parentid>4678483</parentid>
      <timestamp>2026-10-27T13:58:59Z</timestamp>
      <contributor>
        <username>Afreeman8</username>
        <id>3626850</id>
      </contributor>
      <comment>map update</comment>
      <origin>4678487</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20947" sha1="hy234px4ben2bdzo02jkwiyz562i2mz" xml:space="preserve">== Overview ==
&lt;mapframe text=&quot;Glenwood Canyon I-70&quot; width=&quot;535&quot; height=&quot;532&quot; latitude=&quot;39.575&quot; longitude=&quot;-107.223&quot; zoom=&quot;12&quot;&gt;&lt;mapframe latitude=&quot;39.0&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;600&quot; height=&quot;400&quot; align=&quot;center&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&amp;lt;/mapframe&gt;
&lt;/mapframe&gt;The Glenwood Canyon segment of Interstate 70 (I-70) is gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992
The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. Its history may not seem intricate, but the modern management. is complex

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the Colorado River made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.

Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.

Citizen participation helped shape these engineering decisions. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.

However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

* Early parts of 20th century
** Earlier transportation routes establish the canyon’s importance as a regional corridor.
* 1960s–1970s
** Interstate planning proceeds amid environmental concerns and debates about the proposed route.
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the Glenwood Canyon segment.
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original $490 million expenditure equates to approximately $1.154 billion in 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
The Grizzly Creek Fire was a major wildfire that burned 32,631 acres  in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” required heavy equipment and more than 200 loads of debris removed in a single day

These disasters caused Rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction


== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}</text>
      <sha1>hy234px4ben2bdzo02jkwiyz562i2mz</sha1>
    </revision>
    <revision>
      <id>4678488</id>
      <parentid>4678487</parentid>
      <timestamp>2026-10-27T14:00:58Z</timestamp>
      <contributor>
        <username>Afreeman8</username>
        <id>3626850</id>
      </contributor>
      <minor />
      <origin>4678488</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20889" sha1="hdgtk648c74r0f5946tuw7su8747mbd" xml:space="preserve">== Overview ==
&lt;mapframe text=&quot;Glenwood Canyon I-70&quot; width=&quot;535&quot; height=&quot;532&quot; latitude=&quot;39.575&quot; longitude=&quot;-107.223&quot; zoom=&quot;12&quot;&gt;== Location of Glenwood Canyon, Colorado ==

&lt;mapframe text=&quot;Glenwood Canyon, Colorado&quot; width=&quot;500&quot; height=&quot;400&quot; zoom=&quot;9&quot; longitude=&quot;-107.25&quot; latitude=&quot;39.60&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.25, 39.60]
  },
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;A scenic canyon along the Colorado River in western Colorado, traversed by Interstate 70.&quot;
  }
}
&amp;lt;/mapframe&gt;
&lt;/mapframe&gt;The Glenwood Canyon segment of Interstate 70 (I-70) is gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992
The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. Its history may not seem intricate, but the modern management. is complex

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the Colorado River made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.

Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.

Citizen participation helped shape these engineering decisions. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.

However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

* Early parts of 20th century
** Earlier transportation routes establish the canyon’s importance as a regional corridor.
* 1960s–1970s
** Interstate planning proceeds amid environmental concerns and debates about the proposed route.
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the Glenwood Canyon segment.
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original $490 million expenditure equates to approximately $1.154 billion in 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
The Grizzly Creek Fire was a major wildfire that burned 32,631 acres  in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” required heavy equipment and more than 200 loads of debris removed in a single day

These disasters caused Rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction


== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}</text>
      <sha1>hdgtk648c74r0f5946tuw7su8747mbd</sha1>
    </revision>
    <revision>
      <id>4678489</id>
      <parentid>4678488</parentid>
      <timestamp>2026-10-27T14:04:25Z</timestamp>
      <contributor>
        <username>Afreeman8</username>
        <id>3626850</id>
      </contributor>
      <origin>4678489</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20821" sha1="o0lbfoh67wpobf88zhw1jkd0s7jm5qh" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39.0&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;600&quot; height=&quot;400&quot; align=&quot;center&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of Interstate 70 (I-70) is gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992
The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. Its history may not seem intricate, but the modern management. is complex

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the Colorado River made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.

Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.

Citizen participation helped shape these engineering decisions. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.

However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

* Early parts of 20th century
** Earlier transportation routes establish the canyon’s importance as a regional corridor.
* 1960s–1970s
** Interstate planning proceeds amid environmental concerns and debates about the proposed route.
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the Glenwood Canyon segment.
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original $490 million expenditure equates to approximately $1.154 billion in 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
The Grizzly Creek Fire was a major wildfire that burned 32,631 acres  in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” required heavy equipment and more than 200 loads of debris removed in a single day

These disasters caused Rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction


== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}</text>
      <sha1>o0lbfoh67wpobf88zhw1jkd0s7jm5qh</sha1>
    </revision>
    <revision>
      <id>4678492</id>
      <parentid>4678489</parentid>
      <timestamp>2026-10-27T14:20:08Z</timestamp>
      <contributor>
        <username>Afreeman8</username>
        <id>3626850</id>
      </contributor>
      <comment>Editing of sections for mechanics. Addition of information to engineering. Addition of photos.</comment>
      <origin>4678492</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="21630" sha1="0q65ldsf6gzvff0vqhqdqk8ywr1eq46" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;446&quot; height=&quot;372&quot; align=&quot;right&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of Interstate 70 (I-70) is gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992. The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. 

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the Colorado River made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.
[[File:Glenwood Canyon (2614828822).jpg|thumb|Glenwood Canyon as seen from I-70]]
Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.
[[File:CO 28 I70 FHWA 1992.jpg|thumb|Photo from Construction]]
The federal government required the state of Colorado to incorporate the public due to public disapproval of the project. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.
[[File:Glenwood Canyon - panoramio (1).jpg|thumb|View of Stacked Roadway with a viaduct]]
However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. This was the first roadway to make substantial use of posttensioned concrete slabs on at grade construction. This was due to the lack of a suitable foundation in many sections.&lt;ref&gt;{{Cite web |date=March 3, 2021 |title=History Lesson: The last piece of the Interstate Highway System may have been the toughest |url=https://www.asce.org/publications-and-news/civil-engineering-source/civil-engineering-magazine/issues/magazine-issue/article/2021/03/the-last-piece-of-the-interstate-highway-system-may-have-been-the-toughest |access-date=2026-10-27 |website=www.asce.org |language=en-US}}&lt;/ref&gt; The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

* Early parts of 20th century
** Earlier transportation routes establish the canyon’s importance as a regional corridor.
* 1960s–1970s
** Interstate planning proceeds amid environmental concerns and debates about the proposed route.
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the Glenwood Canyon segment.
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original $490 million expenditure equates to approximately $1.154 billion in 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
The Grizzly Creek Fire was a major wildfire that burned 32,631 acres in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue.

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” required heavy equipment and more than 200 loads of debris removed in a single day.

These disasters caused Rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction.
== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered.

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}</text>
      <sha1>0q65ldsf6gzvff0vqhqdqk8ywr1eq46</sha1>
    </revision>
    <revision>
      <id>4678497</id>
      <parentid>4678492</parentid>
      <timestamp>2026-10-27T14:39:11Z</timestamp>
      <contributor>
        <username>Afreeman8</username>
        <id>3626850</id>
      </contributor>
      <origin>4678497</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22348" sha1="7v5dqgldihdlzjamcwsv0wwq08wwys7" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;446&quot; height=&quot;372&quot; align=&quot;right&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of [[wikipedia:Interstate_70|Interstate 70]] (I-70) is gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992. The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. 

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the [[wikipedia:Colorado_River|Colorado River]] made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.
[[File:Glenwood Canyon (2614828822).jpg|thumb|Glenwood Canyon as seen from I-70]]
Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

The public opposition to the project was substantial at times, with the enlistment of [[wikipedia:John_Denver|John Denver]], the movement gained a lot of attention. The groups letter to the governor stated, “It is impossible to put such a highway through this canyon without permanently scarring the several million year old unique geologic formations and further disrupting the Colorado River headwaters.”&lt;ref name=&quot;:2&quot; /&gt; The resistance evolved from trying to block the route in its entirety to making sure it affected the nature of the canyon in the least way possible.

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.
[[File:CO 28 I70 FHWA 1992.jpg|thumb|Photo from Construction]]
The federal government required the state of Colorado to incorporate the public due to public disapproval of the project. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.
[[File:Glenwood Canyon - panoramio (1).jpg|thumb|View of Stacked Roadway with a viaduct]]
However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. This was the first roadway to make substantial use of posttensioned concrete slabs on at grade construction. This was due to the lack of a suitable foundation in many sections.&lt;ref&gt;{{Cite web |date=March 3, 2021 |title=History Lesson: The last piece of the Interstate Highway System may have been the toughest |url=https://www.asce.org/publications-and-news/civil-engineering-source/civil-engineering-magazine/issues/magazine-issue/article/2021/03/the-last-piece-of-the-interstate-highway-system-may-have-been-the-toughest |access-date=2026-10-27 |website=www.asce.org |language=en-US}}&lt;/ref&gt; The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

* Early parts of 20th century
** Earlier transportation routes establish the canyon’s importance as a regional corridor.
* 1960s–1970s
** Interstate planning proceeds amid environmental concerns and debates about the proposed route.
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the Glenwood Canyon segment.
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original $490 million expenditure equates to approximately $1.154 billion in 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
[[File:2020 08 23-20.41.33.572-CDT.jpg|thumb|Grizzly Creek Fire above the Canyon]]
The Grizzly Creek Fire was a major wildfire that burned 32,631 acres in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue.

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” required heavy equipment and more than 200 loads of debris removed in a single day.

These disasters caused Rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction.
== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered.

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}</text>
      <sha1>7v5dqgldihdlzjamcwsv0wwq08wwys7</sha1>
    </revision>
    <revision>
      <id>4678498</id>
      <parentid>4678497</parentid>
      <timestamp>2026-10-27T14:56:08Z</timestamp>
      <contributor>
        <username>Afreeman8</username>
        <id>3626850</id>
      </contributor>
      <minor />
      <origin>4678498</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22397" sha1="eb6u1uyusq3dz8s2t3w98y0li5wjzrf" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;446&quot; height=&quot;372&quot; align=&quot;right&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of [[wikipedia:Interstate_70|Interstate 70]] (I-70) is a gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992. The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. 

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.&lt;ref name=&quot;:2&quot; /&gt;  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the [[wikipedia:Colorado_River|Colorado River]] made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.&lt;ref name=&quot;:2&quot; /&gt;
[[File:Glenwood Canyon (2614828822).jpg|thumb|Glenwood Canyon as seen from I-70]]
Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

The public opposition to the project was substantial at times, with the enlistment of [[wikipedia:John_Denver|John Denver]], the movement gained a lot of attention. The groups letter to the governor stated, “It is impossible to put such a highway through this canyon without permanently scarring the several million year old unique geologic formations and further disrupting the Colorado River headwaters.”&lt;ref name=&quot;:2&quot; /&gt; The resistance evolved from trying to block the route in its entirety to making sure it affected the nature of the canyon in the least way possible.

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.
[[File:CO 28 I70 FHWA 1992.jpg|thumb|Photo from Construction]]
The federal government required the state of Colorado to incorporate the public due to public disapproval of the project. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.
[[File:Glenwood Canyon - panoramio (1).jpg|thumb|View of Stacked Roadway with a viaduct]]
However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. This was the first roadway to make substantial use of posttensioned concrete slabs on at grade construction. This was due to the lack of a suitable foundation in many sections.&lt;ref&gt;{{Cite web |date=March 3, 2021 |title=History Lesson: The last piece of the Interstate Highway System may have been the toughest |url=https://www.asce.org/publications-and-news/civil-engineering-source/civil-engineering-magazine/issues/magazine-issue/article/2021/03/the-last-piece-of-the-interstate-highway-system-may-have-been-the-toughest |access-date=2026-10-27 |website=www.asce.org |language=en-US}}&lt;/ref&gt; The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

* Early parts of 20th century
** Earlier transportation routes establish the canyon’s importance as a regional corridor.
* 1960s–1970s
** Interstate planning proceeds amid environmental concerns and debates about the proposed route.
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the Glenwood Canyon segment.
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original 1992 $490 million expenditure equates to approximately $1.154 billion in January 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
[[File:2020 08 23-20.41.33.572-CDT.jpg|thumb|Grizzly Creek Fire above the Canyon]]
The Grizzly Creek Fire was a major wildfire that burned 32,631 acres in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue.

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” required heavy equipment and more than 200 loads of debris removed in a single day.

These disasters caused rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction.
== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered.

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}</text>
      <sha1>eb6u1uyusq3dz8s2t3w98y0li5wjzrf</sha1>
    </revision>
    <revision>
      <id>4678505</id>
      <parentid>4678498</parentid>
      <timestamp>2026-10-27T15:47:54Z</timestamp>
      <contributor>
        <username>JGiffordAtMason</username>
        <id>3358507</id>
      </contributor>
      <minor />
      <comment>JGiffordAtMason moved page [[Infrastructure Past, Present, and Future/Mississippi River Locks and Dams]] to [[Infrastructure Past, Present, and Future/Glenwood Canyon]]: Correct page title; Fall 2026 case study is Glenwood Canyon.</comment>
      <origin>4678498</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22397" sha1="eb6u1uyusq3dz8s2t3w98y0li5wjzrf" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;446&quot; height=&quot;372&quot; align=&quot;right&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of [[wikipedia:Interstate_70|Interstate 70]] (I-70) is a gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992. The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. 

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.&lt;ref name=&quot;:2&quot; /&gt;  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the [[wikipedia:Colorado_River|Colorado River]] made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.&lt;ref name=&quot;:2&quot; /&gt;
[[File:Glenwood Canyon (2614828822).jpg|thumb|Glenwood Canyon as seen from I-70]]
Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

The public opposition to the project was substantial at times, with the enlistment of [[wikipedia:John_Denver|John Denver]], the movement gained a lot of attention. The groups letter to the governor stated, “It is impossible to put such a highway through this canyon without permanently scarring the several million year old unique geologic formations and further disrupting the Colorado River headwaters.”&lt;ref name=&quot;:2&quot; /&gt; The resistance evolved from trying to block the route in its entirety to making sure it affected the nature of the canyon in the least way possible.

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.
[[File:CO 28 I70 FHWA 1992.jpg|thumb|Photo from Construction]]
The federal government required the state of Colorado to incorporate the public due to public disapproval of the project. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.
[[File:Glenwood Canyon - panoramio (1).jpg|thumb|View of Stacked Roadway with a viaduct]]
However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. This was the first roadway to make substantial use of posttensioned concrete slabs on at grade construction. This was due to the lack of a suitable foundation in many sections.&lt;ref&gt;{{Cite web |date=March 3, 2021 |title=History Lesson: The last piece of the Interstate Highway System may have been the toughest |url=https://www.asce.org/publications-and-news/civil-engineering-source/civil-engineering-magazine/issues/magazine-issue/article/2021/03/the-last-piece-of-the-interstate-highway-system-may-have-been-the-toughest |access-date=2026-10-27 |website=www.asce.org |language=en-US}}&lt;/ref&gt; The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

* Early parts of 20th century
** Earlier transportation routes establish the canyon’s importance as a regional corridor.
* 1960s–1970s
** Interstate planning proceeds amid environmental concerns and debates about the proposed route.
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the Glenwood Canyon segment.
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original 1992 $490 million expenditure equates to approximately $1.154 billion in January 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
[[File:2020 08 23-20.41.33.572-CDT.jpg|thumb|Grizzly Creek Fire above the Canyon]]
The Grizzly Creek Fire was a major wildfire that burned 32,631 acres in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue.

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” required heavy equipment and more than 200 loads of debris removed in a single day.

These disasters caused rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction.
== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered.

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}</text>
      <sha1>eb6u1uyusq3dz8s2t3w98y0li5wjzrf</sha1>
    </revision>
    <revision>
      <id>4678509</id>
      <parentid>4678505</parentid>
      <timestamp>2026-10-27T15:54:44Z</timestamp>
      <contributor>
        <username>~2026-57285-62</username>
        <id>3629487</id>
      </contributor>
      <comment>Timeline</comment>
      <origin>4678509</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23683" sha1="gu8d91hf5fsiffv3dfb8r6d5uun92n1" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;446&quot; height=&quot;372&quot; align=&quot;right&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of [[wikipedia:Interstate_70|Interstate 70]] (I-70) is a gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992. The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. 

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.&lt;ref name=&quot;:2&quot; /&gt;  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the [[wikipedia:Colorado_River|Colorado River]] made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.&lt;ref name=&quot;:2&quot; /&gt;
[[File:Glenwood Canyon (2614828822).jpg|thumb|Glenwood Canyon as seen from I-70]]
Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

The public opposition to the project was substantial at times, with the enlistment of [[wikipedia:John_Denver|John Denver]], the movement gained a lot of attention. The groups letter to the governor stated, “It is impossible to put such a highway through this canyon without permanently scarring the several million year old unique geologic formations and further disrupting the Colorado River headwaters.”&lt;ref name=&quot;:2&quot; /&gt; The resistance evolved from trying to block the route in its entirety to making sure it affected the nature of the canyon in the least way possible.

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.
[[File:CO 28 I70 FHWA 1992.jpg|thumb|Photo from Construction]]
The federal government required the state of Colorado to incorporate the public due to public disapproval of the project. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.
[[File:Glenwood Canyon - panoramio (1).jpg|thumb|View of Stacked Roadway with a viaduct]]
However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. This was the first roadway to make substantial use of posttensioned concrete slabs on at grade construction. This was due to the lack of a suitable foundation in many sections.&lt;ref&gt;{{Cite web |date=March 3, 2021 |title=History Lesson: The last piece of the Interstate Highway System may have been the toughest |url=https://www.asce.org/publications-and-news/civil-engineering-source/civil-engineering-magazine/issues/magazine-issue/article/2021/03/the-last-piece-of-the-interstate-highway-system-may-have-been-the-toughest |access-date=2026-10-27 |website=www.asce.org |language=en-US}}&lt;/ref&gt; The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |date=July 30, 2026 |title=CDOT marks 5-year anniversary of historic Glenwood Canyon damage with 6-part mini-documentary, “From Ashes to Asphalt: Glenwood Canyon Recovery” |url=https://www.codot.gov/news/2026/july2026news/historic-glenwood-canyon-recovery-mini-documentary |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

*1956
** The Federal-Aid Highway Act launches the Interstate Highway System. Plans begin for extending I-70 across Colorado
* 1950s-1970s
** Engineers, planners, environmental groups, and government agencies spend more than two decades studying potential routes addressing environmental concerns.&lt;ref&gt;{{Cite web |last=Noel |first=Thomas |date=2012 |title=I-70 in Glenwood Canyon |url=https://sah-archipedia.org/buildings/CO-01-GF18 |url-status=live |access-date=October 27,2026 |website=SAH ARCHIPEDIA}}&lt;/ref&gt;
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the final 12.5-mile I-70 Glenwood Canyon segment.&lt;ref&gt;{{Cite web |title=I-70 Glenwood Canyon History |url=https://www.codot.gov/about/CDOTHistory/50th-anniversary/glenwood-canyon |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original 1992 $490 million expenditure equates to approximately $1.154 billion in January 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
[[File:2020 08 23-20.41.33.572-CDT.jpg|thumb|Grizzly Creek Fire above the Canyon]]
The Grizzly Creek Fire&lt;ref&gt;{{Cite web |last=Rengers |first=Jaime Kostelnik, Robert Schmitt, and Francis |date=2026-06-12 |title=Monsoon season is causing big problems in northwestern Colorado. Near daily debris flows and flooding in Glenwood Canyon are having enormous economic and environmental impacts for the state of Colorado and beyond. |url=https://storymaps.arcgis.com/stories/25b4a7398e0e406fb6cd0f32a2c71331 |access-date=2026-10-27 |website=ArcGIS StoryMaps |language=en}}&lt;/ref&gt; was a major wildfire that burned 32,631 acres in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue.

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” &lt;ref&gt;{{Cite web |date=2021-08-13 |title=Glenwood Canyon Mudslides Caused A 'Pothole From Hell' On I-70 - CBS Colorado |url=https://www.cbsnews.com/colorado/news/interstate-70-mudslides-glenwood-canyon-rain-forecast/ |access-date=2026-10-27 |website=www.cbsnews.com |language=en-US}}&lt;/ref&gt;required heavy equipment and more than 200 loads of debris removed in a single day.

These disasters caused rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction.
== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered.

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}
&lt;references /&gt;</text>
      <sha1>gu8d91hf5fsiffv3dfb8r6d5uun92n1</sha1>
    </revision>
    <revision>
      <id>4678510</id>
      <parentid>4678509</parentid>
      <timestamp>2026-10-27T15:56:45Z</timestamp>
      <contributor>
        <username>Afreeman8</username>
        <id>3626850</id>
      </contributor>
      <minor />
      <origin>4678510</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23508" sha1="cptof8itjonjioo10icom22sdhai6l0" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;446&quot; height=&quot;372&quot; align=&quot;right&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of [[wikipedia:Interstate_70|Interstate 70]] (I-70) is a gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992. The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. 

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.&lt;ref name=&quot;:2&quot; /&gt;  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed mountains, valleys, and overall terrain in the area proved to be an obstacle which resulted in slower travel through canyon. Connection of communities among other factors could support interstate commerce resulting is an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the [[wikipedia:Colorado_River|Colorado River]] made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.&lt;ref name=&quot;:2&quot; /&gt;
[[File:Glenwood Canyon (2614828822).jpg|thumb|Glenwood Canyon as seen from I-70]]
Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

The public opposition to the project was substantial at times, with the enlistment of [[wikipedia:John_Denver|John Denver]], the movement gained a lot of attention. The groups letter to the governor stated, “It is impossible to put such a highway through this canyon without permanently scarring the several million year old unique geologic formations and further disrupting the Colorado River headwaters.”&lt;ref name=&quot;:2&quot; /&gt; The resistance evolved from trying to block the route in its entirety to making sure it affected the nature of the canyon in the least way possible.

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.
[[File:CO 28 I70 FHWA 1992.jpg|thumb|Photo from Construction]]
The federal government required the state of Colorado to incorporate the public due to public disapproval of the project. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.
[[File:Glenwood Canyon - panoramio (1).jpg|thumb|View of Stacked Roadway with a viaduct]]
However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. This was the first roadway to make substantial use of posttensioned concrete slabs on at grade construction. This was due to the lack of a suitable foundation in many sections.&lt;ref&gt;{{Cite web |date=March 3, 2021 |title=History Lesson: The last piece of the Interstate Highway System may have been the toughest |url=https://www.asce.org/publications-and-news/civil-engineering-source/civil-engineering-magazine/issues/magazine-issue/article/2021/03/the-last-piece-of-the-interstate-highway-system-may-have-been-the-toughest |access-date=2026-10-27 |website=www.asce.org |language=en-US}}&lt;/ref&gt; The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref&gt;{{Cite web |title=Glenwood Canyon Flooding and Debris Flows |url=https://geonarrative.usgs.gov/landslides/grizzly_creek/grizzly_creek_index.html |access-date=2026-10-27 |website=geonarrative.usgs.gov}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

*1956
** The Federal-Aid Highway Act launches the Interstate Highway System. Plans begin for extending I-70 across Colorado
* 1950s-1970s
** Engineers, planners, environmental groups, and government agencies spend more than two decades studying potential routes addressing environmental concerns.&lt;ref&gt;{{Cite web |last=Noel |first=Thomas |date=2012 |title=I-70 in Glenwood Canyon |url=https://sah-archipedia.org/buildings/CO-01-GF18 |url-status=live |access-date=October 27,2026 |website=SAH ARCHIPEDIA}}&lt;/ref&gt;
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the final 12.5-mile I-70 Glenwood Canyon segment.&lt;ref&gt;{{Cite web |title=I-70 Glenwood Canyon History |url=https://www.codot.gov/about/CDOTHistory/50th-anniversary/glenwood-canyon |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* 2024
** Scientific research evaluates post-fire debris-flow thresholds and modeling in the Grizzly Creek Fire area.

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original 1992 $490 million expenditure equates to approximately $1.154 billion in January 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
[[File:2020 08 23-20.41.33.572-CDT.jpg|thumb|Grizzly Creek Fire above the Canyon]]
The Grizzly Creek Fire&lt;ref&gt;{{Cite web |last=Rengers |first=Jaime Kostelnik, Robert Schmitt, and Francis |date=2026-06-12 |title=Monsoon season is causing big problems in northwestern Colorado. Near daily debris flows and flooding in Glenwood Canyon are having enormous economic and environmental impacts for the state of Colorado and beyond. |url=https://storymaps.arcgis.com/stories/25b4a7398e0e406fb6cd0f32a2c71331 |access-date=2026-10-27 |website=ArcGIS StoryMaps |language=en}}&lt;/ref&gt; was a major wildfire that burned 32,631 acres in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue.

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” &lt;ref&gt;{{Cite web |date=2021-08-13 |title=Glenwood Canyon Mudslides Caused A 'Pothole From Hell' On I-70 - CBS Colorado |url=https://www.cbsnews.com/colorado/news/interstate-70-mudslides-glenwood-canyon-rain-forecast/ |access-date=2026-10-27 |website=www.cbsnews.com |language=en-US}}&lt;/ref&gt;required heavy equipment and more than 200 loads of debris removed in a single day.

These disasters caused rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction.
== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered.

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}
&lt;references /&gt;</text>
      <sha1>cptof8itjonjioo10icom22sdhai6l0</sha1>
    </revision>
    <revision>
      <id>4678511</id>
      <parentid>4678510</parentid>
      <timestamp>2026-10-27T16:04:56Z</timestamp>
      <contributor>
        <username>~2026-57285-62</username>
        <id>3629487</id>
      </contributor>
      <origin>4678511</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23606" sha1="ghahrwzsle5s9rimp4yxeag59726g80" xml:space="preserve">== Overview ==
&lt;mapframe latitude=&quot;39&quot; longitude=&quot;-105.55&quot; zoom=&quot;6&quot; width=&quot;446&quot; height=&quot;372&quot; align=&quot;right&quot; text=&quot;Map of Colorado with Glenwood Canyon marked&quot;&gt;
{
  &quot;type&quot;: &quot;Feature&quot;,
  &quot;properties&quot;: {
    &quot;title&quot;: &quot;Glenwood Canyon&quot;,
    &quot;description&quot;: &quot;Canyon on the Colorado River along Interstate 70, east of Glenwood Springs&quot;,
    &quot;marker-symbol&quot;: &quot;marker&quot;,
    &quot;marker-color&quot;: &quot;d33&quot;,
    &quot;marker-size&quot;: &quot;large&quot;
  },
  &quot;geometry&quot;: {
    &quot;type&quot;: &quot;Point&quot;,
    &quot;coordinates&quot;: [-107.20, 39.57]
  }
}
&lt;/mapframe&gt;
The Glenwood Canyon segment of [[wikipedia:Interstate_70|Interstate 70]] (I-70) is a gorge along the Colorado River in western Colorado that is a critical transportation link connecting Denver to Grand Junction, supporting commerce, tourism, and regional mobility. The project closed a major gap in I-70 across Colorado, improving connectivity. Infrastructure needed to be expanded without significantly changing the landscape. In the project, environmental concerns, engineering requirements, construction cost, and public interest needed to be considered. In 1980, construction of the Glenwood Canyon segment began, and the highway opened in October 1992. The case has relevance today as problems have been exposed and emergency repair requirements have raised questions about resilience, coordination of agencies, and public finance. Today Glenwood Canyon is experiencing active lane closures, new regulations/requirements, and ongoing vulnerability to mudslides and rockfall. 

== Historical Context ==
Some of the purposes of I-70 were improved interstate connectivity, traffic movement, access to western Colorado, and overall support of the region. But Preexisting roads and routes needed improvements, which made the canyon a potential regional connection. Glenwood Canyon is a narrow valley along the Colorado River. Steep canyon walls and limited space were obstacles for any transportation infrastructure. The area of the proposed highway already had environmental and recreational resources surrounding it. If a segment were to be built here, it couldn't cause unacceptable environmental damage.
[[File:Map of current Interstates.svg|thumb|Map of the Current Interstate System in the US]]
The section represented the final piece of the original Eisenhower system, finally linking I-70 in Denver to I-15 in Utah as authorized by Congress.&lt;ref name=&quot;:1&quot;&gt;{{Cite web |last=Prosence |first=Richard |last2=Haley |first2=John |date=1980 |title=Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked |url=https://onlinepubs.trb.org/Onlinepubs/trr/1980/757/757-001.pdf |website=Transportation Research Record |edition=757}}&lt;/ref&gt; This link replaced a section of U.S. Route 6 that was treacherous for drivers and a bottleneck for the system.&lt;ref name=&quot;:2&quot; /&gt;  

== Transportation Infrastructure Goals ==
Improvement in access to mountains. Before the segment was completed, mountains, valleys, and overall terrain in the area proved to be an obstacle, which resulted in slower travel through the canyon. Connecting communities, among other factors, could support interstate commerce, resulting in an economic boost. Without the Canyon segment, transportation would continue to be limited by Colorado's geography. 

== Environmental Considerations ==
The development of Interstate 70 through Glenwood Canyon presented a significant policy conflict between improving transportation and protecting Colorado’s natural environment. The canyon’s natural features of steep walls, scenic landscape, and proximity to the [[wikipedia:Colorado_River|Colorado River]] made conventional highway construction difficult. Concerns included damage to the canyon’s visual character, disruption of existing vegetation and wildlife habitats, and potential impacts on recreational resources. Conversely, completing I-70 was important for establishing a continuous interstate route across Colorado. Policymakers therefore faced the challenge of balancing improving transportation access without causing unacceptable environmental harm.

Federal environmental review requirements influenced how the project was evaluated. The National Environmental Policy Act, enacted in 1970, required federal agencies to assess the environmental consequences of major projects and consider alternatives.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |date=January 2019 |title=Historic Context: Glenwood Canyon Segment of Interstate Highway 70 |url=https://www.codot.gov/programs/environmental/assets/copy3_of_assets/documents/glenwood-canyon-historic-context-1.pdf |website=Colorado Department of Transportation |publisher=Mead &amp; Hunt}}&lt;/ref&gt; The alternatives included four routes determined by Chicago Law firm De Leuw, Cather &amp; Company. An environmental impact statement evaluated alternative routes, including bypasses north and south of the canyon, before the canyon alignment was selected. The process demonstrated that environmental concerns could influence the fundamental location and design of a major transportation project rather than simply its construction methods.&lt;ref name=&quot;:2&quot; /&gt;
[[File:Glenwood Canyon (2614828822).jpg|thumb|Glenwood Canyon as seen from I-70]]
Public participation became particularly important because residents and environmental advocates feared that a conventional interstate would permanently damage the canyon. In their 1980 paper, “Glenwood Canyon Interstate 70: A Preliminary Design Process That Worked,” Richard A. Prosence and John L. Haley describe an approach that incorporated public input into the evaluation of environmental, recreational, and aesthetic considerations. Engineers, architects, environmental specialists, recreation advocates, and other participants helped assess alternative designs. Public hearings and an open planning process contributed to broader public support for the project.&lt;ref name=&quot;:1&quot; /&gt;

The public opposition to the project was substantial at times, with the enlistment of [[wikipedia:John_Denver|John Denver]], the movement gained a lot of attention. The groups letter to the governor stated, “It is impossible to put such a highway through this canyon without permanently scarring the several million year old unique geologic formations and further disrupting the Colorado River headwaters.”&lt;ref name=&quot;:2&quot; /&gt; The resistance evolved from trying to block the route in its entirety to making sure it affected the nature of the canyon in the least way possible.

Environmental considerations also changed the highway’s engineering. The final design incorporated terraced roadways, complex cantilevered sections, retaining walls, tunnels, and revegetation to reduce the highway’s impact on the appearance. These features added complexity and required specialized planning and construction techniques. Although they helped limit environmental damage, they also increased project complexity. In their 1983 article, Ralph J. Trapani and Eric A. Beal explain that the lengthy design process and environmental constraints significantly increased project costs.&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Trapani |first=Ralph J. |last2=Beal |first2=Eric A. |date=1983-05-01 |title=Glenwood Canyon I‐70: Environmental Concern |url=https://ascelibrary.org/doi/10.1061/%28ASCE%290733-947X%281983%29109%3A3%28403%29 |journal=Journal of Transportation Engineering |language=en |publisher=American Society of Civil Engineers |volume=109 |issue=3 |pages=403–413 |doi=10.1061/(ASCE)0733-947X(1983)109:3(403)}}&lt;/ref&gt;

== Engineering, Construction, and Project Delivery ==
The Glenwood Canyon section of Interstate 70 required engineers to construct a four-lane highway through a narrow, steep-sided canyon alongside the Colorado River while protecting its scenic and ecological value. The confined terrain left limited space for roadbeds, construction equipment, and conventional highway structures. Construction therefore required extensive excavation, careful traffic management, and engineering solutions adapted to the canyon’s natural contours. Completed in 1992 after approximately 12 years of construction, the project cost nearly $490 million.&lt;ref name=&quot;:2&quot; /&gt;

Engineers combined several specialized techniques to accommodate the terrain. The highway incorporated elevated bridges and viaducts, three tunnels, approximately 15 miles of retaining walls, and terraced roadways. In some locations, roadways extended beyond retaining walls through cantilevered designs, reducing the space needed for construction. Designers also positioned the westbound lanes above the eastbound lanes in selected areas and used slender bridge supports to reduce the highway’s visual impact. Landscaping and revegetation, including planting native trees and shrubs, helped restore areas disturbed during construction.&lt;ref name=&quot;:3&quot; /&gt; These innovations demonstrated that transportation capacity could be expanded without relying entirely on conventional construction methods that would substantially alter the canyon.
[[File:CO 28 I70 FHWA 1992.jpg|thumb|Photo from Construction]]
The federal government required the state of Colorado to incorporate the public due to public disapproval of the project. A citizen advisory group influenced the project’s environmentally sensitive design, while engineers and designers considered public responses to proposed structures and their appearance. Full-scale models of design alternatives allowed the project team and members of the public to evaluate how different structures would look in the canyon.&lt;ref name=&quot;:1&quot; /&gt; This approach connected technical planning with community concerns and helped prioritize scenic preservation alongside transportation needs.
[[File:Glenwood Canyon - panoramio (1).jpg|thumb|View of Stacked Roadway with a viaduct]]
However, the specialized design also created substantial construction challenges. Building tunnels, elevated structures, and retaining walls in confined terrain increased technical complexity, required careful scheduling, and contributed to the project’s high cost. This was the first roadway to make substantial use of posttensioned concrete slabs on at grade construction. This was due to the lack of a suitable foundation in many sections.&lt;ref&gt;{{Cite web |date=March 3, 2021 |title=History Lesson: The last piece of the Interstate Highway System may have been the toughest |url=https://www.asce.org/publications-and-news/civil-engineering-source/civil-engineering-magazine/issues/magazine-issue/article/2021/03/the-last-piece-of-the-interstate-highway-system-may-have-been-the-toughest |access-date=2026-10-27 |website=www.asce.org |language=en-US}}&lt;/ref&gt; The completed infrastructure also created ongoing maintenance responsibilities, particularly for bridges, tunnels, and retaining structures. Environmental mitigation required additional investment in slope stabilization and revegetation.&lt;ref&gt;{{Cite journal |last=Pointner II |first=Norbert J. |date=1993-06-01 |title=A Highway in the Landscape—1-70 Through Glenwood Canyon, Colorado |url=https://doi.org/10.1080/07349165.1993.9725754 |journal=Impact Assessment |publisher=Taylor &amp; Francis |volume=11 |issue=2 |pages=203–207 |doi=10.1080/07349165.1993.9725754 |issn=0734-9165}}&lt;/ref&gt;

Overall, Glenwood Canyon’s final design represented a strong compromise between transportation capacity and environmental protection. Although the project was expensive and complex, its engineering innovations reduced the highway’s visual footprint and helped preserve the canyon’s character while completing a critical interstate connection.

== Key Actors and Institutional Arrangements ==
The development of Interstate 70 (I-70) through Glenwood Canyon required the collaboration of several entities due to the intersection of various policy areas including transportation, environment and emergency management. The Colorado Department of Transportation (CDOT) was the primary state agency responsible for the construction, operation and maintenance of the state highway system. Thus, it took the lead role for planning, engineering, and construction of I-70 through Glenwood Canyon. The role of CDOT was extended beyond construction as evidenced by its collaboration in the management of I-70 in 2021 during debris flows.

The Federal Highway Administration (FHWA) provided federal oversight, financing and approval for the I-70 project. During disasters, it aided in the relief, and recovery efforts for the affected interstate. At the state level, the Colorado Transportation Commission set priorities for the transportation sector, and determined funding allocations for the various transportation projects, while the Governor, in consultation with other executive agencies, invoked emergency powers and managed disruptions in the state’s transportation systems. This created a well-defined division of responsibility for setting priorities, managing transportation projects, and emergency management.

State and Federal environment and land management agencies were also key partners. The U.S. Forest Service, in addition to Federal and State agencies dealing with Environmental Impact Statements and public land management, assisted to address effects on natural resources, recreation and the Colorado River. The U.S. Geological Survey (USGS) provided research on debris flow potential following the 2020 Grizzly Creek Fire. USGS research illustrated how debris flows are a real possibility following wildfires.&lt;ref name=&quot;:4&quot;&gt;{{Cite web |title=Glenwood Canyon Flooding and Debris Flows |url=https://geonarrative.usgs.gov/landslides/grizzly_creek/grizzly_creek_index.html |access-date=2026-10-27 |website=geonarrative.usgs.gov}}&lt;/ref&gt;

Citizen advisory groups and environmental organizations represented public concerns about scenic preservation, wildlife, and recreational access. Their advocacy influenced the debate over highway alignment and design, encouraging engineers to adopt measures that reduced environmental and visual impacts. Engineering firms and construction contractors translated these policy goals into practical designs, developing and building the specialized tunnels, bridges, and retaining structures required by the canyon’s terrain. Local governments, businesses, motorists, and freight operators were also important stakeholders because they experienced the effects of construction, highway closures, and disruptions to regional travel and commerce.

The 2021 debris flows demonstrated how these actors depended on one another during emergencies. Governor Jared Polis declared a disaster emergency and authorized CDOT to seek federal emergency-relief funding through the FHWA.&lt;ref&gt;{{Cite web |title=Governor Polis Authorizes Disaster Declaration in Response to Devastating Glenwood Canyon Mudslides {{!}} Colorado Governor Jared Polis |url=https://www.colorado.gov/governor/news/governor-polis-authorizes-disaster-declaration-response-devastating-glenwood-canyon-mudslides |access-date=2026-10-27 |website=www.colorado.gov}}&lt;/ref&gt; CDOT managed closures, debris removal, and highway repairs, while federal and state agencies coordinated efforts to address damage to the river, public lands, and recreation facilities.

Together, these actors formed a multi-level institutional arrangement in which transportation agencies managed infrastructure, elected officials provided policy direction and emergency authority, scientific agencies assessed hazards, and citizens and businesses communicated public needs. The arrangement enabled coordination across complex responsibilities, although it also required agencies to balance competing priorities, funding constraints, environmental risks, and the need to restore a critical transportation corridor.

== Project Timeline and Major Milestones ==

*1956
** The Federal-Aid Highway Act launches the Interstate Highway System. Plans begin for extending I-70 across Colorado
* 1950s-1970s
** Engineers, planners, environmental groups, and government agencies spend more than two decades studying potential routes, addressing environmental concerns.&lt;ref&gt;{{Cite web |last=Noel |first=Thomas |date=2012 |title=I-70 in Glenwood Canyon |url=https://sah-archipedia.org/buildings/CO-01-GF18 |url-status=live |access-date=October 27,2026 |website=SAH ARCHIPEDIA}}&lt;/ref&gt;
* 1976
** Federal legislation provides flexibility from certain interstate highway standards.
* 1980
** Construction begins on the final 12.5-mile I-70 Glenwood Canyon segment.&lt;ref&gt;{{Cite web |title=I-70 Glenwood Canyon History |url=https://www.codot.gov/about/CDOTHistory/50th-anniversary/glenwood-canyon |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt;
* 1980–1992
** Specialized engineering and environmentally sensitive construction continue.
* October 14, 1992
** I-70 through Glenwood Canyon officially opens.
* 2011
** FHWA approves the Record of Decision for the broader I-70 Mountain Corridor Programmatic Environmental Impact Statement.
* 2020
** The Grizzly Creek Fire burns land near the highway.
* Summer 2021
** Rainfall triggers post-fire flooding and debris flows, resulting in repeated highway closures.&lt;ref name=&quot;:4&quot; /&gt;
* August 2021
** Colorado requests federal assistance for emergency repairs and resilience-related work.
* August 14, 2021
** The highway reopens to traffic following emergency cleanup and repairs.
* Post 2021 
** Ongoing maintenance, bridge rehabilitation, tunnel improvements, rockfall mitigation, wildfire recovery work, and resilience upgrades continue along the corridor. 

== Cost History and Financial Structure ==
The original construction of Interstate 70 through Glenwood Canyon cost approximately $490 million and took about 12 years, from 1980 to 1992.&lt;ref name=&quot;:2&quot; /&gt; Although this was a substantial investment, the project completed a critical interstate connection through difficult terrain while incorporating extensive environmental protections. The cost reflects not only highway construction but also specialized engineering, including tunnels, bridges, retaining walls, and structures designed to minimize disturbance to the canyon.

Federal funding covered the overwhelming majority of the original project’s expenses. The project was funded under the Federal Aid Highway Act of 1956, granting a 90/10, federal/state, split. This funding structure was used to help assist states in building out the nation's system.&lt;ref&gt;{{Cite web |date=June 29, 1956 |title=Title 1: Federal-Aid Highway Act of 1956 |url=https://www.govinfo.gov/content/pkg/STATUTE-70/pdf/STATUTE-70-Pg374.pdf |website=GovInfo}}&lt;/ref&gt;

Environmental requirements also affected project costs. Extensive planning, environmental review, and specialized construction techniques increased the resources needed to protect the canyon while completing the highway. To compare costs across time, the original 1992 $490 million expenditure equates to approximately $1.154 billion in January 2026 dollars.&lt;ref&gt;{{Cite web |title=CPI Inflation Calculator : U.S. Bureau of Labor Statistics |url=https://www.bls.gov/data/inflation_calculator.htm |access-date=2026-10-27 |website=Bureau of Labor Statistics |language=en}}&lt;/ref&gt;

The 2021 debris flows created a separate financial challenge. Colorado requested $116 million in federal emergency assistance, including $50 million for a future resilience and redundancy study. The FHWA initially approved an expedited $11.6 million release to help cover emergency reopening work and begin permanent repairs.&lt;ref&gt;{{Cite web |date=August 18, 2021 |title=Glenwood Canyon Update on Federal Assistance Requested by Colorado |url=https://www.codot.gov/news/2021/august-2021/glenwood-federal-assistance-update |access-date=2026-10-27 |website=Colorado Department of Transportation |language=en-us}}&lt;/ref&gt; These figures represent a funding request and initial assistance, not the final total cost of repairs.

Distinguishing original construction from subsequent maintenance and emergency repairs is essential: these expenditures occurred in different periods and addressed different needs. Ultimately, Glenwood Canyon demonstrates the challenge of balancing cost control with environmental safeguards and long-term resilience. The initial investment delivered a vital transportation corridor, but the 2021 disaster showed that maintaining it requires continued funding, hazard mitigation, and preparation for future extreme weather.

== Disasters ==
[[File:2020 08 23-20.41.33.572-CDT.jpg|thumb|Grizzly Creek Fire above the Canyon]]
The Grizzly Creek Fire&lt;ref&gt;{{Cite web |last=Rengers |first=Jaime Kostelnik, Robert Schmitt, and Francis |date=2026-06-12 |title=Monsoon season is causing big problems in northwestern Colorado. Near daily debris flows and flooding in Glenwood Canyon are having enormous economic and environmental impacts for the state of Colorado and beyond. |url=https://storymaps.arcgis.com/stories/25b4a7398e0e406fb6cd0f32a2c71331 |access-date=2026-10-27 |website=ArcGIS StoryMaps |language=en}}&lt;/ref&gt; was a major wildfire that burned 32,631 acres in Glenwood Canyon, Garfield County, Colorado, from August 10 to December 18, 2020. It was human‑caused, reportedly ignited by a truck’s chains. Much vegetation was damaged. When vegetation loss occurs, the roots that help to hold soil down are disrupted. When this happens, erosion can become a significant issue.

In 2021, mudslides resulted in extended closures of the interstate. Slopes still had little to no vegetation and soil stability from the Grizzly Creek Fire. Steep terrain, heavy rain, and saturated soil left the area susceptible to mudslides. Major damage at Blue Gulch, including what officials called a “pothole from hell,” &lt;ref&gt;{{Cite web |date=2021-08-13 |title=Glenwood Canyon Mudslides Caused A 'Pothole From Hell' On I-70 - CBS Colorado |url=https://www.cbsnews.com/colorado/news/interstate-70-mudslides-glenwood-canyon-rain-forecast/ |access-date=2026-10-27 |website=www.cbsnews.com |language=en-US}}&lt;/ref&gt;required heavy equipment and more than 200 loads of debris removed in a single day.

These disasters caused rest area closures, including Hanging Lake and Grizzly Creek, due to infrastructure damage and safety concerns, 2.5 Hour detours in some cases, and full closure of Glenwood Canyon for days, with one partial reopening planned only after extensive debris removal and roadbed reconstruction.
== Key ideas and Lessons ==
Though beneficial to Colorado, the Glenwood Canyon segment of I-70 offers several lessons for future projects to keep in mind. Future design and construction of similar projects must balance the need for interstate transportation, environmental protection, construction costs, and public safety. Optimizing a structure alone is not enough; interactions among the environment, operations, maintenance, and human safety must be considered.

'''Natural hazards can add up:'''

2020 Grizzly Creek fire combined with the heavy rain of 2021. Unstable slopes from the fires were rained on, causing debris that buried I-70 with mud, rocks, and trees. Planners and engineers will need to consider how disasters can interact.

'''Design needs some resilience:'''

Specifically in areas with mountains and valleys, infrastructure needs to withstand compound and extreme events. Historical averages do not tell the whole story. CDOT has emphasized climate-resilient engineering and improved hazard monitoring since disasters struck.

'''Critical transportation needs redundancy:'''

During the Closure of Glenwood Canyon, long detours were forced. This added hours to travel times and This proved how vulnerable single routes are.{{BookCat}}
&lt;references /&gt;</text>
      <sha1>ghahrwzsle5s9rimp4yxeag59726g80</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Edit filter/False positives/Archive 5</title>
    <ns>4</ns>
    <id>485937</id>
    <revision>
      <id>4678662</id>
      <parentid>4673071</parentid>
      <timestamp>2026-10-28T08:10:30Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <minor />
      <comment>Bot: Archiving 2 threads from [[Wikibooks:Edit filter/False positives]]</comment>
      <origin>4678662</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6752" sha1="d83k35pffn77yhq8uc9vky4fpl722xr" xml:space="preserve">{{talk archive}}

== Earthinators ==

;Username
: [[:b:User:Earthinators|Earthinators]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:Earthinators|discuss]]
|[[:b:Special:Emailuser/Earthinators|email]]
|[[:b:Special:Contributions/Earthinators|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:Earthinators}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:Earthinators}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=Earthinators}} filter log]&lt;/span&gt;)
;Page you were editing
: [[Earthinators]] &lt;span class=&quot;plainlinks&quot;&gt;([{{fullurl:Special:AbuseLog|wpSearchTitle=Earthinators}} filter log]) ([{{fullurl:Special:AbuseLog|wpSearchTitle=Earthinators&amp;wpSearchUser=Earthinators}} user filter log])&lt;/span&gt;
;Description
: I was trying to replace the main page of [[Earthinators]] with a neutral, instructional textbook version ([[Talk:Earthinators|the new text is on the talk page]]). The edit filter blocked me, saying the edit was &quot;potentially unconstructive&quot;. The new version follows Wikibooks guidelines – it’s a textbook, not a promotional page. Please allow the edit or make the change for me.
;Date and time
: 06:56, 11 July 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;

:{{EFFP|rf}} [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:48, 16 July 2026 (UTC)

== ~2026-40102-72 ==

;Username
: [[:b:User:~2026-40102-72|~2026-40102-72]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:~2026-40102-72|discuss]]
|[[:b:Special:Emailuser/~2026-40102-72|email]]
|[[:b:Special:Contributions/~2026-40102-72|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:~2026-40102-72}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:~2026-40102-72}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=%7E2026-40102-72}} filter log]&lt;/span&gt;)
;Page you were editing
: Page not specified
;Description
: 
;Date and time
: 20:26, 15 July 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;
:{{EFFP|nft}} [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 16:39, 16 July 2026 (UTC)

== ~2026-40102-72 ==

;Username
: [[:b:User:~2026-40102-72|~2026-40102-72]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:~2026-40102-72|discuss]]
|[[:b:Special:Emailuser/~2026-40102-72|email]]
|[[:b:Special:Contributions/~2026-40102-72|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:~2026-40102-72}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:~2026-40102-72}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=%7E2026-40102-72}} filter log]&lt;/span&gt;)
;Page you were editing
: Page not specified
;Description
: 
;Date and time
: 20:27, 15 July 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;
:{{EFFP|nft}} [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 16:39, 16 July 2026 (UTC)
== Madan Bibhishan Nagargoje ==

;Username
: [[:b:User:Madan Bibhishan Nagargoje|Madan Bibhishan Nagargoje]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:Madan Bibhishan Nagargoje|discuss]]
|[[:b:Special:Emailuser/Madan Bibhishan Nagargoje|email]]
|[[:b:Special:Contributions/Madan Bibhishan Nagargoje|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:Madan Bibhishan Nagargoje}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:Madan Bibhishan Nagargoje}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=Madan+Bibhishan+Nagargoje}} filter log]&lt;/span&gt;)
;Page you were editing
: Page not specified
;Description
: 
;Date and time
: 06:15, 22 July 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;
:This was correctly prevented because you were trying to add a link to a Google Drive file as a &quot;reference&quot;. If you are genuinely trying to add a reference, do this to a publicly available source and not a private Drive file. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 11:52, 13 August 2026 (UTC)

== ~2026-44191-83 ==

;Username
: [[:b:User:~2026-44191-83|~2026-44191-83]]&lt;span class=&quot;noprint&quot;&gt; {{toolbar|separator=dot
|[[:b:User talk:~2026-44191-83|discuss]]
|[[:b:Special:Emailuser/~2026-44191-83|email]]
|[[:b:Special:Contributions/~2026-44191-83|contribs]]
|[{{fullurl:b:Special:Log|user={{urlencode:~2026-44191-83}}}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;logs&lt;/span&gt;]
|[//tools.wmflabs.org/xtools/pcount/index.php?lang{{=}}en&amp;wiki{{=}}wikibooks&amp;name{{=}}{{urlencode:~2026-44191-83}} &lt;span style{{=}}&quot;color:#002bb8&quot;&gt;count&lt;/span&gt;]
}}&lt;/span&gt; (&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:AbuseLog|wpSearchUser=%7E2026-44191-83}} filter log]&lt;/span&gt;)
;Page you were editing
: [[An_Introduction_to_Dragon]] &lt;span class=&quot;plainlinks&quot;&gt;([{{fullurl:Special:AbuseLog|wpSearchTitle=An_Introduction_to_Dragon}} filter log]) ([{{fullurl:Special:AbuseLog|wpSearchTitle=An_Introduction_to_Dragon&amp;wpSearchUser=%7E2026-44191-83}} user filter log])&lt;/span&gt;
;Description
: Adding/expanding book content (introduction, table of contents, and lesson pages) for the Dragon programming language wikibook, based on the project's own source code and documentation. No spam or promotional intent.
;Date and time
: 08:15, 11 August 2026 (UTC)
;Comments
&lt;!-- Please leave this area blank for now, but be prepared to answer questions left by reviewing editors. Thanks! --&gt;
:The edit was flagged as it deleted a large amount of content in one go, a typical fingerprint of non-constructive editing. I can see your edit was constructive and I recommend you make your changes using smaller edits initially. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 11:50, 13 August 2026 (UTC)</text>
      <sha1>d83k35pffn77yhq8uc9vky4fpl722xr</sha1>
    </revision>
  </page>
  <page>
    <title>Template:Wikibooks Magazine Layout</title>
    <ns>10</ns>
    <id>486411</id>
    <revision>
      <id>4678660</id>
      <parentid>4677912</parentid>
      <timestamp>2026-10-28T08:05:09Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>MathsScienceNerd1 moved page [[User:MathsScienceNerd1/Wikibooks Magazine Layout]] to [[Template:Wikibooks Magazine Layout]] without leaving a redirect: Creating template page</comment>
      <origin>4677711</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2803" sha1="3yvw2we59tzyefcyes2uy2srid4p4gz" xml:space="preserve">{| class=&quot;wikitable mobiel100 pc60&quot; style=&quot;border-collapse: collapse; margin:auto;&quot;
! colspan=&quot;2&quot; style=&quot;width:50%; font-family: Verdana; font-size:50px; padding:10px; border:none; background-color:transparent;&quot; |[[File:Wikibooks-wordmark-vi.svg|frameless|300px|link=|style=margin-right: 50px|center]]&lt;span style=&quot;color:#1565C0&quot;&gt;M&lt;/span&gt;&lt;span style=&quot;color:#1565C0&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color:#1565C0&quot;&gt;g&lt;/span&gt;&lt;span style=&quot;color:#1565C0&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color:#1565C0&quot;&gt;z&lt;/span&gt;&lt;span style=&quot;color:#1565C0&quot;&gt;i&lt;/span&gt;&lt;span style=&quot;color:#1565C0&quot;&gt;n&lt;/span&gt;&lt;span style=&quot;color:#1565C0&quot;&gt;e&lt;/span&gt; &lt;small&gt;{{{issue number}}}&lt;/small&gt;
|-
| colspan=&quot;2&quot; style=&quot;padding:0px; border:none; background-color:transparent;&quot; |{{center|''{{{date}}} • Volume {{{volume}}}, Issue {{{issue}}}''}}
|-
| style=&quot;border:none; text-align: center;&quot; |◄ [[Wikibooks:Magazine/{{{previous issue}}}|Previous]]
| style=&quot;border:none; text-align: center;&quot; |[[Wikibooks:Magazine/{{{next issue}}}|Next]] ►
|-
| colspan=&quot;2&quot; style=&quot;padding:0px; border:none; background-color:transparent;&quot; |&lt;br&gt;&lt;hr style=&quot;margin:0;&quot;&gt;
|-
| style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; |
{{{article 1}}}
| style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; |
{{{article 2}}}
|-
| colspan=&quot;2&quot; style=&quot;padding:0px; border:none; background-color:transparent;&quot; |&lt;hr style=&quot;margin:0;&quot;&gt;
|-
| style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; |
{{{article 3}}}
| style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; |
{{{article 4}}}
{{#if: {{{article 5|}}} |
{{!}}-
{{!}} colspan=&quot;2&quot; style=&quot;padding:0px; border:none; background-color:transparent;&quot; {{!}}&lt;hr style=&quot;margin:0;&quot;&gt;
{{!}}-
{{!}} style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; {{!}}
{{{article 5}}}
{{!}} style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; {{!}}
{{{article 6}}}}}
{{#if: {{{article 7|}}} |
{{!}}-
{{!}} colspan=&quot;2&quot; style=&quot;padding:0px; border:none; background-color:transparent;&quot; {{!}}&lt;hr style=&quot;margin:0;&quot;&gt;
{{!}}-
{{!}} style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; {{!}}
{{{article 7}}}
{{!}} style=&quot;width: 50%; padding:10px; border:none; background-color:transparent; vertical-align: top;&quot; {{!}}
{{{article 8}}}}}
|}&lt;noinclude&gt;{{doc|content=
&lt;pre&gt;
{{Wikibooks Magazine layout
| date = 
| issue number= 
| previous issue= 
| next issue = 
| year = 
| issue = 
| article 1 = 
| article 2 = 
| article 3 = 
| article 4 = 
| article 5 = 
| article 6 = 
| article 7 = 
| article 8 = 
}}
&lt;/pre&gt;
}}[[Category:Wikibooks Magazine|*]]&lt;/noinclude&gt;__NOTOC__</text>
      <sha1>3yvw2we59tzyefcyes2uy2srid4p4gz</sha1>
    </revision>
  </page>
  <page>
    <title>Template:Wikibooks Magazine Article</title>
    <ns>10</ns>
    <id>486428</id>
    <revision>
      <id>4678661</id>
      <parentid>4677910</parentid>
      <timestamp>2026-10-28T08:06:22Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>MathsScienceNerd1 moved page [[User:MathsScienceNerd1/Wikibooks Magazine authorship]] to [[Template:Wikibooks Magazine Article]] without leaving a redirect: Moving to template namespace</comment>
      <origin>4677181</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="375" sha1="61qu3mxia2yyb67ejsxw5hklgm51kgj" xml:space="preserve">== '''{{{title}}}''' ==
&lt;small&gt;''By [[User:{{{author}}}|{{{author}}}]]''&lt;/small&gt;{{#if: {{{co-author|}}}|&lt;small&gt;'' en [[User:{{{co-author}}}|{{{co-author}}}]]''&lt;/small&gt;}}

{{{text}}}&lt;noinclude&gt;{{doc|content=
&lt;pre&gt;
{{Wikibooks Magazine authorship
| title = 
| author = 
| co-author = 
| text = 
}}
&lt;/pre&gt;
}}[[Category:Wikikids:WikiKids Magazine|*]]&lt;/noinclude&gt;__NOEDITSECTION__</text>
      <sha1>61qu3mxia2yyb67ejsxw5hklgm51kgj</sha1>
    </revision>
  </page>
  <page>
    <title>User:Moby-Dick4000/Ragu with pasta</title>
    <ns>2</ns>
    <id>486531</id>
    <revision>
      <id>4678609</id>
      <parentid>4678061</parentid>
      <timestamp>2026-10-27T21:02:45Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678609</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3559" sha1="fuc96rg37xvhs5mmmpa31415chx8zcp" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Gambas al ajillo.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

===Ingredients===

1 lb (454 g) dried pasta

1½ lbs beef chuck, cut into approximately 1½-inch chunks

1 lb Italian sausage (approximately 4–5 links)

3 tablespoons extra-virgin olive oil

1 medium onion, finely chopped

2 medium carrots, finely chopped

2 celery stalks, finely chopped

3 cloves garlic, minced

2 cans (28 oz each) crushed tomatoes

3 tablespoons tomato paste

1 teaspoon dried oregano

1 teaspoon dried basil

Salt, to taste

Freshly grated Parmigiano Reggiano, for serving

=== Procedure ===

1. Brown the meat

Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.

Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.

Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.

Remove the beef and sausages from the pot and set aside.

2. Prepare the soffritto

Reduce the heat to medium.

Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.

Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.

Make a small opening in the center of the vegetables and add the minced garlic.

Cook until the garlic becomes lightly golden, approximately 30–60 seconds.

3. Prepare the tomato sauce

Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.

Add the tomato paste and mix well until completely incorporated.

Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.

Season with salt to taste, keeping in mind that the sausages will contribute additional salt.

4. Return the meat and simmer

Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.

Stir gently, making sure the meat is submerged in the tomato sauce.

Bring the sauce to a gentle simmer, then reduce the heat to low.

Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.

Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.

5. Cook the pasta

Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.

Add the entire 1-pound box of dried pasta.

Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time.

Do not drain the pasta or discard the cooking water.

6. Finish the pasta in the sauce

Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.

Stir thoroughly so that every piece of pasta is coated with sauce.

Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.

Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.

7. Serve

Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.

Grate fresh Parmigiano Reggiano generously over each serving.

Serve immediately while hot.</text>
      <sha1>fuc96rg37xvhs5mmmpa31415chx8zcp</sha1>
    </revision>
    <revision>
      <id>4678611</id>
      <parentid>4678609</parentid>
      <timestamp>2026-10-27T21:08:12Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678611</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3555" sha1="i3retlnobsokqdgp194ko8rbmnumuen" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Gambas al ajillo.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

1 lb (454 g) dried pasta

1½ lbs beef chuck, cut into approximately 1½-inch chunks

1 lb Italian sausage (approximately 4–5 links)

3 tablespoons extra-virgin olive oil

1 medium onion, finely chopped

2 medium carrots, finely chopped

2 celery stalks, finely chopped

3 cloves garlic, minced

2 cans (28 oz each) crushed tomatoes

3 tablespoons tomato paste

1 teaspoon dried oregano

1 teaspoon dried basil

Salt, to taste

Freshly grated Parmigiano Reggiano, for serving

== Procedure ==

1. Brown the meat

Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.

Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.

Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.

Remove the beef and sausages from the pot and set aside.

2. Prepare the soffritto

Reduce the heat to medium.

Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.

Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.

Make a small opening in the center of the vegetables and add the minced garlic.

Cook until the garlic becomes lightly golden, approximately 30–60 seconds.

3. Prepare the tomato sauce

Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.

Add the tomato paste and mix well until completely incorporated.

Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.

Season with salt to taste, keeping in mind that the sausages will contribute additional salt.

4. Return the meat and simmer

Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.

Stir gently, making sure the meat is submerged in the tomato sauce.

Bring the sauce to a gentle simmer, then reduce the heat to low.

Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.

Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.

5. Cook the pasta

Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.

Add the entire 1-pound box of dried pasta.

Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time.

Do not drain the pasta or discard the cooking water.

6. Finish the pasta in the sauce

Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.

Stir thoroughly so that every piece of pasta is coated with sauce.

Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.

Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.

7. Serve

Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.

Grate fresh Parmigiano Reggiano generously over each serving.

Serve immediately while hot.</text>
      <sha1>i3retlnobsokqdgp194ko8rbmnumuen</sha1>
    </revision>
    <revision>
      <id>4678612</id>
      <parentid>4678611</parentid>
      <timestamp>2026-10-27T21:09:46Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4678612</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3569" sha1="1x742dmciykozd2gafhcpbedexlwth7" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Gambas al ajillo.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Procedure ==

1. Brown the meat

Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.

Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.

Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.

Remove the beef and sausages from the pot and set aside.

2. Prepare the soffritto

Reduce the heat to medium.

Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.

Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.

Make a small opening in the center of the vegetables and add the minced garlic.

Cook until the garlic becomes lightly golden, approximately 30–60 seconds.

3. Prepare the tomato sauce

Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.

Add the tomato paste and mix well until completely incorporated.

Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.

Season with salt to taste, keeping in mind that the sausages will contribute additional salt.

4. Return the meat and simmer

Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.

Stir gently, making sure the meat is submerged in the tomato sauce.

Bring the sauce to a gentle simmer, then reduce the heat to low.

Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.

Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.

5. Cook the pasta

Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.

Add the entire 1-pound box of dried pasta.

Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time.

Do not drain the pasta or discard the cooking water.

6. Finish the pasta in the sauce

Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.

Stir thoroughly so that every piece of pasta is coated with sauce.

Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.

Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.

7. Serve

Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.

Grate fresh Parmigiano Reggiano generously over each serving.

Serve immediately while hot.</text>
      <sha1>1x742dmciykozd2gafhcpbedexlwth7</sha1>
    </revision>
    <revision>
      <id>4678617</id>
      <parentid>4678612</parentid>
      <timestamp>2026-10-27T21:18:03Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Procedure */</comment>
      <origin>4678617</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3400" sha1="3md7ajtnezrve76h4256b001f0rt182" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Gambas al ajillo.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.
*Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>3md7ajtnezrve76h4256b001f0rt182</sha1>
    </revision>
    <revision>
      <id>4678624</id>
      <parentid>4678617</parentid>
      <timestamp>2026-10-27T23:19:46Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678624</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3400" sha1="3xiwyh1vs9q1oz8om08v2i4bnzzdac1" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.
*Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>3xiwyh1vs9q1oz8om08v2i4bnzzdac1</sha1>
    </revision>
    <revision>
      <id>4678626</id>
      <parentid>4678624</parentid>
      <timestamp>2026-10-27T23:27:41Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678626</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3557" sha1="mcm1v32y7zlrwa7bd9pdy5kh5qwagtz" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.
*Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>mcm1v32y7zlrwa7bd9pdy5kh5qwagtz</sha1>
    </revision>
    <revision>
      <id>4678627</id>
      <parentid>4678626</parentid>
      <timestamp>2026-10-27T23:28:50Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678627</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3609" sha1="b3fd6g5d8mv5ixun9lpddtw3u1j71u6" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a kitchen scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.
*Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>b3fd6g5d8mv5ixun9lpddtw3u1j71u6</sha1>
    </revision>
    <revision>
      <id>4678628</id>
      <parentid>4678627</parentid>
      <timestamp>2026-10-27T23:29:12Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678628</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3606" sha1="m9vi2easnn91cj8ps9kjeiilz1e3j1d" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot.
*Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>m9vi2easnn91cj8ps9kjeiilz1e3j1d</sha1>
    </revision>
    <revision>
      <id>4678629</id>
      <parentid>4678628</parentid>
      <timestamp>2026-10-27T23:38:01Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Procedure */</comment>
      <origin>4678629</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3605" sha1="mz3mk3qrvm079pgfvxxxeuubmq8pnqe" xml:space="preserve">Beef and Sausage Ragù
{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>mz3mk3qrvm079pgfvxxxeuubmq8pnqe</sha1>
    </revision>
  </page>
  <page>
    <title>Create Vampires/Historical Construction</title>
    <ns>0</ns>
    <id>486581</id>
    <revision>
      <id>4678491</id>
      <timestamp>2026-10-27T14:18:11Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>Created page with &quot;== Historical Vampire Construction == Some vampires are created not from the imagination of a writer, but through the historical construction of a Historian. Historians can lead credibility to the tales about a vampire-person after extensive research, often involving multiple eye-witness reports, and information gathered from written documents. &lt;br&gt; &lt;br&gt; In 1732, Johannes Flukinger, a military surgeon, published his Visum et Reportum, a report presented to the emperor of...&quot;</comment>
      <origin>4678491</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2471" sha1="5hadfd68ahcwyktxyjjrqr5f19gqt3x" xml:space="preserve">== Historical Vampire Construction ==
Some vampires are created not from the imagination of a writer, but through the historical construction of a Historian. Historians can lead credibility to the tales about a vampire-person after extensive research, often involving multiple eye-witness reports, and information gathered from written documents. &lt;br&gt;
&lt;br&gt;
In 1732, Johannes Flukinger, a military surgeon, published his Visum et Reportum, a report presented to the emperor of Vienna. The report, and several versions of it, became bestsellers throughout Europe. [1] &lt;br&gt;
&lt;br&gt;
Johannes Flukinger was sent to Medvegia, Servia to investigate the curious case of Arnold Paole (or Arnold Paul), an army man who claimed he had been bitten by a vampire. A week after he reported his encounter with a vampire, he died. Several weeks later, people reported seeing him around town. A few of the eye-witnesses soon died, four deaths followed his reappearance. &lt;br&gt;
&lt;br&gt;
People began spreading rumors about Paole, claiming he was a returned vampire! The townspeople had Paole's grave opened. Two military surgeons were present. Forty days after his burial, his body was found in a life-like state. There were blood stains around his mouth, and on his burial shroud. His fingernails and toenails had grown, with his old nails found at the bottom of his casket. When his body was cut, he bled freely. It was also reported that he groaned out loud when he was staked. He and the four people connected with his vampire sighting, were decapitated and their bodies burned. &lt;br&gt;
&lt;br&gt;
This should have been the end of Paole, however, in 1731, seventeen village people died of unknown causes. Vampirism was the unofficial believed cause. Word of vampirism reached all the way to Vienna, and the Austrian Emperor ordered an official investigation. &lt;br&gt;
&lt;br&gt;
Under Fluckinger's orders, the townspeople dug up the recently buried dead bodies. Of the forty disinterred bodies, seventeen seemed to be preserved. They were all staked and burned.  &lt;br&gt;
&lt;br&gt;
Because of Fluckinger's skilled documentation, his reports influenced vampire debates in several prominent universities. His reports also influenced Dom Augustin Calmet and Giuseppe Davanzati to write books on vampirism. &lt;br&gt;
Arnold Paole became the most famous &quot;vampire&quot; of the era.
&lt;br&gt;
&lt;br&gt;
==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Edition]. Visible Ink Press, 2014. &lt;br&gt;
&lt;br&gt;</text>
      <sha1>5hadfd68ahcwyktxyjjrqr5f19gqt3x</sha1>
    </revision>
    <revision>
      <id>4678493</id>
      <parentid>4678491</parentid>
      <timestamp>2026-10-27T14:23:54Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678493</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2574" sha1="9oigzxpr5ewwfq4cbl2ryub2h88il5v" xml:space="preserve">== Historical Vampire Construction ==
Some vampires are created not from the imagination of a writer, but through the historical construction of a Historian. Historians can lead credibility to the tales about a vampire-person after extensive research, often involving multiple eye-witness reports, and information gathered from written documents. &lt;br&gt;
&lt;br&gt;
In 1732, Johannes Flukinger, a military surgeon, published his Visum et Reportum, a report presented to the emperor of Vienna. The report, and several versions of it, became bestsellers throughout Europe. [1] &lt;br&gt;
&lt;br&gt;
Johannes Flukinger was sent to Medvegia, Servia to investigate the curious case of Arnold Paole (or Arnold Paul), an army man who claimed he had been bitten by a vampire. A week after he reported his encounter with a vampire, he died. Several weeks later, people reported seeing him around town. A few of the eye-witnesses soon died, four deaths followed his reappearance. &lt;br&gt;
&lt;br&gt;
People began spreading rumors about Paole, claiming he was a returned vampire! The townspeople had Paole's grave opened. Two military surgeons were present. Forty days after his burial, his body was found in a life-like state. There were blood stains around his mouth, and on his burial shroud. His fingernails and toenails had grown, with his old nails found at the bottom of his casket. When his body was cut, he bled freely. It was also reported that he groaned out loud when he was staked. He and the four people connected with his vampire sighting, were decapitated and their bodies burned. &lt;br&gt;
&lt;br&gt;
This should have been the end of Paole, however, in 1731, seventeen village people died of unknown causes. Vampirism was the unofficial believed cause. Word of vampirism reached all the way to Vienna, and the Austrian Emperor ordered an official investigation. &lt;br&gt;
&lt;br&gt;
Under Fluckinger's orders, the townspeople dug up the recently buried dead bodies. Of the forty disinterred bodies, seventeen seemed to be preserved. They were all staked and burned.  &lt;br&gt;
&lt;br&gt;
Because of Fluckinger's skilled documentation, his reports influenced vampire debates in several prominent universities. His reports also influenced Dom Augustin Calmet and Giuseppe Davanzati to write books on vampirism. &lt;br&gt;
Arnold Paole became the most famous &quot;vampire&quot; of the era.
&lt;br&gt;
&lt;br&gt;
==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Edition]. Visible Ink Press, 2014. &lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Vampire History|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;
{{bookcat}}</text>
      <sha1>9oigzxpr5ewwfq4cbl2ryub2h88il5v</sha1>
    </revision>
    <revision>
      <id>4678496</id>
      <parentid>4678493</parentid>
      <timestamp>2026-10-27T14:29:29Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678496</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2584" sha1="4bkvvd2hdz9ngds2rpnj8k4jwaxhl0k" xml:space="preserve">== Historical Vampire Construction ==
Some vampires are created not from the imagination of a writer, but through the historical construction of a Historian. Historians can lead credibility to the tales about a vampire-person after extensive research, often involving multiple eye-witness reports, and information gathered from written documents. &lt;br&gt;
&lt;br&gt;
In 1732, Johannes Flukinger, a military surgeon, published his Visum et Reportum, a report presented to the emperor of Vienna. The report, and several versions of it, became bestsellers throughout Europe. [1] &lt;br&gt;
&lt;br&gt;
Johannes Flukinger was sent to Medvegia, Servia to investigate the curious case of Arnold Paole (or Arnold Paul), an army man who claimed he had been bitten by a vampire. A week after he reported his encounter with a vampire, he died. Several weeks later, people reported seeing him around town. A few of the eye-witnesses soon died, four deaths followed his reappearance. [1] &lt;br&gt;
&lt;br&gt;
People began spreading rumors about Paole, claiming he was a returned vampire! The townspeople had Paole's grave opened. Two military surgeons were present. Forty days after his burial, his body was found in a life-like state. There were blood stains around his mouth, and on his burial shroud. His fingernails and toenails had grown, with his old nails found at the bottom of his casket. When his body was cut, he bled freely. It was also reported that he groaned out loud when he was staked. He and the four people connected with his vampire sighting, were decapitated and their bodies burned. [1]&lt;br&gt;
&lt;br&gt;
This should have been the end of Paole, however, in 1731, seventeen village people died of unknown causes. Vampirism was the unofficial believed cause. Word of vampirism reached all the way to Vienna, and the Austrian Emperor ordered an official investigation. &lt;br&gt;
&lt;br&gt;
Under Fluckinger's orders, the townspeople dug up the recently buried dead bodies. Of the forty disinterred bodies, seventeen seemed to be preserved. They were all staked and burned.  &lt;br&gt;
&lt;br&gt;
Because of Fluckinger's skilled documentation, his reports influenced vampire debates in several prominent universities. His reports also influenced Dom Augustin Calmet and Giuseppe Davanzati to write books on vampirism. [1]&lt;br&gt;
Arnold Paole became the most famous &quot;vampire&quot; of the era.
&lt;br&gt;
&lt;br&gt;
==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Edition]. Visible Ink Press, 2014. &lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Vampire History|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;
{{bookcat}}</text>
      <sha1>4bkvvd2hdz9ngds2rpnj8k4jwaxhl0k</sha1>
    </revision>
  </page>
  <page>
    <title>Talk:Seismic Fitness</title>
    <ns>1</ns>
    <id>486582</id>
    <revision>
      <id>4678499</id>
      <timestamp>2026-10-27T14:59:07Z</timestamp>
      <contributor>
        <username>User97104</username>
        <id>3562800</id>
      </contributor>
      <comment>/* Links to Wikiversity */ new section</comment>
      <origin>4678499</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="341" sha1="ndi53ss76zf1obyz7v3i4ibuajsy1y9" xml:space="preserve">== Links to Wikiversity ==
Do you think it is appropriate for this Wikibook to have so many Wikiversity links? &lt;span style=&quot;color:#FF0000&quot;&gt;[[User:User97104|User]]&lt;/span&gt;&lt;span style=&quot;color:#FF0000&quot;&gt;[[User talk:User97104|97104]] &lt;/span&gt;&lt;span style=&quot;color:#FF0000&quot;&gt;[[Special:Contributions/User97104|(fixes)]]&lt;/span&gt; 14:59, 27 October 2026 (UTC)</text>
      <sha1>ndi53ss76zf1obyz7v3i4ibuajsy1y9</sha1>
    </revision>
  </page>
  <page>
    <title>Infrastructure Past, Present, and Future/Mississippi River Locks and Dams</title>
    <ns>0</ns>
    <id>486583</id>
    <redirect title="Infrastructure Past, Present, and Future/Glenwood Canyon" />
    <revision>
      <id>4678506</id>
      <timestamp>2026-10-27T15:47:54Z</timestamp>
      <contributor>
        <username>JGiffordAtMason</username>
        <id>3358507</id>
      </contributor>
      <comment>JGiffordAtMason moved page [[Infrastructure Past, Present, and Future/Mississippi River Locks and Dams]] to [[Infrastructure Past, Present, and Future/Glenwood Canyon]]: Correct page title; Fall 2026 case study is Glenwood Canyon.</comment>
      <origin>4678506</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="70" sha1="4srypvftg12n8ka8b9pwdf269kv5vo2" xml:space="preserve">#REDIRECT [[Infrastructure Past, Present, and Future/Glenwood Canyon]]</text>
      <sha1>4srypvftg12n8ka8b9pwdf269kv5vo2</sha1>
    </revision>
  </page>
  <page>
    <title>Chess Opening Theory/1. e4/1...e6/2. d4/2...d5/3. e5/3...c5/4. Qg4</title>
    <ns>0</ns>
    <id>486584</id>
    <revision>
      <id>4678512</id>
      <timestamp>2026-10-27T16:13:51Z</timestamp>
      <contributor>
        <username>Atiedebee</username>
        <id>3523910</id>
      </contributor>
      <comment>4...cxd5 and 4...Nc6 as responses + some history</comment>
      <origin>4678512</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3216" sha1="1ip239w17ei6gpyrrfo09azcmw3u3sf" xml:space="preserve">{{Chess Opening Theory/Position
|name=Nimzowitsch attack
|eco=[[Chess/ECOC|C02]]
|parent=[[../|Advance variation]]
|aka=Nimzowitsch gambit
}}
== 4. Qg4 · Nimzowitsch attack ==
{{Chess/sideline}}
While this move may look imposing, it poses no threats. Usually in the French defence, this move is played once Black has moved their dark-squared bishop, which would threaten the g-pawn. Despite the lack of direct threats, White can quickly build up their forces on the kingside, playing for a quick attack. For now, the queen on g4 also prevents Black from moving their dark-squared bishop. Despite its imposing nature, this move is considered unsound, although it might be an interesting surprise weapon if prepared well.&lt;ref&gt;{{cite web
|url=https://www.chesspublishing.com/french/2001-06-01#adv
|website=chesspublishing.com
|title=GM Neil McDonald on Advance, Winawer Mainline 7 Q-0 Winawer Mainline 'Declined' 5...Ba5 Tarrasch 3...Nf6 Tarrasch 3...c5 4 exd5 Qxd5 Tarrasch 3...Be7 Classical 4 Bg5 dxe4 5 Nxe4 Nbd7 Classical 4 e5
}}&lt;/ref&gt;

Because White doesn't defend their d-pawn, Black can simply take it with '''4...cxd4'''. 5. Qxd4? would be unwise, since this loses many valuable tempi in the opening. White can't afford to be materialistic, so they should sacrifice the pawn and continue development with 5. Nf3 Nc6 6. Bd3 Qc7?!. Modern engines give the position after 6...Qc7 as slightly better for Black (-0.5). However, after 6...h5, displacing the queen, evaluation clearly prefers Black (-1.0). This is also reflected in the lichess database, where Black scores best with 6...h5, despite the complicated position.&lt;ref&gt;https://lichess.org/analysis/pgn/1.+e4+e6+2.+d4+d5+3.+e5+c5+4.Qg4+cxd4+5.Nf3+Nc6+6.Bd3&lt;/ref&gt;

'''4...Nc6''' is an alternative, which can transpose to the previous line after 5. Nf3 cxd4. An independent line arises after 5. Nf3 Qa5+ 6. Bd2 which may also pose some problems for White.

=== History ===
The opening is named after [[w:Aron Nimzowitsch|Aron Nimzowitsch]], who played this move for the first time in 1922 against Arthur Hakansson.&lt;ref&gt;{{cite web
|website=chessgames.com
|url=https://www.chessgames.com/perl/chessgame?gid=1102392
|title=Nimzowitsch - Hakansson, 1922
}}&lt;/ref&gt;
{{Quote|text=[My] innovation, played here for the first time. As will be seen, the basis of the idea is overprotection.|sign=Aron Nimzowitsch&lt;ref&gt;{{cite book
|title=Die Praxis meines Systems
|author=Aron Nimzowitsch
|page=190
|isbn=0713450584
}}&lt;/ref&gt;}}
In the game, Nimzowitsch played by overprotecting the e5-pawn to keep Black's position cramped. This was made easier because after 4...cxd4 5. Nf3 Nc6 6. Bd3 Black played the dubious 6...f5? due to which the e5-pawn can never be attacked by any of Black's pawns.

==Theory table==
{{ChessTable}}

{{Chess/theory table|links=0
|line1=4. ... cxd4 5. Nf3 Nc6 6. Bd3 Qc7?! 7. Bf4 Nge7 8. O-O Ng6
|eval1={{chess/not|-}}

|line2=4. ... ... 5. ... ... 6. ... h5 7. Qf4 f6
|eval2={{chess/not|-}}

|line3=4. ... Nc6 5. Nf3 Qa5+ 6. Bd2 Nh6 7. Qg5 Qb6
|eval3={{chess/not|-}}

|line4=4. ... ... 5. ... cxd4
|eval4={{chess/not|-}}
}}

{{ChessMid}}
==References==
{{reflist}}
{{Wikipedia|French Defence}}
===See also===
{{BCO2}}
{{Chess Opening Theory/Footer}}</text>
      <sha1>1ip239w17ei6gpyrrfo09azcmw3u3sf</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:New page patrol</title>
    <ns>4</ns>
    <id>486585</id>
    <redirect title="Wikibooks:Patrolling" />
    <revision>
      <id>4678518</id>
      <timestamp>2026-10-27T17:17:08Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Codename Noreste moved page [[Wikibooks:New page patrol]] to [[Wikibooks:Patrolling]]: New name.</comment>
      <origin>4678518</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="34" sha1="erlbeuu8qlidckqe5efq72546rqruaq" xml:space="preserve">#REDIRECT [[Wikibooks:Patrolling]]</text>
      <sha1>erlbeuu8qlidckqe5efq72546rqruaq</sha1>
    </revision>
    <revision>
      <id>4678521</id>
      <parentid>4678518</parentid>
      <timestamp>2026-10-27T17:17:21Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Changed redirect target from [[Wikibooks:Patrolling]] to [[Wikibooks:Patrolling#Patrolling new pages]]</comment>
      <origin>4678521</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="55" sha1="rtnbygnk1uq61d3f0ubenx6h6mduy8r" xml:space="preserve">#REDIRECT [[Wikibooks:Patrolling#Patrolling new pages]]</text>
      <sha1>rtnbygnk1uq61d3f0ubenx6h6mduy8r</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks talk:New page patrol</title>
    <ns>5</ns>
    <id>486586</id>
    <redirect title="Wikibooks talk:Patrolling" />
    <revision>
      <id>4678520</id>
      <timestamp>2026-10-27T17:17:09Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Codename Noreste moved page [[Wikibooks talk:New page patrol]] to [[Wikibooks talk:Patrolling]]: New name.</comment>
      <origin>4678520</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="39" sha1="h19vdcqltwnyayngqhig6i1yjq65349" xml:space="preserve">#REDIRECT [[Wikibooks talk:Patrolling]]</text>
      <sha1>h19vdcqltwnyayngqhig6i1yjq65349</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:~2026-57125-80</title>
    <ns>3</ns>
    <id>486587</id>
    <revision>
      <id>4678530</id>
      <timestamp>2026-10-27T17:54:00Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Notifying author of speedy deletion</comment>
      <origin>4678530</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="691" sha1="lwk8axaozluav1orie3gfi68pa7yhzs" xml:space="preserve">
== Your page has been speedily deleted ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:Template talk:User language/la]]. However, it does not meet Wikibooks's [[Wikibooks:What is Wikibooks?|standards for inclusion]], and it has therefore been [[Wikibooks:Deletion policy|deleted]]. The reason I provided was: &lt;blockquote&gt;&lt;strong&gt;Test page&lt;/strong&gt;&lt;/blockquote&gt; If you believe that your page should not have been deleted, or you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 17:54, 27 October 2026 (UTC)</text>
      <sha1>lwk8axaozluav1orie3gfi68pa7yhzs</sha1>
    </revision>
  </page>
  <page>
    <title>Writing Adolescent Fiction/Character names/Western Asia and North Africa/saudi</title>
    <ns>0</ns>
    <id>486588</id>
    <revision>
      <id>4678540</id>
      <timestamp>2026-10-27T18:05:41Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>Add saudi names section</comment>
      <origin>4678540</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="21" sha1="49edd6jiqjqclgzti9cly012e94p77k" xml:space="preserve">Saudi Character Names</text>
      <sha1>49edd6jiqjqclgzti9cly012e94p77k</sha1>
    </revision>
    <revision>
      <id>4678543</id>
      <parentid>4678540</parentid>
      <timestamp>2026-10-27T18:09:47Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4678543</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31" sha1="kzlmfsc55wrl2cngrd83ji4h8pixngu" xml:space="preserve">'''Saudi names for character'''</text>
      <sha1>kzlmfsc55wrl2cngrd83ji4h8pixngu</sha1>
    </revision>
    <revision>
      <id>4678544</id>
      <parentid>4678543</parentid>
      <timestamp>2026-10-27T18:12:58Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>Add</comment>
      <origin>4678544</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="510" sha1="q4eph840tg5y5gcqbb8aphreg7rnprs" xml:space="preserve">'''Saudi names for character'''

== القسم الرئيسي (مثلاً: المدن) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>q4eph840tg5y5gcqbb8aphreg7rnprs</sha1>
    </revision>
    <revision>
      <id>4678545</id>
      <parentid>4678544</parentid>
      <timestamp>2026-10-27T18:22:30Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>Add/</comment>
      <origin>4678545</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="703" sha1="0uolmoe8jrqxd50xd7swvo7fq1hacrl" xml:space="preserve">'''Saudi names for character'''

== Boys names ==
(الاسم) Boy name + (اسم الاب) Father name + (لقب القبيلة) Surname 

After the father name you could add the grandfather name and puts ابن before the grandfather name and it mean son

this is how it show in the ID and Passport 

Name+Father name+Son(ابن)+Grandfather name+Surname 

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>0uolmoe8jrqxd50xd7swvo7fq1hacrl</sha1>
    </revision>
    <revision>
      <id>4678546</id>
      <parentid>4678545</parentid>
      <timestamp>2026-10-27T18:23:52Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>Add//</comment>
      <origin>4678546</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1662" sha1="3bii8pubdtvdqco8l9yqfg83y76m5td" xml:space="preserve">'''Saudi names for character'''

== Boys names ==
(الاسم) Boy name + (اسم الاب) Father name + (لقب القبيلة) Surname 

After the father name you could add the grandfather name and puts ابن before the grandfather name and it mean son

this is how it show in the ID and Passport 

Name+Father name+Son(ابن)+Grandfather name+Surname 

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...

== القسم الرئيسي (مثلاً: المدن) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== القسم الرئيسي (مثلاً: المدن) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>3bii8pubdtvdqco8l9yqfg83y76m5td</sha1>
    </revision>
    <revision>
      <id>4678547</id>
      <parentid>4678546</parentid>
      <timestamp>2026-10-27T18:26:01Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* القسم الرئيسي (مثلاً: المدن) */</comment>
      <origin>4678547</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1651" sha1="af2mq117wtibebkuvmfh7z0anlbl57r" xml:space="preserve">'''Saudi names for character'''

== Boys names (اسامي الاولاد) ==
(الاسم) Boy name + (اسم الاب) Father name + (لقب القبيلة) Surname 

After the father name you could add the grandfather name and puts ابن before the grandfather name and it mean son

this is how it show in the ID and Passport 

Name+Father name+Son(ابن)+Grandfather name+Surname 

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...

== Girls names (اسامي البنات) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>af2mq117wtibebkuvmfh7z0anlbl57r</sha1>
    </revision>
    <revision>
      <id>4678548</id>
      <parentid>4678547</parentid>
      <timestamp>2026-10-27T18:40:14Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <origin>4678548</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1436" sha1="5o1cupid0frobru55wzhi1euuvypw4a" xml:space="preserve">'''Saudi names for character'''

== Boys names (اسامي الاولاد) ==
'''Naming Convention and Daily Usage:''' 
'''Official Documents (ID Cards and Passports):'''

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...

== Girls names (اسامي البنات) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>5o1cupid0frobru55wzhi1euuvypw4a</sha1>
    </revision>
    <revision>
      <id>4678549</id>
      <parentid>4678548</parentid>
      <timestamp>2026-10-27T18:41:46Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Boys names (اسامي الاولاد) */</comment>
      <origin>4678549</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1437" sha1="eu0hgeyn1yll5q5s8ddp3c4tj0anmug" xml:space="preserve">'''Saudi names for character'''

== Boys names (اسامي الاولاد) ==
'''Naming Convention and Daily Usage:''' 

'''Official Documents (ID Cards and Passports):'''

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...

== Girls names (اسامي البنات) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>eu0hgeyn1yll5q5s8ddp3c4tj0anmug</sha1>
    </revision>
    <revision>
      <id>4678550</id>
      <parentid>4678549</parentid>
      <timestamp>2026-10-27T18:43:51Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Boys names (اسامي الاولاد) */</comment>
      <origin>4678550</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1196" sha1="1wed65sl1xwautkrbnadgkmgwddcpim" xml:space="preserve">'''Saudi names for character'''

== Boys names (اسامي الاولاد) ==
'''Naming Convention and Daily Usage:''' 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

'''Father's Name:'''

'''Grandfather's Name:'''

'''Family Title (Surname/Tribe):'''

== Girls names (اسامي البنات) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>1wed65sl1xwautkrbnadgkmgwddcpim</sha1>
    </revision>
    <revision>
      <id>4678551</id>
      <parentid>4678550</parentid>
      <timestamp>2026-10-27T18:46:53Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Boys names (اسامي الاولاد) */</comment>
      <origin>4678551</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1868" sha1="41mfioy15w9jfpgjo0p2gwcbh0v6tzi" xml:space="preserve">'''Saudi names for character'''

== Boys names (اسامي الاولاد) ==
'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

== Girls names (اسامي البنات) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>41mfioy15w9jfpgjo0p2gwcbh0v6tzi</sha1>
    </revision>
    <revision>
      <id>4678554</id>
      <parentid>4678551</parentid>
      <timestamp>2026-10-27T18:54:24Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <origin>4678554</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3807" sha1="3a7npfsnaonxnmnvjc6lntriikenocn" xml:space="preserve">'''Saudi names for character'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

== Girls names (اسامي البنات) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>3a7npfsnaonxnmnvjc6lntriikenocn</sha1>
    </revision>
    <revision>
      <id>4678555</id>
      <parentid>4678554</parentid>
      <timestamp>2026-10-27T18:56:28Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <origin>4678555</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3857" sha1="a9aiy3pc224jcu27458dwrdlkfsi6bv" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

== Girls names (اسامي البنات) ==

هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===

تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>a9aiy3pc224jcu27458dwrdlkfsi6bv</sha1>
    </revision>
    <revision>
      <id>4678557</id>
      <parentid>4678555</parentid>
      <timestamp>2026-10-27T19:14:11Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Boys names (اسامي الاولاد) */</comment>
      <origin>4678557</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3908" sha1="11zmxepi32suvh7u5jt4ryqay70ervi" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names===
...

*.
**.
*..
**..

*...
**...

== Girls names (اسامي البنات) ==

هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===

تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>11zmxepi32suvh7u5jt4ryqay70ervi</sha1>
    </revision>
    <revision>
      <id>4678559</id>
      <parentid>4678557</parentid>
      <timestamp>2026-10-27T19:28:23Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Male names */</comment>
      <origin>4678559</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4306" sha1="918hiy6ezcimobwzvj7moyynh4qoq8x" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names===
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.

*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.

*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.

== Girls names (اسامي البنات) ==

هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===

تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>918hiy6ezcimobwzvj7moyynh4qoq8x</sha1>
    </revision>
    <revision>
      <id>4678560</id>
      <parentid>4678559</parentid>
      <timestamp>2026-10-27T19:30:36Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Boys names (اسامي الاولاد) */</comment>
      <origin>4678560</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4304" sha1="sofmzxcc8bhnahag08lzmxk7tbvnvzv" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

==Male names==
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.

*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.

*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.

== Girls names (اسامي البنات) ==

هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===

تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>sofmzxcc8bhnahag08lzmxk7tbvnvzv</sha1>
    </revision>
    <revision>
      <id>4678561</id>
      <parentid>4678560</parentid>
      <timestamp>2026-10-27T19:32:45Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Male names */</comment>
      <origin>4678561</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4306" sha1="918hiy6ezcimobwzvj7moyynh4qoq8x" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names===
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.

*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.

*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.

== Girls names (اسامي البنات) ==

هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===

تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>918hiy6ezcimobwzvj7moyynh4qoq8x</sha1>
    </revision>
    <revision>
      <id>4678562</id>
      <parentid>4678561</parentid>
      <timestamp>2026-10-27T19:38:38Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Contemporary Names (أسماء معاصرة) */</comment>
      <origin>4678562</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4690" sha1="99zua3dbn2nu8m1cr4ze0j3t54tl2x6" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names===
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.
**العبد المملوك لله عز وجل، أو الخاضع والمطيع لأوامره.

*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.
**الحكيم أو القاضي الحاسم، أو الشخص الذي يفصل بين الحق والباطل والخطأ والصواب بسلطة قوية.

*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.
**الخلود أو الأبدي، أو الشخص الذي مُنح عمراً مديداً ووجوداً مستمراً.

== Girls names (اسامي البنات) ==

هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===

تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>99zua3dbn2nu8m1cr4ze0j3t54tl2x6</sha1>
    </revision>
    <revision>
      <id>4678563</id>
      <parentid>4678562</parentid>
      <timestamp>2026-10-27T19:39:37Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Contemporary Names (أسماء معاصرة) */</comment>
      <origin>4678563</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4708" sha1="qgka64rq9vzfcgne16raqb1jtf0sfnx" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names===
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.
**العبد المملوك لله عز وجل، أو الخاضع والمطيع لأوامره.


*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.
**الحكيم أو القاضي الحاسم، أو الشخص الذي يفصل بين الحق والباطل والخطأ والصواب بسلطة قوية.


*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.
**الخلود أو الأبدي، أو الشخص الذي مُنح عمراً مديداً ووجوداً مستمراً.


*..
**..
**..

== Girls names (اسامي البنات) ==

هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===

تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...


== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>qgka64rq9vzfcgne16raqb1jtf0sfnx</sha1>
    </revision>
    <revision>
      <id>4678564</id>
      <parentid>4678563</parentid>
      <timestamp>2026-10-27T19:40:29Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Girls names (اسامي البنات) */</comment>
      <origin>4678564</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4284" sha1="l8lilg2rspq1mnfxdx20ivmfi6kbosr" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names===
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.
**العبد المملوك لله عز وجل، أو الخاضع والمطيع لأوامره.


*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.
**الحكيم أو القاضي الحاسم، أو الشخص الذي يفصل بين الحق والباطل والخطأ والصواب بسلطة قوية.


*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.
**الخلود أو الأبدي، أو الشخص الذي مُنح عمراً مديداً ووجوداً مستمراً.


*..
**..
**..

== Girls names (اسامي البنات) ==

== Surname (القبيلة) ==
هنا تكتب مقدمة قصيرة عن هذا القسم لحاله...

=== الشيء الأول (مثلاً: الرياض) ===
تكتب هنا التفاصيل الخاصة بالرياض...

=== الشيء الثاني (مثلاً: جدة) ===
تكتب هنا التفاصيل الخاصة بجدة...

=== الشيء الثالث (مثلاً: مكة) ===
تكتب هنا التفاصيل الخاصة بمكة...</text>
      <sha1>l8lilg2rspq1mnfxdx20ivmfi6kbosr</sha1>
    </revision>
    <revision>
      <id>4678565</id>
      <parentid>4678564</parentid>
      <timestamp>2026-10-27T19:40:51Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Surname (القبيلة) */</comment>
      <origin>4678565</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3863" sha1="25uml8cwhtzsdccatf40c4du86mtobq" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names===
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.
**العبد المملوك لله عز وجل، أو الخاضع والمطيع لأوامره.


*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.
**الحكيم أو القاضي الحاسم، أو الشخص الذي يفصل بين الحق والباطل والخطأ والصواب بسلطة قوية.


*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.
**الخلود أو الأبدي، أو الشخص الذي مُنح عمراً مديداً ووجوداً مستمراً.


*..
**..
**..

== Girls names (اسامي البنات) ==

== Surname (القبيلة) ==</text>
      <sha1>25uml8cwhtzsdccatf40c4du86mtobq</sha1>
    </revision>
    <revision>
      <id>4678566</id>
      <parentid>4678565</parentid>
      <timestamp>2026-10-27T19:42:35Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Male names (أسماء الذكور) */</comment>
      <origin>4678566</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3889" sha1="83yes62gbpq2fv31ymiwhix6blz1gl4" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names (أسماء الذكور)===
...

====Contemporary Names (أسماء معاصرة)====

*Abdullah (عبدالله)
**The servant or slave of Allah (God), or the one who submits and obeys His commands.
**العبد المملوك لله عز وجل، أو الخاضع والمطيع لأوامره.


*Faisal (فيصل)
**The arbiter or decisive judge, or the one who separates truth from falsehood and right from wrong with firm authority.
**الحكيم أو القاضي الحاسم، أو الشخص الذي يفصل بين الحق والباطل والخطأ والصواب بسلطة قوية.


*Khaled (خالد)
**The eternal or everlasting one, or the one who is endowed with longevity and enduring presence.
**الخلود أو الأبدي، أو الشخص الذي مُنح عمراً مديداً ووجوداً مستمراً.


*..
**..
**..

== Girls names (اسامي البنات) ==

== Surname (القبيلة) ==</text>
      <sha1>83yes62gbpq2fv31ymiwhix6blz1gl4</sha1>
    </revision>
    <revision>
      <id>4678568</id>
      <parentid>4678566</parentid>
      <timestamp>2026-10-27T19:55:13Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <origin>4678568</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3673" sha1="9c3trxx71lmp3t1jy2orec59ssqdfpk" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names (أسماء الذكور)===
...

====Contemporary Names (أسماء معاصرة)====

*Mohammed (محمد)

*Abdullah (عبدالله)

*Faisal (فيصل)

*Khaled (خالد)

*Abdulaziz (عبدالعزيز)

*Abdulrahman (عبدالرحمن)

*Fahd (فهد)

*Saud (سعود)

*Salman (سلمان)

*Turki (تركي)

*Sultan (سلطان)

*Badr (بدر)

*Nayef (نايف)

*Meshari (مشاري)

*Bandar (بندر)

*Sattam (سطام)

*Waleed (وليد)

*Talal (طلال)

*Sanad (سند)

*Rakan (راكان)

*Yazeed (يزيد)

*Firas (فراس)

*Tamim (تميم)

*Saif (سيف)

*Rayan (ريان)

*Eyad (إياد)

Yosif (يوسف)

== Girls names (اسامي البنات) ==

== Surname (القبيلة) ==</text>
      <sha1>9c3trxx71lmp3t1jy2orec59ssqdfpk</sha1>
    </revision>
    <revision>
      <id>4678570</id>
      <parentid>4678568</parentid>
      <timestamp>2026-10-27T19:56:24Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Contemporary Names (أسماء معاصرة) */</comment>
      <origin>4678570</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3699" sha1="4vi0c0czad4131h2he4qobngmek6ltr" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names (أسماء الذكور)===
...

====Contemporary Names (أسماء معاصرة)====

*Mohammed (محمد)


*Abdullah (عبدالله)


*Faisal (فيصل)


*Khaled (خالد)


*Abdulaziz (عبدالعزيز)


*Abdulrahman (عبدالرحمن)


*Fahd (فهد)


*Saud (سعود)


*Salman (سلمان)


*Turki (تركي)


*Sultan (سلطان)


*Badr (بدر)

*Nayef (نايف)


*Meshari (مشاري)


*Bandar (بندر)


*Sattam (سطام)


*Waleed (وليد)


*Talal (طلال)


*Sanad (سند)


*Rakan (راكان)


*Yazeed (يزيد)


*Firas (فراس)


*Tamim (تميم)


*Saif (سيف)


*Rayan (ريان)


*Eyad (إياد)


*Yosif (يوسف)

== Girls names (اسامي البنات) ==

== Surname (القبيلة) ==</text>
      <sha1>4vi0c0czad4131h2he4qobngmek6ltr</sha1>
    </revision>
    <revision>
      <id>4678571</id>
      <parentid>4678570</parentid>
      <timestamp>2026-10-27T19:57:30Z</timestamp>
      <contributor>
        <username>~2026-57327-21</username>
        <id>3629535</id>
      </contributor>
      <comment>/* Contemporary Names (أسماء معاصرة) */</comment>
      <origin>4678571</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3707" sha1="kuijeyakyv464lc1m45d57r2mgnyssp" xml:space="preserve">'''Saudi names for character'''

'''اسماء سعودية للشخصيات'''

== Boys names (اسامي الاولاد) ==

'''English/انجليزي'''

'''Naming Convention and Daily Usage:'''

A boy's full name in daily conversation consists of his first name, followed by his father's name, and then his family title (tribe). 

'''Official Documents (ID Cards and Passports):'''

'''First Name:'''

The boy's first name consists of a single name only, with no multiple given names.

'''Father's Name:'''

The father's name is essential and is used in formal forms of address, such as teachers addressing a student by his first name and his father's name.

'''Grandfather's Name:'''

The grandfather's name is important for official paperwork, but holds little to no significance in daily life.

'''Family Title (Surname/Tribe):'''

The title is extremely important and is heavily used in daily life. A boy is often addressed by his first name combined with his title, or solely by his title if his first name is unknown.

'''Arabic/عربي'''

'''طريقة تسمية الأبناء والاستخدام اليومي:'''

يتكون الاسم الكامل للولد في المحادثات اليومية من اسمه الأول، يليه اسم الأب، ثم اسم العائلة (القبيلة).

'''​الأوراق الرسمية (بطاقات الهوية وجوازات السفر):'''

بالنسبة للمستندات الرسمية مثل بطاقات الهوية وجوازات السفر، يجب أن يُكتب الاسم كاملاً بالشكل التقليدي المعتمد:
اسم الولد + &quot;بن&quot; + اسم الأب + &quot;بن&quot; + اسم الجد + لقب العائلة.
(ملاحظة: قد يتكون لقب العائلة من اسم واحد أو اسمين بحسب العائلة).
ويُضاف حرف أو لفظ &quot;بن&quot; (الذي يعني &quot;ابن فلان&quot;) بوضوح للدلالة على نسب الشخص.

'''​الاسم الأول:'''

يتكون اسم الولد من اسم واحد فقط، دون وجود أسماء متعددة.

'''​اسم الأب:'''

يعتبر اسم الأب مهمًا للغاية ويُستخدم في أساليب المخاطبة الرسمية؛ مثل قيام المعلمين بمناداة الطالب باسمه الأول متبوعاً باسم أبيه.

'''​اسم الجد:'''

يحظى اسم الجد بأهمية في المعاملات والأوراق الرسمية، ولكنه يكاد لا يمثل أي أهمية في الحياة اليومية.

'''​لقب العائلة (اسم العائلة أو القبيلة):'''

يُعد اللقب في غاية الأهمية ويُستخدم بكثرة في الحياة اليومية؛ وغالبًا ما يُنادى الولد بقرن اسمه الأول مع لقبه، أو يُنادى باللقب منفردًا إذا كان اسم الولد مجهولاً.

===Male names (أسماء الذكور)===
...

====Contemporary Names (أسماء معاصرة)====


----


*Mohammed (محمد)


*Abdullah (عبدالله)


*Faisal (فيصل)


*Khaled (خالد)


*Abdulaziz (عبدالعزيز)


*Abdulrahman (عبدالرحمن)


*Fahd (فهد)


*Saud (سعود)


*Salman (سلمان)


*Turki (تركي)


*Sultan (سلطان)


*Badr (بدر)

*Nayef (نايف)


*Meshari (مشاري)


*Bandar (بندر)


*Sattam (سطام)


*Waleed (وليد)


*Talal (طلال)


*Sanad (سند)


*Rakan (راكان)


*Yazeed (يزيد)


*Firas (فراس)


*Tamim (تميم)


*Saif (سيف)


*Rayan (ريان)


*Eyad (إياد)


*Yosif (يوسف)

== Girls names (اسامي البنات) ==

== Surname (القبيلة) ==</text>
      <sha1>kuijeyakyv464lc1m45d57r2mgnyssp</sha1>
    </revision>
  </page>
  <page>
    <title>Create Vampires/Women As Vampires</title>
    <ns>0</ns>
    <id>486589</id>
    <revision>
      <id>4678556</id>
      <timestamp>2026-10-27T19:07:12Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>Created page with &quot;== Women As Vampires == The image of the vampire has been dominated by men, from Dracula to Blade the half-vampire hero. Famous male Actors who played vampires in films have earned respect and praise. Beloved Actors such as Bela Lugosi and Robert Pattinson have benefited from their popularity, yet what about women who have played vampires? Are they equally well known? &lt;br&gt; &lt;br&gt; The male vampire has dominated and obscured the role women have played in the creation of the...&quot;</comment>
      <origin>4678556</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1546" sha1="p9wh40ciyxntma31xis06xngrufw0vi" xml:space="preserve">== Women As Vampires ==
The image of the vampire has been dominated by men, from Dracula to Blade the half-vampire hero. Famous male Actors who played vampires in films have earned respect and praise. Beloved Actors such as Bela Lugosi and Robert Pattinson have benefited from their popularity, yet what about women who have played vampires? Are they equally well known? &lt;br&gt;
&lt;br&gt;
The male vampire has dominated and obscured the role women have played in the creation of the vampire myth, and its gradual mutation to better reflect post-modern cultural values. &lt;br&gt;
&lt;br&gt;
'''The Original Vampires:''' &lt;br&gt;
In cultures from around the world, the oldest vampire figures were female. [1] The Greeks left records of the ''lamiai'' and the ''keres'', the Aztecs spoke of ''cihuateteo'', and the Malaysians of ''langsuyar''. Most of these myths function as a means to explain problems associated with childbirth. For example, the ''cihuateteo'' was a reanimated corpse of a woman who died during childbirth or had given birth to a stillborn. In stories, she hunts children and drains their lives to compensate for the life that was taken from her. [2] &lt;br&gt;
&lt;br&gt;  
Although these vampiric beings were often viewed as frightening threats to pregnant women, over time they slowly evolved. &lt;br&gt;
&lt;br&gt;

==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Version]. Visible Ink Press, 2014. &lt;br&gt;
&lt;br&gt; 
2. Hollyhock, Agnes. Vampires: A Handbook Of History &amp; Lore Of The Undead. Wellfleet Press, 2024. &lt;br&gt;
&lt;br&gt;</text>
      <sha1>p9wh40ciyxntma31xis06xngrufw0vi</sha1>
    </revision>
    <revision>
      <id>4678572</id>
      <parentid>4678556</parentid>
      <timestamp>2026-10-27T19:59:52Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678572</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2976" sha1="37sf7lghh7ersp3atmuqak0m2dc21d5" xml:space="preserve">== Women As Vampires ==
The image of the vampire has been dominated by men, from Dracula to Blade the half-vampire hero. Famous male Actors who played vampires in films have earned respect and praise. Beloved Actors such as Bela Lugosi and Robert Pattinson have benefited from their popularity, yet what about women who have played vampires? Are they equally well known? &lt;br&gt;
&lt;br&gt;
The male vampire has dominated and obscured the role women have played in the creation of the vampire myth, and its gradual mutation to better reflect post-modern cultural values. &lt;br&gt;
&lt;br&gt;
'''The Original Vampires:''' &lt;br&gt;
In cultures from around the world, the oldest vampire figures were female. [1] The Greeks left records of the ''lamiai'' and the ''keres'', the Aztecs spoke of ''cihuateteo'', and the Malaysians of ''langsuyar''. Most of these myths functioned as a means to explain problems associated with childbirth. For example, the ''cihuateteo'' was a reanimated corpse of a woman who died during childbirth or had given birth to a stillborn. In stories, she hunts children and drains their lives to compensate for the life that was taken from her. [2] &lt;br&gt;
&lt;br&gt;  
Although these vampiric beings were often viewed as frightening threats to pregnant women, over time they slowly evolved. &lt;br&gt;
&lt;br&gt;
Stories of the young vamp, a female vampire, emerged from Greek stories about the ''lamiai''. She appeared as a beautiful foreigner who would seduce unsuspecting young males looking for a partner. Philostratus told in ''The Life of Apollonius'' the story of a young man about to marry a beautiful vamp, the young student was saved by his teacher Apollonius. &lt;br&gt;
&lt;br&gt;
Over time, the vamp grew into a hyper-sexual, manipulative woman capable of seducing men in order to drain their blood, wealth, or vital energy. &lt;br&gt; 
This dangerous and seductive character developed around the late 19th and early 20th century. The vamp reflected male concerns regarding women's increased social and sexual liberation, as well as their changing social roles. From a Feminist viewpoint, the vamp was a threat to patriarchy, functioning outside the traditional domestic realm. She matched her male counterparts by showing equal abilities in her use of power to fulfill her needs and desires. Feminist critics note that the vamp operated outside the realm of traditional marriage, reflecting people's fear of a woman who enjoyed sex for pleasure, not for procreation. &lt;br&gt;
&lt;br&gt;
Post-modern people today are focused on reclaiming the &quot;monstrous feminine.&quot; From a cautionary tale to agents of liberation, vamps in modern horror cinema are likely to act as vigilantes preying upon pimps and abusive men, not as powerless silent victims. &lt;br&gt;       

==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Version]. Visible Ink Press, 2014. &lt;br&gt;
&lt;br&gt; 
2. Hollyhock, Agnes. Vampires: A Handbook Of History &amp; Lore Of The Undead. Wellfleet Press, 2024. &lt;br&gt;
&lt;br&gt;</text>
      <sha1>37sf7lghh7ersp3atmuqak0m2dc21d5</sha1>
    </revision>
    <revision>
      <id>4678613</id>
      <parentid>4678572</parentid>
      <timestamp>2026-10-27T21:13:33Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678613</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5452" sha1="4k9wkii0e7elmcqlv9o87ft1pynmtbk" xml:space="preserve">== Women As Vampires ==
The image of the vampire has been dominated by men, from Dracula to Blade the half-vampire hero. Famous male Actors who played vampires in films have earned respect and praise. Beloved Actors such as Bela Lugosi and Robert Pattinson have benefited from their popularity, yet what about women who have played vampires? Are they equally well known? &lt;br&gt;
&lt;br&gt;
The male vampire has dominated and obscured the role women have played in the creation of the vampire myth, and its gradual mutation to better reflect post-modern cultural values. &lt;br&gt;
&lt;br&gt;
'''The Original Vampires:''' &lt;br&gt;
In cultures from around the world, the oldest vampire figures were female. [1] The Greeks left records of the ''lamiai'' and the ''keres'', the Aztecs spoke of ''cihuateteo'', and the Malaysians of ''langsuyar''. Most of these myths functioned as a means to explain problems associated with childbirth. For example, the ''cihuateteo'' was a reanimated corpse of a woman who died during childbirth or had given birth to a stillborn. In stories, she hunts children and drains their lives to compensate for the life that was taken from her. [2] &lt;br&gt;
&lt;br&gt;  
Although these vampiric beings were often viewed as frightening threats to pregnant women, over time they slowly evolved. &lt;br&gt;
&lt;br&gt;
Stories of the young vamp, a female vampire, emerged from Greek stories about the ''lamiai''. She appeared as a beautiful foreigner who would seduce unsuspecting young males looking for a partner. Philostratus told in ''The Life of Apollonius'' the story of a young man about to marry a beautiful vamp, the young student was saved by his teacher Apollonius. &lt;br&gt;
&lt;br&gt;
Over time, the vamp grew into a hyper-sexual, manipulative woman capable of seducing men in order to drain their blood, wealth, or vital energy. &lt;br&gt; 
This dangerous and seductive character developed around the late 19th and early 20th century. The vamp reflected male concerns regarding women's increased social and sexual liberation, as well as their changing social roles. From a Feminist viewpoint, the vamp was a threat to patriarchy, functioning outside the traditional domestic realm. She matched her male counterparts by showing equal abilities in her use of power to fulfill her needs and desires. Feminist critics note that the vamp operated outside the realm of traditional marriage, reflecting people's fear of a woman who enjoyed sex for pleasure, not for procreation. &lt;br&gt;
&lt;br&gt;
Post-modern people today are focused on reclaiming the &quot;monstrous feminine.&quot; From a cautionary tale to agents of liberation, vamps in modern horror cinema are likely to act as vigilantes preying upon pimps and abusive men, not as powerless silent victims. &lt;br&gt;       
&lt;br&gt;
'''The Literary Vampire:''' &lt;br&gt;
Almost all of the vampires found in early literature were women. Starting with the 1797 poem &quot;The Bride of Corinth&quot; by Goethe, based on an ancient Greek source. The poem retells the story of Philinnon (in Goethe's poem she is unnamed), a woman who had died a virgin. The woman returns to the living in order to experience sexual bliss before leaving this world. &lt;br&gt;
Another character, believed to be the first vampire in English literature, was a woman named Geraldine. She is the antagonist in Samuel Coleridge's poem, &quot;Christabel,&quot; written from 1790 - 1800. [1] &lt;br&gt;
&lt;br&gt;
In 1819, John Polidori introduced Lord Ruthven, a vampire character based on the aristocratic Lord Byron. His vampire preyed on unsuspecting women and later was the basis of a series of small pamphlets known as penny dreadfuls. ''Varney the Vampyre'', was published in the form of small pamphlets in 1845. The character Lord Ruthven dominated vampire literature for most of the century. &lt;br&gt;
&lt;br&gt;
Although the early 19th century was heavily dominated by male vampires in literature, occasionally, a few writers would create female vampires. In 1836 Théophile Gautier, a French writer, wrote &quot;The Beautiful Vampire.&quot; In 1848, Alexandre Dumas wrote &quot;The Pale Lady.&quot; Sheridan Le Fanu wrote &quot;Carmilla,&quot; a novella about a female vampire in 1872. Carmilla is considered the most popular female vampire ever created. [1] &lt;br&gt;
Another classic tale, &quot;A Mystery of the Campagna&quot; was written by Anne Crawford in 1887. [1] &lt;br&gt;
&lt;br&gt;
'''The Blood Countess:''' &lt;br&gt;
Elizabeth Báthory, a real woman considered a vampire by millions of people, lived in Hungry from 1560 - 1614. Elizabeth Báthory, or the Blood Countess, was married to Count Ferenc Nádasdy. She soon became a wealthy widow when her husband died fighting in a war with the Ottoman empire. According to legend, Báthory accidently learned the secret to youth, and began drinking and bathing in the blood of young girls in order to maintain her youthful appearance. It is said that she murdered over six hundred servants. She was put on public trial when news of her cruelty reached her political rivals. At her trial, hundreds of people testified against her. She was found guilty and placed under house arrest. Her lands and her title were stripped from her, then redistributed to her family. &lt;br&gt;
&lt;br&gt;

==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Version]. Visible Ink Press, 2014. &lt;br&gt;
&lt;br&gt; 
2. Hollyhock, Agnes. Vampires: A Handbook Of History &amp; Lore Of The Undead. Wellfleet Press, 2024. &lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||All About Vampires|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;

{{BookCat}}</text>
      <sha1>4k9wkii0e7elmcqlv9o87ft1pynmtbk</sha1>
    </revision>
    <revision>
      <id>4678614</id>
      <parentid>4678613</parentid>
      <timestamp>2026-10-27T21:14:10Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4678614</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5456" sha1="ftvhaq8s8gc1ozcpow0vok8sf9rfc2b" xml:space="preserve">== Women As Vampires ==
The image of the vampire has been dominated by men, from Dracula to Blade the half-vampire hero. Famous male Actors who played vampires in films have earned respect and praise. Beloved Actors such as Bela Lugosi and Robert Pattinson have benefited from their popularity, yet what about women who have played vampires? Are they equally well known? &lt;br&gt;
&lt;br&gt;
The male vampire has dominated and obscured the role women have played in the creation of the vampire myth, and its gradual mutation to better reflect post-modern cultural values. &lt;br&gt;
&lt;br&gt;
'''The Original Vampires:''' &lt;br&gt;
In cultures from around the world, the oldest vampire figures were female. [1] The Greeks left records of the ''lamiai'' and the ''keres'', the Aztecs spoke of ''cihuateteo'', and the Malaysians of ''langsuyar''. Most of these myths functioned as a means to explain problems associated with childbirth. For example, the ''cihuateteo'' was a reanimated corpse of a woman who died during childbirth or had given birth to a stillborn. In stories, she hunts children and drains their lives to compensate for the life that was taken from her. [2] &lt;br&gt;
&lt;br&gt;  
Although these vampiric beings were often viewed as frightening threats to pregnant women, over time they slowly evolved. &lt;br&gt;
&lt;br&gt;
Stories of the young vamp, a female vampire, emerged from Greek stories about the ''lamiai''. She appeared as a beautiful foreigner who would seduce unsuspecting young males looking for a partner. Philostratus told in ''The Life of Apollonius'' the story of a young man about to marry a beautiful vamp, the young student was saved by his teacher Apollonius. &lt;br&gt;
&lt;br&gt;
Over time, the vamp grew into a hyper-sexual, manipulative woman capable of seducing men in order to drain their blood, wealth, or vital energy. &lt;br&gt; 
This dangerous and seductive character developed around the late 19th and early 20th century. The vamp reflected male concerns regarding women's increased social and sexual liberation, as well as their changing social roles. From a Feminist viewpoint, the vamp was a threat to patriarchy, functioning outside the traditional domestic realm. She matched her male counterparts by showing equal abilities in her use of power to fulfill her needs and desires. Feminist critics note that the vamp operated outside the realm of traditional marriage, reflecting people's fear of a woman who enjoyed sex for pleasure, not for procreation. &lt;br&gt;
&lt;br&gt;
Post-modern people today are focused on reclaiming the &quot;monstrous feminine.&quot; From a cautionary tale to agents of liberation, vamps in modern horror cinema are likely to act as vigilantes preying upon pimps and abusive men, not as powerless silent victims. &lt;br&gt;       
&lt;br&gt;
'''The Literary Vampire:''' &lt;br&gt;
Almost all of the vampires found in early literature were women. Starting with the 1797 poem &quot;The Bride of Corinth&quot; by Goethe, based on an ancient Greek source. The poem retells the story of Philinnon (in Goethe's poem she is unnamed), a woman who had died a virgin. The woman returns to the living in order to experience sexual bliss before leaving this world. &lt;br&gt;
Another character, believed to be the first vampire in English literature, was a woman named Geraldine. She is the antagonist in Samuel Coleridge's poem, &quot;Christabel,&quot; written from 1790 - 1800. [1] &lt;br&gt;
&lt;br&gt;
In 1819, John Polidori introduced Lord Ruthven, a vampire character based on the aristocratic Lord Byron. His vampire preyed on unsuspecting women and later was the basis of a series of small pamphlets known as penny dreadfuls. ''Varney the Vampyre'', was published in the form of small pamphlets in 1845. The character Lord Ruthven dominated vampire literature for most of the century. &lt;br&gt;
&lt;br&gt;
Although the early 19th century was heavily dominated by male vampires in literature, occasionally, a few writers would create female vampires. In 1836 Théophile Gautier, a French writer, wrote &quot;The Beautiful Vampire.&quot; In 1848, Alexandre Dumas wrote &quot;The Pale Lady.&quot; Sheridan Le Fanu wrote &quot;Carmilla,&quot; a novella about a female vampire in 1872. Carmilla is considered the most popular female vampire ever created. [1] &lt;br&gt;
Another classic tale, &quot;A Mystery of the Campagna&quot; was written by Anne Crawford in 1887. [1] &lt;br&gt;
&lt;br&gt;
'''The Blood Countess:''' &lt;br&gt;
Elizabeth Báthory, a real woman considered a vampire by millions of people, lived in Hungry from 1560 - 1614. Elizabeth Báthory, or the Blood Countess, was married to Count Ferenc Nádasdy. She soon became a wealthy widow when her husband died fighting in a war with the Ottoman empire. According to legend, Báthory accidently learned the secret to youth, and began drinking and bathing in the blood of young girls in order to maintain her youthful appearance. It is said that she murdered over six hundred servants. She was put on public trial when news of her cruelty reached her political rivals. At her trial, hundreds of people testified against her. She was found guilty and placed under house arrest. Her lands and her title were stripped from her, then redistributed to her family.  [2]&lt;br&gt;
&lt;br&gt;

==== Reference: ====
1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Version]. Visible Ink Press, 2014. &lt;br&gt;
&lt;br&gt; 
2. Hollyhock, Agnes. Vampires: A Handbook Of History &amp; Lore Of The Undead. Wellfleet Press, 2024. &lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||All About Vampires|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;

{{BookCat}}</text>
      <sha1>ftvhaq8s8gc1ozcpow0vok8sf9rfc2b</sha1>
    </revision>
  </page>
  <page>
    <title>User:Panic2k4/Sandbox/Central</title>
    <ns>2</ns>
    <id>486591</id>
    <revision>
      <id>4678620</id>
      <timestamp>2026-10-27T21:26:17Z</timestamp>
      <contributor>
        <username>Panic2k4</username>
        <id>2865</id>
      </contributor>
      <comment>test main</comment>
      <origin>4678620</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19" sha1="tklx3wkj4tqjdyphbnx1syawhn7he4p" xml:space="preserve">= Comment Central =</text>
      <sha1>tklx3wkj4tqjdyphbnx1syawhn7he4p</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Meat and Sausage Ragu with Pasta</title>
    <ns>102</ns>
    <id>486592</id>
    <revision>
      <id>4678631</id>
      <timestamp>2026-10-27T23:42:19Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>Created page with &quot;{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3 | Image = [[Image:Ragù napoletano.jpg|300px]] }} {{recipe}} | [[Cookbook: Italian-American cuisine]]  Servings: 6–8 Prep time: 20 minutes Cooking time: Approximately 2 hours 30 minutes  ==Ingredients==  *1 lb (454 g) dried pasta  *1½ lbs beef chuck, cut into approximately 1½-inch chunks  *1 lb Italian sausage (approximately 4–5 links)  *3 tablespoons extra-virgin o...&quot;</comment>
      <origin>4678631</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3582" sha1="h8nbi0nruewbnb1df17is9mdiuy1wwv" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>h8nbi0nruewbnb1df17is9mdiuy1wwv</sha1>
    </revision>
    <revision>
      <id>4678634</id>
      <parentid>4678631</parentid>
      <timestamp>2026-10-27T23:45:10Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678634</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3643" sha1="bd5f9g3ntouhwu1ouzkmpspfmvn97rr" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

Servings: 6–8
Prep time: 20 minutes
Cooking time: Approximately 2 hours 30 minutes

The below recipe is inspired by Neapolitan ragu with pasta.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>bd5f9g3ntouhwu1ouzkmpspfmvn97rr</sha1>
    </revision>
    <revision>
      <id>4678635</id>
      <parentid>4678634</parentid>
      <timestamp>2026-10-27T23:45:47Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678635</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3558" sha1="goc7t3cgdsgvrpbf6qd4kbsaqb8dgoz" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>goc7t3cgdsgvrpbf6qd4kbsaqb8dgoz</sha1>
    </revision>
    <revision>
      <id>4678636</id>
      <parentid>4678635</parentid>
      <timestamp>2026-10-27T23:46:20Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>Codename Noreste moved page [[Meat and sausage ragu with pasta]] to [[Cookbook:Meat and sausage ragu with pasta]] without leaving a redirect: Correct namespace.</comment>
      <origin>4678635</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3558" sha1="goc7t3cgdsgvrpbf6qd4kbsaqb8dgoz" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>goc7t3cgdsgvrpbf6qd4kbsaqb8dgoz</sha1>
    </revision>
    <revision>
      <id>4678637</id>
      <parentid>4678636</parentid>
      <timestamp>2026-10-27T23:51:05Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678637</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3686" sha1="3dsmvosowzttehz8mtcx26co2pqj4ks" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>3dsmvosowzttehz8mtcx26co2pqj4ks</sha1>
    </revision>
    <revision>
      <id>4678638</id>
      <parentid>4678637</parentid>
      <timestamp>2026-10-27T23:51:56Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4678638</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3694" sha1="1wsxmj9af4a0xl3bos31p07hctw2861" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a [[dutch oven]] or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a [[cheese grater]]
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>1wsxmj9af4a0xl3bos31p07hctw2861</sha1>
    </revision>
    <revision>
      <id>4678639</id>
      <parentid>4678638</parentid>
      <timestamp>2026-10-27T23:53:08Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678639</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3686" sha1="3dsmvosowzttehz8mtcx26co2pqj4ks" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>3dsmvosowzttehz8mtcx26co2pqj4ks</sha1>
    </revision>
    <revision>
      <id>4678640</id>
      <parentid>4678639</parentid>
      <timestamp>2026-10-27T23:53:38Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4678640</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3690" sha1="9oaumkhh4w1mu9fabcrnvsfgl17bwye" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>9oaumkhh4w1mu9fabcrnvsfgl17bwye</sha1>
    </revision>
    <revision>
      <id>4678641</id>
      <parentid>4678640</parentid>
      <timestamp>2026-10-27T23:54:01Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678641</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3686" sha1="3dsmvosowzttehz8mtcx26co2pqj4ks" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>3dsmvosowzttehz8mtcx26co2pqj4ks</sha1>
    </revision>
    <revision>
      <id>4678642</id>
      <parentid>4678641</parentid>
      <timestamp>2026-10-28T00:00:56Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678642</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3690" sha1="qhcfvw3auddk53kcv91gtg6rwz429iw" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef [[chuck]], cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>qhcfvw3auddk53kcv91gtg6rwz429iw</sha1>
    </revision>
    <revision>
      <id>4678643</id>
      <parentid>4678642</parentid>
      <timestamp>2026-10-28T00:01:16Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678643</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3686" sha1="3dsmvosowzttehz8mtcx26co2pqj4ks" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>3dsmvosowzttehz8mtcx26co2pqj4ks</sha1>
    </revision>
    <revision>
      <id>4678666</id>
      <parentid>4678643</parentid>
      <timestamp>2026-10-28T08:19:52Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>MathsScienceNerd1 moved page [[Cookbook:Meat and sausage ragu with pasta]] to [[Cookbook:Meat and Sausage Ragu with Pasta]] without leaving a redirect: Title case</comment>
      <origin>4678643</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3686" sha1="3dsmvosowzttehz8mtcx26co2pqj4ks" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragu with pasta cooked in Naples and in the kitchens of many Italian-American family kitchens often referred to as Sunday sauce or Sunday gravy.

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>3dsmvosowzttehz8mtcx26co2pqj4ks</sha1>
    </revision>
    <revision>
      <id>4678673</id>
      <parentid>4678666</parentid>
      <timestamp>2026-10-28T10:57:23Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678673</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3872" sha1="9lsslj4r61ll0ode3ovgnolo4gx54wx" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragù, a dish that originated in [[Naples]] and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>9lsslj4r61ll0ode3ovgnolo4gx54wx</sha1>
    </revision>
    <revision>
      <id>4678674</id>
      <parentid>4678673</parentid>
      <timestamp>2026-10-28T10:57:50Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678674</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3868" sha1="nh1rjzj4rjf1r9qnwomfckad49m7t2t" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]


The below recipe is inspired by Neapolitan ragù, a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>nh1rjzj4rjf1r9qnwomfckad49m7t2t</sha1>
    </revision>
    <revision>
      <id>4678675</id>
      <parentid>4678674</parentid>
      <timestamp>2026-10-28T10:58:11Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678675</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3867" sha1="n1k1rhmirggkmliimlu6ml5rhmv0060" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by Neapolitan ragù, a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated Parmigiano Reggiano, for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>n1k1rhmirggkmliimlu6ml5rhmv0060</sha1>
    </revision>
    <revision>
      <id>4678676</id>
      <parentid>4678675</parentid>
      <timestamp>2026-10-28T11:02:46Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678676</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3881" sha1="9qyg7serkfcobxj7xwulpbc938afx8l" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by Neapolitan ragù, a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia|Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>9qyg7serkfcobxj7xwulpbc938afx8l</sha1>
    </revision>
    <revision>
      <id>4678677</id>
      <parentid>4678676</parentid>
      <timestamp>2026-10-28T11:10:29Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678677</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3881" sha1="rz9oitbzgze1mpd3mhloux0eceog7cq" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by Neapolitan ragù, a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia:Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>rz9oitbzgze1mpd3mhloux0eceog7cq</sha1>
    </revision>
    <revision>
      <id>4678678</id>
      <parentid>4678677</parentid>
      <timestamp>2026-10-28T11:11:05Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4678678</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3901" sha1="f4fon3e992hva16v276q3x43ainj91s" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by Neapolitan ragù, a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia:Parmigiano Reggiano|Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>f4fon3e992hva16v276q3x43ainj91s</sha1>
    </revision>
    <revision>
      <id>4678679</id>
      <parentid>4678678</parentid>
      <timestamp>2026-10-28T11:12:15Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678679</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3921" sha1="0mze54szdb38clmug1kdlzhmatp0q5b" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by Neapolitan [[wikipedia:ragù|ragù]], a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia:Parmigiano Reggiano|Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>0mze54szdb38clmug1kdlzhmatp0q5b</sha1>
    </revision>
    <revision>
      <id>4678680</id>
      <parentid>4678679</parentid>
      <timestamp>2026-10-28T11:13:31Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678680</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3943" sha1="52o4g18jr3p0s9hvftxp3pqrqapadhw" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by Neapolitan [[wikipedia:Neapolitan ragù|Neapolitan ragù]], a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia:Parmigiano Reggiano|Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>52o4g18jr3p0s9hvftxp3pqrqapadhw</sha1>
    </revision>
    <revision>
      <id>4678681</id>
      <parentid>4678680</parentid>
      <timestamp>2026-10-28T11:13:55Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678681</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3932" sha1="jnbpjv7gd5otkuunh5axgbk8rl107vx" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image:Ragù napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by [[wikipedia:Neapolitan ragù|Neapolitan ragù]], a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia:Parmigiano Reggiano|Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>jnbpjv7gd5otkuunh5axgbk8rl107vx</sha1>
    </revision>
    <revision>
      <id>4678682</id>
      <parentid>4678681</parentid>
      <timestamp>2026-10-28T11:15:33Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678682</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3927" sha1="7n3flcdou0mty1o5ozbadh7edavmmvt" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image: Napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by [[wikipedia:Neapolitan ragù|Neapolitan ragù]], a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia:Parmigiano Reggiano|Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>7n3flcdou0mty1o5ozbadh7edavmmvt</sha1>
    </revision>
    <revision>
      <id>4678683</id>
      <parentid>4678682</parentid>
      <timestamp>2026-10-28T11:16:23Z</timestamp>
      <contributor>
        <username>Moby-Dick4000</username>
        <id>198746</id>
      </contributor>
      <origin>4678683</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3952" sha1="akd2x1u0yrw9iqd20xgrsona1swtig5" xml:space="preserve">{{recipesummary|category=Italian-American recipes|servings=6|time=2hours and 20 minutes|difficulty=3
| Image = [[Image: Paccheri rigati al ragù Napoletano.jpg|300px]]
}}
{{recipe}} | [[Cookbook: Italian-American cuisine]]

The below recipe is inspired by [[wikipedia:Neapolitan ragù|Neapolitan ragù]], a dish that originated in Naples and is widely eaten in the Campania region of Italy. It's also popular among Italian-American families who call it Sunday sauce or Sunday gravy because it's often made on Sundays. The recipe presented here is a faster version of the authentic dish which takes several hours to prepare. 

==Ingredients==

*1 lb (454 g) dried pasta

*1½ lbs beef chuck, cut into approximately 1½-inch chunks

*1 lb Italian sausage (approximately 4–5 links)

*3 tablespoons extra-virgin olive oil

*1 medium onion, finely chopped

*2 medium carrots, finely chopped

*2 celery stalks, finely chopped

*3 cloves garlic, minced

*2 cans (28 oz each) crushed tomatoes

*3 tablespoons tomato paste

*1 teaspoon dried oregano

*1 teaspoon dried basil

*Salt, to taste

*Freshly grated [[wikipedia:Parmigiano Reggiano|Parmigiano Reggiano]], for serving

== Equipment ==
*a thick-walled pot such as a dutch oven or an aluminum cauldron
*large tongs
*a large spoon for stirring
*a kitchen knife
*a cheese grater
*a measuring cup
*measuring spoons
*a food scale

== Procedure ==
*Heat the olive oil in a large, thick-walled pot or Dutch oven over medium-high heat.
*Add the beef chuck and whole Italian sausages together. Season the beef lightly with salt.
*Cook, turning occasionally, until the beef develops a brown crust and the sausages are browned on all sides, approximately 8–12 minutes. Work in batches if necessary to avoid overcrowding.
*Remove the beef and sausages from the pot and set aside.
*Reduce the heat to medium.
*Add the chopped carrots, celery, and onion to the same pot, using the remaining oil and rendered fat from the meat.
*Cook for approximately 8–10 minutes, stirring occasionally, until the vegetables have softened.
*Make a small opening in the center of the vegetables and add the minced garlic.
*Cook until the garlic becomes lightly golden, approximately 30–60 seconds.
*Immediately add the crushed tomatoes to prevent the garlic from burning. Stir thoroughly to combine with the vegetables.
*Add the tomato paste and mix well until completely incorporated.
*Add the oregano and basil, stirring to distribute the herbs evenly throughout the sauce.
*Season with salt to taste, keeping in mind that the sausages will contribute additional salt.
*Return the browned beef chuck and Italian sausages to the pot, along with any accumulated juices.
*Stir gently, making sure the meat is submerged in the tomato sauce.
*Bring the sauce to a gentle simmer, then reduce the heat to low.
*Simmer for 2 hours, stirring approximately every 10 minutes to prevent the sauce from sticking to the bottom of the pot. Keep the heat low enough that the sauce bubbles gently rather than boiling vigorously.
*Approximately 10 minutes before the sauce finishes simmering, bring a large pot of salted water to a boil.
*Add the entire 1-pound box of dried pasta.
*Cook until slightly underdone, approximately 1–2 minutes less than the package's recommended cooking time. Do not drain the pasta or discard the cooking water.
*Using tongs, transfer the slightly undercooked pasta directly from the boiling water into the pot of ragù.
*Stir thoroughly so that every piece of pasta is coated with sauce.
*Add a little starchy pasta cooking water, approximately ¼ cup at a time, as needed to loosen the sauce.
*Continue cooking and stirring over medium-low heat until the pasta is tender but not mushy and the sauce clings evenly to it.
*Divide the pasta and ragù among serving plates, distributing the beef and sausage as desired.
*Grate fresh Parmigiano Reggiano generously over each serving.
*Serve immediately while hot.</text>
      <sha1>akd2x1u0yrw9iqd20xgrsona1swtig5</sha1>
    </revision>
  </page>
  <page>
    <title>Birthday Greeting Customs</title>
    <ns>0</ns>
    <id>486593</id>
    <revision>
      <id>4678648</id>
      <timestamp>2026-10-28T04:52:54Z</timestamp>
      <contributor>
        <username>JacksonBirthdayNotes</username>
        <id>3629579</id>
      </contributor>
      <comment>Create book main page with contents link</comment>
      <origin>4678648</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="423" sha1="4pv1vu0v7caeg8549dhtfcjfmw3x4sm" xml:space="preserve">This book introduces birthday greeting customs around the world, with attention to the words, gifts, and gestures people use to mark another year of life.

== Contents ==
* [[Birthday Greeting Customs/Flowers in Birthday Traditions|Flowers in Birthday Traditions]]

Birthday greetings are not only messages. They are social acts that show attention, respect, and affection, and they change with place, family, and occasion.</text>
      <sha1>4pv1vu0v7caeg8549dhtfcjfmw3x4sm</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Magazine</title>
    <ns>4</ns>
    <id>486594</id>
    <revision>
      <id>4678655</id>
      <timestamp>2026-10-28T07:54:40Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <comment>Create starter page, can be expanded if necessary. Based on [https://wikikids.nl/Wikikids:Magazine this page]</comment>
      <origin>4678655</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="738" sha1="2kr69vs9bgjx9z1dsdnutzbsbd9yydh" xml:space="preserve">The '''Wikibooks Magazine''' is the publication of Wikibooks, providing information about what is going on at Wikibooks. This was inspired by the [https://wikikids.nl/Wikikids:Magazine WikiKids Magazine] originally created by [https://wikikids.nl/Gebruiker:Perquirius Perquirius]. See the table below for each issue. It is published at the end of February (excluding February 29th), May, August and November. The magazine was created following consensus in [[Wikibooks:Reading room/Proposals#Wikibooks Magazine]] for the creation of the publication.
{| class=&quot;wikitable&quot;
|+
!
!28th February
!31st May
!31st August
!30th November
|-
|'''2026'''
|n/a
|n/a
|n/a
|[[Wikibooks:Magazine/1|Link]]
|-
|'''2027'''
|
|
|
|
|-
|'''2028'''
|
|
|
|
|}</text>
      <sha1>2kr69vs9bgjx9z1dsdnutzbsbd9yydh</sha1>
    </revision>
    <revision>
      <id>4678656</id>
      <parentid>4678655</parentid>
      <timestamp>2026-10-28T07:56:16Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <origin>4678656</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="735" sha1="lf42n5du2ajhatzugxcfkic89e16ls3" xml:space="preserve">The '''Wikibooks Magazine''' is the publication of Wikibooks, providing information about what is going on at Wikibooks. This was inspired by the [https://wikikids.nl/Wikikids:Magazine WikiKids Magazine] originally created by [https://wikikids.nl/Gebruiker:Perquirius Perquirius]. See the table below for each issue. It is published at the end of February (excluding February 29th), May, August and November. The magazine was created [[Wikibooks:Reading room/Proposals#Wikibooks Magazine|following consensus]] for the creation of the publication.
{| class=&quot;wikitable&quot;
|+
!
!28th February
!31st May
!31st August
!30th November
|-
|'''2026'''
|n/a
|n/a
|n/a
|[[Wikibooks:Magazine/1|Link]]
|-
|'''2027'''
|
|
|
|
|-
|'''2028'''
|
|
|
|
|}</text>
      <sha1>lf42n5du2ajhatzugxcfkic89e16ls3</sha1>
    </revision>
    <revision>
      <id>4678664</id>
      <parentid>4678656</parentid>
      <timestamp>2026-10-28T08:15:52Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <origin>4678664</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="995" sha1="5ftf92cin6jeyhxhy9gd6x9o48rs4ic" xml:space="preserve">The '''Wikibooks Magazine''' is the publication of Wikibooks, providing information about what is going on at Wikibooks. This was inspired by the [https://wikikids.nl/Wikikids:Magazine WikiKids Magazine] originally created by [https://wikikids.nl/Gebruiker:Perquirius Perquirius]. See the table below for each issue. It is published at the end of February (excluding February 29th), May, August and November. The magazine was created [[Wikibooks:Reading room/Proposals#Wikibooks Magazine|following consensus]] for the creation of the publication.
&lt;br&gt;
Do you have an idea for the next issue of the publication? Then please share your ideas! Press the button below to do so, or go to the discussion page of the next Magazine issue!
{{Clickable button|Wikibooks talk:Magazine/1|Share your ideas!|color=blue}}
{| class=&quot;wikitable&quot;
|+
!
!28th February
!31st May
!31st August
!30th November
|-
|'''2026'''
|n/a
|n/a
|n/a
|[[Wikibooks:Magazine/1|Link]]
|-
|'''2027'''
|
|
|
|
|-
|'''2028'''
|
|
|
|
|}</text>
      <sha1>5ftf92cin6jeyhxhy9gd6x9o48rs4ic</sha1>
    </revision>
    <revision>
      <id>4678665</id>
      <parentid>4678664</parentid>
      <timestamp>2026-10-28T08:17:56Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>-button, doesn't work</comment>
      <origin>4678665</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="735" sha1="lf42n5du2ajhatzugxcfkic89e16ls3" xml:space="preserve">The '''Wikibooks Magazine''' is the publication of Wikibooks, providing information about what is going on at Wikibooks. This was inspired by the [https://wikikids.nl/Wikikids:Magazine WikiKids Magazine] originally created by [https://wikikids.nl/Gebruiker:Perquirius Perquirius]. See the table below for each issue. It is published at the end of February (excluding February 29th), May, August and November. The magazine was created [[Wikibooks:Reading room/Proposals#Wikibooks Magazine|following consensus]] for the creation of the publication.
{| class=&quot;wikitable&quot;
|+
!
!28th February
!31st May
!31st August
!30th November
|-
|'''2026'''
|n/a
|n/a
|n/a
|[[Wikibooks:Magazine/1|Link]]
|-
|'''2027'''
|
|
|
|
|-
|'''2028'''
|
|
|
|
|}</text>
      <sha1>lf42n5du2ajhatzugxcfkic89e16ls3</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks talk:Magazine/1</title>
    <ns>5</ns>
    <id>486595</id>
    <revision>
      <id>4678657</id>
      <timestamp>2026-10-28T08:00:01Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <comment>Created page with &quot;Are there any ideas for the next Wikibooks Magazine? ~~~~&quot;</comment>
      <origin>4678657</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="225" sha1="7ovnbieekxb3xjzmkl2oq0rtw65sgky" xml:space="preserve">Are there any ideas for the next Wikibooks Magazine? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:00, 28 October 2026 (UTC)</text>
      <sha1>7ovnbieekxb3xjzmkl2oq0rtw65sgky</sha1>
    </revision>
    <revision>
      <id>4678659</id>
      <parentid>4678657</parentid>
      <timestamp>2026-10-28T08:03:43Z</timestamp>
      <contributor>
        <username>MathsScienceNerd1</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>+idea</comment>
      <origin>4678659</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="433" sha1="swp7na53nlhs90tn1vpfwbciqro00j5" xml:space="preserve">Are there any ideas for the next Wikibooks Magazine? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:00, 28 October 2026 (UTC)
:*Discontinuation of FlaggedRevs.  [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:03, 28 October 2026 (UTC)</text>
      <sha1>swp7na53nlhs90tn1vpfwbciqro00j5</sha1>
    </revision>
  </page>
</mediawiki>