Skip to content
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

Tutorial Series List #1

Open
CesiumBen opened this issue Mar 14, 2022 · 4 comments
Open

Tutorial Series List #1

CesiumBen opened this issue Mar 14, 2022 · 4 comments
Assignees

Comments

@shehzan10
Copy link
Member

@CesiumBen Taking a look at this list, I'm wondering if this can be shortened / combined / edited.

As a reminder, the goal here is to create an impact on Cesium's positioning in metaverse with an eye on making it easier / best practices for VR Applications using Cesium for Unreal. This is provided through authentic education and guidance using the tutorials.

With a 13 part list (14 if you include edits to the existing VR tutorial), at some point its going to have diminishing returns, and we should keep our eyes wide open for this. It would also mean that at a 2-week interval, this would run for 6.5 months.

My questions / notes to help you think about this:

  • Which tutorials have such a narrow window that it wouldn't apply to more than a "handful" of users?
  • Which tutorials can be combined? Eg. can 10 and 11 be combined?
  • Which tutorials can be pointed to other standard tutorials (eg. the Adding OSM Buildings one is probably applicable)
    • Sync up with @argallegos to know which standard tutorials are coming up. That way you are not duplicating content by assuming its not currently live.
  • metadata picking -> Note that OSM Buildings does not support metadata in Unreal. This is because OSM Buildings use Batch Table Hierarchy (as opposed to standard batch table), which is currently not supported.

I don't disagree that the tutorial list is useful, nor am I making specific recommendations here for what should be added/changed/removed. I'm sharing these questions so that you can think about it and then come back with the edits to balance focus and impact vs completeness vs future work.

@CesiumBen
Copy link
Contributor Author

Thank you @shehzan10, this helps prune the list.

We agreed that 6-6 1/2 months to complete the series was long. Ultimately merging tutorials could lead to the content being too large to approach for learners, and would still take a similar amount of time for us to complete. What will get more tutorials out faster would be if we cover strategies and solutions more than the step to step procedure for reproducing a particular piece of logic. We have agreed to take this approach as it seems to be the most useful to a variety of users.

Removed from the series:
#7 - Checked with @argallegos , redundant with C4U tutorials. We will still have coverage of implementing OSM buildings with UI functionality of some kind.
#13 - This isn't specific to Cesium for Unreal or VR, more of a nice to have.

Combined:
#10 and #11 can be combined depending on the complexity of explaining both in one tutorial.
#3 and #4 can be combined in terms of effort, and possibly combined on the tutorial if the content is not too long. Walking has a unique complication with Cesium for Unreal as tiles are unloaded below you, it would warrant a separate tutorial if it takes too long to explain.

Which tutorials have such a narrow window that it wouldn't apply to more than a "handful" of users?

None that we foresee, these tutorials cover most use cases for VR using Cesium for Unreal.


In the meantime, we will be pursuing #3 and get a better understanding of our tasks ahead from our findings.

CC: @argallegos

@shehzan10
Copy link
Member

@CesiumBen Thanks for the update. Can you update the top issue please so that we have a concise view?

@LisaBosCesium
Copy link

Weekly call discussion:

  • Goal of 4/1 to complete draft and code of first tutorials.
  • Timeline for review less clear since haven't done before.
  • Should we publish the first one by itself or wait to push out in combination with a couple more to have a more complete solution before share publicly? Also implies setting up the readme and other docs to share. Team to discuss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants