In part 1 of this series, I explained why I approached building a simple sub-site for our content managers. It was simply to bring a better UI experience than what they were expecting within the site contents section. I use this approach to allow our content managers to update three different lists that display information within our main intranet landing page.
The page is currently set up so that an ajax query executes on page load and pulls all of the news list items. These items are displayed in a table. The table consists of a checkbox to select the item, text areas to review or update the text of the item, and a drop-down menu to select whether or not the item is promoted to the top of the page.
One extra step of functionality that I included in this was the ability to promote this item to the top of the page and then set all of the other items to ‘No.’ This is part of the ‘Add Item’ function and it’s main goal is to ensure that there are no news items that are set so that both are promoted to the top.
In the next post, I will walk through the main pieces of the script and tie all of these pieces together. I will discuss what my thoughts were when I was building the code that makes all of this function.
Need help with SharePoint? Feel free to contact me.
Have a bigger project? Check out my company, UDig, LLC.