Web site to do

From WhyNotWiki

(Redirected from Tylerrick.com to-do list)
Jump to: navigation, search

Web site to do  edit   (Category  edit)

[–] Category:Web site to do
Christian resources
MediaWiki to do
Web site to do
WhyNotWiki:License
WhyNotWiki:To do

Aliases: tylerrick.com to-do list

Contents

[edit] Phase 1: Get content up now

Use a wiki to flesh out pages/content

Problem: I also have a content tree at F:\Notes, containing some overlap.

[edit] Phase 2: Migrate to custom solution

Migrate away from MediaWiki. Add more metadata. Write my own CMS that has all the meta-data services I require.

  1. Research how Mediawiki works.
    • See if it does anything important (updates index of links, f.e.) on page save.
  2. Create ActiveRecord models to read MediaWiki schema.
  3. Use models to migrate MediaWiki data

[edit] Option 1

  1. Continue to use MediaWiki schema during development of custom solution, but exclusively use my new application (models/controllers/views) to interact with the existing database
  2. Until MediaWikiMarkup filter in Rails is ready, possibly just depend on MediaWiki for rendering (doing HTTP calls to a page that exposes the renderer).
  3. Add Ajax in-place editing for existing markup
  4. Supplant MediaWiki categories with custom tagging solution
  5. Develop MediaWikiMarkup filter in Rails (if one isn't already available).
  6. Only later consider migrating away from MediaWiki schema
    • Make other first-class objects besides Articles: Sections, and URLs, for example, that can be tagged homogenously along with Articles. It should be perfectly okay to have many tiny objects.

Problem: Links generated by PHP version will point to wrong URL. Interim solution: search and replace on URL.

Requirement: Extract a reasonable guess of creation time. Don't just take the date of the last revision. If there is a revision history per section (I doubt there is), take the time of the first rather than the last. In any case, show the user what the first revision of the article/section looked like, compared with the current version, to make sure they're actually the same document/the same ancestry.

[edit] Option 2

  1. Create ActiveRecord models to read MediaWiki schema.
  2. Use models to migrate MediaWiki data
  3. Use 'slave copy' (migrated) of data for testing new system
  4. Continue to use MediaWiki as master until new system has enough functionality to be used exclusively

[edit] Impending split on topic lines

I am contemplating soon doing a split of this site, along major topic lines.

Why? Because, due to human psychology, I think people will be much more likely to contribute to a wiki that is named after a topic than one than implies being owned by one individual.

So, I would probably create a wiki for

  • software development
  • ...


[edit] Problems therewith

  • I want to have "pages that link here" feature (not too important)
  • I want to share templates

... But perhaps those aren't strong enough reasons not to.

[edit] Split on privacy/polishedness lines

Possible have 2 sites--one mostly for my private use and one for sharing my better, polished works--that look independent but actually are simply different views into the same database.

  1. Incubation site: mostly for my private use, to flesh out ideas, try to get them organized and polished
  2. Public site: roughly equivalent to a weblog/bliki. Perhaps can have it all RSS syndicated since releases to this site should be polished enough to warrant a new timestamped RSS "announcement".

[edit] Wiki

  • Create/find a logo
  • Redesign stylesheet

[edit] Design

  • stylesheet: font-size: small, all other styles % of that
  • Implement tab layout from bulletproof web design
  • Make PHP template and wiki template the same

[edit] Low priority

Retrieved from "http://whynotwiki.com/Web_site_to_do"
Personal tools