fixed typo on twitter app creation

Author: johndoe12312

docs/asciidoctor-reveal.js-master/.gitignore

@@ -3,19 +3,29 @@
 
 # test stuff
 /examples/*.html
+!/examples/docinfo*.html
+!/examples/*docinfo-revealjs.html
 /examples/reveal.js/
 /examples/node_modules
 
 # node stuff
 node_modules/
 npm-debug.log
 build/
-/dist/main.js
+/dist/
 /asciidoctor-reveal.js-*.tgz
 
 # ruby stuff
 /.bundle/
 /Gemfile.lock
 
-# the compiled slim template
+# the compiled slim template, committed only on releases to avoid noise
 /lib/asciidoctor-revealjs/converter.rb
+
+# ignored tests
+# - coderay is unsupported on JRuby
+test/doctest/source-coderay.html
+# - pygments is unsupported on JRuby
+test/doctest/source-pygments.html
+# - contains invalid content
+test/doctest/with-docinfo-shared.html

docs/asciidoctor-reveal.js-master/.travis.yml

@@ -1,16 +1,14 @@
-sudo: false
 git:
   # use depth 2 just in case two refs get pushed at once (like a tag)
   depth: 2
 language: ruby
 node_js: lts/*
 rvm:
+- 2.6
 - 2.5
 - 2.4
 - 2.3
-- 2.2
-- 2.1
-- jruby-9k
+- jruby-9.2.9.0
 gemfile:
 - Gemfile
 - Gemfile.upstream
@@ -20,13 +18,11 @@ env:
   - NOKOGIRI_USE_SYSTEM_LIBRARIES=true
 script:
 - bundle exec rake build
-- bundle exec rake doctest
+- bundle exec rake test
 - bundle exec rake examples:convert
 - npm install
-- bundle exec rake build:converter:opal
-- npm run build
+- bundle exec rake build:js
 - npm run examples
 - npm test
-
 notifications:
   email: false

docs/asciidoctor-reveal.js-master/CHANGELOG.adoc

@@ -2,3 +2,5 @@ source 'https://rubygems.org'
 
 # Specify your gem's dependencies in asciidoctor-revealjs.gemspec
 gemspec
+# Asciidoctor.js 2.0.0 requires an unreleased Opal 0.11.99.dev (d136ea8)
+gem 'opal', :git => 'https://github.com/opal/opal.git', :ref => 'd136ea8'

docs/asciidoctor-reveal.js-master/Gemfile

@@ -3,3 +3,5 @@
 source 'https://rubygems.org'
 gemspec
 gem 'asciidoctor', :git => 'https://github.com/asciidoctor/asciidoctor', :branch => 'master'
+# Asciidoctor.js 2.0.0 requires an unreleased Opal 0.11.99.dev (d136ea8)
+gem 'opal', :git => 'https://github.com/opal/opal.git', :ref => 'd136ea8'

docs/asciidoctor-reveal.js-master/Gemfile.upstream

@@ -4,6 +4,21 @@
 
 Short instructions that aim to help potential contributors.
 
+== Getting Started
+
+* Setup the Asciidoctor-revealjs plugin in <<ruby-localversion,development mode>>
+* Modify the http://slim-lang.com/[slim templates] in `templates/`
+* Templates need to be compiled before being used, do so with:
+
+    bundle exec rake build
+
+* Then using the following command will render slides with your template changes baked in:
+
+    bundle exec asciidoctor-revealjs <source.adoc>
+
+The next section will provide further help on how to use `print` statements or a debugger to assist development.
+
+
 == Inspect the template system
 
 To understand what you have access to in templates you can inject some ruby.
@@ -15,9 +30,8 @@ Two complementary approaches can be used to explore the context offered by ascii
 
 [NOTE]
 --
-Starting with v1.1.0 the slim templates are compiled to Ruby in order to
-use the same templates from Asciidoctor.js (Javascript / Node.js ecosystem).
-Don't forget to recompile the templates if you make changes to them.
+Debugging is only supported via the Ruby ecosystem.
+You need to recompile the templates when you make changes to them.
 This can be done by running:
 
     bundle exec rake build
@@ -65,6 +79,10 @@ In order to be dropped into the debugger at a specific point in a template simpl
 - binding.pry
 ----
 
+Recompile the templates with:
+
+    bundle exec rake build
+
 Then run `asciidoctor-revealjs` from the command-line to generate your document and you'll be dropped in the debugger:
 
 ----
@@ -96,13 +114,11 @@ You can also query asciidoctor's documentation:
 If you install the `pry-byebug` gem you get additional debugging capabilities.
 See the gem's documentation for details.
 
-Since 1.1.0, templates are compiled. It is easier to inject the debug
-triggering statements and use the templates directly instead of debugging
-compiled templates. You can call the slim templates directly with:
+Since 1.1.0, templates are compiled.
+It is easier to inject the debug triggering statements and use the templates directly instead of debugging compiled templates.
+You can call the slim templates directly with:
 
-// TODO it's still not clear whether `-r slim-htag` is required right now (#153)
-
-    bundle exec asciidoctor --trace -T templates/ examples/customcss.adoc
+    bundle exec asciidoctor-revealjs --trace -T templates/ examples/customcss.adoc
 
 === References
 
@@ -124,22 +140,22 @@ done with `bundler`:
     bundle --path=.bundle/gems --binstubs=.bundle/.bin
     bundle exec rake build
 
-Go to `test/output/slim/` folder and install `reveal.js`:
+Go to `test/doctest` folder and install `reveal.js`:
 
-    cd test/output/slim/
+    cd test/doctest/
     git clone https://github.com/hakimel/reveal.js.git
 
 === Render tests into .html
 
 From the project's root directory:
 
-    bundle exec rake generate FORCE=yes
+    bundle exec rake doctest::generate FORCE=yes
 
 === Open rendered files
 
 NOTE: Right now, https://github.com/asciidoctor/asciidoctor-doctest/issues/12[doctest issue #12] means that the generated examples will not be pretty.
 
-You can open the generated `.html` in `test/output/slim/` in a Web browser.
+You can open the generated `.html` in `test/doctest/` in a Web browser.
 
 
 == Asciidoctor API's gotchas
@@ -192,12 +208,14 @@ Well, for most people.
 
 === Work-in-progress pull-requests
 
-If you prepend "WIP" in front of your pull request we will understand that it is not complete and we will not merge it before you remove the WIP string.
+Letting know to the maintainers that you are working on a feature or a fix is useful.
+Early communication often times save time consuming mistakes or avoids duplicated effort.
+We encourage contributors to communicate with us early.
 
-This is useful to let people know that you are working on stuff.
-Branches are not that visible otherwise but pull requests are.
+Branches on forks of this project are not very visible to maintainers as much as pull requests (PR).
+For this reason we used to recommend sending a PR even if it's not ready and prepend "WIP" in front of its name to let everyone see that you are working on a specific topic.
+Now, instead of prepending "WIP", we recommend using GitHub "draft pull request" feature instead.
 
-You might even be able to get some feedback early which could save you some time.
 
 === 'needs review' label
 
@@ -211,8 +229,7 @@ Makes triaging easier.
 
 In order to test the Node package, you first need to build the converter into Javascript and create a tarball of the project.
 
-  $ bundle exec rake build:converter:opal
-  $ npm run build
+  $ bundle exec rake build:js
   $ npm pack
 
 That last command will produce a file named `asciidoctor-reveal.js-<version>.tgz` in the working directory.
@@ -230,16 +247,47 @@ NOTE: The relative portion of the last command is where you are installing the l
 
 Then proceed as documented in the `README.adoc`.
 
-=== Upgrade Asciidoctor.js version
+[[node-binary-compatibility]]
+=== Binary package compatibility with Asciidoctor.js
+
+Asciidoctor.js is source-to-source compiled into JavaScript from Ruby using Opal.
+The JavaScript generated requires a specific version of the Opal-runtime for it to work with Node.js.
+This project is source-to-source compiled into JavaScript from Ruby using Opal too.
+In order for Asciidoctor.js to be able to call code from this converter, the versions of Opal (both runtime and compiler) must be compatible.
+Right now we track the exact git revision of Opal used by Asciidoctor.js and make sure that we match.
+Here is how:
+
+Versions known to work together can be found by looking at the Asciidoctor.js release notes, just replace <tag> with the `asciidoctor.js` release you are interested in: https://github.com/asciidoctor/asciidoctor.js/releases/tag/<tag>.
+Then that Opal version and git revision (if required) must be specified in `asciidoctor-revealjs.gemspec`.
+
+Starting with 3.0.0 we aim to retain binary compatibility between Asciidoctor.js and Asciidoctor-reveal.js.
+This should allow other Asciidoctor extensions to be called along with this converter.
+Asciidoctor.js is no longer a direct dependency but should be seen as a tool that powers this converter.
+We need to allow users to have flexibility in the version they choose to run.
+Asciidoctor.js maintainer told us that he is going to consider binary package incompatibility a major break and so we adjusted our README to tell users to install with a specific version range.
+
+We will track and maintain the README on the major version supported and recommended:
+
+* In the link:README.adoc#node-install[version range to install by default] for a given release (and on master)
+* In the link:README.adoc#asciidoctorjs-compatibility-matrix[compatibility matrix]
+
+See https://github.com/asciidoctor/asciidoctor-reveal.js/issues/187#issuecomment-570771473[this issue] for background details on that topic.
+
+Asciidoctor.js versioning policy is https://asciidoctor-docs.netlify.com/asciidoctor.js/project/version-and-lifecycle-policies/[available here].
+
+=== Debugging
+
+To debug the JavaScript application, just add `--node-arg=--inspect-brk` to the npx command to run the application.
+For example:
+
+  npx --node-arg=--inspect-brk asciidoctor-revealjs -v presentation.adoc
+
+Then open the Chrome Dev Tools and click on the Node logo in the top left corner.
 
-WARNING: It is important to track `Asciidoctor.js` and `bestikk-opal-compiler` versions together.
-The `opal-compiler` used to compile our node package must match `asciidoctor.js` `opal-runtime`.
-The former is explicitly installed by users on install and the later is specified in our `package.json`.
-When you update one remember to update the other.
-Versions known to work together can be found here, just replace <tag> with the `asciidoctor.js` release you are interested in: https://github.com/asciidoctor/asciidoctor.js/blob/<tag>/package.json
 
 == RubyGem package
 
+[[ruby-localversion]]
 === Test a local asciidoctor-revealjs version
 
 Compile the converter:
@@ -258,44 +306,82 @@ Then run:
 
 == Release process
 
+
+. Make sure that the highlight plugin code embed in _lib/asciidoctor-revealjs/highlightjs.rb_ is up-to-date with the version of reveal.js
+. Do we need to do anything regarding our Opal dependency and Asciidoctor.js?
+  See <<node-binary-compatibility,our section on the topic>>.
+. Update dependencies and test the package in both languages
++
+    bundle update
+    bundle exec rake build
+    bundle exec rake test
+    bundle exec rake examples:convert
+    npm install
+    npm update
+    bundle exec rake build:js
+    npm test
+    npm run examples
+
+. Commit the updated dependencies
 . Update the version in `lib/asciidoctor-revealjs/version.rb` and `package.json`
 . Update the changelog
 ** Generate author list with:
 +
     git log <prev-version-tag>.. --format="%aN" --reverse | perl -e 'my %dedupe; while (<STDIN>) { print unless $dedupe{$_}++}' | sort
 
 . Prepare release commit
+** Add the "Slim compiled to Ruby" converter to the git tree (otherwise ignored to avoid noise to the repo)
++
+    bundle exec rake build
+    git add -f lib/asciidoctor-revealjs/converter.rb
+
 ** commit msg: Prepare %version% release
 ** release commit (--allow-empty) msg: Release %version%
 . Tag the release commit
 ** Annotated Tag msg: Version %version%
 . Push your changes (including the tag)
 . Make a release on github (from changelog and copy from previous releases)
+** Useful vim regex for AsciiDoc to Markdown:
++
+    :%s/{uri-issue}\(\d\+\)\[#\d\+]/#\1/gc
+    :%s/{project-name}/asciidoctor-reveal.js/gc
+    :%s/\(.*\)::/### \1/gc
+    :%s/{uri-repo}/https:\/\/github.com\/asciidoctor\/asciidoctor-reveal.js/gc
+
+** Save as draft
+
 . Pushing the gem on rubygems.org:
 +
  $ bundle exec rake build
  $ gem build asciidoctor-revealjs.gemspec
  $ gem push asciidoctor-revealjs-X.Y.Z.gem
 
 . Check that the new version is available on https://rubygems.org/gems/asciidoctor-revealjs[rubygems.org]
-. Generate a compatible version of the Ruby converter (using opal mode)
-+
- $ bundle exec rake build:converter:opal
-
-. Build the node package (make sure you have `devDependencies` installed with: `npm install`):
+. Generate the javascript version of the Ruby converter
 +
- $ npm run build
+ $ bundle exec rake build:js
 
 . Publish the node package on npm:
 +
  $ npm login # only required if not already authenticated
  $ npm publish
 
-. Check that the new version is available on https://www.npmjs.com/package/asciidoctor-reveal.js[npmjs.com]
-. Update version in `lib/asciidoctor-revealjs/version.rb` and `package.json` (+1 bugfix and append '-dev') and commit
+. Check that the new version is available on https://www.npmjs.com/package/@asciidoctor/reveal.js[npmjs.com]
+. Make binaries release
+** Run `npm run package`. Binaries built will be in `dist/`. Upload them to the GitHub release page.
+. Publish previously saved GitHub release draft
+. Update version in `lib/asciidoctor-revealjs/version.rb` and `package.json` (+1 bugfix and append '-dev')
+** Remove the "Slim compiled to Ruby" converter to the git tree (to avoid noise to the repo and `git status` noise)
++
+    git rm --cached lib/asciidoctor-revealjs/converter.rb
+
 ** commit msg: Begin development on next release
 . Submit a PR upstream to sync the documentation on asciidoctor.org
 ** Modify this page: https://github.com/asciidoctor/asciidoctor.org/edit/master/docs/asciidoctor-revealjs.adoc
+. Submit a PR downstream to update Asciidoctor reveal.js version inside docker-asciidoctor
+** Modify the `Dockerfile`, `Makefile` and `README.adoc` of: https://github.com/asciidoctor/docker-asciidoctor
+. Submit a PR downstream to update AsciidoctorJ reveal.js version
+** Modify `gradle.properties`, `asciidoctorj-revealjs/gradle.properties` and `asciidoctorj-revealjs/build.gradle` in: https://github.com/asciidoctor/asciidoctorj-reveal.js
 
 == Ruby and asciidoctor-doctest tests
 
@@ -324,3 +410,23 @@ This is done using the following command:
 
 Files in the `examples/` directory are used as tests.
 Resulting slides are kept in `test/doctest/`.
+
+
+== Netlify Integration
+
+On every commit or PR, the https://www.netlify.com[Netlify] service will convert some examples into slides and host the resulting pages on its platform where it will be visible by anyone.
+It hosts the converted HTML files, reveal.js framework and static content like images and CSS.
+This integration will allow us to easily preview PRs and demo features to users (source and converted result).
+See the `publish` rake task in `Rakefile` and the `netlify.toml` configuration file.
+
+=== Sensitive Data Accidentally Pushed Out
+
+Only content that is copied into the `public/` directory will be published on the Netlify site.
+If, by accident, something sensitive is copied over there, delete it, rewrite the git history to remove the sensitive information and force push the branch.
+Reach out to our netlify integration contact to make sure that deployed branches were rebuilt and no longer contain the sensitive information.
+
+=== Integration Contact
+
+Main Contact: https://github.com/Mogztter[@Mogztter]
+
+Also, in order to stay with a free plan, only the following people have control over our netlify integration: https://github.com/Mogztter[@Mogztter], https://github.com/mojavelinux[@mojavelinux] and https://github.com/graphitefriction[@graphitefriction].

docs/asciidoctor-reveal.js-master/HACKING.adoc

@@ -1,6 +1,6 @@
 .The MIT License
 ....
-Copyright (C) 2012-2018 Olivier Bilodeau, Charles Moulliard, Dan Allen and the Asciidoctor Project
+Copyright (C) 2012-2020 Olivier Bilodeau, Charles Moulliard, Dan Allen and the Asciidoctor Project
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal