Show Likes
This section allows you to view all posts where this member received or gave a like to.
1
Feature discussion / Re: FB style link preview and walls
godboko71 « on March 23rd, 2014, 05:43 AM »
That is a pretty neat feature piece of code will have to play with it. Thanks for sharing the find @Pandos
3
Looking pretty neato :) No other comments at this time.
4
Wait till NAS is done and reboot!
5
As long as the data is their does it really matter if we have to reset perms. Seems if one is moving to a new platform people should be expected to have to reset settings.
6
As long as the data is their does it really matter if we have to reset perms. Seems if one is moving to a new platform people should be expected to have to reset settings.
7
Off-topic / Re: Initial forecasts of Wedge installs/conversions
godboko71 « on May 30th, 2013, 01:30 AM »
"Will beat whiners with a stick. Doubly so if they don't at least try to read."
8
Feature discussion / Content Management System Wishlist Core + Plugins
godboko71 « on May 30th, 2013, 06:03 AM »
PLEASE NOTE: This is an evolving post as I had very little rest of late however if I don't get it started I won't remember when things calm down.
Some thoughts before I begin. Personally I think wedge is already a content management system, with a few tweaks to some components and you have a full fledged CMS. As an online publisher, I wear many hats, I have very few needs however I do have many wants. This will mainly cover backend and plugin features and not templeting.
Core
Core can be fairly lightweight and still be flexible and usable for the majority of websites.
Multiple Content Types/Boards:
Most content has some of the same basic needs: Subject/Title, Body/Description, and Custom Fields
Custom Fields:
For the majority of content the custom/extra fields are what makes it unique.
Useful Field Types:
Text field
Text Box
Check Box
Radio Buttons
Dropdown Lists
Upload/Media Manager (Should be tied into the media portion of Wedge)
Content States:
Work flow kiddos
Draft (Still writing it boss)
Reviewed (Editors have cleaned it up and the writer needs to approve the changes) *Optional
Published (Boss man Approves & Publishes the article)
Frontpage (Boss man features it on the frontpage) *Optional
Plugins
Stuff to add features and functionality that may be useful for things other than CMS.
Ratings
Provides a rating custom field - useful for reviews
Provide settings to let users rate content.
Provide settings to add rating custom fields to comment areas of selected content types - useful for user ratings/reviews
Some thoughts before I begin. Personally I think wedge is already a content management system, with a few tweaks to some components and you have a full fledged CMS. As an online publisher, I wear many hats, I have very few needs however I do have many wants. This will mainly cover backend and plugin features and not templeting.
Core
Core can be fairly lightweight and still be flexible and usable for the majority of websites.
Multiple Content Types/Boards:
Most content has some of the same basic needs: Subject/Title, Body/Description, and Custom Fields
Custom Fields:
For the majority of content the custom/extra fields are what makes it unique.
Useful Field Types:
Text field
Text Box
Check Box
Radio Buttons
Dropdown Lists
Upload/Media Manager (Should be tied into the media portion of Wedge)
Content States:
Work flow kiddos
Draft (Still writing it boss)
Reviewed (Editors have cleaned it up and the writer needs to approve the changes) *Optional
Published (Boss man Approves & Publishes the article)
Frontpage (Boss man features it on the frontpage) *Optional
Plugins
Stuff to add features and functionality that may be useful for things other than CMS.
Ratings
Provides a rating custom field - useful for reviews
Provide settings to let users rate content.
Provide settings to add rating custom fields to comment areas of selected content types - useful for user ratings/reviews
9
"Support by real people with real attitudes"
10
"Support by real people with real attitudes"