Explorar o código

Removed bogus bits from CHANGELOG, added girth to README.md

teo greenwood %!s(int64=10) %!d(string=hai) anos
pai
achega
28c46ff4c4
Modificáronse 2 ficheiros con 34 adicións e 5 borrados
  1. 3 4
      CHANGELOG
  2. 31 1
      README.md

+ 3 - 4
CHANGELOG

@@ -3,12 +3,11 @@ Version 1.2 "Maxim" Release Notes:
 *Made microblogger start writing posts in JSON notation. This will enable posts from here on out to have additional metadata, manipulation ability, etc.
   -Should mean less HTML knowledge required for editing your microblog postings
   -Falls back to old display/edit method if posting is not JSON so as not to crap on anything.
-*Blog writer also now uses JSON notation to store data.
-  -Stores poster regardless of filesystem permissions this way
-  -Automatically makes a snippet in linklog pointing to blog post on day of posting
 *No longer using Cortado or audioplayer.js to display audio/video, since HTML5 alternatives work well now
  -Video type postings can either be embed or the link to an actual file, if so, it'll validate filetype, etc. then display as HTML5 Video
-*Responsive JS waxed, CSS used instead - will make stuff like libreJS and NoScript irrelevant
+*Responsive JS waxed, CSS used instead - will make stuff like libreJS and NoScript irrelevant.
+ There is still some JS on the microblog editor page, I'll remove that eventually.
+ In any event, all this means is that the person editing posts has to use JS for the div to enable/disable correctly.
 
 GITHUGS RELEASE 1.1.2:
 *Bug fixes, code cleanup, mostly making it more friendly to the github platform

+ 31 - 1
README.md

@@ -1,6 +1,36 @@
 tCMS
 ====
 
-A PHP flat-file CMS (teodesian.net CMS)
+A PHP flat-file CMS (teodesian.net CMS), geared towards a webmaster who mostly already "knows what he's doing".
+As such, it allows for some neat things like posting via flat files,
+in case you just wanted to use vim, etc. to blog (as I do).
+Still, I've added a lot of frontend convenience stuff, mostly as requests.
+
+Oh, yeah, did I mention it's responsive by default and degrades well on IE (last I checked)?
 
 See http://tcms.troglodyne.net for more information.
+
+Installing this is pretty easy,
+either grab an archive from above site and extract it or git clone it into a public html directory.
+
+WARNING: If you don't setup HTTP Server based Authentication, you deserve what you get.
+See the manual for more information: http://tcms.troglodyne.net/index.php?nav=1&dir=fileshare/manual
+
+As of the latest version, there should be no upgrade issues,
+despite switching to using JSON to store new postings.
+The code anticipates and uses the legacy style of accessing old posts in that instance.
+
+TODO:
+ * Convert blog posts to use JSON, similar to microblog, mostly to enable storing better metadata.
+ * Test code. I'll probably do this in perl,
+   since I'm used to it's test harnesses and Selenium::Remote::Driver for functional automated testing.
+ * API conversion for signifigant functionality, mostly as a way to make it easier to extend tCMS.
+   - For example, a cron that watches your install for new posts then crossposts to twitter, etc.
+   - Distributed tCMS installs with gluster would be fun :D
+ * Support for alternative authentication schemes (LDAP, etc.).
+   I doubt a manual mapping table from what you've set HTTP auth users to in tCMS is everyone's cup o tea.
+ * Add option for using an SQLite database to store posting data, configs, etc.
+
+Really, I don't wanna go too hog wild with features on this,
+since I've already accomplished pretty much 100% of what I want tCMS to do for me.
+Most of these are 'nice to have' items. I may think about working on some of these more if there's interest.