Improve grammar and paragraph structure in documentation

[WorldSEnder]

Description

Fixes #2573 @Madoshakalaka maybe you can test the new JetBrains templates and review them
Fixes #2180, i.e. #2178 (comment) (the offending sentence has been removed from the docs. It shall never be seen again. I think I know what it was meant to document, but I'm not sure if that "feature" is intended behaviour at this point)

This also slightly changes the keyed_list example. According to my tests, it did not actually perf-test the time it took for individual renders to happen. This now reports the time it takes from an initial view -> rendered of the wrapper class, which should be more reliable. To see that the current way is absurd, add a few thousand items to the live example and be surprised that it reports <100ms render times even as the browser visibly lags and stops to a crawl.

Checklist

• I have run cargo make pr-flow
• I have reviewed my own code

[github-actions]

Visit the preview URL for this PR (updated for commit 96f36cb):

https://yew-rs--pr2620-improve-docs-6bp4ze8q.web.app

_{(expires Wed, 27 Apr 2022 08:25:08 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

[github-actions]

Size Comparison

examples	master (KB)	pull request (KB)	diff
boids	173.225	173.225	0
contexts	110.501	110.501	0
counter	87.184	87.184	0
counter_functional	87.746	87.746	0
dyn_create_destroy_apps	90.268	90.268	0
file_upload	103.117	103.117	0
function_memory_game	167.623	167.623	0
function_router	353.295	353.295	0
function_todomvc	162.514	162.514	0
futures	226.903	226.903	0
game_of_life	108.204	108.204	0
inner_html	83.682	83.682	0
js_callback	113.266	113.266	0
keyed_list	196.121	196.095	-0.026
mount_point	86.707	86.707	0
nested_list	116.218	116.218	0
node_refs	90.077	90.077	0
password_strength	1539.661	1539.661	0
portals	97.286	97.286	0
router	319.138	319.138	0
simple_ssr	500.580	500.580	0
ssr_router	428.699	428.699	0
suspense	111.021	111.021	0
timer	89.899	89.899	0
todomvc	143.865	143.865	0
two_apps	87.772	87.772	0
webgl	87.358	87.358	0

[Madoshakalaka]

I tested the JetBrains templates and they all work fine.

I was a bit confused when it required a Default trait property when rendered without explicit props, but I guess that's just a breaking behavior compared to 0.19? I didn't follow recent progress~

[WorldSEnder]

I was a bit confused when it required a Default trait property when rendered without explicit props

@Madoshakalaka You might be misremembering, start_app requires COMP::Properties: Default already in 0.19. Thanks for taking the time to try out the macros.

[hamza1311]

We should also

• Rename "Function Components" in sidebar to "Components"
• Rename "Intro With Basic Web Technologies" in sidebar to "Using Basic Web Technologies In Yew" combine "JavaScript with Rust" with it.
• Reorder the concepts in the order they should read in
• Remove use_<hook> page and instead use API docs for those. We shouldn't be documenting the API in the website¹

Footnotes

1. I added them in Add docs for Hooks  #1643. Maybe that wasn't the smartest move ever ↩

[hamza1311]

Suggested change

	let combined_html: Html = html!{
	<div>{header_html}{counter_html}</div>
	let combined_html: Html = html! {
	<div>{ header_html } { counter_html }</div>

Just some formatting

[WorldSEnder]

I've added a space behind html! but the other spaces might suggest spaces in the generated HTML, so I'd leave them out.

[WorldSEnder]

• Remove use_<hook> page and instead use API docs for those. We shouldn't be documenting the API in the website1

I'll leave that for a future PR. I think it would be nice to have the rust docs for master linked here, instead of the rust docs for the most-recently deployed version. That's a bit more effort than I can spend right now.

[hamza1311]

• Remove use_<hook> page and instead use API docs for those. We shouldn't be documenting the API in the website1

I'll leave that for a future PR. I think it would be nice to have the rust docs for master linked here, instead of the rust docs for the most-recently deployed version. That's a bit more effort than I can spend right now.

That's fine. I'll do that soon

I'm going to merge it now. If any docs changes are wanted later, those can come in separate PRs