move sample files to examples directory
simple book sample files
add cli book option
generate book -- title page not yet handled
refactor book creation
add title page, filename: title or _title
add README info about epub library tech debt
update README with --book, increment version 0.1.6)
I believe this used to work -- looking at the code, there seems to be a route and views, but when I got to the URL I see:
related issue: https://github.com/bridgefoundry/bridgefoundry.github.io/issues/28 -- which I think was partially implemented before (and issue doesn't appear to have been updated)
right now it is on ultrasaurus.com -- not a big deal since it is shared with all the right people, but we should move it over someday: https://docs.google.com/a/ultrasaurus.com/forms/d/1gu6WG2Nifj_579VhML_KZWpvi0bM0YpqsgZptSmU6Lw/viewform
here's the current form: https://docs.google.com/forms/d/e/1FAIpQLSeMDxwJHTYuvBV0V9d_EFaFgKsStpt-5VA_kiQveCJRxk20hw/viewform
linked from: https://operations.bridgefoundry.org/fundraising/invoice-request/
unfortunately, this is a copy of the text in the CNCF TOC repo: https://github.com/cncf/toc/blob/main/tags/security-charter.md -- @JustinCappos would you be up for making the change there too?
I was trying out https://github.com/lise-henry/epub-builder and thought I would try your fixed example in my epub reader.
Here's a simple fix to the invalid HTML which allows the output to be opened in iBooks.
Thanks for making this PR!
This is an example of what I think is a typical use case:
The TOC appears with an entry for the TOC itself, which I don't think is the desired behavior:
I've been advised by lawyers long ago that code licenses (like MIT, and maybe Apache) aren't appropriate for "content" -- for RailsBridge documentation lawyer advised that we specifically say code was MIT and course material was some appropriate Creative Commons license. We need to explicitly think about the context for a CC-BY (e.g. what if our text was used by a group that did not share our values, just as a white supremacist organization, how would we want it to be attributed? might be worth specifying text to be included as attribution)
I think there are two reasons to include an example:
For this library in particular, as is, a developer needs to dive deep into
jmdict documentation elsewhere to understand what the library offers. This is fine, of course, and maybe the intent of this library is for people who understand jmdict deeply.
I thought an illustration of a dictionary entry would represent a typical use case. Maybe it could replace the other example and serve both goals?
yaml front matter, refactor file processing
Document can represent Markdown or Other (for images, etc) This pushes more of the logic into Document implementation instead of Web not sure whether this is the right direction in long-term seems to make code easier to manage for now
bump version - 0.1.5 yaml front matter support
seems to work!
Set a default password for postgres
Change format of matrix values
Maybe this would give better names to each job?
Make sure FORCE_POSTGRES env variable is available to other steps
Use different bundler cache depending on
So that we're using postgres for tests when appropriate.
Set up database for testing
Map postgres to port 5432
Set username and password for test database
Reformat database options for matrix config
This way, jobs will specify which database we're using as opposed to "true" or "false" to indicate forced postgres.
Use bin/rake for setting up parallel tests instead of bundle exec
Don't fail other jobs in the matrix if one of them fails
Refer to new matrix key name for caching gems
Merge pull request #1279 from railsbridge/mx/fix-ci
Update CI workflow configuration
This pull requests fixes our CI builds by configuring our postgres setup, which includes specifying the user, password, and port, in order to connect to the database correctly.
These commits also cover a few small formatting updates for consistency and clarity on what kind of job is running.
upgrade ruby to 2.7.7, replace backbone gem
Replace Travis CI setup with GitHub Actions
Since we're no longer using Travis CI, this is an attempt to introduce a GitHub Actions workflow that matches as close to the Travis setup as possible in hopes of fully replacing the original setup.
Remove vendored Bower components
Since they're not needed.
Merge pull request #1278 from ultrasaurus/bb-alt
upgrade ruby to 2.7.7, replace backbone gem