It'd be a great improvement to the Guides if we'd have "learn more" links
which would go directly to relevant API pages. Due to the nature of the
API, these can't be automatically created; they have to be handpicked. I've
started an experimental site, putting together these links:
http://rail
This is a good proposal.
We would need a helper to generate the subdomain depending on whether we
are generating edge or stable guides.
Also, your idea is related to the new API home page that I have in mind.
The home page I envision has a similar purpose than your site, an index
with links to th
:heart: love this idea.
On Wed, Sep 18, 2013 at 2:26 AM, Xavier Noria wrote:
> This is a good proposal.
>
> We would need a helper to generate the subdomain depending on whether we
> are generating edge or stable guides.
>
> Also, your idea is related to the new API home page that I have in min
I'm totally up for working on this. I'll look at the Guides source and
learn how they're compiled. I can imagine a new CSS Guides style is the
minimum that'd be needed: something to set up the API link for deeper
information. And in the best case, this could be a simple database: a
many-to-many
On Wed, Sep 18, 2013 at 6:30 PM, Robb Shecter wrote:
I'm totally up for working on this. I'll look at the Guides source and
> learn how they're compiled. I can imagine a new CSS Guides style is the
> minimum that'd be needed: something to set up the API link for deeper
> information. And in the b
