@carnould - Yes, you can edit this text string in Studio. Just go to the Text Editor and search for the string you want to change. There you can change it to whatever you want it to say.
Learn more about editing default text keys here.
... View more
@daphtan - You can read more about the Community Klout score here. There isn't an intrinsic way from the number icon to see your "ranking" so to speak, but you can use the Klout Insights report to get a list of users listed by Community Klout score, which does give you an idea where you stand. Hope this helps.
... View more
Thanks, @RobertT. Yes, we've started adding mini-TOCs at the tops of longer/more complex articles. We jsut haven't done a full sweep of all older content. You'll also notice in newer content, there are often "related topics" links at the bottom of articles as well as a more liberal use of labels. Keep the ideas coming.
... View more
Thanks to everyone who participation in the OnTheAirWithLithium today. @SuzieH and I had a great time sharing our upcoming projects and doc tips with you. Hope you all found it valuable. Reach out to us anytime with questions and suggestions.
... View more
Last October, we released Community API v2 and Lithium Query Language (LiQL). LiQL is a powerful and flexible language used to filter and sort resources in a collection using a familiar, SQL-like syntax. LiQL does the heavy lifting for the Community API v2, retrieving metadata from resources. Using LiQL helps keep the standard API call set light.
With the LiQL syntax, you select fields from a collection of resources where you optionally define constraints to limit the data returned and order by specific parameters.
Note: LiQL variables are case sensitive. In the image below <fields>, <collection>, and <constraints> must be in lower case. The SELECT, FROM, WHERE, ORDER BY, and IN clauses can be in any case.
In this installment of the Developer’s Corner, we are sharing a couple of LiQL queries that our Services team created in response to customer questions.
Create a Leaderboard of Topics by number of replies
<#assign x= rest("2.0","/search?q=" + "SELECT id, subject, view_href, replies.count(*) FROM messages WHERE board.id = '[ board id ]' AND depth=0 ORDER BY replies.count(*) DESC LIMIT 5"?url) />
<#list x.data.items as message >
Filter Topics by a metadata field
<#assign x= rest("2.0","/search?q=" + "SELECT subject, id, view_href, author.login, body, conversation.last_post_time_friendly, post_time, metadata1, metadata2, metadata3 FROM messages WHERE board.id = '[ board id ]' AND depth=0 AND metadata1='[ filter ]' ORDER BY post_time DESC"?url ) />
<#if x.data.items?? && x.data.items?length gt 0>
Note: board.name was changed to board.id to keep v2 consistent with v1 and what is referred to as a board id by our UI.
Note: This LiQL query only works with out-of-the-box metadata fields, not custom fields.
Learn more about Community v2 API and LiQL in our developer docs.
To ask for help creating LiQL other queries or to share some of your own, join our Developer’s Discussion board.
... View more
Here's my 3-monitor setup. Say "hi" to the Swedish Chef peeking around my laptop...
....and if you're wondering who's coming over my monitor...
I'm protected by my Facehugger sentry, as well as Psyduck, Buddy Christ, and the Doctor and his TARDIS.
... View more
The Lithium documentation team is constantly working to improve the quality, findability, and usefulness of its documentation. Our goal is to remove as much friction as possible and give you the help you need, when and where you need it. As part of this strategy, we’ve just rolled out the revamped Lithium Social Web Knowledge Base, which is part of the overall Lithium Documentation Knowledge Base. As part of this project, we have eliminated the cumbersome LSW Owner’s Guide and have moved all its content into more focused knowledge base articles. Doing so, we gain these benefits:
More targeted content
Ability to link directly to content from Lithium Social Web (coming soon)
The articles have been grouped into themed categories in a new LSW section of the Documentation KB. Here’s what it looks like: Just browse or search for the info you want here and get your answers faster. We know that navigating a bunch of TKBs can be confusing and time-consuming at times. We’ve got your back. We’ve created a number of “index” articles (one for each LSW view as well as some high-level overview articles) which include links to content on common tasks and concepts. We’ve also added a lot of links between articles to help you find related content. We have a couple of other surprises that we’re working on to improve the usability of TKB articles for the entire Documentation Knowledge Base (stay tuned). Join the conversation One of the best advantages of moving to TKB is that we can work together to improve the docs. If you see an error or have a tip to share, add a comment and let us know. Think we’re missing something? Email us or write an article and nominate it to be added to the Doc KB.
Coming Very Soon…In-product Help We’re in the process of connecting the LSW application to the LSW KB via context-sensitive help (CSH) links for each LSW view. Soon, you’ll be able to click a Help link at the top of the page and go right to the content you need. That’s all for now. As always, let us know what else we can do to help you. Your Lithium Doc Team
... View more
Starting with the 13.10 release, Lithium has begun rolling out several documentation and in-product assistance improvements, all working toward single goal…make Lithium products easier to use and provide you with great answers so you can create best-in-class communities.
I joined Lithium earlier this year with the charter of assessing our existing documentation and taking it to the next level. Where to start? With you, of course.
A few months ago, I sent out Lithium’s first Customer Documentation Survey to learn from you what’s working and what needs improvement. Based on the findings from this survey, we’ve been making significant changes to our docs, relating to its content, distribution medium, and usability.
One of the top themes from the survey pertained to organization and usability. About 50% of you felt that our docs were too hard to find and use. We agree.
Other themes that bubbled up were:
Keeping content up to date with the product releases
Providing better in-context help in Admin/Studio
Examples, examples, examples
Time to shake things up…
Organization: We’ve overhauled how we organize and distribute our product docs on Lithosphere. Instead of pages of articles that link to long PDF guides, we’ve bucketed our docs into themed categories for easy browsing and converted most of our PDFs to targeted TKB articles.
(You'll need to have customer or partner access to navigate to the new documentation area)
One of the problems with distributing docs as PDFs is that it’s hard to keep them up to date (another common grumble from the survey), especially when we’re adding and updating features every month. As a result, we’ve ended up with a lot of stale and duplicate content across guides. No more!
By moving our doc into TKBs, we gain these benefits:
Ability to link directly to content from Admin/Studio (coming soon)
Join the conversation: One of the best advantages of moving to TKB is that we can work together to improve the docs. If you see an error or have a tip to share, let us know. Think we’re missing something? Email us or write an article and nominate it to be added to the Doc KB.
Answers at your fingertips: We need to do a lot more that just change how we deliver our docs. We need to make it easier for you to get the answers you need. To that end, we’re moving a lot of content from the docs and embedding it right in the product. Need to know what a specific permission does? Just click the tooltip.
Coming Very Soon…In-product Help
We’re in the process of connecting the new Doc KB directly to Admin and Studio to provide you context-sensitive help (CSH). Soon, you’ll be able to click the Show help for this pagelink at the bottom of each Admin and Studio page.
The new help viewer will open and provide links to relevant content from Lithosphere's documentation so you can jump right to the article or category you need.
Beefing up our developer docs
You’ve already seen a lot of these improvements to our developer docs this year. We’re continuing to improve the REST API documentation page, which provides an overview of how to use the API, as well as categorized groupings of methods for easy browsing and searching.
Click any method to get the details you need.
Improved Studio component groupings and descriptions
Another one of your big requests was more useful information about all the components available in Studio. We’ve revamped the component tooltips to provide you with all the information you need.
Additionally, we have made these Studio component improvements:
More descriptive component names: We updated some of the component names in Studio so that they align with how the component displays in the community.
More intuitive component groupings: We have rearranged the components into more logical groups based on how you will use and look for the components.
Removal of internal components: We have hidden a handful of components from Studio that are intended for internal use only.
And, in the future, we’ll be making these component descriptions even better.
On the horizon…
We’re excited to hear what you think about these changes. We have lots more exciting improvements coming to Lithium docs over the next year. Stay tuned…
John and Suzie
Your Lithium doc champions
... View more