Oops. Don’t forget to put “everyone with the link” as commenter. At a first glance, several important parts (background, experience, motivations, etc) are missing. It is advised to use the recommended template.
I really want one of the mentors to discuss some points related to the approach we should follow
I have mentioned there are two ways to consider moving to Antora
one is to separate the content alone in the repo which is the way Antora docs says
and UI can be within the automation server
The other way is combining all this in one repo and It can be done with versioning as mentioned in the Antora doc we can do versioning using Tags, Branched, or directories names
I discussed with @krisstern on gitter but I think she didn’t get my point. what I did understand from her which we are trying our best to have one repo, which will have blogs using gatsby and Docs with anotra, and the rest of the website will remain Awstruct and haml, this will lead us to use monorepo architecture.
I have no problem doing any of these approaches but I want my proposal to be with one view, my proposal now has pointed to these two approaches
I understand your doubts and your questions are legitimate.
As said during Office Hours, mentors will not tell you (and might not know) what is the best solution. We expect you to be able explain the options clearly and choose/recommend (with argumentation) your solution. We are interested to see in your proposal your communication skills, creativity, and knowledge on the subject matter.
The mentor’s draft review are mainly there to guide you on correctly explaining your proposal, on good comprehension of the problem to solve, and avoid errors.
I fear that calling for a clarification meeting is quite late at this stage of the timeline. But it depends on the availabilities of mentors. They have been quite stretched seen the very large number of proposals and candidates. Don’t forget that they have other responsibilities besides GSoC.
I want to thank Kris (@krisstern ) for his incredible availability and implication in reviewing proposals and relentlessly answering the numerous questions.
Hi @Mahmoudgalalz We will be replacing Awestruck for the entirety of the website as a drop-in replacement, but will start with the Documentation and Blog. This is one issue to be discussed in your proposal on your own, and we would like to stick to a single-repo structure. So I think perhaps there have been some misunderstandings somewhere, as I never expressed we will keep Awestruck at all.
Regarding this statement, I believe there must be a way to make this work within a single repo with different directories for the different parts of the website. I will leave it open for you to suggest how this could be implemented. But this approach undoubtedly will involve a lot more work than you seem to be thinking.