* convert `@docusaurus/plugin-content-blog` to typescript
remove divided plugin
convert `@docusaurus/plugin-content-blog` to typescript
convert `@docusaurus/plugin-content-blog` to typescript
convert `@docusaurus/plugin-content-blog` to typescript
add `packages/docusaurus-plugin-content-blog/lib` to ignores
linted
refactoring type definition
fix test fails
lint
* lint
The approach here is to first strip the HTML from the heading's content, then rendered it with markdown to get the HTML content for the TOC entry, then to strip the HTML from the rendered content again, as to get the text for the TOC entry's link.
Adds an additional dependency of striptags (MIT licensed)
Example TOC Entry, given the heading of:
```markdown
```
```javascript
{
hashLink: 'foo',
rawContent: '<a name="foo"></a> _Foo_',
content: '<em>Foo</em>',
children: []
}
```
Previously this TOC entry would be:
```javascript
{
hashLink: 'a-name-foo-a-_foo_',
rawContent: '<a name="foo"></a> _Foo_',
content: '<a name="foo"></a> <em>Foo</em>',
children: []
}
```
closes issue #1703
* Update users.js
added 1Hive to the Docusaurus users list
* Add files via upload
added 1hive.png bee to the img/users folder
* Update users.js
typo
* Update users.js
* docs: add past versions to the tutorial
I changed "we" to "you" like the other sections of the tutorial.
I removed yarn from the code because `yarn version` didn't run on my Windows 10 system (see issue [1743](https://github.com/facebook/docusaurus/issues/1743)).
I added headings for the current version, next version, and past versions.
* Update tutorial-version.md
* Fix search bar on smaller devices
* Update packages/docusaurus-theme-search-algolia/src/theme/SearchBar/styles.css
Removed blank line
Co-Authored-By: Endi <endiliey@gmail.com>
* docs: make navbar less cluttered
* misc(v2): rename components (#1434)
* misc(v2): clean up work
* misc(v2): rename components
* misc(v2): rename Blog components
* refactor(v2): remove page plugin component
* chore(v2): optimize webpack config
* feat(v2): implement theme component overriding (#1435)
* feat(v2): implement component overriding
* siteDir theme overriding should work for > 1 level directory
* fallback for essential component like Loading
* rename default -> classic
* fix(v2): add missing layout alias on theme-classic plugin
* feat(v2): easier plugin theme components swizzling (#1436)
* feat(v2): easier plugin theme components override
* add context
* refactor again
* rename eject -> swizzle
* nits
* fix(v2-cli): passes the missing host option to start (#1439)
* feat(v2): Algolia search theme (#1440)
* feat(v2): Algolia search plugin
* patch PR #1440 (#1441)
* alternative implementation
* typo
* refactor noop
* rename SearchAlgolia -> SearchBar
* changes.md
* refactor(v2): move headerLinks -> themeConfig & rm dead code (#1442)
* refactor(v2): move headerLinks -> themeConfig & rm dead code
* rm -rf dead code
* chore(v2): better chunk naming
* refactor(v2): add flowtype + refactor test (#1443)
* chore(v2): add flow setup
* nits
* fix
* add flow-typed
* ignore compiled library
* fix error
* fix typing
* fix module name mapper
* setup for @docusaurus/core
* dont try remove type without @flow
* fix can't find @docusaurus/utils
* fix test
* remove obscure relative paths
* more refactoring
* add typing for server/load/theme.js
* no need to ship .flow source
* chore(v2): rm flowtype (#1444)
* chore(v2): tweak eslint config (#1445)
* chore: point website-1.x to correct version so that it can pick latest code
* feat(v2): meta description (#1447)
* feat(v2): meta description
* add description for blog as well
* fix non-descriptive text link
* remove font awesome
* switch front-matter -> gray-matter
* fix(v2): docsearch a11y issue (#1449)
* refactor(v2): blog data revamp (#1450)
* refactor(v2): blog data revamp
* fix(v2): fix incorrect blog total count
* misc: remove console.log
* feat(v2): export frontMatter as an object within MDX file (#1451)
* refactor. Don't confuse metadata & frontmatter
* export frontMatter in content itself
* nits
* nits name
* dont truncate first four lines in blog
* fix(v2): transpiling, window scroll and console error (#1452)
* chore(v2): better error message style (#1454)
* chore(v2): remove docsearch a11y workaround
* fix(v2): slugify tags
* feat(v2): blog tags (#1453)
* feat(v2): blog tags
* feat(v2): blog tags
* chore(v2): use remark-slug so that rightToc can benefit from it
* fix: right TOC should not strip special chars (#1458)
* fix: right TOC should not strip special chars
* nits
* fix(v2): handle non existent blog, docs, pages (#1459)
* fix(v2): handle non existent blog, docs, pages
* nits
* feat(v2): list blog tags on posts (#1456)
* feat(v2): list blog tags on posts
* fix date handling on blog header
* fix console log error due to non unique key
* test(v2): test different type of sidebar item
* chore(v2): fix typo
* v2.0.0-alpha.14
* fix(v2): fix wrong dependency problem (#1460)
* v2.0.0-alpha.15
* Chore(v2): use alias instead of relative path for blogpost
* feat(v2): theme config for Footer (#1461)
* feat(v2): theme config for Footer
* fix: dont show footer if themeConfig.footer is undefined
* Import fresh docusaurus.config.js for better hot reload
* chore(v2): update dependencies (#1462)
* chore(v2): update dependencies
* nits
* v2.0.0-alpha.16
* fix(v2): fix cannot import css from node_modules in userland (#1463)
* docs: showcase user Express Validator (#1464)
* docs: sort user with alphabetical (#1465)
* chore: fix typo (#1466)
* docs: showcase user tipsi-stripe (#1423)
* docs: make it clear in the tutorial where the `docs` folder is (#1468)
* Make it clear where the `docs` folder is
It was not clear, to the beginner user—who this tutorial is for—where the `docs` folder was . The only reason I know this is because I'm a beginner user and I tried for too many minutes to find the `docs` folder inside the `website` folder. I had this assumption because the previous example is offered under the assumption that you're in the `website` folder.
Feel free to change the wording, I just want to make it clear where you should be looking, if you're new.
* Update tutorial-create-pages.md
* docs: add hint for linking dependencies time (#1470)
In this tutorial we assume that the user may or may not have used Node.js. It would follow then, based on how long it takes the "Linking dependencies" step to complete—243.61s for me—that we give them a hint that it might take a minute.
* doc: mention HTTPS approach in tutorial git clone step (#1471)
* doc: change tutorial git to suggest HTTPS
Since we're instructing the user to create a new repository, it might be a safe bet to assume that they don't have their SSH keys set up. HTTPS might be a better option in this context.
* docs: keep ssh add https
@Hongarc said, "How about keep `SSH` and add `HTTPS`." This is one way to do that.
* Update tutorial-setup.md
* docs: normalized spelling of `web server` (#1473)
* docs: clarify location of sidebars.json (#1472)
In #1468 we clarify where the `docs` folder is.
Here, we make it clear where `sidebars.json` is.
* fix: missing cli commands (#1478)
* fix: missing cli commands
* centralize
* feat(v2): move navbar config into themeConfig (#1477)
* feat(v2): move navbar config into themeConfig
* misc: fix tests
* fix: support external url for logo
* docs(v2): CLI docs (#1476)
* WiP: CLI docs
* Tweak word choices for CLI docs
- Use the word swizzle directly
- Follow variable convention for shell
* Resolve docs discussion
* Update cli.md
* fix(v2): should be able to build even if static folder doesnt exist (#1479)
* chore: remove noWatch cli options because you cant disable watch in wds (#1480)
* docs: update StreamPipes logo (#1481)
* docs: showcase user Ax (#1483)
* docs: remove pinned for Taro (#1482)
* docs: fix typo for `docs` folder (#1484)
* docs: fix typo for `docs` folder
* docs: request change for #1484
* Update api-doc-markdown.md
* docs: add some showcase user of `facebook` (#1486)
* docs: showcase user Idb
* docs: showcase user Netconsd
* docs: showcase user Redex
* added css for feedback page contrast issue
* docs: add the repository to the localhost:3000 link
Fix two links on **[Create Pages](https://docusaurus.io/docs/en/next/tutorial-create-pages)**.
* docs: use the same start command on both pages
The start command in **[Scaffold the Site](https://docusaurus.io/docs/en/next/tutorial-create-new-site)** is "Run `npm start` or `yarn start.`" It will help new users to see the same start command again. A slightly different command will make new users think that something slightly different is happening.
* docs: change the ID of the new documentation page
The page ID "doc4" is already used by one of the downloaded pages, docs/exampledoc4.md, shown below:
```
---
id: doc4
title: Other Document
---
this is another document
```
* docs: removed docusaurus-tutorial/ from the links
I think the tutorial should tell Windows users to use Git Bash. Later in the tutorial is a command that worked in Git Bash, `publish-gh-pages`, but didn't work for me at the Windows command prompt.
* docs: add an HTTPS example for publish-gh-pages
I moved step 1 to step 2 so the terminal steps would be together. I added Git Bash, because `publish-gh-pages` worked for me in Git Bash but didn't work at the Windows command prompt.
I added HTTPS to step 4 because, on my system, HTTPS worked for me but SSH didn't work. I changed <GIT_USER> to USERNAME and deleted the $ prompt, to be consistent with other examples in the tutorial.
* Update tutorial-publish-site.md
* feat(v2): blog support date front matter
* feat(v2): blog support date front matter
* feat(v2): blog support date front matter
* feat(v2): blog support date front matter
* Update CHANGELOG-2.x.md
The description of `npm` fits better in the opening paragraph than in a numbered step. The note about version 8 fits better in the Check section than the Install section.
