generated from leonetienne/LaTeX-Paper-template
feat: digitization
This commit is contained in:
@@ -5,6 +5,29 @@
|
||||
\chapter{Glossar}
|
||||
|
||||
\begin{description}
|
||||
|
||||
\item [Frontend] \hfill \\
|
||||
\quotecite{Das Frontend einer Webseite ist der Teil der Webseite, der Endnutzern präsentiert wird. Ein Frontend besteht aus HTML und Cascading Style Sheets} \cite{bib:udjaja}.
|
||||
|
||||
\item [TYPO3-Backend] \hfill \\
|
||||
\quotecite{The backend's main role is to enable users to create and publish
|
||||
content for their site.
|
||||
The backend is also used to configure a TYPO3 installation. Domains,
|
||||
languages and other information that determine how a site behaves are managed
|
||||
via the backend. Tasks such as adding backend users and managing
|
||||
third-party extensions also take place in the backend.
|
||||
} \cite{bib:typo3-docs-concepts}.
|
||||
|
||||
\item [TYPO3-Extension] \hfill \\
|
||||
\quotecite{Developed by the community, extensions provide a range of solutions that
|
||||
help extend TYPO3} \cite{bib:typo3-docs-concepts}.
|
||||
|
||||
\item [TYPO3-Plugin] \hfill \\
|
||||
\quotecite{Plugins are a specific type of content elements [...]
|
||||
Plugins often use additional database tables which contain records which
|
||||
are dynamically displayed via the plugin - often in a list view, a
|
||||
single view, optionally with pagination and search functionality.
|
||||
An extension may provide several plugins, each with a dedicated function,
|
||||
such as the list view.} \cite{bib:typo3-docs-content-elements-plugins-introduction}
|
||||
|
||||
\end{description}
|
||||
|
||||
Reference in New Issue
Block a user