* add contributor list to each document
* handle case where there is no github repo
* Move to v1
* Revert "handle case where there is no github repo"
This reverts commit a76a887901.
* Revert "add contributor list to each document"
This reverts commit c0cc79f995.
* Add last updated by field
* -Include enableUpdateBy in the config
- Rename css class to be more general
* Fix lint
* Refactor :
- s/getGitlastupdated/getGitLastUpdatedTime
- refactor part in getGitLastUpdated[Time|By] that overlaps
- remove getAuthorInformation
* -Modify the display logic
-Refactor the utils, combine lastupdatedtime and lastupdatedby
-Replace the test
* Modify docs based on the display change
* Update docs for url and baseurl
For more clarity and to make relationship more clear
* Update support for Web App Manifest (#1046)
* misc: update nits
* misc: update nits
* Add ability to specify sub categories in sidebar.json
* move v1 files to correct place
* refactor implementation
* refactor naming for implementation clarity
* Added option for client to include there own remarkable config
* Better use merge here
* Added lodash ...
* Change use of lodash to deepmerge and added description to api site
* markdownConfig -> markdownOptions
* Update api-site-config.md
* remove 1.4 docs change
since it is unrelated (the feature will only be available in next release)
* Run prettier
* Adding last updated time for docs
* Making file path general and other suggested changes
* Checking if time returned is null due to absence of git or some other issue
* Adding option to enable/disable update time feature and test-doc
* Adding simple unit tests for getGitUpdateTime()
* nits & rewrote failing test
* consistent test naming
* Adding optional updateEnableTime in documentation
* package-lock & yarn.lock
* Fix conflicting strings issue in translations
* Preserve structure of `customTranslations`
* Use `deepmerge` to merge whole of `localized-strings`
* Simplify and make deep property access on an object safe
* Fix deep property accessor and rename it to idx
* Updating step 2 to be more intuitive
Use of word Github is very confusing. When starting, most of devs wont have an existing github repo. And normally not everyone will be using Github. Since devs will be following this step by step: we need to stress on telling them to create a new or use existing local project folder which may or may not be a github repo.
* Update getting-started-installation.md
I added back information about extra search options for Algolia. A previous commit removed the section about extra search options, but it appears the information might actually be useful.
* Enable user to use prism.js as syntax highlighter
* add package-lock
* if 'usePrism' is true, use prismjs on all languages
* don't get lang by hljs if use prism
* Update api-site-config.md
* Update api-doc-markdown.md
* only load prism css when usePrism is true
