Posts Tagged ‘recommendation’Preview of Next Version of Shadowbox ThemeNovember 18th, 2009 by Alex ChapinI attended part of the LIS website team meeting today and gave a presentation of the ShadowBox theme and some of the new features that will be available in the next version including updates to author pages, more custom header options and most importantly, higher contrast text in comment fields. I also gave a preview of some new ShadowBox variations based on the new college website design. Below is a screencast from that meeting:
"Resources" content for Academic Department pagesSeptember 23rd, 2009 by Carrie MacfarlaneHow about something like this? It might be too text-y, but some explanation of why you’d want to contact these people/groups seems necessary. eg, for Chemistry: (more…) LIS Website Team – RecommendationsSeptember 10th, 2009 by Elin WaagenHere’s the draft for LISt. OK? The web team met recently with the LIS Area Directors to present our recommendations for the new LIS web presence. One Blog to Pool them AllSeptember 8th, 2009 by Ian McBrideHere are my initial ideas of how this could be organized. Existing Infrastructure We’ll take the current LISt blog, rename it to just “LIS” and grant all staff in LIS Editor access to the blog. Student workers and LIS-related people like department advisory groups will have Author access granted as needed. Porting Content Users and groups with existing blogs may move their content into the LIS blog by going to Tools -> Export -> Download Export file in their blog, then Tools -> Import -> WordPress -> Upload file and Import. After doing so, they should go to Posts -> Categories and use the Category to Tag Converter to change any custom categories their blog had into tags on the LIS blog. Categories The LIS blog will start with this set of categories:
All other existing categories in the LIS blog will be changed to tags. In general, we’ll encourage the use to tags to mark things like posts that have photos in them, posts about particular workgroups, posts about particular projects, or other things that tend to have a more temporally mutable quality to them. Categories will be used chiefly for broad categories that change infrequently. Private Blogs The LIS blog will not be used to store private content. Groups, such as ACS, who wish to have a private blog should continue to use and maintain their blog in its present form or create new private blogs if one has not yet been set up. Internal vs. External Posts that are likely to be interesting only to LIS staff should be marked with the Internal category. Examples of this content might include a notice about LIS goal setting. Note that these posts would still be readable by the public, but that those subscribed to the public feed wouldn’t see them in the feed. Posts that are likely to have broader appeal, like a cookie party for students, should be marked with the External category, or both the Internal and External categories. There will be links to both the External and Internal feeds on the blog homepage with a description of the content featured in each so that site visitors can choose how they will read about LIS. Added "LIS in IA" to Recommendations DocAugust 19th, 2009 by Carrie MacfarlanePlease read and edit! Here it is: LIS within the IA of the College Site Meeting agenda for 8/12August 7th, 2009 by Jess IslerAgenda for Wed 8/12:
Recommendations: Preparing a Document to ShareJuly 22nd, 2009 by Ian McBrideI started the LIS Website Recommendations document a few weeks ago, based on my personal views of the project and some of the discussions we have had early on during team meetings. I will commit to working later in this week to flesh this document out more with specific references to materials which support the changes it recommends. However, here are some framing questions we can use to think about these recommendations. What sections of this document conflict with goals of the team? What goals of the team are missing from this document? What changes do we need to make to these recommendations based on the survey results? What changes do we need to make to these recommendations based on other data sources? What resources should we reference within this document to support the recommendations it proscribes? Criteria: What do we need for a LIS website?July 22nd, 2009 by Ian McBrideThis is a place to coordinate discussion about the criteria we desire for the LIS site. We’ve created two sections in the wiki to store this information: How can we combine these sections? Do we need to combine these sections? What information from our own personal views are missing from these sections? What information from our survey results is missing from these sections? What information from the other analytics and analysis we’ve conducted is missing from these sections? What information in these sections should be removed or is no longer applicable knowing what we know now? How do these criteria allow us to meet our goals and achieve our vision? LIS Website RecommendationsJuly 7th, 2009 by Ian McBrideWe’ve really been making quick progress through the outline of the team structure, goals, criteria, etc. Soon we’ll be at the point to offer up recommendations and then decide on resource allocation. I spent a little time this afternoon drawing up an outline document for recommendations on each area of the scope we defined at the last meeting. In each part of the scope I put down recommendations based on the discussion we had at the last meeting of those areas (though we haven’t yet agreed/voted on anything) and in those we hadn’t discussed, just wrote up some off-hand thoughts. In no way do I mean that these are the thoughts and opinions of the team at this time, but I did want to flesh out a framework that we can discuss and revise, more so than just topic headings. We can use this as a rough outline and solidify or reverse the recommendations once the team comes to a consensus on the specifics, as well as inject findings from the survey we’ll build out this week. This is probably ridiculously presumptuous of me to have even done, but I like to write out my thoughts rather than say them aloud and find that its often helpful for discussion to have a framework like this in place, even if everyone disagrees with me and we end up recommending the exact opposite of whatever I wrote. I guess, in a way, this is my longish answer to Elin’s questions from the DIY Content Workbook draft, particularly the last four questions. |