(1) logging into backend
(2) choosing the article menu itself
(3) finding the actual article in the list (sometimes long and complex)
(4) and then clicking the edit button
represents 'extra steps' from end users perspectives.
Edit Article Strategy
Rather it has been suggested that having an edit button available on a per article basis might simplify and streamline the process. This button would be available (maybe at bottom of the article (when logged in), and might be based on this expression:
Code: Select all
if($_SESSION["wcs_user_admin"]==1){show_edit_button code}
This link would have the embedded parameters to be sent to wcms backend:
http://www.mydomain.com/phpwcms.php?do= ... s=1&id=147
which would open in a new window.
Any edits (adding content parts or editing summary) could be submitted in this new window, and changes viewed in the orignal window by hitting the refresh button.
Add New Article Strategy
Similarly an add new artilcle option would appear in article listings/site category pages, and might look something like this:
and have the embedded link, sending parameters to backend:
http://www.mydomain.com/phpwcms.php?do= ... &struct=13
and again would spawn a new window like this:
And again, any edits (adding content parts or editing summary) could be submitted in this new window, and changes viewed in the original window by hitting the refresh button.
Loggin Strategy
This would still respect the login strategy in place and basically be an extension of the existing login, but to make things easier for end users, it would be accessed via the public site, something like this:
and go to a simplified login window, like this:
upon successful login, the SESSION varialbes would be set, the screen would show GNU copyright information (per Oliver's requirements) and then refresh to the original site with the 'edit article' and 'add new article' indicators showing up.
These suggestons are based on simple end user feedback and would make the wcms more usable from end-users perspectives, imo. I recognise that some of the particulars of this new strategy would need to be clarified, but I do beleve that these changes represent no significant modifications of the Wcms core. Having this functionality in place would be a plus in 'selling' the wcms conept to prospective clients/end-users. Would be interested in hearing others opinion on this.
about this kind of implementation? A very nice suggestion to the invisible, yet wanted roadmap 
