Editing
Project:Observatory Users Manual
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Article pages== === About editing Articles of all kinds === There are three ways to edit an Article: ==== Edit with form ==== [[File:Edit with form Editorial Domain.png|650x650px]] Use a form to fill in fields for the basic information about an Article. This is especially useful when starting an Article. ==== Edit ==== [[File:Edit Editorial Domain.png|650x650px]] The “Edit” link on top of an Article page (to the right of “Discussion”) is the best way to edit the Article body. Once you click “Edit,” there are two ways to edit Articles that you can toggle between using the pencil icon: Visual editing and Source editing. “Visual editing” refers to editing content directly on a screen, seeing the changes as you make them, similar to a word processor, while “Source editing” involves modifying the underlying code (like HTML) that generates the content. ===== Visual editing ===== [[File:Visual editing.png|none|thumb|650x650px]] This is a simple way to edit your Article body visually. The body will appear close to how readers will see it, with some exceptions such as multimedia or the use of templates. ''(See also: [[Project:Observatory Users Manual#Source editing (code)|Source editing (code)]].)'' ===== Source editing (code) ===== [[File:Source editing.png|none|thumb|650x650px]] This requires knowledge of the markup language (wikitext). It is how you edit “under the hood.” Your editor can assist you with Source editing. ''(See also: [[Project:Observatory Users Manual#Visual editing|Visual editing]].)'' === About the two kinds of Articles: Observatory (typical) and Classic (rare) === Most Articles are Observatory Articles that follow the instructions directly below. If your editor tells you your work involves Classics Articles, see the section after this. === How to enter an Article (typical Observatory Article case) === ==== I. Starting an Article ==== Ask your editor to start an Observatory Article page for you, including information via email (preferred) or [https://ed.observatory.wiki/Special:Contact/requestarticle request form]. Ask them to send you the link to work on. Then follow the instructions in Part II below. When you’re done editing your Article Draft, email your editor to let them know it’s ready for their review. Your editor will then review it and either give you feedback for revisions or Publish it. Include the following in your email to your editor: # [[Project:Style Guide/Editorial Process#Headline-Style Capitalization|Headline formatted in Observatory house style]] # Area (if you don’t know, leave this out) # Author(s) # Source (i.e., affiliated organization/previous or partner publisher) if any # Google Document of the Article (if you started one) # Wikimedia Commons image (optional: can be done later, or your editor can pick for you) # Any other information your editor should know about this Article (e.g., has this Article been previously Published?) ==== II. Filling in Observatory Article form fields ==== '''How to enter initial metadata (first Save):''' ===== Describe ===== ====== Headline ====== Required. Follow the [[Project:Style Guide/Editorial Process#Headline|Headline guidelines in the Observatory Style Guide]]. And use headline-style capitalization rules from the [[Project:Style Guide/Editorial Process#Headline|Observatory Style Guide]]. ====== Sort As ====== * This field determines the alphabetical order to display lists of Articles in some contexts, such as lists. * Headlines that start with “The” or “A” or “An” or a punctuation mark (including a single open-quotation mark) need this field filled in with any of those elements removed. ** For example, for the Headline '''The Headline''', we would fill in the Sort As '''Headline, The'''. * If there are special characters in the Headline, such as an accented letter such as é or â or ç, an umlaut such as ö or ï, or a character i like ı, etc., you should put the Headline in the Sort As field with the letter presented in its standard way. ** For example, for the Headline '''Café Culture of Italy''', we would fill in its Sort As '''Cafe Culture of Italy'''. * The first letter must always be capitalized (it won’t display this way, but it will sort out of order if the first letter is lowercase). * Leave this field blank if the Headline does not start with “The,” “A,” “An,” or a punctuation mark, ''and'' it does not contain special characters. The sorting order for Articles with blank Sort As fields will be determined by the Headline field. ====== Subtitle (Teaser) ====== Required. Follow the [[Project:Style Guide/Editorial Process#Teaser (i.e., Subtitle/Subheadline)|Teaser guidelines in the Observatory Style Guide]]. ====== Editor’s Notes ====== This will appear at the bottom of Article for all readers (section is visible to the public too). ====== Author(s) ====== Fill in Author(s). If a coauthor needs to be created and you don’t have access, ask your editor for help (provide your editor with their email address so we can onboard them). ====== Has audio version ====== Generally leave unchecked and let your editor handle. ====== Has video version ====== Generally leave unchecked and let your editor handle. ====== Cover Image ====== Let your editor handle for you. ====== Cover Image Page ====== Let your editor handle for you. ====== Suppress cover image display ====== Let your editor handle for you. ====== Suppress uploaded media caption ====== Let your editor handle for you. ====== Limit uploaded media width ====== Let your editor handle for you. ====== Section ====== A radio field with options for “Observatory” and “Classics.” Make sure the page was set to “Observatory” if you are entering a typical Article (“Classics” is only used for public domain content and will display fields in this form that don’t apply.) Ask your editor if you notice the wrong button was Pushed to make sure you’re working in the right namespace before continuing. ====== Source ====== Start typing in the Source of the Article, if there is one. For example, if it was originally produced by an affiliated organization, or if it was previously Published by another publication (including your organization or the Independent Media Institute or one of its projects: Earth Food Life Project, Economy for All Project, Human Bridges Project, Local Peace Economy Project, Our Schools Project, or Voting Booth Project). Select it as it starts to appear. Articles have nothing in the Source field if the above does not apply. If the organization name does not start to appear as you type, ask your editor if they would consider adding it to the Observatory as a Source. (In your request, please provide your editor with the organization’s website, contact email address of someone who can handle permissions requests at that organization, and their logo if you have it.) ====== Date first published ====== Enter the date of original publication if this is a reprint/embargoed, or today’s date if it’s original to the Observatory. If you only know the month and year, you may leave the exact day empty. An administrator may later change this to the date they Publish and Push. ====== Display date checkbox ====== Generally, always check this box, unless it’s extremely evergreen or your editor tells you not to. This will buy you some leeway on updating and give readers context (the date only appears at the bottom of the piece if this is checked, not up top or near the byline in the sidebar). ===== Explain ===== ====== URL of the Google Doc source ====== Paste the URL of the Google Document where you worked on this Article with your editor. ====== Credit Line ====== Generally you might copy-paste from your previous Articles, unless there is a difference in the Source or permissions. Use the Credit Line from your Article template in most cases. Your editor can help with this. ===== Classify ===== ====== Area ====== Required. You can only pick one Area per Article. ====== Tags ====== Enter a few keywords related to the Article, using headline-style capitalization and the [[Project:Style Guide/Editorial Process#Headline|Observatory Style Guide]]. Between 1 and 6 relevant tags is recommended, but you may use more. A maximum of 6 will be displayed in a random order on the page load. If you used more than 6 tags, “View More” button will cut the rest off. ===== Publish ===== ====== Publish Checkbox ====== Your editor will handle this on your behalf after all revisions are complete. ===== Other ===== ====== Bibliography ====== Many Articles leave this field blank. If you have a bibliography to add at the bottom of your Article (in addition to/separate from the consideration of footnotes/endnotes), you may enter it here. Follow MLA style and the [[Project:Style Guide#Links and Footnotes for Observatory Articles/Dual Pub Plan|Observatory Style Guide]], and enter in the format of a numbered list. This field should benefit the public with additional sources to look up (it is not just used internally). ===== Article text ===== This will be your Article body. It is recommended to fill this in ''after'' your first Save. (Skip this field on your first Save and return to it later via “Edit with form” or “Edit” options.) See Part III below on how to prepare your Article body for the Observatory site. If you don’t follow those instructions and try to copy-paste directly from the Google Document, you will create critical hyperlink and other formatting errors. ===== Save the Article page ===== ====== Summary ====== Add a short statement summarizing changes you made (optional). ====== This is a minor edit checkbox ====== If it’s a minor edit, click to check this box. You can change your default settings for this field in the top navigation menu’s “Edit” button→“Account Settings”→“Editing”→“Mark all edits minor by default” checkbox. ====== Watch this page ====== Check this box if you want to receive email notifications about changes to the Article. Leave it unchecked if not. You can change your default settings for this field in the top navigation menu’s “Edit” button→“Account Settings”→“Watchlist”→Scroll down to “Watched pages” and check or uncheck the three checkboxes. ====== Save page (blue button) ====== Click this button when you’re done with this round of edits to the form. You can make further edits after your first or subsequent changes via “Edit with form” or “Edit” after this. If you exit the page/tab/window in your browser or click the “Back” button in your browser, your changes may be lost. Change your default settings to prompt a pop-up warning you if you will lose your work in “Edit” button→“Account Settings”→“Editing”→“Warn me when I leave an edit page with unsaved changes” checkbox. '''Next, you will fill in the Article body.''' ==== III: Prepare your Article copy for the Observatory site ==== Consult with your editor on how to enter your Article. Most Observatory editors prefer you begin with a Google Document. Once it is finalized, '''you will need to convert the text so it is compatible with the Observatory software (MediaWiki/wikitext)'''. (In the rare case that you have prearranged to enter your copy directly into the Observatory site, you may skip Part III.) If you have any questions or need help with the following conversion process, ask your editor for help. ===== PC: Follow the instructions for the free online converter: “Try Pandoc!” ===== Go to https://pandoc.org/try/. Follow the ScribeHow instructions linked here: [https://scribehow.com/shared/Convert_from_a_Word_Doc_from_a_Google_Doc_to_Wikitext_Using_Free_Online_Pandoc_Converter__0XduCdANRqulMn1XPjKmRA “Convert from a Word Doc (from a Google Doc) to MediaWiki (wikitext) Using Free Online Pandoc Converter.”] ===== Mac: Software requirements ===== The first time you do this, you will need to set up some software. Get the Pandoc app and set up the Quick Action workflow: # Install Pandoc, a file converter app, by going to https://pandoc.org/installing.html and clicking the big blue button “Download the Latest Installer.” Select the latest Mac file—it will end in “macOS.pkg.” (As of 1/8/25, available at [https://github.com/jgm/pandoc/releases/download/3.6.1/pandoc-3.6.1-x86_64-macOS.pkg pandoc-3.6.1-x86_64-macOS.pkg].) Go through the installation prompts and finish installing it. # '''Install a Quick Action workflow''' to your computer to easily convert Article files into MediaWiki format in Finder with control+click and Pandoc: ## Download the customized Observatory workflow at this link: [https://drive.google.com/file/d/1TgIQdf8LP_mciyaEER2a6ao1vi1EwBDE/view?usp=sharing PandocConvertMediawiki.workflow.zip]. ### Download all files at [https://drive.google.com/file/d/1TgIQdf8LP_mciyaEER2a6ao1vi1EwBDE/view?usp=sharing PandocConvertMediawiki.workflow.zip] (including subfolders). ### Unzip the file you downloaded. ### In Finder, open the unzipped .workflow file with the Automator app. Here’s how: #### In Finder, find the file '''PandocConvertMediawiki.workflow''' that you just unzipped. #### Double-click '''PandocConvertMediawiki.workflow'''. #### Click “Install” on the dialog that has appeared. #### Once installed, the “'''PandocConvertMediawiki'''” action will appear under the “Quick Actions” item of the context menu. # '''Convert the Article file into MediaWiki format:''' These steps convert your Article body from Google Docs to a local Word Document or Open Office file to a TextEdit file containing the code of your Article formatted in MediaWiki language. ## In Google Docs, click “File”→“Download”→“Microsoft Word” to Save your Article as a local file (.docx or .doc). (OpenDocument format .odt is also acceptable if you use Open Office software.) ## In Finder, find your Article file and hover over it. ## Do not open the file—'''don’t double-click''' on it. Instead, press '''control+click''' (on a Mac keyboard; or right-click on a mouse) on the file to open a pop-up menu. ## At the bottom of the pop-up menu, hover over the option “Quick Actions” and then click on the “'''PandocConvertMediawiki'''” action. ## Your Article file will be converted to your new Article file in MediaWiki format at the top of your folder in Finder. ==== IV: Insert the MediaWiki code of your Article into the Observatory “Article text” (body) field of your Article Draft ==== Now you have your MediaWiki source code for the Article body ready to upload into the Observatory. Here’s what’s next: # '''Open the new converted MediaWiki file''' of the Article body with your plaintext editor of choice ('''TextEdit''' or '''Notes'''). ## Macs have the TextEdit app; PCs have Notes or a similar app. ### Mac users: If when you double-click the file it doesn’t open in TextEdit by default, then you can set it up: #### Select the MediaWiki file, then open up a pop-up menu by pressing '''control+click→“Open With”→“Other'''.” #### Change “Enable” field from “Recommended Applications” to “All Applications” and then look for TextEdit. #### Double-click the TextEdit icon. #### After this, TextEdit should appear on the “Open With” part of the above. #### Recommended: You can make TextEdit the default app to open this kind of file now or later or never. If you made TextEdit default, it will open with TextEdit if you double-click a file of this type from now on. # Copy the Article body (exclude frontmatter) part of the contents of the plaintext document and paste it into the “Article text” (Article body field) of your Draft on Observatory.wiki (whether you are in “Edit with form” or “Edit” mode, you need to be in “Edit Source” mode for “Source editing,” not Visual Editor). # Check for errors in Visual Editor mode. ==== Tips for setting up the Article body ==== ===== Best practices in Google Docs before converting files to MediaWiki ===== Keep the formatting of your Google Doc simple: * No decorations or embedded images (those can come after you enter it on the Observatory). * Structure elements/headings/subheadings need to be formatted as headers at the correct level (see [[Project:Observatory Users Manual#Follow these best practices for Headings and Subheadings|below]]). * Carefully format your links and bold and italic text. ** Make sure you do not use the above-mentioned special formatting over blank spaces that appear before or after the text that you are italicizing, bolding, or hyperlinking. ** ''See: [[Project:Observatory Users Manual#Links|“Links” in the Glossary]].'' *Make a note of any block quotes as you create your Google Doc draft; you will manually convert paragraphs into blockquote formatting using the Header dropdown when you enter the piece on the Observatory. ====== Follow these best practices for headings and subheadings ====== * You can format the section titles within your Article body (headings/subheadings) at two points: *# In the Google Doc: in the toolbar, change a heading from Normal text to Heading 1. *#* Best practice: Keep '''section header formatting''' of Articles '''within the range of Heading 1→Heading 3''' when setting up sections of an Article in a Google Doc before converting. *# After you convert via Pandoc to wikitext: change, using search and replace function, <nowiki>'''</nowiki>bolded line headings<nowiki>'''</nowiki> with three single apostrophes into <nowiki>==Wikitext Headings==</nowiki> with two equal signs around the line. If you have a subheading within a section, use three equal signs: <nowiki>===Wikitext Subheadings===</nowiki>. * Wikitext guide: Don’t combine heading tags (equal signs) plus bold formatting—using just headline-style formatting will be sufficient, and bold formatting is redundant and discouraged. **There is no need to make headings bold (with three straight apostrophes in the code); they are bold by default: ***'''Unnecessary:''' <nowiki>== '''Heading''' ==</nowiki> ***'''Good:''' <nowiki>== Heading ==</nowiki> **The space between the heading text and the equal sign is optional. It doesn’t make a difference if it’s flush or if there is a space. #Title is the page title—don’t use this except over your Article’s Headline. #*Use: It’s the title of the Article that appears at the top of the page. It can only be used once per Article. #H1 is the highest level of an Article’s sections. You can use it for section titles like “Introduction” and “Background” or longer ones; it’s also not uncommon to only use this level throughout the Article body for all sections. Use H1 the way you normally use bold section headers in a Google Doc (if you format them as Heading 1 level in the Google Doc as opposed to simple bolding, they should automatically be converted during the Pandoc/workflow process the way you want them to look). #*Use: Many Articles will only use this level of heading as the deepest level of heading, and that’s fine; H2–H3 are not necessary, H4–H5 are inadvisable, and H6–H7 and beyond are not possible on the Observatory. #*Table of contents (TOC) appearance: It appears flush-left in the table of contents on Article pages. #* Short Articles that don’t have tables of contents might not even use this or any lower levels of section headers at all. #* On the Observatory site, the menu calls this “Heading” (don’t confuse this with “Sub-heading 1,” which is actually H2, below!). #H2 is the second-highest level of an Article’s sections. Use medium to sparingly. #*Use: If you have subsections within H1 that need to appear in the TOC. (If it shouldn’t go in the TOC, just format the text as bold rather than using H2.) #*TOC appearance: It appears one indentation to the right of H1. #*On the Observatory site, the menu calls this “Sub-heading 1.” #H3 is the third-highest level of an Article’s sections. Use sparingly. #*Use: If you have subsections within H2 that need to appear in the TOC. (If it shouldn’t go in the TOC, just format the text as bold rather than using H3.) #*TOC appearance: It appears one indentation to the right of H2 (at this point, things start to become indented so deeply that the TOC sidebar is going to be hard to read—that’s why our developer advises against using H3–H5, and the Observatory does not allow H6). #*On the Observatory site, the menu calls this “Sub-heading 2.” #<span style="color:#FF0000;">H4 is the fourth-highest level of an Article’s sections (one level deeper than H3). Don’t use</span>. Rather, just use the formatting you need to (bold, list, etc.) rather than formatting as a heading/subheading. #<span style="color:#FF0000;">H5 is the fifth-highest level of an Article’s sections (one level deeper than H4). Don’t use</span>. Rather, just use the formatting you need to (bold, list, etc.) rather than formatting as a heading/subheading. #<span style="color:#FF0000;">H6 has no way to render on the Observatory at all. Don’t use</span>. #<span style="color:#FF0000;">H7 is what MediaWiki calls “Preformatted” for coding purposes. Don’t use</span>. #H8 is MediaWiki’s default way to style block quotes (we use “blockquote” [adj.] and “block quote” [n.]; note that they add a space per the noun styling, calling it “Block quote” in the dropdown Header menu selection on top of text fields). This renders as a body paragraph that is indented on both the left and right sides. #*Use: This is for quotations that are at least three lines long that should appear in their own separate paragraph(s). #*Does not appear in the TOC. ====== Double-check links in Article Drafts====== Always test your links and fix any broken ones before finalizing any page Draft. Ask your editor for help if needed. ''(See: [[Project:Observatory Users Manual#Links|“Links” in the Glossary]].)'' One common issue with links is if you accidentally used internal links instead of external links (easy to do, especially if you copy-pasted without converting to wikitext first). If when you click a link in an Article Draft, the result is a prompt to create a new page on the Observatory or an error message, that usually means it was accidentally formatted as an internal instead of an external link. Pay attention to if you used the single bracket <span style="color:#e83e8c;">[</span> (for external links; which you use for most links) versus double bracket <span style="color:#e83e8c;">[[</span> (internal links, only for pages on the Observatory or Wikipedia and its project sites) in “Source edit” mode, or click the link in “Visual edit” mode and see if it’s toggled to the wrong kind of link (internal when it should be external) and then change it to external and fix the URL to the desired result (you will probably have to remove '''<nowiki>https://observatory.wiki/</nowiki>''' and add in '''<nowiki>https://www</nowiki>.''' depending on what the original link was; make sure you copy from the URL bar for the correct page, since that’s easier than removing and replacing part of a URL—and '''always test the result again after you’ve clicked to Save that new link'''. Note: This also applies to any text field in any namespace, not just Article pages but also in Guide pages, Author pages, Source pages, Classic pages, Area pages, and more. ====== Footnotes, Citations, and Links ====== Here are the best practices for footnotes (whether notes or bibliographic citations) in your Article’s Google Document/Word Document. Once you convert the document into wikitext and upload it to the Observatory, these references will become endnotes. You can insert a footnote by using the “Cite” button (the open-quotation mark icon) in the top ribbon of the Edit text field. In your Google Doc or word processor file, use internal links to sources the same way you would with syndicated Articles if you do not want them to appear as endnotes/footnotes/references. However, we usually want as much of the research you did to appear as references/footnotes at the end of the Observatory Article, so it’s recommended to both use internal links over text to cite sources available online and also to format your links as MLA-style endnotes/footnotes inside the Google Doc/Word Doc prior to conversion. Check the [[Project:Style Guide#Links and Footnotes|Observatory Style Guide]] for more information about citations. In Google Docs: #Put your mouse in the Article document where you want to insert your footnote, then click to keep your cursor there (it should remain blinking). #In the top menu bar, click '''Insert''' and then pick '''Footnote'''. (You can also use the hotkey command+option+f on a Mac). #A number will appear where your cursor was in the body text, and a line will appear at the bottom of the page where you can insert and edit your footnote text. #Google Docs will automatically number your footnotes correctly if you have more than one. The Pandoc/workflow conversion from .docx/.odt files into MediaWiki text files will automatically treat the endnotes/footnotes as references. You may find it’s best to code these using the Visual Editor after upload for new Articles ''(see section: [[Project:Observatory Users Manual#Insert references via Visual Editing (recommended)|Insert references via Visual Editing (recommended)]] for instructions)''. === Changing the title of an Article (URL and/or Headline) === It is inadvisable to retitle an Article after it has gone through editing, so make sure to suggest the final title when you request the Article to be started. If your title change is approved by your editor, your editor will change the page title and Move the page. The URL may not be able to be altered (aka the page may not be able to be moved), especially if the page was already Published. This applies to Articles, Guides, Sources, and all other page types. === Formatting Article body text/content on the Observatory site === ==== Paragraph breaks ==== Hit the “enter”/“return” button twice in “Edit” (“Visual editing”) mode to insert a line break. This also works to end block-quote formatting and bulleted/numbered list formatting. ==== Table of contents (“Sections” tab on Article pages) ==== By default, Articles with headings in the body will display a table of contents (TOC) in the left sidebar under the “Sections” tab. Check that your headings were formatted correctly in the Article body if you notice any errors in the hierarchy or titles in the TOC; update in the body if necessary, and upon Saving and refreshing, the TOC will reflect your changes. Your editor is able to customize and turn the TOC on or off on an Article, but it is rare to do so. ==== Footnote references (external citations/notes) ==== Similar to how Wikipedia includes external citations as footnotes, the Observatory aims to thoroughly cite authoritative sources using endnotes/footnotes in MLA bibliographic style (check the [[Project:Style Guide#Links and Footnotes|Observatory Style Guide]] for more thorough guidance)—in other words, not only using internal citations in the form of external links in the Article body the way many news sites do, but also using external links in the Article body as well as footnote citations. Many of the sources in your Articles may be hyperlinks rather than printed sources, and that is acceptable. ===== Insert references via Visual Editor (recommended) ===== #Click where you want to insert a footnote superscript bracketed numeral antecedent/reference in the Article body (usually after terminal punctuation [period or close quotation mark] in the relevant sentence, or after the relevant first phrase if there are multiple citations in one sentence). #Click the “Cite” button (the open-quotation mark icon). #Click “Basic.” #Type in the text and format as you would with an Article body. #*The A icon offers special formatting options including bold and italic. #*Carefully select any text that is supposed to be formatted as a link, then click the link/chain icon. Insert the full canonical URL that should go over that selected text. Make sure you are careful about internal and external links, as with links in the Article body. #Click the top blue “Insert” button when you’re done entering and formatting your footnote to add it to the Article body. #If you need to change something in the footnote after you Save it, you can click the superscript bracketed numeral, then click the “Edit” button to open the footnote text box again. Make your changes and then click the blue “Insert” button to Save them. #*If you have advanced formatting needs you can’t adjust using the pop-up box in “Visual editing” mode, use “Source editing” mode or ask your editor for help. #As with the rest of the body text, changes to the footnotes don’t Save until you hit the blue “Save changes…” button at the top right of the Visual Editor for the Article page. ===== Insert references via Source editing/coding (advanced) ===== Alternatively to the easy Visual Editor, you could use Source Editor and use <span style="color:#e83e8c;"><nowiki><ref></nowiki></span><nowiki>[Linked|Citation]</nowiki> text here.<span style="color:#e83e8c;"><nowiki></ref></nowiki></span> tags in the Article body. To code an endnote/footnote to appear at the bottom of an Article, the source code to insert into the Article body where you want your number reference to go is: :'''<nowiki><ref></nowiki>'''Author Name, ''Book Title'', (City: Publisher, YYYY), p–p.'''<nowiki></ref></nowiki>''' This will insert a numbered endnote formatted, like this (different text than the above is used below for illustration):<blockquote>1. Jane Doe, ''The Book Title'', (New York: Publisher Name, 2019), pp. 2–24.</blockquote>''(See the [[Project:Style Guide#Links and Footnotes for Observatory Articles/Dual Pub Plan|Observatory Style Guide]] for further guidance on footnote citations.)'' It’s easier to use “Visual editing” mode and start typing <nowiki><ref> where you want your number to go in your body, and then a pop-up will appear where you can format the note, group it with other notes of different sections, etc.</nowiki> Check your endnote formatting before Publishing. For more advanced help on notes, see: https://www.mediawiki.org/wiki/Help:Cite. ===== Repeating footnotes: Cite→Re-Use ===== You don’t have to repeat the same footnote text more than once (you don’t even need to write “ibid”!). If you want to cite the same footnote more than once throughout an Article body, you may. After you have entered the text with all its footnotes, make a note of which footnotes are supposed to match. Then in the Observatory Draft, delete the second numbered reference. Move your cursor to the part of the Article body where your second footnote reference is supposed to go and click the “Cite” button (the open-quotation mark icon). Then click “Re-Use.” Then select the first footnote you want to re-use and they should connect. For example, see Footnote #7 in this Article: [[Why Charter Schools Open Where They Do—And Why That’s a Problem#cite ref-:0 7-1|https://observatory.wiki/Why_Charter_Schools_Open_Where_They_Do%E2%80%94And_Why_That%E2%80%99s_a_Problem]]. === LanguageTool: SpellCheck browser extension for proofreading/editing the text of an Article or your Author page on the Observatory === Most of us are used to an automatic live SpellCheck software (such as that in Microsoft Word, Google Documents, Grammarly, etc.). If you use software like Grammarly, you might notice that it does not work in the Observatory. You will need to download the compatible browser extension for the Observatory to see suggested corrections in live time. This is '''strongly''' recommended before working on your first Article or your Author page copy to make sure your copy is typo-free. The SpellCheck software for the Observatory is called '''LanguageTool'''. It is available for free. Here’s how to get it. ==== Instructions: How to install LanguageTool ==== ===== Software ===== Download the plugin for your browser from the link below that corresponds to the browser you use for editing on the Observatory: # [https://chromewebstore.google.com/detail/ai-grammar-checker-paraph/oldceeleldhonbafppcapldpdifcinji?utm_source=lt-homepage&utm_medium=referral Chrome] # [https://microsoftedge.microsoft.com/addons/detail/hfjadhjooeceemgojogkhlppanjkbobc Microsoft Edge] # [https://addons.mozilla.org/firefox/addon/languagetool/ Mozilla Firefox] # [https://apps.apple.com/app/id1534275760 Safari] # [https://addons.opera.com/extensions/details/grammar-and-spell-checker-languagetool/ Opera] It will appear in your extensions as LT (Language Tool). Use the Free version, not the Pro version. Do '''''not''''' create an account. (Note: If you do accidentally create an account, you won’t be able to set the extension server settings below [they will be grayed out]; if so, select “Log out of your LT account” in the browser extension Settings; after that, you will be able to set <nowiki>https://apply.observatory.wiki/v2</nowiki> in a field in the “LanguageTool server” section.) ===== Set the extension settings to add the Observatory as the server ===== In the plugin/extensions preferences (if you click the LT icon in your browser, you should see a Settings icon gear wheel to click), navigate to '''Advanced settings (only for professional users)''' (at the bottom). Specify the Observatory LanguageTool server by: # going to the field “LanguageTool server:” # then selecting the radio button for “Other server—requires LanguageTool server running there” # and then typing <code><nowiki>https://apply.observatory.wiki/v2</nowiki></code> # and finally, clicking “Save.” One last setup step (or thing to check is left as the default): Leave the field “'''Autocheck on all domains'''” checkbox in the checked position. ===== How to Review Suggestions by LanguageTool in the Observatory ===== As you review suggestions, you can choose to accept or ignore the suggested corrections. If you encounter an issue that you expect to come up again, you can choose to add the word to your personal dictionary. [[File:LanguageTools popup add to dictionary, catios.png|none|thumb|650x650px]] You can also access the list of suggestions in a sidebar, rather than one pop-up at a time. [[File:LanguageTools sidebar.png|none|thumb|650x650px]] You can customize your settings by clicking the LT icon in your browser and adjust for pickiness: [[File:LanguageTools customize extension settings.png|none|thumb|650x650px]] === Insert images and media === Follow the [[Project:Style Guide/Images and Multimedia Files: Rights and Practical Considerations|Observatory Style Guide Images and Multimedia Files: Rights and Considerations]] guidance and recommendations about using Wikimedia Commons for images and other media. Work with your editor to insert images and other media. ==== Slideshows, quizzes, audio files, video files, etc.: adding special kinds of content templates into Articles ==== To insert special content, there are templates your editor can insert into an existing Article/Guide for a slideshow, quiz, audio, video, etc. Ask your editor for help with templates. === Collaborative Research: How to add Info pages (aka Talk pages) soliciting feedback or offering queries to the public === ==== About Collaborative Research/Mainframes ==== [[Project:Types of Content#Collaborative Research and Mainframes|Collaborative Research]] is an open-ended investigatory tool that allows multiple contributors to explore a topic, deciding what to share with the public through a peer research and editorial oversight process. Unlike Articles or Guides that don’t use this feature, Collaborative Research pages give interested audiences access to text with ongoing queries—the work in progress is part of the point. A related content type, the [[Project:Types of Content#Collaborative Research and Mainframes|Mainframe]], is a knowledge-gathering project designed to be expanded by future scholars and researchers, building on the original Author’s line of inquiry and methods while broadening its scope. The Info/Talk page tools described in this section apply to both content types. ==== About Info or Talk pages ==== You or your editor/an administrator can insert an Info/Talk page on any Article, Guide, chapter/Recipe subpage, or other page to post a public subpage called an Info page that prompts readers to consider contributing helpful information to improve or update the text. The Article/Guide/chapter/Recipe page (main page) will display a pencil icon. When hovered-over, an Info page pop-up appears that displays: * a linked '''Pop-Up Heading''' summarizing the query that, when clicked, opens the individual Info page ** a right-facing '''arrow''' to the right of the pop-up title also links to open the individual Info page * a text '''Prompt''' that explains the query in more detail than the Pop-Up Heading (but less detail than the individual Info page) * an “'''Open'''” link at the bottom left that also opens the individual Info page * an “'''Edit'''” link to the right of the Open link that opens the query’s “Edit with form” page (this appears only on the Editorial site, and not on the Public site) * a “'''See All Queries'''” link at the bottom right of the pop-up to view the All Queries page (a list or report of all Info pages related to the Article/main page) The Info pages related to each Article/main page are numbered in the All Queries page/Talks report. These numbers are in order of how they appear on the main page, excluding repeated Info pages, and the numbers are dynamic (they will change if the Info page icons are added or removed). They only appear on the Public site Talks report page list when their contents are created and Saved, so an empty placeholder won’t appear even if on the Editorial site it looks like there is a pencil icon there (if the pencil icon is red and says “'''Create'''” at bottom right, it won’t appear on the Talks report). If no Info page was created for a pop-up icon, nothing appears on the Article/main page to the public on the Public site. You will want to quote relevant text from the Article/main page on the Info page for context since the page opens anew and the context is useful. In the Info page, use the Quoted Text field in the form. ===== Info page Glossary ===== # Info/Talk pop-up icon = Edit Icon = pencil icon on the Article/main page # Info/Talk page = Edit Note = Query = individual Info/Talk page item resulting from clicking “Open” on the Edit Icon # Talks report = Full Edits Talk page = Queries = “See All Queries”/the All Queries page aka full discussion collecting all Info/Talk page items related to the Article/main page ===== About Info or Talk page pop-up icons’ reactivity and color coding ===== About the pencil icons: ====== Reactivity ====== The Info/Talk page pop-up '''appears''' on “mouse enter” of the pencil icon on an Article/main page: * hover-over/mouse-over of the icon * left-click of the icon The Info/Talk page pop-up '''will not disappear''' on: * cursor leaving the pop-up * right-mouse button click (control+click on Macs) The Info/Talk page pop-up '''will disappear''' on: * left-mouse button click of the x button in the pop-up * page scroll * hovering over another pencil icon ====== Color-coding and Visual Hints ====== Editorial site color-coding of the pencil icon: * red: the Info page with this UUID doesn’t exist * black: existing Info page * green: the most recently visited Info page (e.g., to easily find the icon when one returns from the Info page to the host page via the “Return to the host page” button); this only works if you did not open the Info page in a new tab (it has to have been the same tab) Public site color-coding of the pencil icon: * hidden: the Info page with this UUID doesn’t exist * black: existing Info page * green: the most recently visited Info page Visual Hints: If a main page has Info page pop-ups that are not created, not only will the pop-up icons be red, but that page also will have a red error message at the top until the Info pages on the main page have all been created:<blockquote>Unfinished pop-ups!</blockquote><blockquote> Talk page pop-ups exist that lack the creation of their corresponding Talk pages on this page.</blockquote> [[File:Visual Hint Unfinished Pop-Ups Info Pages Collaborative Research.png|none|thumb|650x650px]] Note that the error message only appears after the page is refreshed after being Saved with the uncreated Info page pop-ups. (An unrefreshed page with uncreated Info pages will not display the error message until it is refreshed.) ==== How to create and manage an Info or Talk page ==== Here’s how to create an Info page (aka a Talk page) for Collaborative Research Articles and other content. This is a note to the public soliciting their input for a query on the text of an Article or other content. You will insert a placeholder first and fill it in immediately after. ===== How to insert an Info or Talk page into an Article or other main page content ===== ====== Insert a blank placeholder pop-up icon in the Article ====== # In the Article/main page you’re editing’s Edit mode (Visual editing, not Source editing), put your cursor in the exact placement in the text where you want to insert the pencil icon and click. # Click '''the Comment icon''' (a speech bubble with a plus sign inside) in the Edit top toolbar of the Visual Editor to insert a pencil icon where your cursor was left in the text. # Click the blue '''Save changes''' button on the page. #* You now have a placeholder with an empty pencil icon to fill out. It will appear red until you create an Info page for it (and won’t appear on a Public site page if left unfinished); after you create a page for it, it will turn black. # '''Refresh''' your browser on the page (this is the easy solution if nothing happens when you click the icon in the next step). # Go to the spot where the new red pencil icon is and hover over it. Click “'''Create'''” in the bottom left of the pop-up. ====== Create the Info or Talk page connected to the placeholder pop-up icon ====== Fill in the Info page form fields: # '''Pop-Up Heading''' #* This will appear as both the title of the Info page and the header in the top blue part of the pop-up on the Article page. #* You can either select something preexisting from the dropdown menu (recommended; many Pop-Up Headings already exist), or create a new one that will be both used in your case and added as a dropdown option for others to use. This field works like the Tags field on Articles with typing and a dropdown menu, except that you can only have one selection in the field. #*# You can start '''looking through preexisting options''' in one of two ways: #*## Click in the text box and '''scroll through preexisting options alphabetically'''. This is unwieldy if you have a good keyword instead, but this will give you a general sense of preexisting options to choose from. #*## Start '''typing a keyword''' that would be in the Pop-Up Heading in the text box (such as Citation, Fact-Check, Illustration, Map, Add a Section…). #*# '''Click on the preexisting option that applies to your query in the dropdown menu.''' It will appear in the text box as a gray-background button. If you change your mind, replace it by clicking the x on the left side of the button (or clicking in the field, selecting all, and backspacing) and repeat the steps above to find something fitting. #*# If no preexisting option applies to your query, you can '''create a new option''' by typing it in exactly as it should appear in the pop-up, and then clicking the new dropdown option directly below the text field. Note that your new Pop-Up Heading option will be available to you and all other Users after you Save the Info page. #*#* Follow the rules of preexisting options: look at other Pop-Up Headings and follow their lead. Keep your new Pop-Up Heading short, and use [[Project:Style Guide/Editorial Process#Headline-Style Capitalization|headline-style capitalization and punctuation]]. (Unlike for Headlines, no verb is required for Pop-Up Headings.) #*# After you’re done typing, '''click the dropdown menu item''' or hit enter; otherwise, your Pop-Up Heading will be lost if you click outside the field after typing something in, and the vague default (“Collaborative Research”) will be inserted instead. #* If you leave this field blank before Saving the Info page form, the vague default (“Collaborative Research”) will be inserted instead. If you see “Collaborative Research” as the Pop-Up Heading/Info page title later, you can always go back in and Edit the Info page form to add the Pop-Up Heading later. You might want to search for “Collaborative Research” on a page’s See All Queries page to find accidentally blank Pop-Up Heading fields to fill in. # '''Prompt Type''' ## This controls the text that appears in the white part/body text of the pop-up. It will not appear on the Info page. Keep it short (one or two short sentences). '''Think of it as a pop-up subheading.''' ## Choose from Manual or Predefined using the radio buttons. ### '''Manual:''' Select Manual, and then type your desired text into the text box that appears. You can use the Visual Editor if you want to include links or bold or italic formatting. ###* Remember: it’s a pop-up, so it should be short! You can put more detail in the Talk field. ###* '''Type in your Manual Prompt below:''' Summarize the Talk field (the full query text) in one or two short sentences here. If your Talk field contents above the <nowiki>{{CollabPost}}</nowiki>} template are short, you may copy them here, adapting the text for the context of only being visible in the pop-up on the Article page if necessary. For example: ###** Strip links, especially internal links to the Article page. It is recommended not to include any links in this field, or to keep them limited, in order to encourage researchers to open the query through the emphasized links of the Pop-Up Heading, right-facing arrow, or Open link. ###** Do not include any templates in this field (for example, <nowiki>{{CollabPost}}</nowiki> templates). ### '''Predefined:''' Click inside the dropdown text field that appears after selecting Predefined, below the text “Click to choose from the Predefined text options (hover to preview at right).” The available options will appear in the dropdown menu. Scroll through and hover over each one to see a preview at right of what will appear for each. If you pick one and want to preview others, click the x button or delete everything in the field and hover over the options (you may type to search). # '''Quoted Text (this is a fragment of the original content for discussion; it is optional)''' #* This is where you might copy-paste text from the Article page near the pop-up icon that’s relevant to the query. It has Visual Editor built in that should allow copy-pasting normally even with rich text like links and italics, but if there are more complicated rich text elements such as section headings and footnotes, you can copy the source code from the Article (we recommend changing Info page tags <nowiki>{{i|</nowiki><span style="color:#e83e8c;">UUID</span><nowiki>}}</nowiki> into interquery links <nowiki>[[Info:</nowiki><span style="color:#e83e8c;">UUID|visible text</span><nowiki>]]</nowiki> if any appear in your selection) and paste it into this form field in code mode. # '''Talk''' ## This is where we put more information about what we are soliciting feedback about. You can use the Visual Editor for this field. It becomes the body of the Info page, so it can be as long and complex as you want. ##* One example of an Illustration Query that is a good sample to recreate is [[Info:5ec6f361-e25e-47ce-943d-cebf8c3d617d|this one]]. Note the use of interquery links <nowiki>[[Info:</nowiki><span style="color:#e83e8c;">UUID|visible text</span><nowiki>]]</nowiki><nowiki> rather than pop-ups {{i|</nowiki><span style="color:#e83e8c;">UUID</span><nowiki>}} on an Info page.</nowiki> ##* Remember, the Prompt field will not appear on the Info page (only the pop-up), so it is very common to repeat what was in the Prompt field here if you want the same text to appear in the pop-up as on the Info page. ## '''CollabPost''' (Info page button for Contact form) ### Every Info page needs to add the <nowiki>{{CollabPost}}</nowiki> template at the bottom (information on including more than one is explained with the following two asterisks*). This inserts a green-background ribbon with text and a button leading readers to a Contact page form to answer the question asked on that specific Info page. ### '''To insert a CollabPost template into the Info page Talk field:''' #### Add a line break at the bottom of your Text field below the normal text. Click your cursor at the end where you want to insert the CollabPost line. #### In the Visual Editor ribbon at the bottom of this field, click the '''envelope icon''' at right (two to the right of the “Cite” button or open-quotation mark icon). If you hover over it, it says “Collaborator form.” #### The default CollabPost template text and button text will be inserted. #### If you’d like to change the text to '''customize''' to your query: ##### Click anywhere in the green text/button part of the Talk field for a pop-up to appear. ##### Click the '''“Edit”''' button to open the template pop-up. ##### '''Filling in CollabPost template fields:''' ###### The defaults are generally fine, but if you make customizations, click “'''Apply changes'''” in the CollabPost template pop-up after making changes to any of the following three CollabPost template fields ('''Button text''', '''Prompt text''', and/or '''Hashtag'''). Then Save the page. ###### If you want to customize the button text, edit what is in the '''Button text''' field. ######* The default button (including if you remove all text here or never alter it) is to show “'''Reply'''” with an '''arrow'''. ###### If you want to customize the green text at left, edit what is in the '''Prompt text''' field. ######* The default green text (including if you remove all text here or never alter it) is: “'''Suggest an edit or addition for this query. Join the research!'''” ###### *'''Hashtag''' field (checkmark at left in the CollabPost template menu) is optional to check or change: ######* Do this only if you are using multiple CollabPosts on the same page or have some other reason to mark emails filled out via this form with your specific query: ######*# Check the Hashtag checkbox at left to indicate you will use it (uncheck it if you change your mind later). ######*# Fill in the newly appeared Hashtag field with a keyword/keywords (without spaces, punctuation, or special characters including #). (The default is “'''collaborativeresearch'''.”) ######* Note that Hashtags are visible to the public in the Collaborative Research Contact form (as readonly). ######* A Hashtag is a tool for Authors and editors to recognize the source of a query that led a reader to fill in the form. Imagine you have two occurrences of the CollabPost on the same page and need to know which one triggered the post. You can assign ''a'' to one occurrence and ''b'' to the other, making it easy to tell them apart when you receive an answer (you probably want to be specific and use keywords instead of letters). The Hashtag field is not suggested by default when using the “Insert”→“Template” menu in Visual Editor. You can simply leave it out if there is only one CollabPost on the page, or if the context that triggered the post is not important to you. ###You can insert multiple* CollabPost templates per Info page if you have more than one query on the page and want people to have more than one Contact form about each; see “Hashtag field” above if you insert more than one. ###You can always '''edit''' the contents of a CollabPost by editing the page (via “Edit with form” mode), then clicking anywhere in the green ribbon so “Template” pop-up appears, then clicking the “'''Edit'''” button. # '''Save page''' ## Save your newly created Info page. ##* or: use the “Cancel” button to cancel your edits (this is only if you want to abandon your changes). ##** Note that if you click the “Cancel” button next to the “Save” button to abandon your edits, if nothing happens, that’s because you opened in a new tab and your browser doesn’t know what page to open with a “Back” button. Simply close the tab if you wish to cancel/abandon your edits in this case. # You will '''automatically be redirected to the Info page you just created''', and on the Article page where the pencil icon appears, this pencil icon will automatically be updated to display as black instead of red, indicating it now links to your newly created Info page! #* '''Refresh''' the Article page in your browser if the pop-up does not appear when you hover over the pencil icon (this is normal). You may need to use a keyboard shortcut for a hard refresh (ignoring the cache) rather than the browser refresh button for a soft refresh if refreshing multiple times does nothing. Keyboard shortcuts for hard refreshes are: #*# Mac: command+shift+r #*# PC: control+shift+r (OR control+F5) ===== How to edit the contents of an Info or Talk page ===== # You can go back in and edit the page if necessary at any time. #* From the Article page: Click either “Open” or “Edit” in the bottom left of the pencil icon pop-up when viewing the Article page. #* From the Talks report (“'''See All Queries'''”/the All Queries page) for any Article: #*# Click “'''[open]'''” at right of any Info page item in the list to open its individual Info page. #*# Click “Edit with form.” #*#* When editing an Info page, usually you need “Edit with form” (especially if what you want to change is in the pencil icon pop-up text); use “Edit” or “Edit source” only for Info page edits requiring advanced code (such as to replace links). #*#* In “Edit” and “Edit source” mode, please ignore/do not touch the Widget part of things that seems locked (those are better edited in the form)—just edit what’s in the text below the close–double curly brackets <span style="color:#e83e8c;"><nowiki>}}</nowiki></span>. ===== How to change the UUID of the Info or Talk page referenced in the Article body ===== If you need to change which Info page is linked to in a pop-up on the Article page… # Open the Info page you want to replace the current one with. ## Click the gray “'''Copy UUID'''” button. ## A pop-up should appear confirming successful copying to your clipboard: “UUID copied to clipboard!” ## Click “'''OK'''” to close the pop-up. # Open the Article page, click “Edit” to unlock “Visual Editing,” and then click on the pencil icon whose referenced Info page you want to change. # A pop-up should appear that says “Template” and “Generated from: I.” # Click the “'''Edit'''” button at the top right of this pop-up. # In the '''field “UUID”''' delete the text that was there before (the old Info page UUID referenced) and paste in what was copied to your clipboard (the Info page UUID you want to change to). # Click “'''Apply changes'''” at top right. # Click “'''Save changes'''” on the Article page. # '''Refresh''' your browser tab. # The Info page pop-up should now link to the Info page you desire. ===== Deleting an Info or Talk page ===== If you need to delete an Info page that you abandoned and that should not be Published, ask an administrator. Send them the link to the old Info page and tell them that you’ve replaced it and that it should be deleted. (Before you do this, double-check you or others haven’t used it elsewhere! If you aren’t sure of this, ask your editor/administrator to check before they delete it.) It may be automatically Pushed if this is not done before the Article affiliated with the Info page is Published. ===== How to create an All Queries page ===== Once you have inserted all Info pop-up icon placeholders on the Article page or chapter subpage, you are ready to create the All Queries page. (You don’t need to fill in the Info page form fields yet.) # On the Article page, hover over any Info pop-up icon. (If nothing happens, try a hard-refresh.) # Click “See All Queries” at the bottom right of the pop-up. A new All Queries page Draft will open in a new tab. #* All Info page UUIDs on the Article page are automatically copied to your clipboard. (To verify: paste into TextEdit or Notes—you should see a series of 32-character alphanumeric strings.) #* Use a normal left-click; right-clicking to open in a new tab may not copy the UUIDs. # Click “create this page” to open “Source editing” mode in a new tab. # Paste the UUIDs from your clipboard below <span style="color:#e83e8c;"><nowiki>{{Queries|<!-- insert info uuids below --></nowiki></span> and above the closing <span style="color:#e83e8c;"><nowiki>}}</nowiki></span>. # Click “Save page.” #* The page will reload. The new URL (Queries:page UUID) is where queries for the Article will appear. # After creating Info pages, hard-refresh the All Queries page to see Info pages with completed forms populate. #* Uncreated Info pages will appear as errors on the Editorial site and will not appear on the Public site until they are created (and Pushed by an administrator). Notes about what appears on All Queries pages: * Info page form contents that appear on individual Info pages (as opposed to in Info pop-ups) are the same on All Queries pages: ** Pop-Up Heading ** Quoted Text (if any) ** Talk ** (Note: Prompt field contents do ''not'' appear on All Queries pages.) * On All Queries pages, footnotes do not all appear at the bottom; instead, each footnote pops up only when a footnote numeral is clicked (see: [[Project:Observatory Users Manual#Pop-up bibliographical footnotes on All Queries pages: Copy-paste trick|Pop-up bibliographical footnotes on All Queries pages: Copy-paste trick]]). ====== Keep All Queries pages updated after edits to Info pages ====== If you add, delete, or replace Info pop-up icons on an Article page or chapter subpage that already has an All Queries page, you must manually update the UUIDs on that All Queries page—they won’t update automatically. # On the edited Article, hover over any Info page pop-up. (Hard-refresh if nothing happens.) # Click “See All Queries” at the bottom right of the pop-up. The current Info page UUIDs are automatically copied to your clipboard. # On the All Queries page, click “Edit source.” # Replace the old UUIDs with the updated UUIDs from your clipboard, below <span style="color:#e83e8c;"><nowiki>{{Queries|<!-- insert info uuids below --></nowiki></span> and above the closing <span style="color:#e83e8c;"><nowiki>}}</nowiki></span>. # Click “Save page.” # Check that the expected updates are reflected on the All Queries page. ====== About repeated Info pages: Multiple uses of the same UUID ====== '''Re-using UUIDs within a single Article''' You may re-use an Info page UUID multiple times within an Article; for example, using the same UUID in a footnote citation, an in-text citation, and a bibliography section of the body text. If any instance requires unique content, use a different UUID and copy the relevant form field content. You can link between two Info pages so editors can check related entries together. Note: If the same UUID appears multiple times on an Article page, only the first instance will appear on the All Queries page. (Two separate UUIDs with the same or similar content are a different case—both will appear.) '''How to re-use Info page IDs within a single Article''' # Open the Info page you want to re-use and copy its UUID (everything after Info: in the URL). # Open the Article/chapter in “Edit” mode. # Insert an Info page placeholder in the usual way. # Click on the pencil icon. # Click the “Edit” button in the pop-up. # Replace the UUID in the form. # Click “Apply changes.” # Save the page. '''Don’t re-use UUIDs across multiple Articles or chapters''' We recommend '''not re-using the same UUID across multiple Article pages or chapter subpages'''. Because an individual Info page’s “Return to the Host Page” button links only to the page where the Info page was originally created, it won’t navigate back correctly. (For example, if an Info page is created in Chapter 2 and then re-used in Chapter 3, its “Return to the Host Page” button will always go to Chapter 2, even if it was accessed from Chapter 3.) Instead, create new Info page placeholders with separate UUIDs and copy the relevant form field content into each. You can link between related Info pages so editors can check them together. ===== Pop-up bibliographical footnotes on All Queries pages: Copy-paste trick ===== Footnotes (bibliographical footnotes or other kinds of notes in footnotes) on “See All Queries”/All Queries pages work differently than on other kinds of pages: they open as pop-ups at the bottom of the page instead of triggering a jump page anchor link to an all-footnotes space (there is no all-footnotes space at the bottom of an All Queries page). This needs to happen for All Queries pages so that the various fields in individual Info pages displayed there don’t trigger <span style="color:#e83e8c;"><nowiki><references /></nowiki></span> that conflict with the numbered order of footnotes at the bottom of a page. If you need to copy text from a pop-up footnote on an All Queries page, here’s how: On a Mac: # Click the footnote. # Select the text, but before lifting your finger off the mouse at the end of your selection, add the control key (control+click over your selected text). # A context menu should appear with the option to “Copy”; click “Copy.” On a PC: # Click the footnote. # Highlight the text. The text will automatically be copied. # To paste, use a middle click. ===== How to batch-Push Info or Talk pages, or All Queries pages, associated with any page (such as Collaborative Research Articles) ===== Since the Editorial and Public sites are separated, your editor has to Push Info pages and All Queries pages in a new Collaborative Research Article or other page with Info pages to make the Info pages Published or to make updates appear on the Public site. If you don’t see the Info pop-ups or pages you expect to on the Public site, kindly remind your editor they need to Push the Info page(s) as well. (In case they need further reminding, they have a “'''Copy Info pages for Pushing'''” dropdown item in their top menu “Admin” button to do it in a batch.) ===== Custom TOCs on Article pages: How to customize the table of contents in the sidebar ===== On Article pages/chapter subpages, you might want to add a line to the top of the sidebar’s TOC to point people to an All Queries page or an anchored link. The <nowiki>{{Custom TOC}}</nowiki> template adds special navigation links to the top of the Contents tab in the sidebar, above the section headings in the table of contents. A common use is to add links to All Queries or General Queries pages for any Article/page or chapter/subpage. For example, [[The Creation of Order/Summer: Balancing Self-Expression With Group Order/4. Alphanumeric Notation and the Calendrical-Musical Kosmos|here in Chapter 4 of ''The Creation of Order'']], click the “Contents” tab in the sidebar to see the custom TOC links (under “Click on the following links to”) to jump to the Key Concepts part of the chapter page (“jump to a glossary of key concepts for this chapter”) or to open the All Queries or General Queries pages. [[File:Custom TOC.png|alt=a screenshot showing a two-tab interface (Author / Contents), with the Contents tab active. It lists three clickable links: 1. Jump to a glossary of key concepts for this chapter 2. See general queries for this chapter, including its stub nature and possible areas of expansion, bibliographical notes, and illustration notes 3. See all other queries for this chapter|none|thumb|650x650px]] To add a custom TOC, open the Article or chapter subpage in “Source editing” mode. Add the template at the top of the page: :<nowiki>{{Custom TOC|[[</nowiki><span style="color:#e83e8c;">Page title goes here</span><nowiki>|</nowiki><span style="color:#e83e8c;"><nowiki>Text you want to display goes here.</nowiki></span><nowiki>]]}}</nowiki> If you are linking to a Queries page, you would include the Queries: namespace before the UUID: :<nowiki>{{Custom TOC|[[Queries:</nowiki><span style="color:#e83e8c;"><nowiki>UUID goes here</nowiki></span><nowiki>|</nowiki><span style="color:#e83e8c;"><nowiki>Click here to see all queries for this chapter.</nowiki></span><nowiki>]]}}</nowiki> As with anywhere on the Observatory where you’d use a page title as an internal link: * Include the namespace with a colon before the page title for any page outside the Mainspace (i.e., not an Article, Author, Source, or Guide), such as Classics, Project, Queries, Info, or Recipe pages. * Include the path if it is a subpage (for example, a link to [[The Creation of Order/Summer: Balancing Self-Expression With Group Order/5. Music, Temperament, and Social Concord|Chapter 5 of ''The Creation of Order'']] would look like this: <span style="color:#e83e8c;"><nowiki>{{Custom TOC|[[The Creation of Order/Summer: Balancing Self-Expression With Group Order/5. Music, Temperament, and Social Concord|Click here to open Chapter 5.]]}}</nowiki></span>). If you are linking to multiple pages in the custom TOC, you can add numbered or unnumbered bullet points and line breaks in between the <span style="color:#e83e8c;"><nowiki>{{Custom TOC|</nowiki></span> and the closing curly brackets <span style="color:#e83e8c;"><nowiki>}}</nowiki></span>; here is an example of a numbered list: :<nowiki>{{Custom TOC|Click on the following links to:</nowiki> :<nowiki># [[The Creation of Order/Summer: Balancing Self-Expression With Group Order/4. Alphanumeric Notation and the Calendrical-Musical Kosmos#Key Concepts|jump to a glossary of key concepts for this chapter]]</nowiki> :# <nowiki>[[Queries:5188|see general queries for this chapter, including its stub nature and possible opportunities for expansion, bibliographical notes, and illustration notes]]</nowiki> :<nowiki># [[Queries:4035|see all other queries for this chapter]]}}</nowiki> === How to enter a Classics Article (public domain content; rare case) === ==== Starting a Classics Article ==== On your User dashboard, click the light blue button that says “CREATE CLASSICS ARTICLE.” You will be redirected to a [[Special:Contact/requestclassics|Classics Article request form]]. Alternatively, you can ask your editor via email to start a Classics Article page for you, including information via email (preferred) or [[Special:Contact/requestclassics|request form]]. (If your Classics book has subpages/chapters, please email your editor the desired book TOC with hierarchy indicated in a numbered list like an outline or with H1, H2, H3 spelled out in text.) Ask them to send you the link to work on. When you’re done editing your Classics Article Draft, email them to let them know it’s ready for their review. Your editor will then review it and either give you feedback for revisions or publish it.
Summary:
Please note that all contributions to The Observatory may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Project:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Project page
Discussion
English
Views
Read
Edit source
View history
More
Refresh
Search
Tools
What links here
Related changes
Special pages
Page information