Changes to Weblit skill model in django

[alicoding]

Just had a discussion with @alanmoo about our weblit skill page and how we are going to deal with localization.

There are some challenges with the current model for weblitskill and it can make both localization and content editing hard to do, so me and Alan want to propose these changes.

1. We are only going to store structured data for Activities
2. We are not going to store Competencies strings in django
3. We are going to store key name that mapped to pontoon for each weblit skill name

The user flow would be like this (technical)

When a user request for open practices skill we will display the static content with react-intl based on their requested locale. We will also fetch the activities based on that locale and skill requested.

@alanmoo @hannahkane @gideonthomas what do you all think?

[hannahkane]

I think this makes sense. I assume the 21st Century skills will be handled the same?

[alicoding]

@hannahkane those may not be part of django at all if we are going to go with this approach.

[hannahkane]

Why not?

[alicoding]

@hannahkane by putting them on Pontoon I think it will help get the translation done for those faster since the content won't change much after all?

[hannahkane]

K. But the Activities will store info about web lit skills and 21st century skills, right? Even if it's via a key.

[alicoding]

Yup activities for each of those will still be stored in django