Refine the styling of code elements so that they no longer have a
distracting blue outline. The style is now closer to the stock GitHub
look.
Closes gh-48
This commit removes all dark variants of hilight.js styles, as the
custom styles we're shipping with this project only work with light
variants.
Closes gh-40
See gh-25
Previously, Asciidoctor used spread for a full-width table but this
changed [1] to stretch in 1.5.7. As a result, a table that should be
full-width is not when using spring.css with Asciidoctor 1.5.7+.
This commit updates the CSS to apply 100% width to stretch. This is
done in addition to spread to avoid breaking backwards compatibility.
[1] https://github.com/asciidoctor/asciidoctor/issues/2589
* Update sample to include larger table (#16)
Update the sample table to show the issues discussed in #16.
* Improve table style (#16)
Update table CSS so that alternate rows are shaded and any
code blocks are styled.
I accounted for how to produce PDF and HTML when the two output types use separate code highlighters (it takes a separate task to do). I also documented a new feature that I added for Oleg Zhurakousky but that I am sure many of other proects (notably in Spring Cloud) can reasonably use, too.
I added a features section for it, since I suppose we'll get other features as time marches along.
If you add a role with a id of index-link, the href that you specify below that role ID becomes the link in the "Back to index" link in the table of contents.
The inserted role has the following form:
[#index-link]
https://spring.io
The URL can be any valid URL, whether relative or absolute.
This fix meets a need that Oleg Zhurakousky identified.
* Adding the Spring Style Guide
Per a request from Michael Minella, I'm adding the Spring Style Guide to spring-doc-resources, giving it a more sensible location than my personal account.
* Updated style guide
I know more about Asciidoctor than I did when I last modified the style guide, so I set up better Asciidoctor attributes. I also trimmed off a bit at the end.
This commit contains a few fixes for the CI release process.
The base CI image now installs the `jq` binary as it's
required by the promotion process.
The staging script is fixed to use the correct `sed` syntax
for this Linux container, and only consider Gradle as a build
system. This also changes the staging script to correctly
choose the release version depending on the release type.
This commit also adds a `RELEASE_TYPE` parameter to the state
task.
The project build version is moved to a `gradle.properties`
to align with the stage+promote script.
The promote release script is now executable.