Understanding the Scope of Customization Requests

Sometimes it's easier to understand what is not supported instead of jumping right into supported customizations. This is mostly helpul after you understand the sections we can and cannot customize.

An easy way to understand if your request is likely not covered by a Frontend Customization is to look at the URL of the page you are accessing. If it contains /admin, it's not a Frontend Customization - it's a Feature Request.

Here are some examples:

• Migration
• Swifty Customization
• Creating Custom Reports
• Implementing Features that are Backend Related
• Content Editing
• Removing Extra Formatting in Articles
• Adding / Removing / Adjusting options on the admin side of helpjuice, such as:
  • Article Editor
  • Settings section
  • Analytics section
  • Activities section
  • Users section
  • Dashboard
  • Files Manager section

If you can manage the options directly from the dashboard, even though they could also be managed via code, they are considered outside the scope of customizations. The reason is rather simple: you have control over the options with just a few clicks and don't need to wait for us to update the code for you.

An example of this would be uploading category icons. Since you can do this via dashboard, we won't accept requests for uploading icons. However, if there's an issue such as the icons not reflecting on the frontend despite being uploaded correctly, then it might require customization support as it could be a glitch or a technical issue beyond what can be managed through the dashboard alone. In such cases, a customization request would be accepted.

Here are some examples of frontend customizations not supported:

• Updating category icons
• Updating article subtitle/descriptions
• Creating redirects
• Creating different behaviors for different categories
• Creating too many different designs for categories
• Hardcoded sections should be avoided, since the code will need to be updated every time the section needs to be changed

As previously highlighted, your Knowledge Base offers extensive customization options, limited only by your imagination! While it's challenging to list every possibility, here are some great examples:

• Updating the design for the following page:
  • Home Page
  • Category Page
  • Article Page
  • Contact us Page
  • Thanks Page
  • Login/Forgot password Page
• Updating the design of standard sections, such as:
  • Most viewed articles
  • Recently added/updated articles
  • Followed articles
  • Search results design
• Default formatting for specific article components (won't be reflected on the article editor)
• Adding external libraries or plugins (preferable using JavaScript embed codes)
• Adding header/footer from other pages
• Brand-matching customization (colors, fonts, logos etc)
• Adding sidemenu/sidemap
• Adding Google analytics
• Adding/Removing Article Preview
• Adding/Removing Click to Zoom