Website Layout

[skyem123]

Note that all paths with a / at the end of their URL do not need it, but ones without a / at the end will not work with it.

/ - (the homepage, contains popular content, basic account status, and latest news)
 news/ - (like a blog with MCMUCH news and status, this page links to all of them)
      <year>/<month>/<day>/<post number>/<short title>/ - (individual news post)
 about/ - (short about page)
 creations/ - (lists new and popular creations)
           // TODO, what will the creation layout be?
 account/ - (account management page, change password, email, link, unlink, delete, etc...)
         login/ - (prompts the user to log in, with a warning about confusion of methods)
         logout/ - (prompts user to log out session, log out all, or cancel)
 styles/ - (directory with all the css files, and cannot be navigated with a web browser!)
        * - (the css files and assorted things that go with them)
 images/ - (directory with all the images that are not part of a style, can't be navigated!)
        * - (images that are not tied to a style)
 favicon.ico - (favicon, link to /images/favicon.ico)

Currently done:

• /
• /about/
• /news/
• /news/<year>/<month>/<day>/<post number>/<short title>/
• /creations/
• /account/
• /account/login/
• /account/logout/
• /styles/
• /images/
• favicon.ico

[RX14]

Most websites have a directory or subdomain called static which contains images, css and other files. css and image files should also have a checksum in their file name so that you can instruct the browser to cache that file forever, and the updated image has a new URL to bypass the caching.

[RX14]

Ont he topic of caching, we should eventaully use NGINX as a HTTP/2 proxy with smart server push so the client gets super fast load times.

[RX14]

But again, that's far into the future...