Closed robertocarroll closed 9 years ago
In the existing website, each Press Release Page (ASP Page) is created by PIDS using a Press Release Template. These Press Release Pages are then stored in a centralized Press Releases Pages library and accordingly the list is displayed on main page, at each case and Situation level etc. The press release page will have appropriate content and further links to any Video, other Pages etc. For new public website, we will be using similar Pages library to generate "news" section for Home, Situation, Case, etc pages.
Rob - In existing website, we do not have anything called as Announcements. Can you please provide clarity that what we need to store for each Announcement in backend SP list. I believe it will be:
Also we do not have any "Announcements" section for Situation pages. Is it intentional? Also I would like to hear final word on below issue to decide if any UI changes are required for "News" and "Announcements" section: How to make users aware of the difference between news and announcement? #60
It was my understanding that Announcements are form of tweets. We would like to be able to create our own quick information tool with more than 140 characters limit. I would use an SP list for this and the order would be a reverse date/time (newest on top). There would not be a link pointing to the announcement itself.
So the rule would be: Announcements do not have:
The body of the announcement would need to be able to contain full HTML, so links, images and so on.
The announcement would need to use the "Related to" field, so we can show them in different places (Cases, Situations, OTP and so on).
Thanks. This is clear for me. I believe the overall Announcements design i.e. how we will publish the Announcements to public website, multiple twitter Accounts etc is still under discussion. But independent of that, I can create this centralized Announcements SP list and can implement the WebPart for Home, other pages accordingly.
Armin: did you get chance to review the announcements proposal? #60
Follows the COPE approach - create once, publish everywhere - would be the most efficient and effective way and making it keep within Twitter's 140 characters means it can reach potential users well beyond the limits of the website.
Rob, initially I thought this would be 140 characters items, so I imagined this being connected to Twitter with the possibility of not posting, but PIDS wanted to be able to put longer posts. That was the reason behind the request.
On Wednesday, January 14, 2015, Robert Carroll notifications@github.com wrote:
Armin: did you get chance to review the announcements proposal? #60 https://github.com/robertocarroll/icc-beta/issues/60
Follows the COPE approach - create once, publish everywhere - would be the most efficient and effective way and making it keep within Twitter's 140 characters means it can reach potential users well beyond the limits of the website.
— Reply to this email directly or view it on GitHub https://github.com/robertocarroll/icc-beta/issues/59#issuecomment-69898669 .
The implementation details for this section is as below. Announcement create/ publish discussion will continue as part of Issue #60