projects/fipamo
projects/fipamo
1
0
Fork 0
Code Issues 4 Pull requests Projects Releases 24 Packages Wiki Activity Actions
fipamo/resources/views/includes/submenu-start.blade.php

12 lines
541 B
PHP
Raw Normal View History

Started template conversion Brought over a template from the old build to see how the conversion process would go (it's not bad) and see if the CSS would still stick (it did) The wiring will be finished when the auth class is completed
2024-03-01 18:16:24 -06:00
<div class="submenu">
removed nested buttons from href tags #105 main navigation had buttons nested inside of href tags to house previous font icons that were removed, so the nesting is no longer needed and it could introduce accessibility propblems, so it needed to be cleande up now they are hrefs styled as the previous buttons so there is no visual change in the UI
2024-05-08 13:23:42 -06:00
<a class="main-nav-primary" href='/dashboard/pages' title="view pages">
<svg id="option-menu-pin" class="icon">
reorganized text editor moved page meta data to it's own ui to clean up the page editing experience as it was becoming a bit crowded. also moved to saving and deleting buttons to title bar so they are always available added a note to web routes to reorganize them within the web routes file to reduce the confusion present by having them in their own Controllers. it's just an extra layer that's not needed
2025-05-12 13:12:58 -06:00
<use id="option-menu-pin" xlink:href="/assets/images/global/sprite.svg#minicute-book" />
removed nested buttons from href tags #105 main navigation had buttons nested inside of href tags to house previous font icons that were removed, so the nesting is no longer needed and it could introduce accessibility propblems, so it needed to be cleande up now they are hrefs styled as the previous buttons so there is no visual change in the UI
2024-05-08 13:23:42 -06:00
</svg>
Started template conversion Brought over a template from the old build to see how the conversion process would go (it's not bad) and see if the CSS would still stick (it did) The wiring will be finished when the auth class is completed
2024-03-01 18:16:24 -06:00
</a>
removed nested buttons from href tags #105 main navigation had buttons nested inside of href tags to house previous font icons that were removed, so the nesting is no longer needed and it could introduce accessibility propblems, so it needed to be cleande up now they are hrefs styled as the previous buttons so there is no visual change in the UI
2024-05-08 13:23:42 -06:00
<a class="main-nav-primary" href='/dashboard/page/add/new' title="add new page">
<svg id="option-menu-pin" class="icon">
reorganized text editor moved page meta data to it's own ui to clean up the page editing experience as it was becoming a bit crowded. also moved to saving and deleting buttons to title bar so they are always available added a note to web routes to reorganize them within the web routes file to reduce the confusion present by having them in their own Controllers. it's just an extra layer that's not needed
2025-05-12 13:12:58 -06:00
<use id="option-menu-pin" xlink:href="/assets/images/global/sprite.svg#entypo-squared-plus" />
removed nested buttons from href tags #105 main navigation had buttons nested inside of href tags to house previous font icons that were removed, so the nesting is no longer needed and it could introduce accessibility propblems, so it needed to be cleande up now they are hrefs styled as the previous buttons so there is no visual change in the UI
2024-05-08 13:23:42 -06:00
</svg>
Started template conversion Brought over a template from the old build to see how the conversion process would go (it's not bad) and see if the CSS would still stick (it did) The wiring will be finished when the auth class is completed
2024-03-01 18:16:24 -06:00
</a>
reorganized text editor moved page meta data to it's own ui to clean up the page editing experience as it was becoming a bit crowded. also moved to saving and deleting buttons to title bar so they are always available added a note to web routes to reorganize them within the web routes file to reduce the confusion present by having them in their own Controllers. it's just an extra layer that's not needed
2025-05-12 13:12:58 -06:00
</div>
Reference in a new issue Copy permalink