Clean up default init template

[lhw-1]

What is the purpose of this pull request?

• Documentation update
• Bug fix
• Feature addition or enhancement
• Code maintenance
• DevOps
• Improve developer experience
• Others, please explain:

Overview of changes:

Cleans up the default template for markbind init, consisting of minor changes in wording, etc.

As this PR is not tied to a specific issue, any suggestions on improving the current template (in terms of pure cosmetics without changing the functionalities) are welcome.

Anything you'd like to highlight/discuss:

Testing instructions:

Proposed commit message: (wrap lines at 72 characters)
Clean up default init template

---

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• Linked all related issues
• No unrelated changes

[lhw-1]

Update in b7c8cbd:

The placeholder text in the topicx.md files were changed to be:

# Topic XX

> This is a placeholder page - more content to be added.

Some of the whitespaces in 404.md were removed to be standardized with the rest of the .md files. Additionally, the text was changed from "File not found ..." to "Page not found ...".

[itsyme]

Hi @lhw-1! Thanks for the PR! Just a small nit in the home page under "Heading 3". I noticed that for the third panel: "Expanded panel", the panel is meant to be expanded on load, however, it seems to be missing the expanded property in index.md. Perhaps you could include that to make the panel expand on load as intended!

[lhw-1]

Thanks for looking through the changes @itsyme!

Just a small nit in the home page under "Heading 3". I noticed that for the third panel: "Expanded panel", the panel is meant to be expanded on load, however, it seems to be missing the expanded property in index.md. Perhaps you could include that to make the panel expand on load as intended!

This is the current output for index.md under "Heading 3":

Essentially, the minimized panel at the top is set to change its header back to "Expanded panel" once it is no longer minimized (by clicking on it at least once):

Additionally, the expanded panel at the bottom will become a minimized panel as well after clicking the "X" button:

So I believe that the heading "Expanded panel" refers not to having the panel already expanded on load, but to differentiate between a minimized and an expanded panel - I don't think including the property for this bottom panel is a necessity, since it could potentially further obfuscate the meaning of "expanded" for new users (if it already isn't doing so...).

Regardless, what you've pointed out is still a good example to showcase for panels (especially to differentiate between these two meanings of "expanded"), so it may be worth including another panel at the bottom that showcases this property specifically!

On that note, it might also be worth looking into improving the template to be more comprehensive to a new user, instead of having filler texts. With reference to the above example, some brief explanation of the features could be more handy than the standard Lorem ipsum 😄 This is probably out of scope for this PR, though.

[tlylt]

Just a small nit in the home page under "Heading 3". I noticed that for the third panel: "Expanded panel", the panel is meant to be expanded on load, however, it seems to be missing the expanded property in index.md. Perhaps you could include that to make the panel expand on load as intended!

Essentially, the minimized panel at the top is set to change its header back to "Expanded panel" once it is no longer minimized (by clicking on it at least once):

Additionally, the expanded panel at the bottom will become a minimized panel as well after clicking the "X" button:

So I believe that the heading "Expanded panel" refers not to having the panel already expanded on load, but to differentiate between a minimized and an expanded panel - I don't think including the property for this bottom panel is a necessity, since it could potentially further obfuscate the meaning of "expanded" for new users (if it already isn't doing so...).

Regardless, what you've pointed out is still a good example to showcase for panels (especially to differentiate between these two meanings of "expanded"), so it may be worth including another panel at the bottom that showcases this property specifically!

If you add the expanded property in, does it look better/make the example clearer? I think this is a good point - I re-read the conversation above at least twice to understand what this is all about, it's definitely not the clearest example that we can give. Would be great if we can modify this part slightly to make the example clear.

FYI the deployed output of the standard template can be viewed here.

[lhw-1]

If you add the expanded property in, does it look better/make the example clearer? I think this is a good point - I re-read the conversation above at least twice to understand what this is all about, it's definitely not the clearest example that we can give. Would be great if we can modify this part slightly to make the example clear.

Right now, the wording we are using in the template for "Expanded panel" vs "Minimized panel" is referring to the panel header, and not the panel body itself, which is what the expanded property is for. So I think that we can add in a third panel to showcase the expanded panel using the expanded property, and also change the wording for the two panels to "Expanded panel header" and "Minimized panel header". How does that sound?

[tlylt]

If you add the expanded property in, does it look better/make the example clearer? I think this is a good point - I re-read the conversation above at least twice to understand what this is all about, it's definitely not the clearest example that we can give. Would be great if we can modify this part slightly to make the example clear.

Right now, the wording we are using in the template for "Expanded panel" vs "Minimized panel" is referring to the panel header, and not the panel body itself, which is what the expanded property is for. So I think that we can add in a third panel to showcase the expanded panel using the expanded property, and also change the wording for the two panels to "Expanded panel header" and "Minimized panel header". How does that sound?

Sure let's try that 🚀

[lhw-1]

As per suggestions above, I've included a new panel in 4ebf484:

Which makes more sense to me 😄

[lhw-1]

Also, given that this PR has been up for quite some time & there has not been more suggestions, I think it's fine to consider this PR as complete.

(Requesting for approving reviews!)