If it impractical to include both the font family profile and individual
font profile under a single [root]/font URL, we could use another scheme
such as:
[root]/family/(family_id)/((family_name))
[root]/font/((font_id))/((common_name))
For example:
openfontlibrary.org/family/1/pt-serif
openfontlibrary.org/font/27/pt-serif-caption
This has the advantage of shorter URLs overall, as well as keeping the
designs on font family profiles and font profiles on separate URLs
(which makes designing the pages easier in Aiki).
** Changed in: openfontlibrary
Milestone: None => 0.2
** Changed in: openfontlibrary
Status: New => Incomplete
** Changed in: openfontlibrary
Status: Incomplete => Triaged
** Changed in: openfontlibrary
Importance: Undecided => Medium
** Changed in: openfontlibrary
Assignee: (unassigned) => Christopher Adams (christopheradams)
--
You received this bug notification because you are a member of Open Font
Library Developers, which is subscribed to Open Font Library.
https://bugs.launchpad.net/bugs/747994
Title:
font families need pretty URLs
Status in Open Font Library:
Triaged
Bug description:
The URL representation for specific fonts within font families can be
generated in this way
[root]/font/((family_id))/((family_name))/((font_id))/((sub_family))
For example, the profile page for PT Sans Bold Italic would exist on
the URL:
http://openfontlibrary.org/font/3/pt-sans/17/bold-italic
The slight disadvantage of this scheme is that it includes id numbers
for both the font family and font file in the URL. The advantage is
that it entirely mitigates the risk of name collisions across the
entire system. In the final analysis the advantage outweighs the
disadvantage.
In the case above, the value of pt-sans and bold-italic are generated
by running the value of ((family_name)) and ((sub_family)) through
AIki's URL generator. However, the actual selectors for the database
are the URL arguments (!(1)!) and (!(3)!) for family_id and font_id
respectively.
To fix this:
On the home page and font list page, generate links to each individual
family using the above scheme. On the individual font page, read in
the values of (!(1)!) and (!(3)!)
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework.admins
Post to : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework.admins
More help : https://help.launchpad.net/ListHelp
