Enhancements & Improvements
- TJ VanWert
- Kayla Ingersoll
Please Note 8/22/24: We have decided to start adding issues/requests directly into Jira backlog to make it easier to move requests into the workflow for the dev team. Follow the steps below to open Jira tickets.
Adding Jira Tickets: https://arinet.atlassian.net/jira/software/c/projects/ID/boards/609 < Go to project and click Create button at the top.
Below are the fields that need to be filled in when created a issue or request
Summary: Title of issue/request
Description: include all the details about the issue or request
Attachments: Any screenshots that would be pertinent to the request
Components: Sitesmith
Investment Type: Support
Goal: Operating Efficiency
Parent: Sitesmith: Enhancements & Improvements
Q1 2024
Request Status | What | Why | Example | Notes | Version |
|---|---|---|---|---|---|
complete In progress reviewed Requested | What enhancement, improvement, or bug do you have to report
| Why is this request important? Does it solve a workflow issue for the FED team, is it an improvement, is it a fix for something? | Provide a example. |
|
|
reviewed | Address link in header and footer were not linked to anything, but should be linking to directions to that location. | FED will need to fix this every time unless it is resolved at the source. I don’t remember if there is a spot in Sitesmith to implement a “Directions” link, but it can by default simply link to that. This should be true pretty much anywhere a full address is displayed, but especially in the header/footer. | Reported on and fixed on Colaw. | Reported by Kiwani on Colaw RV. @Kayla Ingersoll - this is a bigger thing we need to look at and determine what the best approach is so we can have consistency and have a good user experience for single location dealers vs multi location dealers. | 1.0 adding ticket |
reviewed / see notes | Site is populating without a favicon. | I am not sure if there’s a way for design to add this upfront before exporting, but if they don’t, that means FED has to create it and upload it later. It would be nice if we had a way for design to add this in during setup (I don’t know if it’s wise to automate this since some logos are not conducive to a favicon as-is). | Reported on Colaw, also true on Coumbs | Reported by Kiwani on Colaw RV. (TJ Note - design will need to create the favicon and it could be add as we typically done, its not viewed or approved by the client so we would just follow the same path that a favicon needs to be created by design and added) | 1.0 |
reviewed / See Notes | Staff page - creating a Staff Page Template that can be reused as a standard staff page. | it might be helpful for this page to have a template of some kind out of the box – might be good to discuss how we’d like to handle that and if we want the dealer to eventually be able to choose a staff page layout. | Reported on Colaw and Coumbs RV. Coumbs is still broken here: http://coumbsrv.interactrv.com/staff | This would be a system level product not SiteSmith related. (TJ Notes: We currently do not accomplish secondary pages within SS. It could be something in the future we look at doing, but Standard Staff pages could be created by fulfillment teams.) | 1.0 |
reviewed / In Discussion | Google fonts preloaded by default in <head> | This will make it easier for us to add and swap out fonts once it comes to FED. | Reported on Steve’s since we were specifically asked to change the font, but I believe all Sitesmith sites do not have this added by default | We are planning to try and introduce font variety after export, so it would be helpful to have an easy start point. | 1.0 |
reviewed / In Discussion | Additional, more expansive options for changing colors on sections beyond the “main” colors used on the site overall. | Design team would like the ability to be a little more selective on what colors are in sections aside from header/footer and have those choices potentially be different/override the “overall” color scheme in some scenarios. I think this would provide the design team the ability to be more creative and to keep sites looking different despite being the same template. Alternately, it would also be helpful to just have additional “default” theme color options besides the ones that pull already from the logo colors. | No specific example, but this was reported during revisions on Steve’s RV | Requested by Michael Grubbs | 1.0 |
In Progress | Indicator of saved progress existing on an account/an account being in use by someone else, and clear indicators that the changes to the account itself in Sitesmith have been saved when user clicks “Continue”. | There seems to be some confusion on these items that has resulted in 1) work on Sitesmith designs being overridden by someone who was not aware there was a saved setup there/multiple people being in the same account, and 2) work on Sitesmith being lost because users were not clear on whether their progress had been saved when pressing Continue. Something to make it easier to identify when both of those things have occurred to avoid overwriting and not saving properly would be helpful for the design and launch teams as they set up the site. | Michael Grubbs reported that progress was lost on Walnut Ridge because of one of these factors, but was not sure which one. | (TJ Notes - we are working on adding warning messages for user improvements, first iteration will not include a “saved” message, but warn messages for specific elements that have been updated in the backend and that will need to be updated as its using old code. More work will be done to improve other messages) | 1.0 |
complete | Bulk uploader for Sitesmith image library files in ICC | Design currently has to upload every image individually, which is time consuming when they are being asked to make a large group of images every week. | Michael Grubbs reported this in regards to being able to upload images. | (TJ Notes - we have the ability to bulk upload images into the SS library.) | 1.0 |
Reviewed | Add Tiktok icon to default social media selection | It is being requested frequently by clients and design is unable to add/FED needs to manually add every time it is requested | No example, but Michael B reported being asked for this often. |
| 2.0 adding ticket |
reviewed / on the list | Add Mega Menu option to Platinum builds | It would be good for clients to be able to see and adjust this feature in Sitesmith rather than waiting to see it until after FED has added it. | No example | Obviously, Mega Menu can be extensive and very dynamic. We are proposing that we use the most basic one (https://www.leisurenation.com/ ) to test this out with. | 2.0 adding ticket |
Requested | Allow more than 6 types in RV Types bar | There are some situations where we may need a larger number, but currently Sitesmith limits this to 6 types. | No specific example | While I think 6 works fine most of the time, there are situations where this is insufficient. For example, if a dealer wishes to break out Motorhomes into A/B/C, they’ve already used half their slots, and will likely want more than 3 more to cover the rest of their inventory. | 2.0 adding ticket |
Requested | Add “Site-Specific SRP/VDP” section back into CSS stylesheet | This is a section FED uses very frequently to maintain and adjust individual changes for SRPs and VDPs for dealers – things like hiding prices, payment styling, etc. Ensuring that we have this section set up in advance will be helpful for us to know where to put these changes on builds going forward. | Beckley’s RVs is an example where this is in place - line 3600 in the CSS | We don’t need anything special for this – just a line inserted that says “/*-- Site-Specific Styling For Listing & Detail Pages --*/” in the appropriate spot (currently under section called Detail V2 Inventory listing) | 2.0 adding ticket |
Requested | Allow SVG logos to be used in Sitesmith | Although it is an uncommon format, we do get this provided from the dealer from time to time. It is generally a better format/saves loading time as well, so it’s not a bad thing to have. This way, the project team (who does not have the training or access to the tools necessary to convert files like this) can simply upload the file without needing help to get it in a format that can be used. | Lovesick was the dealer that brought this to light | See related ticket on 2.0 bugs about logo not displaying properly on Lovesick | 2.0 Cannot reproduce issue, SVG are allowed for logos, we believe it was just the Lovesick logo that had the issue |
reviewed / In Discussion | Font customization in Sitesmith tool | Dealers do not feel the current default font (Arial) looks professional. Having a few different options would help both with making the output seem more customized, as well as improving the overall image of the mockup in the tool. | All sites are exporting with the same font currently | Design noted that while they’d prefer to have some options on font, simply using a different default font aside from Arial would also help with dealer approval. Some suggestions: Roboto, Lato, Montserrat | 2.0 adding ticket |
in progress | Multiple Shop Your Way/Popular Ways to Shop layouts | This is a common feature on sites that Sales show incoming dealers that get them excited about using them in their own designs. A frequent reason for needing a mockup is due to the fact that there are other appearances for this feature that feel more “premium” to dealers. | Obviously this will have to be something FED helps build out; if we think it’s feasible to add more versions of this to swap out, happy to help arrange getting that built out for you. | 2.0 Already in progress | |
Requested | Adjustment of overlay transparency on Hero | Design has noted that the standard “dark” overlay on the hero is often considered too dark by dealers and a common reason to need a mockup. If there was a way to adjust the percentage of overlay transparency manually this would be helpful for adjusting on a case-by-case basis for the hero image. | n/a |
| Will consider for future development |
Requested | Ability to layer images on hero | Design has noted that creating more complex hero setups that dealers are expecting is not possible currently as the options are simply to add a text header w/no font changes. It would be helpful if design could, within the Sitesmith tool, swap this text out to be an image, OR add an image to the side of the text. | Blue Compass (has logo image floating on top of hero image) General RV (currently has Hot Summer Sale image next to text and button) |
| Will consider for future development |
Requested | Generally allow for layout elements such as images and text to be added that overlap with other existing elements (or at least have some standardized spots that extra overlapping elements can be added to) | Design has cited that a common request from dealers that they feel makes a site look more premium is overlapping elements and elements that sit on top of other sections. Many sites that Sales are showing to incoming dealers feature elements of this kind, and dealers feel this makes for a more “premium” look. | Maxie Price RV (the “How Much Can I Tow” shape) General RV (the set of 3 RVs layered over the bottom of the background of the “Industry Leading Experience” section) Johnson RV (the hands icon on the Get Cash For Your RV CTA)
| Not sure how possible this is or what FED would need to build out in order for this to happen. I realize this is a more vague request, but being able to add layering elements (even if it’s just images and text) and have a couple options for positioning them on top of existing layout elements would be a huge help to design making more innovative and “premium” looking designs. | Will consider for future development |
Requested | Allow for non-image sections in layouts to have some options for textures/patterns in backgrounds | Having a texture or something a little more interesting than a plain color on a section is something that dealers feel gives them a more “premium” look. | PEI Home & RV (Banner & deals section has a textured background) |
| adding ticket |
ALL NEW REQUESTS SHOULD BE ADDED THROUGH Jira TICKETS | ALL NEW REQUESTS SHOULD BE ADDED THROUGH Jira TICKETS | ALL NEW REQUESTS SHOULD BE ADDED THROUGH Jira TICKETS | ALL NEW REQUESTS SHOULD BE ADDED THROUGH Jira TICKETS | ALL NEW REQUESTS SHOULD BE ADDED THROUGH Jira TICKETS |
|