add api workflow

[stevenhua0320]

Add api workflow

[bobleesj]

Are these generated dynamically by the cookiecutter? It doesn't look like it. It's probably best to have a single PR that both removes older docs and handle generated API so that we don't have to have additional PRs related to docs/workflows.

[stevenhua0320]

screenshot of new api page

[bobleesj]

@stevenhua0320 good, now can you follow the API workflow instruction to generate .rst files and render them? There should be a new section called "Package API" Ex) Billingegroup/bg-mpl-stylesheets#66

[bobleesj]

.rst files have been removed - please double check the "Files Changed"

[stevenhua0320]

.rst files have been removed - please double check the "Files Changed"

Yeah, I removed them right now since it is generated by the old cookiecutter.

[stevenhua0320]

updated api workflow build

[bobleesj]

The file extending.rst is not being rendered here in the screenshot?

[stevenhua0320]

@bobleesj

Here is the extending srmise page

[bobleesj]

@stevenhua0320 is there nav on the left column for this ? maybe put it under the source?

But then i see that you have two, let's remove the other while ensuring all doc files are copied including licenses, etc.

[stevenhua0320]

I've put extending.rst under the source dir but I did not see it is on nav.

[bobleesj]

let's make one? then we can remove the ones that are not needed once deployed (probalby all will be useful)

[bobleesj]

I also see lots of useful content under tutorials let's add those too

[sbillinge]

@bobleesj thanks for the help with this ,🙏

[sbillinge]

Polese let me know when it is ready to merge

[stevenhua0320]

Hi Simon @sbillinge, right now the functionality of loading extending.rst and tutorial.rst to the nav on the index page might not be possible right now. But these ones could be searched when typing the keywords. I have made an issue for that. So, we should merge these first.

[sbillinge]

ok, understood. Thanks @stevenhua0320