joshuali7536 / lennahssg Goto Github PK

This logic could be more concise and done with less variable declarations.

Improve Accessibility of generated HTML files.
Instead of pressing the back button on the browser I want to add a home button as well.

Improve Accessibility of generated HTML files.
Will do this by:

• adding a new home page html file, that will provide links to the generated html files

Improve Accessibility of generated HTML files.
Will do this by:

• add a nav bar at the top of each html

Improve Accessibility of generated HTML files.
Will do this by:

• add a side bar or links to the other html files in a specific generated html (table of contents)

You want to avoid putting binaries or generated files into git, and instead focus on source code. It looks like you've added your entire VS solution and all generated/built files and folders. You can add a .gitignore for VS to deal with this, and use git rm -fr filenames... to remove these.

I'd like to add markdown support to your SSG by:

1. Checking around line 50 for a ".md" filetype
2. Adding logic in your readTxt() function to find the first and last instance of a string such as "*" /
   "_" or "**" / "__" and prepend/append the relevant html tags to the line for italics and bold, respectively

My compiler flagged some warnings regarding multiple declarations as well as declaring functions "extern" and then later "static" .

Compiled and ran fine after ignoring the warnings though!

I want to add another feature for markdown files. It will convert text surrounded by the backtick character to inline code.
For example this markdown:
`Test sentence`

Become this html:
<code>Test sentence</code>

So it will look like:
Test sentence

I want to add a feature that will be able to read the --- markdown syntax, and turn it into a <hr> tag.
Just like regular markdown syntax it will need to be the only characters in the line for it to work.
If the line is ---w or hi --- it won't work.

Users want to be able to specify all of their SSG options in a JSON formatted configuration file instead of having to pass them all as command line arguments every time. For example, consider the following config file, ./ssg-config.json:

I think it's supposed to be version 0.1

Right now this is written in a way that is heavily dependent on Visual Studio. That's fine, but since your code is essentially a single cpp file, it might be a good idea to provide some additional build system options for other operating systems, so you can build it with clang or gcc on macOS, Linux, etc.

You've got a good start on the README, but don't provide too many examples of the various ways the program can be called (you show only one). It might be good to show a few alternatives.