-
Notifications
You must be signed in to change notification settings - Fork 90
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
URL 的结构 #12
Comments
For now I will stay as RESTful default, which is
|
I think lynda's better, have a category |
Would love things like
The rules:
For a course, you can give it a long detailed Chinese name, like "Html 超越经典“,but this will be a title field in database. The name field will be what is shown in the url, which will be the same as the directory name of all videos of this very course. No space in the name, use |
use |
@luckyyang if you are writing C code, and want to name a variable, but to use as part of URL, I think |
fine with |
对于课程的链接格式做些改变现在我更倾向于用,
其他的东西不变
|
|
lynda竟然有字幕,做的真细 |
CC is great to have if you have international audience. However our courses will be done in Chinese, and our audience will be mostly native-Chinese speaker. So it's OK for us to go without CC, IMO. |
每个课程都会有分类标签,未来可以在 hpcasts.com/category/git 看到类似 http://happycasts.net/episodes?tag_id=2 的页面,所以分类效果就达到了。 我觉得 lynda.com 上把分类写在链接里没有太多必要。 http://www.lynda.com/Ruby-on-Rails-3-tutorials/essential-training/55960-2.htm 这个太啰嗦了。 |
恩,分类还是要的。lynda的确实有点罗嗦。 |
@luckyyang 不仅要分类,还要分初级中级高级。 |
Need to fix 可见,把课程名放在顶级还是会有一些意想不到的不方便。 |
http://warpspire.com/posts/url-design/ 还是要把 course_name 放在 top section of the URL, 这样我们可以有
等等一切 github 在 user_name 之后做的所有事情。 刚也想了一下要不要像 github 一样把 user_name 放在 top section. 这样我们就要:
感觉比现在的差远了:
|
html5 onPushState 一定要学一下。 |
我非常想要的是 将来我可以在 |
hpcasts.com/course/5 我倾向的课程地址 |
@asmcos 可以先看看这篇文章。 |
hpcasts.com/course/course_name 更合适? 我担心课程名字含有中文名(或者空格,《,等)会让我们有麻烦。 |
Which is the best for us?
The text was updated successfully, but these errors were encountered: