mirre-mt/masters-thesis
Archived
1
0
Fork 0
Code Releases 1 Activity

tex: enhance frontend section

Browse Source
This commit is contained in:
surtur 2023-08-14 18:33:47 +02:00
parent 53ffbb8bbf
commit 770141d01d
Signed by: wanderer
SSH Key Fingerprint: SHA256:MdCZyJ2sHLltrLBp0xQO0O1qTW9BT/xl5nXkDvhlMCI
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
tex/part-practical.tex
View File

@ -356,14 +356,18 @@ JavaScript.
\n{2}{Frontend}
Frontend-side, the application was styled using TailwindCSS, which promotes
using of flexible \emph{utility-first} classes in the markup (HTML) instead of
usage of flexible \emph{utility-first} classes in the markup (HTML) instead of
separating out the specific styles out into all-encompasing classes. The author
understands this is somewhat of a preference issue and does not hold hard
opinions in either direction, Tailwind simply looked nice, especially with its
built-in support for dark/light mode. The templates containing the CSS classes
need to be parsed by Tailwind in order to construct its final stylesheet and
there is also an original CLI tool for that called \texttt{tailwindcss}.
Overall, simple and accessible layouts had preference over convoluted ones.
opinions in either direction, however, a note has to be made that this approach
empirically allows for a rather quick UI prototyping. Tailwind was chosen
partially also because it \emph{looked} nice, had a reasonably detailed
documentation and offered built-in support for dark/light mode. The templates
containing the CSS classes need to be parsed by Tailwind in order to construct
its final stylesheet. Upstream provides the original CLI tool for that action
called \texttt{tailwindcss}. Overall, simple and accessible layouts had
preference over convoluted ones and data-backed effort was made to create
contrasting pages.
\n{3}{Frontend experiments}