simple shellscript CMS/blog-platform

Derek Stevens 8e8daf33c5 updated readme 1 month ago
templates 5a80b330a4 git link in *top.html points here 1 month ago
.gitignore 06fc0d255e initial commit 1 month ago
LICENSE 06fc0d255e initial commit 1 month ago
README.md 8e8daf33c5 updated readme 1 month ago
ayanami.sh 06fc0d255e initial commit 1 month ago
config.sh 06fc0d255e initial commit 1 month ago
tmplt.db 06fc0d255e initial commit 1 month ago

README.md

// Ayanami Simple CMS & Blog Platform //

Initial setup consists of: setting the environment variables in config.sh, putting together your css (the templates give you a lot of room to play),
setting up headers and navigation links in the *top.html template files.

After setting up your html headers, titles, nav links, etc, do a git update-index --skip-worktree templates/*.top.html to preserve them if you do another pull. Do the same with the config.sh

Additional pages can be added to a site by duplicating the index.*.html files, renaming from index to the appropriate name, editing headers and navigation links, and adding the page to the array in the config.

Posts are in a four-part structure:
post_meta: a file containing the post type and its human-readable name
post_files: a file containing all file links referenced in the post, line by line (unless you do inline linking in a longer format post)
post: contains the textual body of the post in rawtext. can put html in here to pretty it up
post_web: contains the same textual body formatted for integration into the html files (i will make these obsolete soon enough)

The archiver functions independently of your page structure. Whatever directories you give it in its configuration array will be displayed on the archive page in that order. I recommend an accordian setup for the css on this. Makes it look snazzy.

For now, don't use spaces in filenames. Just don't.