Weather • GoWhere? • YahooMaps (mine) • GoogleMaps • Metro (map) • FairfaxConnector • GreaterGreaterWashington • DCMetrocentric • WhatsUpArlington • Restonian • BeyondDC • BaconsRebellion

ZBB • Vreleksá • AwkWords • Omniglot • Scriptorium • More...

• AnnalsOfArda • Arda • SilmarillionChronology • TolkienGateway •

• CentauriDreams • ColdNavy • ConceptShips • RavenstarStudios • SkyscraperPage • StarTrek • StarTrekVsStarWars •

IMDB • BigHollywood • DKnowsAll • Jabootu • KyleSmith

RIAA

• Resources • Garage • University • WebRing • Forums: • REAL • ElfData • Plugins and Code: • BKeeney • DeclareSub • Einhugur • Joe • Restrepo • Tempelmann • ZAZ

Forums: • PowWeb • PHP • Webmaster • Coding • Walkers • Perl • Intro • Monks • PHP • JavaScript • Toolbox • UnobtrusiveJavaScript • JavaScriptCompressor • RegularExpressions (test) • JSLint • SQL • Cocoa • CocoaBuilder • CocoaDev • CocoaLab • AppleScript • BBS • Userland • Faqintosh • FileMaker • FileMakerTips • FileMakerWorld • FileMakerPlugins

DarwinCentral • PhysOrg • PandasThumb • TalkOrigins • TalkRational • AstronomyDailyPics • Curmudgeon • SmallThings • ArchaeoBlog • AntiEvolution.org • SkepticsGuide • EvC • BadAstronomer • PhysicsForum • SlashdotScience • JunkScience • Engadget • Thunderbolts • Icecap • CentauriDreams • NewScientist • Gizmodo • CO2Science • ClimateDebate • ScienceDaily • Nrich • Math • TalkOrigins • GoodMathBadMath • Magazines • AmericanScientist • NationalGeographic • Space.com

• 1421

WideAwakes • Anchoress • Lucianne • Strata • AceOfSpades • BigLizards • BlackAndRight • Cannonfire • DrSanity • FloppingAces • GatewayPundit • HillBuzz • HotAir • Husaria • JawaReport • JimTreacher • JsCafeNette • LittleGreenFootballs • MyVRWC • Newsbusters • Pal2Pal • PinkFlamingo • PowerLine • RachelLucas • RogerLSimon • SisterToldjah • StolenThunder • SultanKnish • TCSDaily • UppityWoman • Wizbang • NewsGroper • NewsRightNow • OriginalSignal • Blogs...

• Clambake • Infidels •

Fun: Agony ICanHas? ObSkills Snopes Pix: Deviant Places Renderosity Blender Artists X86: OSX86 ArsTech OSNews TUAW

Tools: Calculator AsciiArt XMLVal

FunStuff: Pictures: Photobucket (eg Dubai) Videos: YouTube Subtitler

InterestingThings: LibraryThing FlashCards GoogleDocs Wowio Bubbl.us Colemak Audible PodioBooks WonderfulInfo BooksOnline AboutUs.org

• View
• Edit
• History
• Print

DesirableFeatures

Entry storage

• Save entries as text files so that data can be retrieved with a text editor.
• Keep old versions of pages to allow recovery from mistakes or malicious changes. See EntryFileFormat?.
• Large maximum number of entries. Each entry is saved in a subfolder whose name is the first three characters (set to lowercase) of the entry name. This scheme is dead simple and yet permits millions and millions of entries. See EntryFolders.

Interface (display and editor)

• Provide user and password boxes on the editor page. The username and the password are passed to the save routine. If the password is blank or wrong, the user is returned to the editor with a message: "Incorrect password. Changes not saved."

Tags (or journals)

• Add tags to pages so that pages can be indexed by tags. See TagIndexFormat, SaveProcess, WhyTags.
• Filter and sort pages by tags so that multiple small pages can be output as one or more large pages. See SearchResults.
• Add entries to journals. See Journals.

Easy maintenance and customization

• Use an HTML file as a template for output. TigerWiki works by loading a template file, replacing the word "{CONTENT}" in that file with the contents of a Wiki page, and outputting the altered file content. This is both simpler and more flexible than providing "skins" to alter the appearance of a Web page, for the template file can contain any sort of customized content.
• Keep configuration files as special pages to simplify customization. (These pages should have a special administrator-only password.) These configuration files would include pages for setting passwords for other pages (or for allowing any visitor to edit the pages). They might also include things like the name of the template file, custom markup, permitted or forbidden tags, etc.
  • Template and CSS files. You should be able to edit the template HTML file and its CSS file from within the Wiki editor. The editor would have an option to edit a file as is, and not just the first or second line of a file; this would be used to edit the HTML and CSS files. (This would be transparent to the Wiki user.)

Other things

• Scripts that can be called from Wiki text, so that their results are displayed in the page. (These too would be saved in configuration files.)
• Nice URLs as in PmWiki. (Probably through a custom .htaccess file.) See URLs.