Showing changes from revision #39 to #40:
Added | Removed | Changed
Content
Resources
Community
Contributors?
An easy introduction for elemenatry basics is
The following provides more details.
See also the FAQ.
An easy introduction for elemenatry basics geared towards readers familiar the nCafe is
Hit “edit page” to see how pages are coded. Use the Sandbox to warm up.
Creating a new page is done by
first creating a preliminary link (represented by a question mark) by entering double square brackets;
then clicking on the question mark and following the instructions.
Watch out: the name of a page is case sensitive, so make your link lowercase if it comes at the beginning of a sentence. ([[like this|Like this]].) We loosely agreed to try to follow that and some other naming conventions; see below.
However, this is less of an issue now that we have redirects.
When you edit a page, you can (and should) put your name (with normal capitalisation and spacing) in the box after ‘Submit as’. If you don't, then your contribution will be credited to the AnonymousCoward.
Once you edit a page for the first time, your name will appear at the bottom, grayed out with a question mark since there is no page with your name yet. You may take this as an invitation to create a user page and tell us about yourself. But if you don’t want to or don’t have the time right now, you can forget about this. If you just want to show up on category: people, then you make a page containing only ‘category: people’ (or someone else may do this for you).
To create your user page, simply click the question mark that appears next to your name at the bottom of the page after making a modification and add content to the edit box that appears. If you’d like to make a user page prior to modifying an existing page, you can do so by making some trivial modification to the Sandbox, which will put your name at the bottom of the page where you can click the question mark. (Or hack the URL.)
These are not set in stone, but we're following them for now. Most days, Toby Bartels goes around and corrects any violations (while reading the new material). But changing page titles results in unnecessary kruft (in category: redirect), so you should try to follow these if possible (or dispute them if not!).
Page titles should contain only ASCII characters.
[[omega-category]] instead of [[$\omega$-category]] or [[∞-category]].$\omega$-[[omega-category|category]]. Unfortunately, $\omega$-category does not work.[[∞-category]] is now redirected to ∞-category.Page titles should be singular nouns.
[[category]] instead of [[categories]], [[faithful functor]] instead of [[faithful]], and [[categorification]] instead of [[categorify]] or [[categorified]].[[category|categories]]. To produce ‘faithful endofunctor’, try [[faithful functor|faithful]] [[endofunctor]].[[category|categories]]. If you find yourself frequently typing [[internalization|internal to]], then you might consider adding a redirect to internalization (which we’ve done now) so that [[internal to]] is redirected to internal to.Page titles should be uncapitalised, except for word words that are always capitalised.
[[homotopy theory]] instead of [[Homotopy Theory]], but use [[Lie algebra]].[[homotopy theory|Homotopy theory]] is important!.Except as contradicted above, use standard American English spelling conventions.
[[internalization]] instead of [[internalisation]] and hyphens as shown in the ASCII-only requirement.[[internalization|internalisation]].Regardless of the above, pages named after specific categories should use the capitalised singular abbreviated form.
[[Set]] instead [[Sets]] and [[Cat]] instead of [[Category]].If you want to make a comment or question about a page without changing its main content, then edit the page and put your comment or question in a query block as shown in this example:
+-- {: .query}
How do I ask a question?
=--which produces
How do I ask a question?
Note that a query block should be less permanent than the rest of the page; once your comment is addressed or your question is answered, you can probably remove your query block.
If you want to ask a question of a specific person, then you can place a query block on their user page (which is just a page whose title is their name). You should be able to find all user pages here.
If your comment or question is more general than a specific page or person, then try the n-Forum. Previous discussions have been on the General Discussion page and on an entry at the n-Cafe. These previous discussions should not be added to but you may find your question answered there. Important answers are being migrated to this How To and the FAQ. As this is a Wiki, if you find an answer to your question and feel it should be added to one of those then do so.
If you want to make some text stand out (an important theorem, or slogan), you can do it using a standout box:
+-- {: .standout}
First quantization is a mystery, but second quantization is a functor.
=--which produces
First quantization is a mystery, but second quantization is a functor.
To fiddle with the CSS code, go to “Edit web” on the main page of your wiki, and then click on “Stylesheat tweaks”. Here you can add new CSS gismos like query boxes and standout boxes. These kind of gismos come from the mechanism of putting CSS classes into the Markdown syntax, in the same way that Jacques created the Theorem environments in Instiki. In other words, a query box is like a theorem environment: it’s a way in Markdown to create an HTML block with a specific id, which you can then style in the CSS. You can grab the CSS code for query boxes from the main nLab page. It requires a password to change the CSS, but to view it does not require one.
Here are two search plugins for firefox that will let you search the nLab from the firefox search bar.
The first one searches the nLab (like the search box at the top of every page), and the second takes you directly to the page with a given title (if it exists; otherwise it takes you to an edit box to create it). It would be nice if they had different icons.
To use one or both, drop it in the ‘searchplugins’ directory of your firefox profile.
One way to do this is to install this firefox extension or another one like it.
If your favorite editor is Emacs with AucTeX, you may find the following snippet useful to put in your .emacs file:
(add-to-list 'auto-mode-alist '("/\\(www.\\)?ncatlab.org" . latex-mode))
(add-to-list 'auto-mode-alist '("/golem.ph.utexas.edu" . latex-mode))
(defun nlab-latex-fixes ()
(when (or (string-match "/\\(www.\\)?ncatlab.org" buffer-file-name)
(string-match "/golem.ph.utexas.edu" buffer-file-name))
(longlines-mode t)
(set (make-local-variable 'TeX-open-quote) "\"")
(set (make-local-variable 'TeX-close-quote) "\"")))
(add-hook 'LaTeX-mode-hook 'nlab-latex-fixes)This will tell Emacs to automatically edit nLab pages (and nCafe comments as well, for good measure) in LaTeX mode, with long lines wrapped using soft returns, and ordinary double-quotes rather than LaTeX ones.
If you have some material at a page called foo that you want to include directly in pages called bar and baz, then type [[!include foo]] in bar and baz. For an example, see how contents is included at the tope of this page. Also see how contents itself has been formatted so that it will appear as a sidebar when included.
Besides such sidebars that appear in many pages, you can also use inclusion to put in something that contains a bunch of ugly code (such as raw SVG) without mucking up the rest of the page. That is, you put your messy code in bar/foo and then put [[!include bar/foo]] in bar. Note that this is for something that, logically, should appear within bar itself, which is why bar appears in the name of the included page.
You may wish to customize the font scheme (both for math or text) on the nLab, as well as tweak things such as the small edit box for comments. Experienced users can do this themselves by tweaking the CSS. Alternatively, one can try the nLab Stylish theme for Firefox available here. You might also want to try a Firefox extension which allows you to edit the text box using your favourite text editor.
See redirects.
For general information and help with Instiki, see the Instiki wiki.
Here are some useful specifics: * Use basic Markdown syntax * Make tables, footnotes, etc * Add definitions and theorems * Add metadata to your markup * Type itex equations * Use wiki syntax * Embed SVG in equations * Upload files * Use keyboard shortcuts * Make slideshows
Revision on July 23, 2009 at 10:51:23 by Urs Schreiber See the history of this page for a list of all contributions to it.