Replace old project name references with ttag #106
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
doc(gitbook/SUMMARY.md) Replace old name occurences by `ttag` It also removes the old name from file names to keep them agnostic and only focused on what they are describing doc(gitbook/README.md) Replace old name with ttag Some sentences were changed and extra links were added as well doc(gitbook/README.md) Remove absolute URL references. doc(gitbook/configuration.md) Replace old project name references with `ttag` It also adds all default values for all configuration options and uses the same style to list available options doc(gitbook/configuration-lib.md) Rename old project name references * It only refers to `ttag` now * Some small fixes on typos were included. doc(gitbook/*) Replace old project names for all 'General' doc section * Small typos and style normalization is included. * Fix references to `.html` files as gitbook will automatically convert `.md` file extentensions to `.html` doc(gitbook/installation.md) Rename `chapter1.md` to a more meaninful name `installation.md` ref(book.json) Change old project name to ttag ref(gitbook/*) Remove old project name from file name to keep file structure agnostic doc(gitbook/quick-start.md) Remove old project name references Some adjustments on styling and order of presentation of the instructions were changed. A small footnote was added to point to a more advanced usage, using webpack. doc(gitbook/localization-with-webpack.md) Remove old project name refs Some changes and notes regarding ussage with Webpack 4 were also added. doc(gitbook/*) Rename old project name to ttag It also normalizes all API documentation with the `reference-` file name prefix Some references (i.e.: CHANGELOG) were not changed to keep the history. doc(*) Add notice to main README file It also includes some style changes to the gitbook files.
erickwilder
force-pushed
the
replace-old-project-name-references-with-ttag
branch
from
8af9a88
to
7c9efdb
Compare
It also now points to the official GNU gettext documentation for language ISO codes
|
Great, thanks for your help! |
serjshevchenko
pushed a commit
to serjshevchenko/ttag
that referenced
this pull request
Dec 21, 2020
* npm audit fix * another audit fix, update caniuse-lite, serialize-javascript * update jest, ts-jest * update typescript to keep ts-jest happy * update yargs to fix vulnerability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should address the first changes in the direction of renaming the project. My approach was to limit my changes only to the
gitbook/directory and keep other changes as minimal as possible.Assumptions
It's worth to mention that some assumptions were made while patching the docs:
ttag, so links and references may look likehttps://github.com/ttag/ttag- you may want to discuss this and make new suggestions.babel-plugin-c-3potobabel-plugin-ttag1.0.0version was added but nothing changed onCHANGELOGdue to the fact I don't know what's the plan to release a new package under the new name.All in all, I'm looking forward for your feedback.