</la:link>
				<div
					class="navbar-form col-md-6 col-sm-8 col-7 mr-auto p-0"
					role="search">
					<div class="input-group">
						<la:text property="q" maxlength="1000" styleId="query"
							styleClass="form-control" autocomplete="off" />
						<span class="input-group-append">
							<button type="submit" name="search" id="searchButton"
								class="btn btn-primary">
								<em class="fa fa-search">

				</la:link>
				<div
					class="navbar-form col-md-6 col-sm-8 col-7 mr-auto p-0"
					role="search">
					<div class="input-group">
						<la:text property="q" maxlength="1000" styleId="query"
							styleClass="form-control" autocomplete="off" />
						<span class="input-group-append">
							<button type="submit" name="search" id="searchButton"
								class="btn btn-primary">
								<em class="fa fa-search">

Complex logic ahead...
We have three sets of values, in order of precedence (last wins):
1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).

                                                key="labels.dict_stemmeroverride_source"/></th>
                                        <td>${f:br(f:h(input))}<la:hidden property="input"/></td>
                                    </tr>
                                    <tr>
                                        <th><la:message key="labels.dict_stemmeroverride_target"/></th>

                                            key="labels.elevate_word_file"/></th></label>
                                    <div class="col-sm-9">
                                        <input type="file" id="elevateWordFile" name="elevateWordFile" class="form-control-file"/>
                                    </div>
                                </div>
                            </c:if>

                                            key="labels.dict_kuromoji_file"/></label>
                                    <div class="col-sm-9">
                                        <input type="file" id="kuromojiFile" name="kuromojiFile" class="form-control-file"/>
                                    </div>
                                </div>
                            </div>

				<la:message key="labels.page_not_found_title" />
			</h2>
			<div>
				<la:message key="labels.check_url" />
				<br /> ${f:h(url)}
			</div>
		</div>
	</main>
	<jsp:include page="../footer.jsp" />
	<input type="hidden" id="contextPath" value="<%=request.getContextPath()%>" />
	<script type="text/javascript"
		src="${fe:url('/js/jquery-3.6.3.min.js')}"></script>

        How has this issue affected you? What are you trying to accomplish?
        Providing context helps us come up with a solution that is most useful in the real world
    validations:
      required: false
  - type: input
    id: page
    attributes:
      label: Page with the problem
      description: Please, provide a link to the relevant documentation page
    validations:

								<la:message key="labels.index_form_option_btn" />
							</button>
						</div>
					</fieldset>
				</div>
			</div>
		</main>
		<jsp:include page="footer.jsp" />
	</la:form>
	<input type="hidden" id="contextPath" value="${contextPath}" />
	<script type="text/javascript"
		src="${fe:url('/js/jquery-3.6.3.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/bootstrap.min.js')}"></script>

Complex logic ahead...
We have three sets of values, in order of precedence (last wins):
1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).