Dashboard: promote features on sidebar

[humitos]

Initial iteration to promote some features to our users.

Closes #103
Requires readthedocs/readthedocs.org#11287

[agjohnson]

This is great start. I feel these all might benefit from a link/button call to action to though, as the only thing linking these is the header right now and the headers are goal focused (Preview changes before building!) instead of actionable (Enable pull request previews)

[agjohnson]

This feels like it's making two points. Both are valid, but if feels like the better focus is pointing the user how to get started instead.

Example projects guide the user on how to bootstrap a project, users don't start off blocked on writing documentation without having a project yet. This should probably focus on "Not sure how to get started?" instead. We're mostly concerned about the user learning how to use Read the Docs with this content.

The tutorial is probably an even better resource, or a good resource in addition.

[humitos]

I updated it a little bit. Let me know if that's fine or you prefer to change it completely and show the tutorial. In any case, feel free to make a suggestion.

[agjohnson]

This block is the default if all other blocks are not shown, so we could potentially be showing this to community users. It seems we should focus this not just on organization security logs. Perhaps this is just the wrong fall back content?

[humitos]

Yes. We need to think about a better fallback content for community 👍🏼

[humitos]

Maybe we can point to the addons blog post once it's merged/published: readthedocs/website#278

[humitos]

I made some updates based on feebdack. I like where it's going 👍🏼

[agjohnson]

That looks great! I noted some simplification and minor style changes on the card structure, but what you have there is great

[agjohnson]

These don't need grids to affect the content width of the button and can instead use a fluid button. I would use primary instead of positive too. The card examples show positive/negative as an example of a yes/no dialog prompt, where instead we just want a nice looking link.

And the button looks quite big, I might try small to reduce it just a little.

Suggested change

	<div class="ui grid extra content">
	<a class="ui sixteen wide column positive basic button" target="_blank" href="{{ url }}">
	{% trans "Check out example projects" %}
	</a>
	</div>
	<div class="ui extra content">
	<a class="ui small primary fluid basic button" target="_blank" href="{{ url }}">
	{% trans "Check out example projects" %}
	</a>
	</div>

[humitos]

This is how it looks with this change:

I think it's fine 👍🏼

These don't need grids to affect the content width of the button and can instead use a fluid button

Honestly, I'm not able to understand how this pattern works yet and I had pretty bad time trying out these different classes 😅 until I found something that didn't break. I need to go back to the basics of this framework at some point and try to understand it.

[agjohnson]

The changes you have here look like what I was describing, yeah. But the code in the PR is still not updated it seems.

[humitos]

I think this is ready to merge. @agjohnson can you make a final review here?

[agjohnson]

Did you forget to push up? I don't see any changes since last review.

[humitos]

Meh, yeah, I pushed but it failed because I didn't have my SSH keys into the agent 👎🏼 . I just pushed the changes.