-
Notifications
You must be signed in to change notification settings - Fork 145
chore: reformat markdown with prettier #2114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
B4nan
wants to merge
5
commits into
master
Choose a base branch
from
reformat-markdown
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -150,7 +150,6 @@ Any repetitive job matching the following criteria might be suitable for turning | |
|
|
||
| If you look closely, you'll start seeing opportunities for new Actors everywhere. Be creative! | ||
|
|
||
|
|
||
| ## Use the Actor ideas page | ||
|
|
||
| The [Actor ideas](https://apify.com/ideas) page is where you can find inspiration for new Actors sourced from the Apify community. | ||
|
|
@@ -166,28 +165,23 @@ Build and publish new tools on Apify and have multiple chances to win big prizes | |
| ::: | ||
|
|
||
| 1. _Visit_ [apify.com/ideas](https://apify.com/ideas) to find ideas that interest you. Look for ideas that align with your skills. | ||
| 2. _Select an Actor idea_: Review the details and requirements. Check the status—if it's marked **Open to develop**, you can start building. | ||
| 3. _Build your Actor_: Develop your Actor based on the idea. You don't need to notify Apify during development. | ||
| 4. _Prepare for launch_: Ensure your Actor meets quality standards and has a comprehensive README with installation instructions, usage details, and examples. | ||
| 5. _Publish your Actor_: Deploy your Actor on Apify Store and make it live. | ||
| 6. _Monitor and optimize_: Track your Actor's performance and user feedback. Make improvements to keep your Actor current. | ||
|
|
||
| 1. _Select an Actor idea_: Review the details and requirements. Check the status—if it's marked **Open to develop**, you can start building. | ||
|
|
||
| 1. _Build your Actor_: Develop your Actor based on the idea. You don't need to notify Apify during development. | ||
|
|
||
| 1. _Prepare for launch_: Ensure your Actor meets quality standards and has a comprehensive README with installation instructions, usage details, and examples. | ||
|
|
||
| 1. _Publish your Actor_: Deploy your Actor on Apify Store and make it live. | ||
|
|
||
| <!-- 1. _Claim the idea_: After publishing, email [[email protected]](mailto:[email protected]) with your Actor URL and the original idea. Apify will tag the idea as **Completed** and link it to your Actor. | ||
|
|
||
| 1. To claim an idea, ensure your Actor is functional, README contains relevant information, and your Actor closely aligns with the original idea. --> | ||
|
|
||
| 1. _Monitor and optimize_: Track your Actor's performance and user feedback. Make improvements to keep your Actor current. | ||
| <!-- | ||
| 1. _Claim the idea_: After publishing, email [[email protected]](mailto:[email protected]) with your Actor URL and the original idea. Apify will tag the idea as **Completed** and link it to your Actor. | ||
| 1. To claim an idea, ensure your Actor is functional, README contains relevant information, and your Actor closely aligns with the original idea. | ||
| --> | ||
|
|
||
| <!-- #### Multiple developers for one idea | ||
|
|
||
| Apify Store can host multiple Actors with similar functions. However, the "first come, first served" rule applies—the first developer to claim an idea receives the **Completed** tag and a link from the Actor ideas page. | ||
|
|
||
| Competition motivates developers to improve the code. You can still build the Actor, but differentiate with a unique set of features. --> | ||
|
|
||
|
|
||
| <!-- ### Submit your own ideas | ||
|
|
||
| The Ideas page is also where you contribute concepts to drive innovation in the community. | ||
|
|
||
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather keep only 1. as ordered lists. It makes for much easier maitenance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to me, having only 1. everywhere is a hack, not a proper solution. it produces warnings in webstorm, and i am actually surprised it doesnt trigger linter errors.
this is a job for IDE, you shouldn't do that by hand. not sure if vscode doesnt have a helper, webstorm does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not a hack, this is based on CommonMark spec which Docusaurus supports. Either way in VSC/Cursor this is handled by extension, I was curious that here I saw it changed to regular numbering but not in other cases