I know that this is an old question, but I am fairly new to Storyline and could do with some help. I need to add some image branding to the html page for a customer. I've tried adding the
<body background="my image"> in the header html, and I've tried an external css file, but so far, nothing has worked.
Funny. You haven't seen spammy Saturdays yet. That flag button is pretty handy to dim and eventually vote out of sight some of the "Watch this soccer game here" spam we get in large quantities some evenings and weekends.
I dig the idea of the like button / great idea / thumbs up as an addition.
Yes, Emily, I do know that you have the "Mark As Helpful" button but I was saying that you could use that little button bar to tag items which could be tracked for suggestions/improvements. Like a "Great Idea for Product Improvement" button. By allowing more than one person to click on it then it would serve as a vote button.
It's just that I see so many of you staff folks saying, "Hey why not submit that for product improvement" but that doesn't give your community the opportunity to vote for something and no one actually KNOWS if they did submit it for a suggestion. People are awfully darn busy (I know I am), so that is why I am making this suggestion here. You're a staff member, Emily, why can't you do it for me if you think it's got value? And if you don't want to do it for me then at least make it easy for me to do so with a single button or allow others to promote the idea by clicking on the button to submit to Articulate as a suggestion. Why make people go to a separate form? Why not give this audience the chance to vote and know the item is submitted for improvement?
I understand why this feature would be of value in the community. I wanted to share this recent thread here where this topic was discussed as well. This may give you some additional information regarding this particular feature.
You are totally correct about that, Emily. And do you really like having to make that recommendation so frequently? Wouldn't it make your job easier, too?
Wouldn't it be great if you agreed with an improvement and you could easily just vote for it right on the screen instead of saying, "Hey, go over here and fill out a form."
The dev team does participate in the forum. I've seen quite a few instances of both dev team and dev ops jumping into threads. However, they don't have time to spend a lot of time here so they rely on the community managers, the feature requests (to document requests to a trackable number), and the support staff to point in the direction of specific threads.
Articulate is a connected company. I wouldn't be surprised if this very thread is getting some chat on the staff network;) The community staff is a vital part of paying attention to what's going on here so the development staff can focus on improving and shipping product.
Yes, the voting and visibility of priority has been a popular request. I, too, would love to see some kind of idea lab.
Other platforms I've seen that do this show the number of votes and chime in for [planned] to project that something is on the roadmap. In one such platform, I saw today that the highest number of votes are for things that haven't been implemented. Stuff that has the initial idea date of 2011:) Goes to show just because something gets a lot of votes, there's always space for reasoning to dump the priority.
Still, I love the idea of leveraging crowd sourcing to shape feature priority.
I wanted to let you know that Steve is correct that we do have processes in place that keeps us in constant communication with the development and quality assurances teams regarding feature requests. The request to have a public facing feature request page is certainly something we have discussed and will continue to discuss. We do see value in that, however there are also issues inherent with publicly exposing a feature request page.
We do often tell folks to submit feature requests. I can totally see why, from a customer's perspective, it might look like they are going into a black hole but I can assure you that we review each and every request that comes in. We have dedicated staff in each department that does review feature requests, including several members of my technical support team.
Justin, there would be an easy way to solve this problem... Just set up the button to mark an item as a feature request so that it is only visible to logged in users.
I have tested the published output and it works as expected. However when I try applying this to my project it does not work. The only difference I can see between the two projects is my version is published in Storyline 2 whilst the version Kumar has uploaded was published in Storyline 1.
Does anyone know of any new workarounds for Storyline 2 as it appears this is no longer supported...
I don't want to look like a lazy man, but I'm trying to make it works for two weeks.
Not trying to "make the others do your job", but if someone could do the code for me, so I can learn it and apply in my other projects, I would be very grateful.
The background image must be the "background.png".
Hi, Guilherme -- As this thread is a bit dated and Phil and some of the participants may no longer be subscribed, you are welcome to reach out to individuals directly using the 'Contact Me' link on their profile pages. Hopefully, someone will be able to chime in and assist you further with your question. :)
65 Replies
Funny. You haven't seen spammy Saturdays yet. That flag button is pretty handy to dim and eventually vote out of sight some of the "Watch this soccer game here" spam we get in large quantities some evenings and weekends.
I dig the idea of the like button / great idea / thumbs up as an addition.
Hi Dave,
Have a look at the attached file.
Note: Works only for html but not html5.
Hello Joseph!
We do have the Mark as Helpful button that can be used to show support for a particular comment in a thread.
Yes, Emily, I do know that you have the "Mark As Helpful" button but I was saying that you could use that little button bar to tag items which could be tracked for suggestions/improvements. Like a "Great Idea for Product Improvement" button. By allowing more than one person to click on it then it would serve as a vote button.
Hi Joseph,
That does sound like a good idea, but this would need to be submitted as a feature request. I know that is probably not what you want to hear.
It's just that I see so many of you staff folks saying, "Hey why not submit that for product improvement" but that doesn't give your community the opportunity to vote for something and no one actually KNOWS if they did submit it for a suggestion. People are awfully darn busy (I know I am), so that is why I am making this suggestion here. You're a staff member, Emily, why can't you do it for me if you think it's got value? And if you don't want to do it for me then at least make it easy for me to do so with a single button or allow others to promote the idea by clicking on the button to submit to Articulate as a suggestion. Why make people go to a separate form? Why not give this audience the chance to vote and know the item is submitted for improvement?
Hello Joseph,
I understand why this feature would be of value in the community. I wanted to share this recent thread here where this topic was discussed as well. This may give you some additional information regarding this particular feature.
You are totally correct about that, Emily. And do you really like having to make that recommendation so frequently? Wouldn't it make your job easier, too?
Wouldn't it be great if you agreed with an improvement and you could easily just vote for it right on the screen instead of saying, "Hey, go over here and fill out a form."
Wow, are they reading this?
The dev team does participate in the forum. I've seen quite a few instances of both dev team and dev ops jumping into threads. However, they don't have time to spend a lot of time here so they rely on the community managers, the feature requests (to document requests to a trackable number), and the support staff to point in the direction of specific threads.
Articulate is a connected company. I wouldn't be surprised if this very thread is getting some chat on the staff network;) The community staff is a vital part of paying attention to what's going on here so the development staff can focus on improving and shipping product.
Oh, good, Steve.
Yes, the voting and visibility of priority has been a popular request. I, too, would love to see some kind of idea lab.
Other platforms I've seen that do this show the number of votes and chime in for [planned] to project that something is on the roadmap. In one such platform, I saw today that the highest number of votes are for things that haven't been implemented. Stuff that has the initial idea date of 2011:) Goes to show just because something gets a lot of votes, there's always space for reasoning to dump the priority.
Still, I love the idea of leveraging crowd sourcing to shape feature priority.
I can't really mark your last comment as "LIKED" but I do like the comment.
Hi Joseph.
I wanted to let you know that Steve is correct that we do have processes in place that keeps us in constant communication with the development and quality assurances teams regarding feature requests. The request to have a public facing feature request page is certainly something we have discussed and will continue to discuss. We do see value in that, however there are also issues inherent with publicly exposing a feature request page.
We do often tell folks to submit feature requests. I can totally see why, from a customer's perspective, it might look like they are going into a black hole but I can assure you that we review each and every request that comes in. We have dedicated staff in each department that does review feature requests, including several members of my technical support team.
Justin, there would be an easy way to solve this problem... Just set up the button to mark an item as a feature request so that it is only visible to logged in users.
Hi Joseph.
This is certainly something we can take into consideration.
I have tested the published output and it works as expected. However when I try applying this to my project it does not work. The only difference I can see between the two projects is my version is published in Storyline 2 whilst the version Kumar has uploaded was published in Storyline 1.
Does anyone know of any new workarounds for Storyline 2 as it appears this is no longer supported...
Hi Phil,
I'm not aware of any threads with updates to this modification, but hope someone is able to pop into the forum to assist you!
I have sussed it now, I needed to change
var g_strWMode from window to transparent
var g_strWMode = "transparent";
All working :)
Thanks for that update Phil and hopefully it helps other who come across this thread using Storyline 2. :-)
Sorry Phil, but I couldn't make it happen here.
I changed the line with the var code, but the results weren't positives.
Maybe you have something to suggest so I can make my project work?
I'm using Storyline 2.
I don't want to look like a lazy man, but I'm trying to make it works for two weeks.
Not trying to "make the others do your job", but if someone could do the code for me, so I can learn it and apply in my other projects, I would be very grateful.
The background image must be the "background.png".
If someone can help me, thanks for that.
Hi, Guilherme -- As this thread is a bit dated and Phil and some of the participants may no longer be subscribed, you are welcome to reach out to individuals directly using the 'Contact Me' link on their profile pages. Hopefully, someone will be able to chime in and assist you further with your question. :)
Thanks for the hint, Christie.
;)
Hi,
Is there any way of setting a custom background image in a html5 file?
This discussion is closed. You can start a new discussion or contact Articulate Support.