* Initial commit; starting new design
Dropdown menu
* Begin docs layout of new design
* Get themes under control; button hover splash
* Some basic responsiveness
* Finish responsive layout; several bug fixes
* Avoid flash during color scheme change
* Begin building top of homepage
* docs: Start building quick-assist feature
* Work on homepage a little more
* Keep working on homepage
* More homepage progress
* Some sponsor SVGs
* Add sponsor features
* Implement basic Sponsor Experience box
* Reorganize some styles
* WIP sponsors page
* Start features page WIP
* Minor improvements
* Fix headings; work on features page
* WIP features page
* Continue work on marketing pages
* Continue work on features page
* More features WIP
* Continue features page...
* More work on features page
* Keeping going :)
* Continue home and features pages
* More homepage/features content, screenshots, tweaks
* Minor fixes to features page
* Minor tweaks
* Work on testimonials
* Work on homepage more
* More homepage work
* Continue work on homepage
* Add some sponsor logos
* Some citation screenshots
* Add citations
* Start making homepage responsive
* Re-add cache busting
Fix docs
* Use markdown syntax highlighting on frontpage
* Rework AJQuery to $_ to not interfere with jQuery
* Rewrite quick assist with AlpineJS, use markdown for contents
* More work on marketing pages
* Rebase and fix code displays
* Syntax highlight on-demand example, fix rollover
* Adjust on-demand demo
* Work on responsiveness
* Keep working on responsiveness
* Mainly finish making design responsive
* Thiccer favicon
* More work on marketing pages
* Keep on going
* Fix link
* Move new site into src folder
* Add open graph image
* Add recorded demo for homepage
* Tweak caption
* Fix Poppins font for now
* Minor tweaks
* Trim demo ending
* Remove unfinished pages
Also update Framer logo
---------
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
On Firefox, we were seeing an extra large horizontal scrollbar. Didn't happen on Chrome though. I think it's an edgecase bug with Firefox... but I think we can take a better approach that can avoid it anyways.
The CSS for `paper` classes was set up so that they would stack/overlap onto eachother. It was using `left: -100%;` and `left: -200%;` on `paper2` and `paper3`, to stack the next two on top of the first one, all three being relative positioned.
The problem comes because I think Firefox calculates the scrollbar width before relative positioning calculations come into play, so because the elements were rendered way off to the right before being moved over, it would "grow" the page really wide. Go to https://caddyserver.com/docs/ on any browser, element inspector, find `#paper2` and `.paper3`, uncheck the `left` CSS prop on both of those. You'll see that they render over to the right.
An alternate way to do the same thing is to use negative margins to stack the elements. I think margins are calculated earlier, so on Firefox this doesn't cause a scrollbar problem.
I did need to use a `calc()` unfortunately to get it pixel-perfect positioning compared to how it was before, because `#paper1` has `margin-left: 20px` and then `#paper2` inherits that margin so it needs to remove the extra 20px to realign. `calc()` is cheap though. It's fine.
Also, need `z-index: -1;` to make sure the BG papers go behind the page content.
In /docs/modules/, show both modules if module IDs are not globally unique.
Show both modules' docs on same page in expandable containers.
In /docs/json/, both modules appear in lists in the doc, but disambiguating them isn't implemented yet.
* doc(tls): Add the tls.client_auth Caddyfile directive doc
* doc(client_auth): Additional explanation for the client_auth example
* doc(client_auth): Add multiple trusted_ca directive notes
- Update the example as well
* Fine-tune tls docs formatting
Co-authored-by: Matthew Holt <mholt@users.noreply.github.com>
