Open kempsterrrr opened 9 months ago
My tow cents here
I also proposed/asked this (CMS) a time ago, and the answer was that having the .mdx files publicly in the github repo helps with the building/reviewing process which is true. So I believe into keeping it this way.
regarding duplication of information, there is information that is there but is not being used. Maybe what we should do is a clean up. Most of the lesson's and track's information are coming from the database which is what we are keeping because the progress tracking works with the database.
- No unique descriptions are showing for individual lesson pages
@kempsterrrr mate, regarding this point I will have to disagree.. Can you check the database lessons table? We already have Lesson Descriptions (unique) stored in the db.
check screenshots for reference:
Note: both screenshots refer to staging env so the info might NOT be precise
Duplicated data across DB and .mdx files
I would be much appreciated if you can point some examples of duplicated data @kempsterrrr :pray: most of the scenarios I can tell.. It's beacause the source of truth for the Layouts components (TracksLayout and LessonsLayout) is hardcoded text in each file.. Please notice this, IF there are duplicated data (client & DB) would be MAINLY because the I added the data to the DB so I can start handling it in that layer and IT'S NOT refactored to that source YET.
Let me know any good example you can point :pray: Thank you very much!
215 introduces several improvements to SEO. However, we still have the following problems:
@Markkos89 is working on an admin panel. I suggest also considering moving from local
.mdx
files to a headless CMS for content authoring in the mid-to-long term.Opening this specific issue to close #214