m-kruse / resume Goto Github PK

As a user, I want to be able to specify multiple publishing methods to a single resume.

Shows "viewer.Employment.None" in the view for the employment of a reference.

References:
--
Johnny Dough \| viewer.Employment.None \| Available On Request

Reproduce Steps:
1.) Add an employment
2.) Create a reference
3.) Associate the reference with the employment
4.) Load the view and look at the employment field

It makes more sense to have the employee model be named applicant in terms of relating it to the other models.

https://simpleisbetterthancomplex.com/tutorial/2016/09/19/how-to-create-password-reset-view.html

All an employee should have to do is select a list of the experiences and then the associated experience domains will be generated in the view.

Just a simple diagram to show the process of adding/reviewing data, selecting styles, creating cover letter and then publishing it via a web server, sendmail, or to save it locally.

Add a title and relationship field

Example

Reference: Rusty Shackleford
Title: CEO & Founder
Relation: Manager
Contact: Available Upon Request

Re work it like this

PROJECT_ROOT = os.path.abspath(os.path.dirname(__file__))
PROJECT_DIR = os.path.join(PROJECT_ROOT,'../myapp')

STATIC_ROOT = os.path.join(PROJECT_ROOT,'staticfiles/')
STATIC_URL = '/static/'
STATICFILES_DIRS = (
    os.path.join(PROJECT_DIR,'static/'),
)
``

As a user, I want to be able to serve my resume in a JSON format.

An employee should be able to associate themselves with multiple employments.

A separate app can be used for tracking where the resume is published and your applications.

It makes more sense especially when deploying to app frameworks like Heroku.

This is the one I normally template
https://gist.github.com/PurpleBooth/109311bb0361f32d87a2

Found these recently
https://gist.github.com/fvcproductions/1bfc2d4aecb01a834b46
https://github.com/othneildrew/Best-README-Template

A lot of the templates have CSS that could be stored in another template/block to make it cleaner.

For example/testing have an example user or a method to create an example user

I was playing with the static asset serving and ran a command meant for production which generates all of the necessary static files for production.

Getting this error on trying to generate and preview new resume from template

BadZipFile at /docx/1

Turns out that DOCX are actually zip files so probably something wrong with the DOCX it is generating.

Add error handling for when there is no model data in part of the view. The view should either initialize all the required values with defaults or have special handling for when there is none.

https://medium.com/@frfahim/django-registration-with-confirmation-email-bb5da011e4ef

Add a breadcrumb bar to the top of the view pages

As a user, I want to present a page that shows which formats the resume can be generated in.

https://www.django-rest-framework.org/

Rename TechField and Tech to more general term like Domain and Experience to describe Experience domains and those individual experiences.

The scope changed to where it is more of a builder than a viewer. The final step of the builder is to view it so it makes more sense to call the app the builder.

The other app in this resume project will be the publisher.

Some of the views aren't thread safe currently.

https://code.djangoproject.com/wiki/Jenkins

Right now you have to upload the basic template.

Logout leads to the django admin logout page

Also the user icon in the navbar is broken and doesnt have the right css anymore.

Previewing the HTML output format of a resume is missing some fields.

When creating a new applicant, you shouldn't have to select the experiences and other fields you already created as part of the wizard. Or they should at least already be selected.

Some copy/paste coding has lead to unwanted deletion of tables in a cascade.

As a user, I want to be able to create a full resume in a single form.

Right now there is no discrete association with the resume data. Everyone can access everyone's data. It should only be accessed by the user who created it.

As a user, I want to be able to publish my resume in DOCX format.

This can be used to track applications. Where you used your resume, when, URLs, questions, notes, etc.

Rename to Domains and Experiences.

Requires renaming the model and finding all the model references to replace them.

As a user, I want to be able to export my resume in a format that can be imported into the app.

The root view "/" shows the HTML resume format. The seperate resume views should be accessed from respective named view (/html /json /pdf)

As a user, I want to be able to see all my duties and projects, and other list elements, in the table view.

Add a bootstrap or similarly supported frontend. It is better than plain HTML.

Integration with sites that publish resume data like Linkden, Indeed, CareerBuilder, Glassdoor, etc.

Right now it is on a separate page and doesn't use a shared template.

As a user, I want to be able to create multiple resumes using different styles and formats.

As a user, I want to be able to create and publish a cover letter.