https://github.com/live627/post-fields

Custom fields for posts
https://github.com/live627/post-fields

Last synced: 10 months ago
JSON representation

Custom fields for posts

• Host: GitHub
• URL: https://github.com/live627/post-fields
• Owner: live627
• License: isc
• Created: 2016-03-02T04:37:33.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2017-03-06T05:24:16.000Z (almost 9 years ago)
• Last Synced: 2025-01-22T11:28:53.508Z (11 months ago)
• Language: PHP
• Size: 211 KB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Post Fields

[![Build Status](https://img.shields.io/travis/live627/post-fields/master.svg)](https://travis-ci.org/live627/post-fields)

[![Coverage Status](https://img.shields.io/scrutinizer/coverage/g/live627/post-fields.svg)](https://scrutinizer-ci.com/g/live627/post-fields/code-structure)

[![Quality Score](https://img.shields.io/scrutinizer/g/live627/post-fields.svg)](https://scrutinizer-ci.com/g/live627/post-fields)

[![GitHub issues](https://img.shields.io/github/issues/live627/post-fields.svg)](https://github.com/live627/post-fields/issues)

[![ISC license](http://img.shields.io/badge/license-ISC-blue.svg)](http://opensource.org/licenses/ISC)

[![Latest Version](https://img.shields.io/github/release/live627/post-fields.svg)](https://github.com/live627/post-fields/releases)

Custom fields for posts

I've long thought that SMF is very one-sided in allowing for profiles to be expanded upon but not posts. This is my answer.

It takes the principle of the custom profile field and applies it to posts. In fact, most of the design is derived from them.