Being able to point to this one css instead of individually at each one
will make it easier in the future to make changes to the stylesheets
without breaking things like the docs build.
This hasn't worked for a few years (since 900946df) and nobody has
complained. Getting rid of it allows similifying a few things on the
search server side as well.
Borrowing from 5112187fa[1] in the pgeu-system codebase,
this returns the ability to bold text within pgweb by ensuring
the Open Sans heavier fonts are loaded.
To accomplish this, this patch includes a few more changes:
- Normalize the heavier weights under 400, 600, 800.
- Ensure any font-weight settings using Open Sans match the
standards listed above.
- An adjutsment on the event archive page to ensure the font
weights are not too bold.
[1] https://git.postgresql.org/gitweb/?p=pgeu-system.git;a=commit;h=5112187fac45e0bcadb34e61c6e3e0ac398a5df3
There were cases that the fixed width for this box would cause the
thread selector to explode outside of the email header table in the
thread viewer. We should keep the select dropdown itself to the width
of the overall list of email addresses in the chain.
Multi-paragraph statements in the warning/caution/note/tip boxes
were being smushed together due to the removal of paragraph
margins. It is still essential to remove the paragraph margin
on the final paragraph, which is accounted for in this change.
Reported by: Peter Geoghegan <pg@bowt.ie>
* Move links to current manuals to /docs/, decommission /docs/manuals/
* Add link to /docs/current/ with a large button
* Add links to /docs/devel/ at the bottom of the version table
* Remove translated manuals from left nav menu, since they are in the
right one
* Remove redundant wording around "comprehensive manual"
* Clean up some incorrect template tags
Discussion: https://www.postgresql.org/message-id/CABUevEymaWDL4JywHxBDBATUUPPrAf4_tGwin4CtGFdQ5tx5Hg@mail.gmail.com
* Get rid of the django_markwhat dependency, and implement our own
classes to get more control. In passing also remove django-markdown,
because we never used that.
* Instead of trying to clean markdown with regexps, use the bleach
library (NEW DEPENDENCY) with special whitelisting of allowed tags
based off standard markdown. This means that one can input links or
formatting in HTML if one prefers, as long as it renders to the same
subset of tags that markdown allows.
* Replace javascript based client side preview with an actual call to a
preview URL that renders the exact result using the same function,
since the use of showdown on the client was increasingly starting to
differ from the server, and since that cannot be kept secure the same
way. Rewrite the client side javascript to work better with the now
longer interval between updates of the preview.
Long in planning, but never got around to it.
Suggestion to use bleach for escaping from David Fetter.
* Add a fa icon for tags to the buttons that are clicked for news tags,
to make it more clear what they are.
* Show a badge with the tag on each item when browsing the list.
* Change the buttons to be badges when viewing an individual item, and
move them to the top of the page instead of the bottom for consistency
with the listing.
In passing, add some spacing between the header and the text when
viewing a news item, because it looks a lot better.
Up to bootstrap 4.4.1 containing a lot of fixes.
While at it, put the version in the filenames, so we don't have to
cache-bust them every time we modify something unrelated, since they do
have well defined versions.
We apparently had some old /admin/ code that used an old version of
jquery-ui, but AFAICT we don't have that anymore. So remove teh loading
of them and also the files, so we have just one version of jquery
around.
When a news article is approved, it gets delivered as an email to the
pgsql-announce mailinglist. It will render the markdown of the news
article into a HTML part of the email, and include the markdown raw as
the text part (for those unable or unwilling to read html mail).
For each organisation, a mail template can be specified. Initially only
two templates are supported, one "default" and one "pgproject" which is
for official project news. The intention is *not* to provide generic
templates, but we may want to extend this to certain related projects in
the future *maybe* (such as regional NPOs).
These templates are stored in templates/news/mail/*.html, and for each
template *all* images found in templates/news/mail/img.<template>/ will
be attached to the email. "Conditional image inclusion" currently not
supported.
To do CSS inlining on top of the markdown output, module pynliner is now
required (available in the python3-pynliner package on Debian).
A testing script is added as news_send_email.py in order to easier test
out templates. This is *not* intended for production sending, so it will
for example send unmoderated news. By sending, it adds it to the
outgoing mailqueue in the system, so unless the cronjob is set up to
send, nothing will happen until that is run manually.
Support is included for tagged delivery using pglister, by directly
mapping NewsTags to pglister tags.
While at it, update the moderation preview forms to preview news items
using the HTML template for the email (while leaving other types of
items previewing without a particular stylesheet).
This includes a number of new features:
* Move some moderation functionality into shared places, so we don't
keep re-inventing the wheel.
* Implement three-state moderation, where the submitter can edit their
item and then explicitly say "i'm done, please moderate this now".
This is currently only implemented for News, but done in a reusable
way.
* Move moderation workflow to it's own set of URLs instead of
overloading it on the general admin interface. Admin interface remains
for editing things, but these are now separated out into separate
things.
* Do proper stylesheet clearing for moderation of markdown fields, using
a dynamic sandboxed iframe, so it's not ruined by the /admin/ css.
* Move moderation email notification into dedicated moderation code,
thereby simplifying the admin subclassing we did which was in some
places quite fragile.
* Reset date of news postings to the date of their approval, when
approved. This avoids some annoying ordering issues.
- Don't use inline event handlers
- Simplify some of the wording
- Replace the package download list with nice buttons
Design by me & Jonathan, code by me, review by Jonathan and others.
Instead of a weirdly located "hover over the checkbox to get a
description" message, put the actual description underneath the
checkboxes. This removes the need for javascript for it, and make the
description a lot more readily available.
This applies only to news tags for now, since that's the only use of
described checkboxes, but hopefully it will make those more clear to
people submitting.
In passing, fix how help_text for multi-checkbox field is shown -- it
was previously shown almost as part of the field name itself, making it
very hard to make out. Now make it look like all other form field help
texts.
* Merge all commands into a single text area for ease of copy/paste.
* Add a Copy Script button to each text area to copy the script (without comments and blanks) to the clipboard.
* Centralise the copy/paste code so it can be used elsewhere.
* Always install the database server.
Based on reviews/discussion with Magnus, Jonathan, Daniel and Sehrope.
As part of the ongoing effort to make the documentation
both easier to read visually and more friendly for the
PDF building, there have been improvements to the layout
of the reference tables.
This set of changes focuses on the catalog tables that
detail the information in the different PostgreSQL catalogs.
There is also a small adjustment for the function tables, as
one of the CSS classes was renamed in the SGML source.
Author: Tom Lane <tgl@sss.pgh.pa.us>
The new documentation contains a new look & feel for how functions
and operator information are displayed, but this requires some
adjustments to the stylesheet.
This also removes from of the "!important" tags that are used
in top-level parts of the code, as we do not want those to cascade
down to lower layers of the stylesheets.
This helps to ensure readability of the new function table listings
while working around some of the generated code from DocBook
Authors: Tom Lane <tgl@sss.pgh.pa.us> and myself
As the align/valign attributets are deprecated in HTML 5 and as our
documentation generation scripts still spit these out, these selectors
will ensure compatibility, and also fix present alignment issues.
As part of ongoing changes to the structure of tables in the
documentation[1], the HTML property valign is being set to middle
in the table headers, but was not being respected in the pgweb CSS
rules.
This adjusts the table headers to respect the valign property, which
in testing works with both the latest documentation as well as previous
versions (and given most, if not all, table headers to date are not
multi-lined).
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=e894c61836e4b967f7ec65358fdaed2ba86ed238
The main.css file had inconsistent whitespacing throughout, including a
mixture of tabs / spaces as well as different intervals of 2 / 4.
This patch brings the formatting to use 2 spaces at a time for each indent,
which is consistent with generally accepted best practices.
This creates a consolidated area to reference all of the notes from
previous releases of PostgreSQL, as current releases only keep the
the notes for that specific major release of PostgreSQL.
From user feedback, the scrolling navigation bar would cause problems with
readability, especially in larger font views. This keeps the navigation bar
pinned to the top, until we can find a way to more easily handle this.
This was an regression introduced by the new styles that affects
readability of nested variables lists (e.g. on the message protocol
page). This brings the look more in line with the previous documentation
styles and should help with readability.
In some situations, this would make it look like some directives
required spaces (e.g. .pgpass file set up), which would be incorrect.
Reported By: Vik Fearing
This patch brings the web-based documentation to match the current styles
on the main postgresql.org website. The CSS supports the generated markup
from the main PostgreSQL documentation and supports the new/old class
that are visible in the documentation (e.g. uppercase classes pre-v10).
Authors: Sarah Conway, Jonathan Katz
