Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 12 additions & 9 deletions user-manual/administer/static-pages.rst
Original file line number Diff line number Diff line change
Expand Up @@ -665,21 +665,24 @@ Examples of the Static pages menu in use
Styling static pages
====================

Basic styling of :term:`static pages <static page>` can be achieved in two ways.
Basic styling of :term:`static pages <static page>` can be achieved in two ways.

The first method is to use AtoM's Markdown_ formatting to style content. For
more information on formatting content using Markdown, see:
more information on formatting content using Markdown, see:

* :ref:`formatting`

The second method of styling AtoM static page content is by adding
HTML_ and inline CSS_ code to the static page's editable area. There are
plenty of online tutorials and resources out there for instruction on HTML and
inline CSS use, but a few basic examples commonly employed by AtoM users have
been included here as an example.

You can use a mix of Markdown and HTML in static pages. Note that HTML content
is **not** supported outside of static pages in AtoM.
HTML_ to the static page's editable area and calling BS5 or custom CSS_ classes
defined in theme's SCSS files. There are plenty of online tutorials and resources
out there for instruction on HTML and CSS use, but a few basic examples commonly
employed by AtoM users have been included here as an example.

.. note::
AtoM now enforces a :ref:`security-csp-headers` across the application.
As a result, inline CSS styles within static page content will no longer
be applied. Consider using Markdown formatting or BS5 classes instead where
styling is required.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add something to the effect of "CSP can be disabled which would allow inline scripts and styles to be used in static pages, but this is not recommended."?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so anvit and i have discussed that an experienced dev who understands the implications of CSP would know that disabling CSP is an option, but we don't want to openly suggest to users (who may not have a good technical background) that disabling CSP is an option. thoughts?


See below for instructions on how to use HTML to create and edit:

Expand Down
Loading