{"id":16805,"date":"2022-01-26T16:04:41","date_gmt":"2022-01-26T21:04:41","guid":{"rendered":"https:\/\/carleton.ca\/webservices\/?p=16805"},"modified":"2024-06-08T09:43:36","modified_gmt":"2024-06-08T13:43:36","slug":"tips-for-submitting-great-feature-requests","status":"publish","type":"post","link":"https:\/\/carleton.ca\/webservices\/2022\/tips-for-submitting-great-feature-requests\/","title":{"rendered":"Tips for Submitting Great Feature Requests"},"content":{"rendered":"\n<section class=\"w-screen px-6 cu-section cu-section--white ml-offset-center md:px-8 lg:px-14\">\n    <div class=\"space-y-6 cu-max-w-child-5xl  md:space-y-10 cu-prose-first-last\">\n\n            <div class=\"cu-textmedia flex flex-col lg:flex-row mx-auto gap-6 md:gap-10 my-6 md:my-12 first:mt-0 max-w-5xl\">\n        <div class=\"justify-start cu-textmedia-content cu-prose-first-last\" style=\"flex: 0 0 100%;\">\n            <header class=\"font-light prose-xl cu-pageheader md:prose-2xl cu-component-updated cu-prose-first-last\">\n                                    <h1 class=\"cu-prose-first-last font-semibold !mt-2 mb-4 md:mb-6 relative after:absolute after:h-px after:bottom-0 after:bg-cu-red after:left-px text-3xl md:text-4xl lg:text-5xl lg:leading-[3.5rem] pb-5 after:w-10 text-cu-black-700 not-prose\">\n                        Tips for Submitting Great Feature Requests\n                    <\/h1>\n                \n                                \n                            <\/header>\n\n                    <\/div>\n\n            <\/div>\n\n    <\/div>\n<\/section>\n\n<p>At Web Services, it&#8217;s our goal to continuously improve all of the pages housed within Carleton.ca, and that means we always welcome your web suggestions and feature requests. In fact, we have a handy <a href=\"https:\/\/carleton.ca\/webservices\/support\/feature-request\/\">feature request form<\/a> just for that purpose. Please use it!<\/p>\n\n\n\n<p>That said, some feature requests are a better fit for Carleton.ca than others. We\u2019re more likely to successfully implement a new web feature if we fully understand the problem a new feature is trying to solve. As well, new web features should align with the look and feel of Carleton.ca, fit into our current web infrastructure, and serve all web managers at Carleton.<\/p>\n\n\n\n<p>As a potential requester of new web features, we want to set you up for success. We\u2019ve compiled a list of tips for submitting feature requests based on many years of experience within the Web Services team. Please use them as a guide the next time you submit a feature request.<\/p>\n\n\n\n<h2 id=\"understand-the-problem-youre-trying-to-solve\" class=\"wp-block-heading\">Understand the problem you\u2019re trying to solve<strong>&nbsp;<\/strong><\/h2>\n\n\n\n<p>When approaching Web Services about new web features, it\u2019s best to take the time to understand the problem you\u2019re trying to solve in advance. Some questions you can ask yourself include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What kinds of functionality would this new feature bring to our site?<\/li>\n\n\n\n<li>Would this new feature fill a gap for visitors to our site?<\/li>\n\n\n\n<li>Are we seeing lower web traffic in the absence of this feature?<\/li>\n<\/ul>\n\n\n\n<p>Spending the time to answer these questions will help you better communicate your needs and help us get to work finding solutions.<\/p>\n\n\n\n<p>About solutions. It\u2019s best not to approach us with a fixed solution already in mind, because there are many factors we need to consider before implementing new features. Flexibility is important for everyone involved. For best results, we recommend coming to us with your web-related problems and leaving the solutions to us.<\/p>\n\n\n\n<h2 id=\"try-to-avoid-the-allure-of-flashy-web-design\" class=\"wp-block-heading\">Try to avoid the allure of flashy web design<strong>&nbsp;<\/strong><\/h2>\n\n\n\n<p>There is no shortage of flashy page design on the web! We love slick websites \u2013 in fact, you\u2019ll see some very attractive web design as part of our <a href=\"https:\/\/carleton.ca\/webservices\/2021\/cutheme-almost-here\/\" target=\"_blank\" rel=\"noopener noreferrer\">upcoming cuTheme rollout<\/a>. That said, if a flashy new feature isn\u2019t in the service of solving a problem or fulfilling a need, it\u2019s likely not a great fit for Carleton.ca.<\/p>\n\n\n\n<h2 id=\"spotted-something-you-like-on-a-non-carleton-website-great-send-it-our-way\" class=\"wp-block-heading\">Spotted something you like on a non-Carleton website? Great, send it our way!<strong>&nbsp;<\/strong><\/h2>\n\n\n\n<p>We\u2019ll take a look at it and determine if there\u2019s a way to fit the feature into our development roadmap.<\/p>\n\n\n\n<p>But. And there\u2019s always a <em>but<\/em>. Understand that Carleton.ca is unique in many ways, and that features and solutions from other websites won\u2019t necessarily transfer over seamlessly. In that case, we\u2019ll work with you to find a solution that best fits your needs.<\/p>\n\n\n\n<h2 id=\"put-yourself-in-the-shoes-of-your-fellow-site-managers\" class=\"wp-block-heading\">Put yourself in the shoes of your fellow site managers<strong>&nbsp;<\/strong><\/h2>\n\n\n\n<p>When thinking about putting together a feature request to solve a web-related problem, put yourself in the shoes of your fellow site managers to see how they might see the problem. You might even want to start a dialogue with them to get their read on the issue before submitting your request. You\u2019ll be able to add their thoughts to your request and help us understand the scope of the problem.<\/p>\n\n\n\n<p>Taking the time to do this might mean your feature request has a positive impact on the entire university. And who knows? Maybe your co-workers will return the favour someday.<\/p>\n\n\n\n<p><strong>Have a question for Web Services? <a href=\"https:\/\/carleton.ca\/webservices\/support\/\">Contact us<\/a>!<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>At Web Services, it&#8217;s our goal to continuously improve all of the pages housed within Carleton.ca, and that means we always welcome your web suggestions and feature requests. In fact, we have a handy feature request form just for that purpose. Please use it! That said, some feature requests are a better fit for Carleton.ca [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":16807,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[369],"tags":[],"class_list":["post-16805","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-carleton-cms"],"acf":{"cu_post_thumbnail":""},"_links":{"self":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/16805","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/comments?post=16805"}],"version-history":[{"count":0,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/16805\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/media\/16807"}],"wp:attachment":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/media?parent=16805"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/categories?post=16805"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/tags?post=16805"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}