Replies: 4 comments 5 replies
-
|
As previously discussed it will be good to remove the dependancy on AppEngine, and GitHub pages looks like a good home. Will be interested to see how the maintenance of downloadable vocabulary definition files, .owl file, and JSON-LD context file, etc. are managed. Maybe we can also end up with a better solution to the perenial http/https JSON-LD context issue as part of the move. Meanwhile looking at the simple example version currently available; the home page contains lots of wasted white space and large font in the intro paragraph - not too much of a problem on a desktop but on a mobile not very user friendly. Cannot comment on any other pages as they all return 404. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry about the 404. Fixed |
Beta Was this translation helpful? Give feedback.
-
|
My feedback: I always find it interesting how many sites promoting JSON-LD use actually do not include JSON-LD in their own sites. Hope that can be kept in mind here for any upgrades. |
Beta Was this translation helpful? Give feedback.
-
|
Good point. will add that. |
Beta Was this translation helpful? Give feedback.
-
|
The about page (https://staging-github.schema.org/about.html) seems to be filled with the content of the about property (https://staging-github.schema.org/about). Furthermore I'm wondering whether there are any intended design/functionality changes versus the current site, or whether the new version should be an exact copy? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the late reply. This would be a good time to discuss what we, as a community, would like. The current version of the site runs on App engine and is very hard to modify. Schema.org's site does not need to be dynamically generated. So, storing it as a set of static pages makes a lot of sense. Further, this structure makes it easy for someone else to have their own set of github pages that extend the schema in some fashion |
Beta Was this translation helpful? Give feedback.
-
|
Examples are missing from term pages. On mobile the menu icon in header doesn’t appear to do anything. |
Beta Was this translation helpful? Give feedback.
-
|
What do you mean by term pages? Will look at the mobile version |
Beta Was this translation helpful? Give feedback.
-
|
The term pages are the individual pages that describe each term. eg. https://staging-github.schema.org/Event In the current version most term pages have one or more examples listed to show how the term might be used using each of the supported markup types (Microdata, RDFa, JSON_LD) eg. https://schema.org/Event#eg-0009 These are missing from this github version of the pages. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello folks,
After a period of relative hiatus, we are working on restarting updates to http://schema.org/.
As a first step, we are moving from hosting the Schema.org website as an application on AppEngine to a set of github pages. The goal is both to simplify the maintanence of the website and to make it easy for others to create extensions in a fashion where we can easily link to approved extensions.
Before we switch over, it would make sense for us, as a community to take a close look at what the new site will look like and iron out the bugs. The site is available at https://schemaorg.github.io/gh_pages/.
As a next step, it will also be made available at https://staging-github.schema.org/, sometime later this week.
Please give us your feedback.
thanks,
Guha, on behalf of the Schema.org team
Beta Was this translation helpful? Give feedback.
All reactions